|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Using Spring Namespace configuration(and by backend org.granite.spring.FlexFilter automatic configuration) and services-config.xml for custom destination spring configuration
|
|
|
Using the tide and Spring namespace configuration, the org.granite.spring.FlexFilter don't take care of the serviceConfig configuration of the destination with id "spring"
(for exemple to custom the validator-class-name)
In fact,
The org.granite.spring.FlexFilter (line 172) try to find an services-config.xml for destination "spring" by using this method
Destination destination = servicesConfig.findDestinationById("flex.messaging.services.RemotingService", "spring");
But services.RemotingService is the classname
and messages.RemotingMessage is the MessageType correct parameter
like the say the method signature
org.granite.config.flex.ServicesConfig {
...
public Destination findDestinationById(String messageType, String id) {
...
To correct this bug,
just past the messageType parameter in order to have
Destination destination = servicesConfig.findDestinationById("flex.messaging.messages.RemotingMessage", "spring");
I have tested it, and it take of the services-config.xml destination configuration
Best regards
|
|
Description
|
Using the tide and Spring namespace configuration, the org.granite.spring.FlexFilter don't take care of the serviceConfig configuration of the destination with id "spring"
(for exemple to custom the validator-class-name)
In fact,
The org.granite.spring.FlexFilter (line 172) try to find an services-config.xml for destination "spring" by using this method
Destination destination = servicesConfig.findDestinationById("flex.messaging.services.RemotingService", "spring");
But services.RemotingService is the classname
and messages.RemotingMessage is the MessageType correct parameter
like the say the method signature
org.granite.config.flex.ServicesConfig {
...
public Destination findDestinationById(String messageType, String id) {
...
To correct this bug,
just past the messageType parameter in order to have
Destination destination = servicesConfig.findDestinationById("flex.messaging.messages.RemotingMessage", "spring");
I have tested it, and it take of the services-config.xml destination configuration
Best regards |
Show » |
Sort Order:
|
Bug
Resolved
Major
Tide: automatic configuration do not take care of services-config.xml custom <destination id="spring">
===================================================================
--- spring/org/granite/spring/FlexFilter.java (revision 4007)
+++ spring/org/granite/spring/FlexFilter.java (working copy)
@@ -169,7 +169,7 @@
service = new Service("granite-service", "flex.messaging.services.RemotingService",
"flex.messaging.messages.RemotingMessage", null, null, new HashMap<String, Destination>());
}
- Destination destination = servicesConfig.findDestinationById("flex.messaging.services.RemotingService", "spring");
+ Destination destination = servicesConfig.findDestinationById("flex.messaging.messages.RemotingMessage", "spring");
if (destination == null) {
List<String> channelIds = new ArrayList<String>();
channelIds.add("graniteamf");