[
http://jira.jboss.com/jira/browse/JBESB-52?page=all ]
Jason Lenhart closed JBESB-52.
------------------------------
Resolution: Done
Documentation has been upgraded and the database script modified accordingly to resolve
the rosetta/jbossesb conflict.
Fix documentation in Alpha release
----------------------------------
Key: JBESB-52
URL:
http://jira.jboss.com/jira/browse/JBESB-52
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Documentation
Affects Versions: 4.0 Alpha 1
Reporter: Daniel Brum
Assigned To: Jason Lenhart
Priority: Minor
Fix For: 4.0 Beta 1
Comments received from testers:
- I had to modify buildOne.xml in EsbServices to not use server/all/lib but use
server/default/lib instead. EJB3 requires use of the JEMS installer (to get EJB3 RC8 for
Seam 1.0) and it doesn?t give you an ?all? just a ?default?
- In the JBossESB Getting Started Guide, step 4 for loading the schema. I built
a Postgres database via pgAdmin (create a new database of your choice) so I had to modify
the .sql script to not try to build and connect to a ?rosetta? database. The
JBossESB-DS.xml pointed to ?JBossESB? not a ?rosetta? database.
- I had to change several file:///dev/JBossESB in FileMoverConfigExample.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira