[
https://issues.apache.org/jira/browse/PLUTO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788532#action_12788532
]
David Jencks commented on PLUTO-585:
------------------------------------
As of rev 889103 I have pluto running in geronimo under osgi wired using
blueprint. There are some bits of code still at geronimo. This commit:
1. fixes poms to generate working osgi metadata
2. Adds some DI constructors to avoid requiring components to read their own
configuration files
3. For the read-your-own-config-file approack, abstracts away from direct use
of ServletContext to find the files.
4. provides hardcoded defaults for ToolTIps resourse bundles in case osgi can't
find the appropriate properties file(s).
With the possible exception of (3) I would not expect these to impact embedders
of pluto.
> Make pluto more osgi friendly
> -----------------------------
>
> Key: PLUTO-585
> URL: https://issues.apache.org/jira/browse/PLUTO-585
> Project: Pluto
> Issue Type: Bug
> Components: general
> Affects Versions: 2.0.1
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.0.1
>
>
> Geronimo needs pluto to come with more osgi support. We don't know yet
> exactly what this will entail. Some possible bits:
> 1. make the jars into osgi bundles. This should be completely
> non-controversial and easy.
> 2. use the osgi blueprint service instead of spring. This could be an
> optional other way of assembling the portal (most likely) or a replacement (I
> doubt this would be acceptable to everyone at this point).
> 3. Investigate deploying the wars as rfc 66 web app bundles. I'm not sure
> whether or not this would be useful for geronimo.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
