Bug 779668 (SOA-2034) - jars referenced in Systinet setup guide are not in 4.3 CP03 build
Summary: jars referenced in Systinet setup guide are not in 4.3 CP03 build
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2034
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: 3rd Party
Version: 4.3 CP04 ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Zuzana Zoubkova
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-09 14:29 UTC by Len DiMaggio
Modified: 2010-06-08 05:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 779669 (view as bug list)
Environment:
Last Closed: 2010-06-01 10:46:54 UTC
Type: Bug

Attachments (Terms of Use)
SystinetIntegration.pdf (171.18 KB, application/download)
2010-04-09 14:40 UTC, Len DiMaggio 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779032 0 high CLOSED Need to incorporate "HP SOA Registry Foundation Integration" into SOA Admin Guide 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-2034 0 Major Closed jars referenced in Systinet setup guide are not in 4.3 CP03 build 2013-08-06 18:14:38 UTC

Internal Links: 779032

Description Len DiMaggio 2010-04-09 14:29:05 UTC 
Date of First Response: 2010-04-14 04:52:49
project_key: SOA

The document refers to:

3. Copy jbossesb-transport-1.0.jar to server/[jboss_configuration]/deploy/registry.war/WEB-INF/lib
4. Copy jbossesb-transport-client-1.0.jar to server/[jboss_configuration]/deploy/jbossesb.sar/lib

But - the files are missing in ER1:

$ pwd
/opt/local/43_CP03_ER1/jboss-soa-p.4.3.0

$ find . -name jbossesb-transport-client-1.0.jar -print
<null>

$ find . -name jbossesb-transport-1.0.jar -print
<null>
Comment 2 Len DiMaggio 2010-04-09 14:40:45 UTC 
Attachment: Added: SystinetIntegration.pdf
Comment 3 Kevin Conner 2010-04-14 08:52:49 UTC 
These are built by the build.xml within product/tools/systinet but it does not look like this is included in our build, either explicitly (to build the jars) or implicitly by including this in the tools directory.
Comment 4 Len DiMaggio 2010-04-14 15:51:41 UTC 
Link: Added: This issue related SOA-1444
Comment 5 Kevin Conner 2010-05-13 14:37:40 UTC 
Link: Added: This issue depends JBESB-3318
Comment 6 Kevin Conner 2010-05-13 14:51:17 UTC 
The ESB build now generates the systinet plugin jars and places them in the product/build/jbossesb/lib/ directory.  The filenames are jbossesb-transport-client-1.0.jar and jbossesb-transport-1.0.jar.

This will be in the next merge but the SOA build process now needs to move them where required.
Comment 7 David Le Sage 2010-05-17 00:47:31 UTC 
This is documented as a Known Issue.  Will move over to Resolved Issues when it is included in the next merge.  Release note reads:

https://jira.jboss.org/jira/browse/JBESB-3318

    The systinet plug-in JAR files (jbossesb-transport-client-1.0.jar and jbossesb-
    transport-1.0.jar) are not being included in the build. They should be places in the
    product/build/jbossesb/lib/ directory but are being excluded due to a bug in the build
    process.
Comment 8 Zuzana Zoubkova 2010-05-20 14:10:27 UTC 
Revision 5690. Will be tested after ESB merge.
Comment 9 Zuzana Zoubkova 2010-05-21 14:27:01 UTC 
File renamed and then fixed in revision 5709.
Comment 10 Jiri Pechanec 2010-05-28 12:59:33 UTC 
Files are present, it is necessary to check correct location in documentation
Comment 11 Jiri Pechanec 2010-06-01 10:46:54 UTC 
Verified in CR1
Comment 12 Dana Mison 2010-06-08 05:22:14 UTC 
Added to SOA 5.0.2 release notes as resolved:

SOA-2034
The files required for integration of the JBoss Enterprise SOA Platform with HP Systinet where not included.  
These files, jbossesb-transport-client-1.0.jar and jbossesb-transport-1.0.jar, are now included in the 
directory $JBOSS_HOME/tools/systinet/
Note You need to log in before you can comment on or make changes to this bug.