The following issue has been updated:
Updater: Markus Bollig (mailto:[EMAIL PROTECTED])
Date: Sat, 6 Aug 2005 6:54 AM
Comment:
I wrote a patch to solve the problem.
I is now possible to set the following attributes:
@websphere.mdb listenerPort="lport" activationspec-jndi-name="aspecjndi"
activationspec-auth-alias="alias" destination-jndi-name="destjndi"
I added the new params to the websphere tag because i think that they are
websphere specific (I hope so).
Because the activationspec is only available in websphere versions >= 6.0 (i
think so) i also had to add a new websphere subtask attribute called version.
If the version is set to values >= 6.0 the new behaviour is activated.
In cases the listenerport and the activation spec are both set the
activationspec values will be used.
At the moment only the following version values are supported 5.0,5.1 and 6.0.
Changes:
Attachment changed to patch.diff
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1401?page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1401
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-1401
Summary: No support for activationSpecJndiName in @websphere.mdb tag
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: XDoclet
Components:
IBM Module
Versions:
1.2.3
Assignee: xdoclet-devel (Use for new issues)
Reporter: paul Taylor
Created: Fri, 13 May 2005 7:52 AM
Updated: Sat, 6 Aug 2005 6:54 AM
Environment: Windows XP using Websphere Application Server v6 and xdoclet 1.2.3
Description:
With Websphere 6 the recommended way to deploy a MDB is to use an
activation-spec, the activationSpecJndiName is required in the
ibm-ejb-jar-bnd.xmi file.
i.e
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="Message_bnd_1"
activationSpecJndiName="jms/ActivationSpec" >
<enterpriseBean xmi:type="ejb:MessageDriven"
href="META-INF/ejb-jar.xml#MessageDriven_1" />
<!-- ML FIX. enterpriseBean xmi:type="ejb:MessageDriven"
href="META-INF/ejb-jar.xml#MessageDriven_Trade"/-->
</ejbBindings>
Unfortunately Xdoclet doesnt support this as an option only the alternative of
listenerPort, which is not suitable.
I am new to Websphere myself and I do not know if this is a Websphere 6
Specific change or not. A doc explaining this stuff is available here
http://www-128.ibm.com/developerworks/websphere/techjournal/0504_reinitz/0504_reinitz.html
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
xdoclet-devel mailing list
xdoclet-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
