Return-Path: X-Original-To: apmail-flex-issues-archive@minotaur.apache.org Delivered-To: apmail-flex-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C17CA17227 for ; Tue, 9 Jun 2015 08:47:00 +0000 (UTC) Received: (qmail 22996 invoked by uid 500); 9 Jun 2015 08:47:00 -0000 Delivered-To: apmail-flex-issues-archive@flex.apache.org Received: (qmail 22969 invoked by uid 500); 9 Jun 2015 08:47:00 -0000 Mailing-List: contact issues-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list issues@flex.apache.org Received: (qmail 22959 invoked by uid 99); 9 Jun 2015 08:47:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2015 08:47:00 +0000 Date: Tue, 9 Jun 2015 08:47:00 +0000 (UTC) From: "Robert Hunt (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLEX-34886) BlazeDS 4.7.0 incompatible replacement for BlazeDS 4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-34886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Hunt updated FLEX-34886: ------------------------------- Description: 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 relatd 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 5.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/ was: 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 relase notes state that there are no changes from Adobe BlazeDS 4.6 there seems to be some significant differences. I am encountering an exception relatd 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 5.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/ > 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 relatd 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 5.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)