Felix Meschberger wrote:
Hi Niall,
To me the manifest looks good, except perhaps for the import of the
javax.portlet package: I fear, not all servlet containers have this
package, so it might be a good idea to either import it dynamically or
optional:
Dynamic import:
Karl,
Thank you for the fix. Yes, it (the maven snapshot) does seem to have
worked.
When is the next release of Felix? If it is soon, it might be better for
Tuscany to wait for the release rather than switch to using the snapshot
builds.
Thank you...
Regards,
Rajini
On 1/15/08, Karl Pauls
Thank you, Karl. That is very promising.
Thank you...
Regards,
Rajini
On 1/16/08, Karl Pauls [EMAIL PROTECTED] wrote:
Karl,
Thank you for the fix. Yes, it (the maven snapshot) does seem to have
worked.
Great :-)
When is the next release of Felix? If it is soon, it might be
Karl,
Thank you for the fix. Yes, it (the maven snapshot) does seem to have
worked.
Great :-)
When is the next release of Felix? If it is soon, it might be better for
Tuscany to wait for the release rather than switch to using the snapshot
builds.
Felix 1.0.2 will be out end of next
I guess that people that want to swap Http Service implementations
they will stick to Http Service API so basically they should get the
same expected behavior on using any of the implementations.
Extensions can be added as like there was another service that they
can use. and when a developer
Stuart McCulloch wrote:
+1 for portable bundles... I've been really frustrated at times when
I want to mix certain compendium services, only to find there's no
framework that can support certain mixes of Equinox, Knopflerfish
and Felix bundles
Agreed.
sounds like we need a testing harness
I've started a wiki page for Commons to track progress of releasing
OSGi enabled components and notes about any issues here:
http://wiki.apache.org/commons/CommonsOsgi
Niall
Hi all,
I built two implementations of JPA that are able to work with OSGi,
these are Hiberate and Glassfish JPA implementations (there are still
some issues as there is no easy way to unload any of these
implementation based on several issues, but in both cases you are able
to use them within
Thanks for your input Felix
That was not the answer I was expecting :)
Anyway, do you have any idea about how to workaround this problem ?
Thanks
--Guillaume
Felix Meschberger wrote:
Hi Guillaume,
The problem with this method is, that upto and including Java 1.4 it is
marked final. It is
After a bit of thinking, I was wondering if a possible solution could be
to have the ability to change the ContentClassLoader implementation.
If something like this was present, I could have my own JDK5 only
ContentClassLoader that extends ContentClassLoader and override the
getResources
Guillaume Sauthier wrote:
After a bit of thinking, I was wondering if a possible solution could
be to have the ability to change the ContentClassLoader implementation.
If something like this was present, I could have my own JDK5 only
ContentClassLoader that extends ContentClassLoader and
11 matches
Mail list logo