[
http://jira.jboss.com/jira/browse/JBESB-569?page=comments#action_12362360 ]
Kurt Stam commented on JBESB-569:
---------------------------------
Yeah it'd be nice if you name the project "ESBTest" that it builds an
ESBTest.esb archive.
I think the classnames and package can be set to some default like:
my.action.package.HelloWorldAction
as far as the jbossall-client.jar goes we should just find the smallest jar in the
AS/client jar that fits our need. I think we only need some JMS API classes.
Put our jars in a Library (rules and jbpm do this too) "JBESB Library", I think
we can add the JBM messaging jar on the classpath so we're ready to go.
Should we make the classes in mypackage.test to be real log4j unittests? So you have
somekind of validation you're starting from something that works?
build.properties should be defaulted to:
org.jboss.esb.server.home=/jbossesb-server-4.2.GA
org.jboss.esb.server.config=default
update the readme
the juddi.properties file can be deleted, since the registry is configured to use an RMI
connection.
JBoss ESB Template Enhancements
-------------------------------
Key: JBESB-569
URL:
http://jira.jboss.com/jira/browse/JBESB-569
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.2 Milestone Release 2
Reporter: Tom Cunningham
Assigned To: Tom Cunningham
Here's a list of enhancements that have been suggested:
Parameterize the name of the project in the build.xml to match the eclipse project name
Parameterize the classnames of the ESB code we generate
Add directory jars (jaxr,scout,juddi)
To conserve space, pare down jboss-all jar into just the jms classes we need
Use InitialContext in SendJMSMessage.java (we have a jndi.properties file)
--
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