[ http://issues.apache.org/jira/browse/GERONIMO-1649?page=all ]
John Sisson updated GERONIMO-1649:
----------------------------------
Attachment: TEST-org.apache.geronimo.schema.SchemaConversionUtilsTest.txt
For future reference.. Attached test report showing failure in newly added test
before fix was committed. In the 2nd dump of xml (the output of the schema
conversion from the EJB 2.0 format) in the report you will see that the
security-identity element is in the wrong place. It should be after the
resource-ref elements.
> Invalid deployment descriptor error when deploying an EJB 2.0 MDB
> -----------------------------------------------------------------
>
> Key: GERONIMO-1649
> URL: http://issues.apache.org/jira/browse/GERONIMO-1649
> Project: Geronimo
> Type: Bug
> Components: OpenEJB, deployment
> Versions: 1.0
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Blocker
> Fix For: 1.1, 1.0.1
> Attachments: TEST-org.apache.geronimo.schema.SchemaConversionUtilsTest.txt
>
> There is a bug in
> org.apache.geronimo.schema.SchemaConversionUtils.convertBeans(..) for a EJB
> 2.0 MDB where the security-identity element is not moved to after the
> JNDIEnvironmentRefsGroup causing an error such as:
> org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error:
> cvc-complex-type.2.4b: Element not allowed: reso
> [EMAIL PROTECTED]://java.sun.com/xml/ns/j2ee in element [EMAIL
> PROTECTED]://java.sun.com/xml/ns/j2ee, error: cvc-complex-type.2.4b: El
> ement not allowed: [EMAIL PROTECTED]://java.sun.com/xml/ns/j2ee in element
> [EMAIL PROTECTED]://java.sun.com/xml/ns/j2ee, error: cv
> c-complex-type.2.4b: Element not allowed: [EMAIL
> PROTECTED]://java.sun.com/xml/ns/j2ee in element [EMAIL
> PROTECTED]://java.sun.com
> /xml/ns/j2ee, error: cvc-complex-type.2.4b: Element not allowed: [EMAIL
> PROTECTED]://java.sun.com/xml/ns/j2ee in element message-dri
> [EMAIL PROTECTED]://java.sun.com/xml/ns/j2ee]
> I will attach a test case to reproduce the problem tomorrow.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
