After playing with the sample applications, I tried to setup a common file batching processing
scenario using InboundFileAdapter:

then I found a bug in AbstractChannelAdapter:

public Message receive(long timeout) {
if (!this.initialized) {
throw new MessageHandlingException("adapter not initialized");
}

ExecutorService executor = Executors.newSingleThreadExecutor();

try {
Future result = executor.submit(new Callable() {
public Message call() throws Exception {
return receive();
}
});
try {
result.get(timeout, TimeUnit.MILLISECONDS);
if (result.isDone()) {
return result.get();
}
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
return null;
} catch (TimeoutException e) {
return null;
} catch (ExecutionException e) {
throw new MessageHandlingException("Exception occurred in message source", e);
}
result.cancel(true);

} finally {
executor.shutdown();
}
return null;
}

the executor is not shutdown properly (I have added the finally clause).

I can not find the support forum for Spring Integration yet, so I raise the bug here.

Hi Mark,

Your blog entry was very helpful for me in checking out SpringIntegration source and running the samples w/o any problems. This is a very good introduction to a new framework like SpringIntegration. I would love to see more advanced examples on how to use SI and may be implementation of some of the EIS patterns discussed in Gregor Hohpe's book.

Great job.

Thanks
Srini

Hi, Mark,

I am very interested in the bright future of Spring Integration and we will base our solution on this new project(We have already integrated Spring Batch and are not afraid of being cutting edge.)

When I digged deeper with current release, I find another issue in class MessageBus:

public void registerEndpoint(String name, MessageEndpoint endpoint) {
Assert.notNull(name, "'name' must not be null");
Assert.notNull(endpoint, "'endpoint' must not be null");
this.endpoints.put(name, endpoint);
if (logger.isInfoEnabled()) {
logger.info("registered endpoint '" name "'");
}
endpoint.setChannelRegistry(this);
if (endpoint.getInputChannelName() != null && endpoint.getConsumerPolicy() != null) {
Subscription subscription = new Subscription();
subscription.setChannel(endpoint.getInputChannelName());
subscription.setEndpoint(name);
subscription.setPolicy(endpoint.getConsumerPolicy());
this.activateSubscription(subscription);
}
if (this.autoCreateChannels) {
String defaultOutputChannelName = endpoint.getDefaultOutputChannelName();
if (StringUtils.hasText(defaultOutputChannelName)) {
this.registerChannel(defaultOutputChannelName, new PointToPointChannel());
}
}
}

when autoCreateChannels is set and defaultOutputChannelName has text， the channel with defaultOutputChannelName should first be lookuped in the channel registry, if failed then fall back to create a new one.

-Steven

Hi Mark,

First of all, thanks for this nice intro into your framework.
After running your examples w/o any problems and trying to understand the code so far, I'm
wondering if it could make sense to extend the XML-element like his:

Defines a consumer policy.

where bean-ref points to a policy-bean, somthing like:

I gave it a try and changed the EndpointParser in parseConsumer() method:

String beanName = element.getAttribute(POLICY_NAME_ATTRIBUTE);
if (StringUtils.hasText(beanName)) {
parserContext.registerBeanComponent(
new BeanComponentDefinition(consumerDef, beanName));
} else {
beanName = parserContext.getReaderContext().generateBeanName(consumerDef);
parserContext.registerBeanComponent(
new BeanComponentDefinition(consumerDef, beanName));
}
return beanName;

and it seems to work quite well.
Any comments or restrictions on doing it this way?
Would your recomment an other solution for this kind of problem?

kind regards
-peter

Hi Mark,

I have been playing around with the samples and I tried to create some nice examples myself.
Today I kicked off a SVN update and when I came back I was surprised to see that SVN deleted the project content.
When I try to access the repository I get an error saying the repository is no longer available.

Is the latest version available in a different location? Or can you provide me the sources in some other way?
It would be much appreciated.

Kind regards,
Roel

Mark,

I'm very interested in the project but stuck with JDK 1.4.2. I downloaded the latest tree and tried to compile for 1.4.2 by adjusting the compliance levels in the spring-build/standard/common.xml script file but without luck.

Is there any plan to support 1.4.2 or do I have to use some retroweaving library?

Many thanks,

Hi Mark,

I want to write a MessageHandler which make use of the CorrelationId header to support request/reply message processing:

public class MessageHandler1 {
public Message processMessageSimple(Message requestMessage) {
Message responseMessage = new StringMessage("return from message: " requestMessage.getPayload());

responseMessage.getHeader().setCorrelationId(requestMessage.getHeader().getCorrelationId());

return responseMessage;
}
}

but the DefaultMessageHandlerAdapter uses SimplePayloadMessageMapper to extract the payload of the message as the argument to the handler method,

public class DefaultMessageHandlerAdapter extends AbstractMessageHandlerAdapter
implements Ordered, InitializingBean {

public Object doHandle(Message message, SimpleMethodInvoker invoker) {
return invoker.invokeMethod(this.getMapper().fromMessage(message));
}

}

So, that is not possible to pass the raw Message as the parameter to the handler method. Is that by design or is there another way to manipulate the correlationId
header? And How can I customize the MessageMapper?

Thanks.

Hi,

why do you use Ivy for dependency-management? Do you plan to migrate to maven for spring-integration in near future or will Ivy be the build-tool for new subprojects?

Thanks

Jörg

While I can run the examples from the Subversion repository fine, when I attempt to create my own usages of message endpoints I have noticed that the PollingSourceAdapter.start method never gets called (though its constructor and setPeriod methods do). I am loading my application context using the ContextLoaderListener via the web.xml, and am wondering if the Lifecycle.start method even gets called on my ApplicationContext.

My code looks almost identical to the (annotated) Quote example.

I have no idea what I'm doing wrong here, but has anybody successfully made Spring Integration work from an application inside a servlet container?

Sorry to drag this on, and this may not be the right forum for this, but I've noticed that other Lifecycle beans do not get start() events either, presumably because the application context has not been started. Would it be safe to write my own context loading listener, and have it invoke the start() method on the application context, and would that in turn start the MessageBus?

Autostart on the bus sounds great, but I'm really wondering in general about Spring's application context start() and the general lack of documentation (that I can see) on it…

Mark,
How would I get a Cobol application connected to Spring Integration?