Mark Fisher f99911cf89 Removed ChannelRegistry. It has been replaced by the ChannelResolver strategy.

2008-10-13 02:40:15 +00:00

build-spring-integration

Moving 'org.springframework.integration.test' module to the sandbox until post 1.0

2008-09-25 20:52:15 +00:00

org.springframework.integration

Removed ChannelRegistry. It has been replaced by the ChannelResolver strategy.

2008-10-13 02:40:15 +00:00

org.springframework.integration.adapter

Separated annotation post processors and bean definition parsers into 'annotation' and 'xml' sub-packages of the 'org.springframework.integration.config' package.

2008-10-10 18:55:24 +00:00

org.springframework.integration.event

The Message Bus no longer creates a default TaskScheduler. However, a default thread-pool version is created in the MessageBusParser if no "task-scheduler" reference is provided.

2008-10-09 16:03:10 +00:00

org.springframework.integration.file

Separated annotation post processors and bean definition parsers into 'annotation' and 'xml' sub-packages of the 'org.springframework.integration.config' package.

2008-10-10 18:55:24 +00:00

org.springframework.integration.ftp

Separated annotation post processors and bean definition parsers into 'annotation' and 'xml' sub-packages of the 'org.springframework.integration.config' package.

2008-10-10 18:55:24 +00:00

org.springframework.integration.httpinvoker

Refactored existing Message-consuming endpoints to only implement MessageConsumer (not MessageEndpoint). Now, either a PollingConsumerEndpoint or SubscribingConsumerEndpoint delegates to the MessageConsumer thereby separating the Lifecycle responsibilities and configuration settings (trigger, transactions, etc) since they are different for polling vs. subscribing and not relevant for simply consuming Messages. Essentially all MessageConsumers are now "event-driven" since a "polling consumer" is actually handled by the PollingConsumerEndpoint class. The next refactoring step involves renaming several components to clarify this endpoint vs. consumer distinction.

2008-10-06 17:24:46 +00:00

org.springframework.integration.jms

Added support for the <poller/> sub-element within jms:outbound-channel-adapter, and added the "channel" attribute for the inbound console channel adapter.

2008-10-12 03:34:17 +00:00

org.springframework.integration.mail

Added support for the <poller/> sub-element within jms:outbound-channel-adapter, and added the "channel" attribute for the inbound console channel adapter.

2008-10-12 03:34:17 +00:00

org.springframework.integration.rmi

Refactored existing Message-consuming endpoints to only implement MessageConsumer (not MessageEndpoint). Now, either a PollingConsumerEndpoint or SubscribingConsumerEndpoint delegates to the MessageConsumer thereby separating the Lifecycle responsibilities and configuration settings (trigger, transactions, etc) since they are different for polling vs. subscribing and not relevant for simply consuming Messages. Essentially all MessageConsumers are now "event-driven" since a "polling consumer" is actually handled by the PollingConsumerEndpoint class. The next refactoring step involves renaming several components to clarify this endpoint vs. consumer distinction.

2008-10-06 17:24:46 +00:00

org.springframework.integration.samples

Updated template.mf to include org.springframework.beans.*

2008-10-13 01:50:16 +00:00

org.springframework.integration.security

Separated annotation post processors and bean definition parsers into 'annotation' and 'xml' sub-packages of the 'org.springframework.integration.config' package.

2008-10-10 18:55:24 +00:00

org.springframework.integration.stream

Added support for the <poller/> sub-element within jms:outbound-channel-adapter, and added the "channel" attribute for the inbound console channel adapter.

2008-10-12 03:34:17 +00:00

org.springframework.integration.ws

WebServiceHandler classes are now WebServiceOutboundGateways. The "service-activator" element has also been replaced with <ws:outbound-gateway/> (INT-404).

2008-10-08 18:25:32 +00:00

org.springframework.integration.xml

The router hierarchy abstract method names are now 'determineTargetChannel', 'determineTargetChannelNames', etc (instead of "resolve..."). This clarifies the distinction between the target channel decision and the resolution of a channel *name* to a channel instance. The latter is now the responsibility of a ChannelResolver strategy, and all subclasses of AbstractChannelNameResolvingMessageRouter now delegate to a ChannelResolver after 'determineTargetChannelNames' has returned the channel name(s). In most cases, it will be a BeanFactoryChannelResolver.

2008-10-12 17:58:36 +00:00

spring-integration-reference

updated documentation

2008-10-06 19:39:02 +00:00

build.properties

Come up to BRITS

2008-05-20 21:26:25 +00:00

Description

No description provided

83 MiB

Languages

Java 99%

XSLT 0.9%