Search:

How many processor cores do you have? Simply ramping up threads and expecting that to improve throughput wont work and as I suspect you are already seeing switching threads on and off the core can...

In general the programmatic creation of flows or parts of flows is not well supported at the moment in Spring Integration. This is in part due to the focus on the use of Spring namespaces. Often...

Spring Integration In Action is currently available as pdf and is expected to be on the shelves shortly http://www.manning.com/fisher/ (note vested interest since I am one of the authors)

Pro...

The send-timeout is used to determine the timeout when sending the completed group on to the output-channel or messages to the discard-channel.
I suspect you want a reaper, details of which can be...

This is now fixed in head although I may do some further refactoring to tidy up a bit more.

The name SourcePollingChannelAdapterFactoryBean is auto generated for your channel adapter stdin-channel-adapter. You can either define a poller as a child element of the stdin-channel-adapter or...

Looking at the code this appears to be a bug
https://jira.springsource.org/browse/INT-1812

The XPathRouter class does expose a setter for the converter however this is not currently exposed in the Spring Integration XML namespace. Therefore to make use of this you would need to define the...

BTW there is no getNodeValue() on DOMResult only getNode().

Still not clear what makes you think this is not working. Regarding
"output is again seen as null instead of 'architecture'" this is for the same reason. You are printing out a Node so the null...

Both DocumentImpl and NodeImpl in Xerces return null for the getNodeValue() call used in toString() defined in NodeImpl. Hence the output you are seeing or have you converted this to a String to get...

In the first case where you are printing out the result of toString on a org.w3c.Node or org.w3c.Document it will give you what you see ie '[interest: null' for the split node and '[#document: null]'...

The namespace for the XSL transformer allows the specification of a result-factory and a result-transformer. Providing custom implementations of these should give you the control you want by...

Not easily at the moment since the XPath header enricher exposes the standard return types provided by the instance of org.springframework.xml.xpath.XPathExpression it delegates to which only...

Are you defining a default poller anywhere else? Maybe with rejection-policy="ABORT"?

A long shot but this might cause this if the poll is slow since the default behaviour of your...

In order to persist messages as they sit on the channel I would provide an implementation of PollableChannel or SubscribableChannel rather than attempt to use an interceptor to add this persistence...

Hi Gyuszi

The behaviour you expect is the same as I would expect. Could you post your xml configuration here. Also what mail server and version of Spring Integration are you using?

Jonas

Not 100% clear on what you are saying. Are you saying that it works while there is mail but breaks once there is no more mail?

The IampMailReceiver attempts to avoiding repeated selection of the...

Use the depends-on attribute on the SingleConnectionFactory bean(s) to ensure the pool is initialised after the broker and is destroyed before.

see section 3.3.3
...

JndiDestinationResolver has a setCache method which defaults to true and also implements the CachingDestinationResolver interface which allows removal of specific items from the cache or the clearing...

Glad you worked out the Xpath expression issue.

This issue with DOMSource is now fixed in head and will be part of 2.0 M1 release.

Jonas

As to why you are getting nulls, namespaces? Your example Xpath expression assumes everything is in the default namespace. Is that really the case?

You might want to take a look at the...

The XPath routers use the DefaultXmlPayloadConverter which as Iwein says does not support sources however for the case where we are converting to a Node it seems so trivial that we should. I have...

The main advantage is in giving greater flexibility both in the mapping and with regard to how you express your mapping. The one killer feature for me is the XPath support which allows you to use a...

Writing your own marshaller/unmarshaller implementations using XPath is also worth considering. It is more work up front but if done well will allow you to create a mapping that is less fragile in...