[
https://jira.jboss.org/jira/browse/JBESB-2245?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2245:
----------------------------------------
The following are my findings so far. This was done by running 'ant deploy' from
the install directory. After the first two modifications in build.xml I removed alla the
.esb archives except jbossesb.sar and jbossesb.esb and my goal is to deploy the helloworld
quickstart. I'll then move on and add more of the services.
1. JMS Provider check
jms.config.check:
BUILD FAILED
/opt/jboss/esb/trunk/product/install/build.xml:70: Could not determine JMS provider
Solution:
Added:
<available property="jbm.present"
file="${deploy.dir}/messaging"/>
To the jms.config.check target.
2. Bindings file.
deploy.bindings:
BUILD FAILED
/opt/jboss/esb/trunk/product/install/build.xml:295: input file
/opt/jboss/as/jboss-5.0.0.GA/docs/examples/binding-manager/sample-bindings.xml does not
exist
Solution:
Modified the init.bindings.props target:
<condition property="bindings.dir"
value="${org.jboss.esb.server.home}/docs/examples/binding-manager"
else="${conf.dir}">
<available
file="${org.jboss.esb.server.home}/docs/examples/binding-manager"/>
</condition>
<condition property="bindings.location"
value="${bindings.dir}/sample-bindings.xml"
else="${bindings.dir}/bootstrap/bindings.xml">
<available
file="${org.jboss.esb.server.home}/docs/examples/binding-manager"/>
</condition>
3. JBossESBPropertyService
This class uses org.jboss.system.server.ServerConfigLocator:
final ServerConfig serverConfig = ServerConfigLocator.locate() ;
locate returned org.jboss.system.server.ServerConfig in the previous version but now
returns org.jboss.bootstrap.spi.ServerConfig.
We need to fix this in our code.
The same goes for JBoss4ESBDeployer and JuddiRMIService and probably a few more of our
services.
Solution:
I've temporary created a project in the rosetta directory that builds jboss5
versions of the effected classes to see if I can get the helloworld quickstart to deploy
and get an
idea of how much more work is required.
4. Deployment error:
08:53:45,064 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of
incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
persistence.unit:unitName=#rhqpu
-> jboss.jca:name=RHQDS,service=DataSourceBinding{Create:** NOT FOUND Depends on
'jboss.jca:name=RHQDS,service=DataSourceBinding' **}
*** CONTEXTS IN ERROR: Name -> Error
jboss.jca:name=RHQDS,service=DataSourceBinding -> ** NOT FOUND Depends on
'jboss.jca:name=RHQDS,service=DataSourceBinding' **
Solution:
Currently have not found the cause of this.
Investigate support for AS 5
----------------------------
Key: JBESB-2245
URL:
https://jira.jboss.org/jira/browse/JBESB-2245
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
We need to take a look at ESB within AS 5 to determine how this will impact the ESB. If
the necessary changes are not too invasive then we should look at supporting AS5 as well
as AS 4.
The focus of the ESB 4.x stream is still the AS 4.x releases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira