geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-3310) Geronimo is not finding message-destination elements in ejb-jar.xmls
Date Thu, 02 Aug 2007 22:18:52 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks closed GERONIMO-3310.
----------------------------------

    Resolution: Invalid

The code actually does look for the message-destination elements, but we only pay attention
to them if there is an additional geronimo mapping in a geronimo message-destinationType element
from the message-destination-name in the spec jar to the message-destination-name in the geronimo
plan (inside an admin-object-instance).  If the names match, we don't need the additional
mapping so ignore it.

> Geronimo is not finding message-destination elements in ejb-jar.xmls
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-3310
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3310
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 2.0-M6
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.0.x
>
>
> daytrader has a couple message-destination elements in the ejb-jar.xml.  They aren't
getting picked up by the time AdminObjectRefBuilder needs to see them.
> I think in g. 1.x we had some hackery whereby the openejb deployer was calling naming
builders initContext with the entire ejb-jar.xml, and then buildNaming for each ejb.  Not
sure what we want to do yet.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message