geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sisson (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1649) Invalid deployment descriptor error when deploying an EJB 2.0 MDB
Date Fri, 24 Feb 2006 06:46:45 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1649?page=comments#action_12367629 ] 

John Sisson commented on GERONIMO-1649:
---------------------------------------

Note that the comment by Anita above is for a separate issue and is not addressed by this
JIRA.

> 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
> urce-ref@http://java.sun.com/xml/ns/j2ee in element message-driven@http://java.sun.com/xml/ns/j2ee,
error: cvc-complex-type.2.4b: El
> ement not allowed: resource-ref@http://java.sun.com/xml/ns/j2ee in element message-driven@http://java.sun.com/xml/ns/j2ee,
error: cv
> c-complex-type.2.4b: Element not allowed: resource-ref@http://java.sun.com/xml/ns/j2ee
in element message-driven@http://java.sun.com
> /xml/ns/j2ee, error: cvc-complex-type.2.4b: Element not allowed: resource-ref@http://java.sun.com/xml/ns/j2ee
in element message-dri
> ven@http://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


Mime
View raw message