flex-issues mailing list archives

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

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

Robert Hunt commented on FLEX-34886:
------------------------------------

Well I haven't managed to successfully get Apache BlazeDS 4.7.0 working in our project due
to this problem, I was expecting it to be a drop in replacement. I should also mention we're
using spring-flex 1.6.0.RC1 which required some manipulation of the pom.xml to ensure that
it doesn't pull in the old version of BlazeDS (due to the new groupId and artifactId):

<dependency>
    <groupId>org.springframework.flex</groupId>
    <artifactId>spring-flex-core</artifactId>
    <version>1.6.0.RC1</version>
    <exclusions>
        <exclusion>
            <groupId>com.adobe.blazeds</groupId>
            <artifactId>blazeds-core</artifactId>
        </exclusion>
        <exclusion>
            <groupId>com.adobe.blazeds</groupId>
            <artifactId>blazeds-common</artifactId>
        </exclusion>
        <exclusion>
            <groupId>com.adobe.blazeds</groupId>
            <artifactId>blazeds-proxy</artifactId>
        </exclusion>
        <exclusion>
            <groupId>com.adobe.blazeds</groupId>
            <artifactId>blazeds-remoting</artifactId>
        </exclusion>
    </exclusions>
</dependency>

I did check the behaviour with BlazeDS 4.6 and the code path still appears to be the same,
it still hits the JMSSelector class but doesn't cause an issue as it's not missing dependencies
in 4.6.

It's a blocker for our project at the moment, it may well work if we include Apache MQ and
the JMS API dependencies but it seems a bit wrong as we're not actually making use of these
libraries in our project. Clearly you've had a better success with your projects, I'm not
that familiar with the inner workings of BlazeDS so I can't really say if our project is non-standard
in terms of configuration.

Let me know If I can provide any more information that might be of use.

> 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