Bug 780962 (SOA-3431) - JBossWS Native testsuite depends on aop version not compatible with EAP aop version
Summary: JBossWS Native testsuite depends on aop version not compatible with EAP aop v...
Keywords:
Status: NEW
Alias: SOA-3431
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossWS, Build Process
Version: 5.2.0.ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: Nobody
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-03 14:22 UTC by Boris Belovic
Modified: 2020-04-27 01:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Some tests fail when using JBossWS Native. This occurs when the AOP version is not compatible with the EAP AOP version.
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP-6585 0 Major Closed JBossWS Native testsuite depends on aop version not compatible with EAP aop version 2017-03-06 06:13:11 UTC
Red Hat Issue Tracker SOA-3431 0 Major Closed JBossWS Native testsuite depends on aop version not compatible with EAP aop version 2017-03-06 06:13:11 UTC

Description Boris Belovic 2011-10-03 14:22:03 UTC 
project_key: SOA

org.jboss.test.ws.jaxws.samples.dar.JMSClientTestCase.test 
org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase.testJMSEndpointPort 
org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase.testMessagingClient 
org.jboss.test.ws.jaxrpc.samples.jmstransport.JMSTransportTestCase.testSOAPMessageToEndpointQueue 

These 4 tests are failing with following exception:

java.lang.NoSuchMethodError: org.jboss.aop.AspectManager.instance(Ljava/lang/Class;)Lorg/jboss/aop/AspectManager;

Reason is missing Maven artifacts, same issue has been seen on EAP, see JBPAPP-6585 for the details.

This issue can be worked around by modifying pom.xml as described in JBPAPP-6585.

Brief workaround description:
exclude JBoss AOP jars from pom.xml
install AOP jars into (local) Maven repository
reference these jars in pom.xml
Comment 1 Boris Belovic 2011-10-03 14:22:51 UTC 
Link: Added: This issue is related to JBPAPP-6585
Comment 4 Suz 2012-06-15 04:04:45 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Some tests fail when using JBossWS Native. This occurs when the AOP version is not compatible with the EAP AOP version.
Comment 6 JBoss JIRA Server 2014-04-09 14:54:36 UTC 
Rostislav Svoboda <rsvoboda> updated the status of jira JBPAPP-6585 to Closed
Note You need to log in before you can comment on or make changes to this bug.