Reference Manual feedback please!

[Mark Fisher]

Spring Integration Community,

We have an open issue for Reference Manual typos to be fixed in 1.0.3:
http://jira.springsource.org/browse/INT-676

Please feel free to add to that!... not only typos but also suggestions for any material that is unclear or lacking sufficient detail. The 1.0.3 release is planned for the end of next week, and we also have plenty of other issues, but we will try to address as much as possible based on comments added to that issue.

I will soon be posting another thread for 2.0 roadmap suggestions - as soon as JIRA is reorganized a bit to reflect our current plan.

Regards,
Mark

[paul.mckenzie]

"The no-argument send and receive methods block indefinitely. Note however, that calling the no-arg versions of send() and receive() will block indefinitely."

I think you have said the same thing twice. It may be that you have repeated yourself.

[sudheerk84]

It would be great if the reference manual also concentrates on API based usage of spring integration . This would help in dynamic creation of channels and dynamic addition of adapters and their removal.

[jerdavis]

I see the reference document,
I see javadoc.

But where would I find a complete explanation of all the various tags on things like:

<rmi:inbound-gateway>
<rmi:outbound-gateway>
<jms:inbound-gateway>
<jms:outbound-gateway>
...etc

what is 'expect-reply', what happens if I set it to true/false?
what is 'remote-invocation-executor'..

If it wasn't for my IDE, I wouldn't even know these tags existed...
etc etc...

[ellyka112]

I see the reference document,
I see javadoc.

But where would I find a complete explanation of all the various tags on things like:

<rmi:inbound-gateway>
<rmi:outbound-gateway>
<jms:inbound-gateway>
<jms:outbound-gateway>
...etc

what is 'expect-reply', what happens if I set it to true/false?
what is 'remote-invocation-executor'..

If it wasn't for my IDE, I wouldn't even know these tags existed...
etc etc...

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

[oleg.zhurakousky]

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

[turnrob]

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.

thanks
Rob

[MmarcoM]

any tips as well on how to use ApplicationEvent?

if springapp services could be managed via JMX?

regards
marco

[jmc42]

A pdf version would be good.

An overview of how spring integration compares with other intergration frameworks (or esbs) such as mule or servicemix would be useful.

Detailed documentation on the tags would be useful. If there are annotation versions of the tags, it would be best if the xml tags were documented by reference to the annotation classes as well as comments in an xsd.

James

[fkh]

In section 7.1 Router Implementations - HeaderValueRouter there is no information about the attribute ignore-channel-name-resolution-failures. The default-output-channel seems to be ignored as long as one doesn't set this attribute to true.