2:03 a.m.
[ http://jira.jboss.com/jira/browse/JBESB-519?page=comments#action_12363164 ]
Daniel Bevenius commented on JBESB-519:
---------------------------------------
Committed revision 12132
This is an update of the samples/quickstars/conf/base-build.xml
The concern the following user forum thread:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=109345
Mail conversation with Burr:
Burr wrote:
I posted a note in the forums. Can you cook up an update to
base-build.xml and we'll make sure to get it out to everybody?
Daniel Bevenius wrote:
I downloaded jbossesb-4.2MR2-src.zip from
http://labs.jboss.com/jbossesb/downloads.
Yes, those are the targets I ran and yes, running from source is no
problem but there is a problem with when downloading the zip above.
Maybe we should ask the guys having troubles to download the src or
check out from svn to save them the hassel and also gives us time to
sort things out.
/Daniel
Hi Burr,
I just downloaded the jbossesb-server-4.2MR2.zip and tried it and I
noticed that the ant targets do not work. This is my fault. When I
tested this I always assumed that there would either be a
build/jbossesb/lib or a lib/ directory in the directory to which the
bundle had been unzipped. I assumed this by looking at the previous
release but I realize now that this bundle was not available then.
I'll look into this staight away. Really sorry about this.
/Daniel
Hi Burr,
I just checked in a updated base-build.xml file.
Can you confirm or correct the following statements about the directory layouts for
different distributions:
Directory for esb jar files:
Source distribution=${product.dir}/build/jbossesb/lib
Bundled
distribution=${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}/deploy/jbossesb.sar/lib
GA = ${product.dir}/lib
Directory with ext jar files:
Source distribution=${product}/lib/ext
Bundled
distribution=${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}/deploy/jbossesb.sar/lib
GA=${product.dir}/lib
I think what confused me a bit was that the GA release had a lib directory which the
bundled version does not. Also that for the bundled server distribution the ext jar files
are in the jbossesb.sar/lib directory.
I have tested this with the bundled version and the source dist using the code in the
trunk. Could you double check this so that I have not missed anything.
Would also be great if we could continue working on
http://jira.jboss.com/jira/browse/JBESB-519 to set the names for the different ways to
run/deploy and also verify that we have covered all types of distributions so we can avoid
this in the future.
Thanks,
Daniel
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)
Components: Examples
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Daniel Bevenius
Fix For: 4.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