[
http://jira.jboss.com/jira/browse/JBESB-519?page=comments#action_12360189 ]
Burr Sutter commented on JBESB-519:
-----------------------------------
I just had a thought, we can leave the ant target as "deployToESB" for both ESB
Server & ESB within AS options.
However, I believe there is a classpath problem that will need to be corrected when
testing and support those 2 options. Plus I think the deprecated section can just be
yanked out since this is for example/educational purposes and the comments leads to
confusion.
The current "deploy" target still maps to StandaloneBootStrapper deployment.
Update quickstarts to more clearly demonstrate deployToAS vs
deployToESB
------------------------------------------------------------------------
Key: JBESB-519
URL:
http://jira.jboss.com/jira/browse/JBESB-519
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Daniel Bevenius
Fix For: 4.2 Milestone Release 2
Based on the introduction of the ESB Server in 4.2 MR1 the quickstarts are a little bit
confusing. Helloworld base-build.xml refers to "JBoss ESB Server at
'${jbosshome.dir}'." when jbosshome.dir should be mapped to the AS, not to
the ESB home.
I propose that quickstart.properties have a AS home and ESB home and the build.xml's
updated accordingly. As it stands not the jbosshome.dir is being overloaded.
The helloworld quickstart (and ideally all of them) should illustrate:
- StandAloneBootStrapper
- AS deployment (previously known as SAR deployment)
- ESB server deployment (new in 4.2)
- WAR deployment (if that model actually works)
Not every quickstart works with the ESB server and I believe this needs to be more
clearly specified in the readme.txt
--
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