flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34886) BlazeDS 4.7.0 incompatible replacement for BlazeDS 4.6
Date Tue, 09 Jun 2015 11:21:00 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578741#comment-14578741
] 

Christofer Dutz commented on FLEX-34886:
----------------------------------------

These artifacts are optional dependencies. You don't need them in every case and there could
be issues if we did include them. I agree that defining them as "optional" might be the better
solution, but nevertheless in both cases they are not included automatically. I am using BlazeDS
4.7.0 in several projects and I have never needed these jars ... so If you are using the JMS
related parts you need to provide the JMS related libs. I think this is ok this way and I
wouldn't like to change it.

> BlazeDS 4.7.0 incompatible replacement for BlazeDS 4.6
> ------------------------------------------------------
>
>                 Key: FLEX-34886
>                 URL: https://issues.apache.org/jira/browse/FLEX-34886
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: BlazeDS
>    Affects Versions: BlazeDS 4.7
>            Reporter: Robert Hunt
>
> I've recently noticed that Apache BlazeDS 4.7.0 has become available and have attempted
to migrate a project currently using Adobe BlazeDS 4.6.
> Although the release notes state that there are no changes from Adobe BlazeDS 4.6 there
seems to be some significant differences. I am encountering an exception related to the messaging
system:
> java.lang.NoClassDefFoundError: javax/jms/InvalidSelectorException
> 	at flex.messaging.services.MessageService.testSelector(MessageService.java:1182) ~[flex-messaging-core-4.7.0.jar:4.7.0]
> 	at flex.messaging.services.MessageService.manageSubscriptions(MessageService.java:930)
~[flex-messaging-core-4.7.0.jar:4.7.0]
> 	at flex.messaging.services.MessageService.serviceCommand(MessageService.java:339) ~[flex-messaging-core-4.7.0.jar:4.7.0]
> 	at flex.messaging.MessageBroker.routeCommandToService(MessageBroker.java:1573) ~[flex-messaging-core-4.7.0.jar:4.7.0]
> 	at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:1016)
~[flex-messaging-core-4.7.0.jar:4.7.0]
> ...
> The exception seems to be getting thrown from the "testSelector" method on line 1182
in flex.messaging.services.MessageService.java when it tries to instantiate a new flex.messaging.services.messaging.selector.JMSSelector
> I've noticed that the JMSSelector class has dependencies on org.apache.activemq in BlazeDS
4.7.0 where as the version in 4.6 did not. These dependencies are missing from my project
which is probably why I get an exception, they must be an optional dependency of BlazeDS.
> Does the Apache Flex team have any idea which verison BlazeDS 4.7.0 was built on top
of when it came from Adobe? The Original BlazeDS 4.6 nightly builds are still around: http://sourceforge.net/adobe/blazeds/wiki/download%20blazeds%20trunk/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message