[ http://nagoya.apache.org/jira/browse/GERONIMO-281?page=history ]
     
Gianny DAMOUR closed GERONIMO-281:
----------------------------------

     Resolution: Fixed
    Fix Version: 1.0-M3

This has been fixed by Dain when he has rewritten the deployment code.

> Optional packages support
> -------------------------
>
>          Key: GERONIMO-281
>          URL: http://nagoya.apache.org/jira/browse/GERONIMO-281
>      Project: Apache Geronimo
>         Type: New Feature
>   Components: deployment, OpenEJB
>     Versions: 1.0-M1, 1.0-M2
>     Reporter: Jacek Laskowski
>     Assignee: Jacek Laskowski
>      Fix For: 1.0-M3

>
> Add optional packages support. Optional packages are resources listed in 
> META-INF/MANIFEST.MF as a value of the Class-Path main attribute.
> As a workaround it's possible to copy the resources to repository directory 
> and specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.
> The suggested approach to handle it is (Dain's email to OpenEJB dev mailing 
> list):
> [...]Instead I would create a lib directory in the config-store directory for 
> the module (i.e., a config-store/${number}/lib directory).  Then, just read 
> in the manifest class path entries for the ejb jar, copy them into the lib 
> dir and add them to the configuration class-path.  One trick is you must 
> repeat this for each jar copied into the lib as each of these can have 
> manifest class path entries.  Also watch out for circular dependencies in the 
> manifest class path entries.[...]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to