I committed a fairly substantial DI refactoring in rev 89368. It
works in geronimo under osgi assembled with blueprint, but I haven't
figured out how to test the spring assembly. This should not affect
jetspeed since the only changes in the portlet container are a javadoc
typo fix and a suggestion not to use the PortletContainerFactory.
I'd really appreciate some help figuring out how to test the spring
assembly since there is a very good chance I didn't port all the xml
changes correctly back from the blueprint version. I'd also like to
find out how to run the tck :-)
many thanks
david jencks
On Dec 11, 2009, at 12:00 PM, David Sean Taylor wrote:
On Dec 11, 2009, at 11:01 AM, David Jencks wrote:
On Dec 10, 2009, at 3:41 PM, David Sean Taylor wrote:
On Dec 9, 2009, at 10:19 PM, David Jencks wrote:
See also https://issues.apache.org/jira/browse/PLUTO-585
I've been working on getting pluto to run under osgi in geronimo
3, wiring the pluto components with the osgi blueprint service.
I now have the basic geronimo admin console working this way.
(there are a few exceptions but they aren't related to pluto).
I'm wondering how much of this to push back into pluto, and
when. Geronimo is not yet acting as a osgi rfc 66 web container,
so the web app bits of pluto are currently deployed in geronimo
as regular web apps (which means geronimo processes them into
osgi bundles in its own non-rfc-66 way). I have the blueprint
wired bits in a separate bundle from the web app bits. So, at
the moment it seems to me that the blueprint plan might be
interesting but the whole thing is somewhat geronimo specific at
the moment.
As long as we can still build against the trunk, or we are
notified about any changes we need to make to our code, I 'd be
interested in seeing it pushed back to Pluto
Does "we" == jetspeed2?
Yes, we as in Jetspeed and any other projects using Pluto.
What do I need to do to check compatibility?
Either check out the project and build it, or work with me, I can
also check the compatibility as you go, with your help of course
