geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anita kulshreshtha <a_kuls...@yahoo.com>
Subject Re: [jira] Commented: (GERONIMO-1649) Invalid deployment descriptor error when deploying an EJB 2.0 MDB
Date Fri, 24 Feb 2006 13:41:15 GMT
John, 
    This was in HEAD (rev. 379574). I hastily assumed
that these were related :(. I will look further and
file an issue if the problem still exists. 

Thanks
Anita

--- John Sisson <jrsisson@gmail.com> wrote:

> Anita,
> 
> the issue you have found in described in your
> comment below should be 
> moved to a separate mail thread or separate JIRA as
> it is a different 
> issue to the one my JIRA is describing.
> 
> In the mail/JIRA for your problem, can you also tell
> us whether is is in 
> HEAD or branches/1.0.
> 
> Thanks,
> 
> John
> Anita Kulshreshtha (JIRA) wrote:
> >     [
>
http://issues.apache.org/jira/browse/GERONIMO-1649?page=comments#action_12367495
> ] 
> >
> > Anita Kulshreshtha commented on GERONIMO-1649:
> > ----------------------------------------------
> >
> > These MDBs do not start during startup of the
> j2ee-tomcat-server built with fresh copy of G at rev
> 379835.
> >  ..............................
> >   WARNING: Some GBeans were not started
> successfully:
> >     TradeBrokerMDB (starting)
> >     TradeStreamerMDB (starting)
> >
> > Geronimo Application Server started
> >
> >   
> >> 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
> >>     
> >
> >   
> >> 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.
> >>     
> >
> >   
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Mime
View raw message