geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sisson (JIRA)" <>
Subject [jira] Updated: (GERONIMO-1649) Invalid deployment descriptor error when deploying an EJB 2.0 MDB
Date Fri, 24 Feb 2006 06:46:43 GMT
     [ ]

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:
>      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
> urce-ref@ in element message-driven@,
error: cvc-complex-type.2.4b: El
> ement not allowed: resource-ref@ in element message-driven@,
error: cv
> c-complex-type.2.4b: Element not allowed: resource-ref@
in element message-driven@
> /xml/ns/j2ee, error: cvc-complex-type.2.4b: Element not allowed: resource-ref@
in element message-dri
> ven@]
> 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:
For more information on JIRA, see:

View raw message