You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Forrest Xia (JIRA)" <ji...@apache.org> on 2012/05/17 11:27:08 UTC
[jira] [Created] (GERONIMO-6353) Add "DynamicImport-Package: *"
when using install-bundle command to transform a jar into a bundle
Forrest Xia created GERONIMO-6353:
-------------------------------------
Summary: Add "DynamicImport-Package: *" when using install-bundle command to transform a jar into a bundle
Key: GERONIMO-6353
URL: https://issues.apache.org/jira/browse/GERONIMO-6353
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: deployment
Affects Versions: 3.0-beta-1, 3.0
Reporter: Forrest Xia
Assignee: Forrest Xia
Priority: Minor
Fix For: 3.0
Think this scenario:
User has a custom Tomcat Valve class to be defined via server.xml, first he generated a jar from an IDE, then use install-bundle command to install into the server, then the user defines the valve in the server.xml to use.
This scenario introduces a cycle dependencies relationship between the user bundle and Tomcat bundles.
1. To resolve the user bundle, the Tomcat bundles need to be resolved first
2. To start Geronimo Tomcat module, the user bundle needs to be resolved first.
Currently, the install-bundle command add "resolution:=optional" properties to the installed user bundle, though the user bundle could be started when server boot, but if the there are packages cannot be resolved with "resolution:=optional", those packages won't be resolved anymore.
An improvement is to add "DynamicImport-Package: *" header to the generated menifest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6353) Add "DynamicImport-Package: *"
when using install-bundle command to transform a jar into a bundle
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Forrest Xia resolved GERONIMO-6353.
-----------------------------------
Resolution: Fixed
> Add "DynamicImport-Package: *" when using install-bundle command to transform a jar into a bundle
> -------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-6353
> URL: https://issues.apache.org/jira/browse/GERONIMO-6353
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 3.0, 3.0-beta-1
> Reporter: Forrest Xia
> Assignee: Forrest Xia
> Priority: Minor
> Fix For: 3.0
>
>
> Think this scenario:
> User has a custom Tomcat Valve class to be defined via server.xml, first he generated a jar from an IDE, then use install-bundle command to install into the server, then the user defines the valve in the server.xml to use.
> This scenario introduces a cycle dependencies relationship between the user bundle and Tomcat bundles.
> 1. To resolve the user bundle, the Tomcat bundles need to be resolved first
> 2. To start Geronimo Tomcat module, the user bundle needs to be resolved first.
> Currently, the install-bundle command add "resolution:=optional" properties to the installed user bundle, though the user bundle could be started when server boot, but if the there are packages cannot be resolved with "resolution:=optional", those packages won't be resolved anymore.
> An improvement is to add "DynamicImport-Package: *" header to the generated menifest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira