Bug 777775 (SOA-291) - quickstart webservice_wsaddressing asking for wrong jboss remoting patch
Summary: quickstart webservice_wsaddressing asking for wrong jboss remoting patch
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-291
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 Beta 1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 Beta 2
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-08 10:02 UTC by trev
Modified: 2008-02-05 17:47 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-05 17:47:27 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-291 0 Major Closed quickstart webservice_wsaddressing asking for wrong jboss remoting patch 2013-07-26 10:10:58 UTC

Description trev 2008-01-08 10:02:41 UTC
Date of First Response: 2008-01-08 12:56:07
project_key: SOA

from email from jdelong
The quickstart webservice_wsaddressing has a message that:

This Quickstart requires the JBossRemoting 2.2.2SP2 patch to be applied.
       This simply involves downloading <a href="http://repository.jboss.org/jboss/remoting/2.2.2.SP2/lib/jboss-remoting.jar">jboss-remoting.jar</a>

If you run ant deploy it barfs complaining:

build file parsing, attempting to resolve. Future versions of Ant may support
referencing ids defined in non-executed targets.
    [echo] JBR Version String: 'JBossRemoting Version 2.2.2.SP4 (Bluto)'.

BUILD FAILED
/shared/software/soa-p-standalone/jboss-soa-p-standalone.4.2.0/samples/quickstarts/conf/base-build.xml:494: Invalid version of JBossRemoting installed on target server.  Please install version 2.2.2.SP2: http://repository.jboss.org/jboss/remoting/2.2.2.SP2/lib/jboss-remoting.jar


So it looks like the version is 2.2.2.SP4, but the build script is looking for 2.2.2.SP2.

Comment 1 trev 2008-01-08 10:04:21 UTC
Link: Added: This issue depends JBESB-1454


Comment 2 Jeff DeLong 2008-01-08 17:56:07 UTC
Two other quickstarts, webservice_wssecurity and webservice_mtom, have the same issue.

Comment 3 Kevin Conner 2008-01-14 14:03:39 UTC
Fixed in ESB, merge happening soon

Comment 4 Len DiMaggio 2008-02-05 17:23:56 UTC
The deployment is working - still seeing this though:

assert-jbossremoting-version:
Warning: Reference exec-classpath has not been set at runtime, but was found during
build file parsing, attempting to resolve. Future versions of Ant may support
 referencing ids defined in non-executed targets.
Warning: Reference compile-classpath has not been set at runtime, but was found during
build file parsing, attempting to resolve. Future versions of Ant may support
 referencing ids defined in non-executed targets.
Warning: Reference quickstart-dependencies-classpath has not been set at runtime, but was found during
build file parsing, attempting to resolve. Future versions of Ant may support
 referencing ids defined in non-executed targets.
     [echo] JBR Version String: 'JBossRemoting Version 2.2.2.SP4 (Bluto)'.


Comment 5 Len DiMaggio 2008-02-05 17:47:27 UTC
Verified fixed in CR2



Note You need to log in before you can comment on or make changes to this bug.