Our RMI support is built on top of Spring, so I would suggest to read the following documentation http://static.springsource.org/sprin...l#remoting-rmi to learn how to expose a regular POJO as a remote component.
Then you can hook up SI to it.
Our RMI support is built on top of Spring, so I would suggest to read the following documentation http://static.springsource.org/sprin...l#remoting-rmi to learn how to expose a regular POJO as a remote component.
Then you can hook up SI to it.
Oleg Zhurakousky
Spring Integration team
http://twitter.com/z_oleg
http://blog.springsource.com/author/ozhurakousky/
If you have a proxied service method defined as a gateway bean and/or annotated with @Gateway, if you define one parameter of type java.util.Map, it will automatically have its contents added to the Headers. This means that annotating that method parameter with @Headers is optional.
(Per other forum thread including this recommendation from Oleg)
I suggest the XMPP connection namespace section reference the XMPP appendencies for more advanced configurations.
Hello , I would like to see better explaination of the route from using default directChannels to asychronous messaging.
The manual does tackle the config for each type of channel, but it would benefit from a larger section on tips/why/when etc.
Can you also help with tips for logging/debugging an async system. e.g. are there plugins/tools to show performance of the channels etc.
_______________________
download wii game
burn wii game
Our documentation went through major update for the upcoming 2.0 release. We also have a new samples repository http://blog.springsource.com/2010/09...ation-samples/ with many more samples where you can find most of what you need and if you don't open a JIRA - https://jira.springframework.org/browse/INTSAMPLES
As far as tips. Please ask specific question about your use case on this forum. That is why its here in the first place.
As far as channel performance, one thing you must understand is that channel is not a performance bottleneck in the first place. There is nothing that is going on inside the channel that could potentially represent a performance problem. Channel is all about decoupling producer and consumer. Internally it is just a handoff of the message from the producer to the consumer. Such handoff might be sync/async, but that is another story. In any event channel can throughput as many messages as the amount of simplest java method that you can invoke on your machine![]()
Oleg Zhurakousky
Spring Integration team
http://twitter.com/z_oleg
http://blog.springsource.com/author/ozhurakousky/
Section "24.7 Transforming xml messages using XPath" refers to an xpath-transformer element which, as far as I can tell, has been removed from the 2.0.0 release.
This is this the second issue I've stumbled on in the last couple of days (the other being section "24.5 Routing xml messages using XPath" which is also out of date).
When will the documentation be updated to reflect the 2.0.0 release?
There definitely is an <xpath-transformer> element in 2.0. Can you explain what you're seeing that makes it appear to be unavailable?
Also, we have made some updates to the XML section (specifically related to routers) that will be available in the 2.0.1 release (planned for tomorrow). Can you please let us know if you are seeing something that has not yet been addressed by this issue?: https://jira.springsource.org/browse/INT-1653
FWIW, we tried to make sure everything was up-to-date for 2.0 GA, but there's quite a bit of material there; So please be patient as we catch a few things that were left out. Since we are releasing 2.0.1 tomorrow, I would especially like to know if the issue I pointed to above has missed anything that you noticed.
Thanks,
Mark
Mark Fisher
Spring Integration Lead
SpringSource, a division of VMware
http://www.springsource.com
http://www.springsource.org/spring-integration
http://blog.springsource.com/main/author/markf
My bad. It looks like a problem with my STS. I'm using STS 2.5.1 with these namespaces:
Using the XML completion in STS only three transformers are being shown as available in the int-xml namespace:Code:<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:int="http://www.springframework.org/schema/integration" xmlns:int-xml="http://www.springframework.org/schema/integration/xml" xsi:schemaLocation="http://www.springframework.org/schema/integration/xml http://www.springframework.org/schema/integration/xml/spring-integration-xml-2.0.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd http://www.springframework.org/schema/integration http://www.springframework.org/schema/integration/spring-integration-2.0.xsd>
With the changes to xpath-router, when I didn't see an xpath-transformer in STS I assumed it had been removed. Adding an xpath-transformer works as per the documentation.Code:xslt-transformer marshalling-transformer unmarshalling-transformer
Incidentally, what's the best way of reporting typos and other minor documentation issues?
I tried building Spring Integration from source using the instructions here...
http://www.springsource.org/node/2960
It failed with the following error message:
:spring-integration-xmpp:processResources
:spring-integration-xmpp:classes
:docs:api
:docs:preprocessDocbookSources
:docs:docbookHtml
:docs:docbookHtmlSingle
:docs:docbookPdf
FAILURE: Build failed with an exception.
* Where:
Empty build file
* What went wrong:
Execution failed for task ':docs:docbookPdf'.
Cause: Java heap space
* Try:
Run with -s or -d option to get more details. Run with -S option to get the full (very verbose) stacktrace.
BUILD FAILED
Total time: 14 mins 49.05 secs
Looks like it ran out of heap space.
Joshua Smith
Joshua
All you need to do is set the GRADLE_OPTS
For example:
Code:export GRADLE_OPTS="-Xmx1024m"
Oleg Zhurakousky
Spring Integration team
http://twitter.com/z_oleg
http://blog.springsource.com/author/ozhurakousky/