[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[
https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12988533#action_12988533
]
Shawn Jiang commented on GERONIMO-5680:
---
Seems require-bundle is not calculated when generating the import list ?
{code}
environment
...
require-bundlexx/require-bundle
/environment
{code}
Find a way to slove the wired bundle cache
--
Key: GERONIMO-5680
URL: https://issues.apache.org/jira/browse/GERONIMO-5680
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 3.0
Reporter: Ivan
Assignee: Ivan
Fix For: 3.0
Attachments: GERONIMO-5680-NEW.patch, GERONIMO-5680.patch
http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm
The root cause is the dynamic import * is used, think that we should have a
way to replace it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12988534#action_12988534 ] Ivan commented on GERONIMO-5680: Hi, Shawn All the required bundle configurations are left there with no change. I just tried to deploy a simple application, the required-bundle data could be found in the MANIFEST.MF file of the deployed applications. Could you provide more details ? Thanks. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Attachments: GERONIMO-5680-NEW.patch, GERONIMO-5680.patch http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[
https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984098#action_12984098
]
Ivan commented on GERONIMO-5680:
Some extra codes are need to add, or there will be issues after the first start.
--
//init installed bundles
for (Bundle bundle : bundleContext.getBundles()) {
installed(bundle);
}
---
Find a way to slove the wired bundle cache
--
Key: GERONIMO-5680
URL: https://issues.apache.org/jira/browse/GERONIMO-5680
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 3.0
Reporter: Ivan
Assignee: Ivan
Fix For: 3.0
Attachments: GERONIMO-5680-NEW.patch, GERONIMO-5680.patch
http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm
The root cause is the dynamic import * is used, think that we should have a
way to replace it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984531#action_12984531 ] David Jencks commented on GERONIMO-5680: The new patch looks solid to me I think committing it is a good idea. I still hope we can eventually avoid the problem entirely by using bundle extenders so apps don't have access to server classes unless they specifically ask for it. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Attachments: GERONIMO-5680-NEW.patch, GERONIMO-5680.patch http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984570#action_12984570 ] Ivan commented on GERONIMO-5680: Thanks for reviewing the patch, David. Commit changes to trunk at rev.1061636. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Attachments: GERONIMO-5680-NEW.patch, GERONIMO-5680.patch http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12969191#action_12969191 ] Ivan commented on GERONIMO-5680: Agree to have the same sytnax with mavne bundle plugin, think that we should have a builder for calculating the import result, a simple string type is not enough. Will raise a thread in dev or irc. I commited the changes of DependencyManager to trunk at revision: 1043307, it now records the bundle dependency relation, as this function will be used for other modules. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Attachments: GERONIMO-5680.patch http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966334#action_12966334 ] David Jencks commented on GERONIMO-5680: This looks to me like a reasonable way to proceed. The only part I don't like is using the old class filters hidden classes. I was hoping to remove that bit of the schema. I wonder if we should look into using a maven-bundle-plugin compatible configuration for plugin import-export details? Then you can use a !foo.bar.* to prevent importing a particular package. If you want to commit this work we can discuss configuration options later. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Attachments: GERONIMO-5680.patch http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930702#action_12930702 ] David Jencks commented on GERONIMO-5680: As a long term goal I would like to move towards using bundle extenders to create the runtime components for ee modules rather than exposing server bundles to application components. I don't understand much about this current problem but perhaps this might suggest other ways of approaching a solution. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930705#action_12930705 ] Jarek Gawor commented on GERONIMO-5680: --- Two ideas: 1) As a short term solution, update the BundleClassLoader to only search statically imported bundles. That is, don't consider dynamically wired bundles. That might require updating some of our deployers to add appropriate import-package statements to the deployed bundle. 2) Update the Geronimo deployment descriptor to specify what bundles should be searched when doing resource lookup. For example, in addition to import-package/ add support for import-resource/. The bundles specified in import-resource/ would be searched when doing lookup via BundleClassLoader. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930521#action_12930521 ] Shawn Jiang commented on GERONIMO-5680: --- One of the possible solution is to compute the import set for a plugin at build time.And then specify the plugin dependency for different apps in deployers to attach the import set of a plugin to app bundle. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
