The following comment has been added to this issue:
Author: Andrew Stevens
Created: Thu, 16 Dec 2004 6:28 PM
Body:
Can you provide an example file which does this, as I'm having trouble
reproducing this behaviour? Also, can you confirm what version of XDoclet
you're using, and re-try it with the current version (1.2.2) if you're not
using that version?
The only mention of run-as I can find in the EJB templates already has the
description before the role-name; there was a problem with this in the past
(see XDT-105), but it was fixed in October 2002, prior to the 1.2 beta 2
release...
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1191?page=comments#action_15455
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1191
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-1191
Summary: run-as element in message driven beans contains out of order
elements
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: XDoclet
Components:
EJB Module
Versions:
1.2.1
Assignee: xdoclet-devel (Use for new issues)
Reporter: John Kroll
Created: Thu, 9 Dec 2004 5:55 PM
Updated: Thu, 16 Dec 2004 6:28 PM
Description:
Within the security-identity element in a message-driven element the elements
within the run-as section appear in reverse order.
For example, the generated XML looks like:
<security-identity>
<description>Security identity description</description>
<run-as>
<role-name>DESIG_USER</role-name>
<description>Security identity to assume</description>
</run-as>
</security-identity>
However, the J2EE ejb-jar_2_0.dtd lists the element order as
<!ELEMENT run-as (description?, role-name)>
So the generated XML should really be:
<security-identity>
<description>Security identity description</description>
<run-as>
<description>Security identity to assume</description>
<role-name>DESIG_USER</role-name>
</run-as>
</security-identity>
This problem will prevent an EJB jar file from deploying in Websphere.
Current work around is to remove the description elements prior to packaging
the jar file.
---------------------------------------------------------------------
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 email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
