fyi: (2/2)
Begin forwarded message:
From: "Bennett, Timothy (JIS - Applications)"
<[EMAIL PROTECTED]>
Date: 28. July 2005 19:48:50 GMT+02:00
To: "Timur Mehrvarz" <[EMAIL PROTECTED]>
Cc: "Eelco Hillenius" <[EMAIL PROTECTED]>, "Richard S.
Hall" <[EMAIL PROTECTED]>, "Marcel Offermans"
<[EMAIL PROTECTED]>, "Jan Mikkelsen" <[EMAIL PROTECTED]>
Subject: RE: [ wicket-Feature Requests-1245268 ] Enable the use of
Wicket in an OSGi container
-----Original Message-----
From: Timur Mehrvarz [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 28, 2005 10:59 AM
To: Bennett, Timothy (JIS - Applications)
Cc: Eelco Hillenius; Richard S. Hall; Marcel Offermans; Jan Mikkelsen
Subject: Re: [ wicket-Feature Requests-1245268 ] Enable the
use of Wicket in an OSGi container
thank you for your kind words. Do you think we should start a
dedicated OSGi-Wicket wiki entry on the Wicket site? It
wouldn't take too much effort to get this done (explain the
idea and how to use it). I think you already started doing a
very good job for this.
Yeah... It might be next week before I can get started on that, but my
intention
from the start has been to share my osgi-wicket experience with the
wicket community.
Regarding your question about who should maintain a Wicket
bundle: I would say it depends on how important the Wicket
community values this. If they see it as a low priority, it
would be nice to have this done from the Oscar side. But if
they think it's hot, I would really like them to take care of
it. Ideally, this would ensure that a new Wicket bundle would
be available, whenever a new version of Wicket is released.
But something tells me, that this, when taken care of from
the Wicket side, will even mount in much bigger advantages.
Things we are not yet able to foresee yet. So, I would wish,
the Wicket community would maintain the manifest file and the
build target.
However, for something like this to be possible in
decentralized manner, it will require some sort of
"standard/bestPractice"
regarding the list of Java packages Wicket itself can expect
to import. What I did...
Bundle-Classpath: ., lib/concurrent-1.3.3.jar,
lib/ognl-2.6.7.jar, lib/dom4j-1.4.jar,
lib/commons-fileupload-1.0.jar, lib/commons- collections-2.1.jar
...to get my sample up is of course not ideal. Because
concurrent, ognl, dom4j, etc. might as well be available in
the VM as bundles already. I think we need OSGi bundles for
everything. Doesn't this cry for active participation of the
software vendors?
Thoughts?
Seems daunting to get the 100's of third-party vendors to build
osgi-compatible
jar artifacts, and it seems equally daunting for the osgi/oscar
communities to
maintain a secondary repository for these jars that we modified for
ourselves.
Wished Oscar could somehow auto-load dependent jars into a bundles'
classloader/classpath
similar to maven, but that's a different discussion for a different
day.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
