On Wed, Nov 12, 2008 at 10:47 AM, David Leangen <[EMAIL PROTECTED]> wrote:
>> thats too bad. i havent been following osgi closely to be familar
>> with all
>> the problems. you would think there would be something like
>> OsgiObjectInput/OutputStream that is provided by the platform to
>> handle t
Note: reposted to ops4j to get their input. This thread is about the
state of Wicket+OSGi, specifically regarding classloaders. I have
stated my opinion, but thought it would be a good idea to include the
core developers working on this project.
> even that solution is technically a "hack"