Hi
I'm working on the Together 5.0 JBoss deployer . I don't have CVS write
access but there is a quick fix that I would appreciate.
The MDB message-interceptor is an optional element but the JBoss deployer
insists on it being there. unfortunately the Together ejb-jar.xml step
doesn't write an empty element so you have to edit the file by hand after
generation to include and empty message-interceptor element. To avoid this
hacking the deployer could be changed to accept no message-interceptor
element. This is a very quick one line change :-)
Could someone change the following (assuming there are no objections) on
the 2.2 branch.
In file org\jboss\metadata\MessageDrivenMetaData.java
on or about line 83
messageSelector = getElementContent(getUniqueChild(element,
"message-selector"));
change it to
messageSelector = getElementContent(getOptionalChild(element,
"message-selector"));
thanks
Mike Swainston-Rainford
At 09:25 22/05/2001 -0700, you wrote:
>I'm looking to do another release on the 2.2 branch to pickup some
>enhancements and bug fixes that have been commited to the main branch.
>The target date is next Tuesday May 29. If there is something you want
>in this release add it to the 2.2 branch by Monday May 28.
>
>Enhancements I'm looking to add include:
>- Support for integrating all web-app JNDI ENC entries
>- Integrated servlet/ejb security for bundled web containers
>- Simplified resource ref syntax
>- InheritableThreadLocal used for security information
>
>Bug fixes include:
>- Deployment order of wars/ejb jars
>- Handling of jnp urls
>
>
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
