[
https://issues.apache.org/jira/browse/JAMES-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639343#action_12639343
]
Joerg Buchberger commented on JAMES-835:
----------------------------------------
Thank you, Bernd.
Last week I managed to have a look at attaching fragments with custom
ApplicationContext to the Spring extender bundle, as described in their
documentation. The mechanism in itself is fine. And it's easy to adapt
JamesApplicationContext et al. to compile with
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext
and receive an org.osgi.framework.BundleContext - unfortunately, I just had so
much time as to get stuck at config file path issues during startup of my
"james-bundle". This probably, will not be too hard to resolve, once
investigated further.
Currently my idea is to have one bundle providing the james app-context and its
dependencies for our fragment, and another, spring-dm-based, bundle that gets
its app-context from our fragment - but I'm not sure, whether this really is
the right approach.
I certainly will have another look at it. Unfortunately, I can only put it low
on my agenda for now - i.e. I won't get back at it soon.
> Create OSGi deployment
> ----------------------
>
> Key: JAMES-835
> URL: https://issues.apache.org/jira/browse/JAMES-835
> Project: JAMES Server
> Issue Type: New Feature
> Components: Deployment Modules
> Reporter: Bernd Fondermann
> Assignee: Bernd Fondermann
>
> This task aims at providing James Server as an OSGi bundle, based on the
> spring-deployment and spring's spring dynamic modules for osgi
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
