Also, make sure the jsf-api isn't deployed as an OSGi bundle, else
that one could be used and it would not be able to find the
implementation inside the jar.
On Fri, Feb 11, 2011 at 09:22, Charles Moulliard cmoulli...@gmail.com wrote:
The WAR contains the spec and the implementation.
Could you make:
la|grep -i jsf
to see if JSF api and implementation are not outside your bundle.
Else you have to use fragment to gather all in the same classloader.
Regards
JB
On 02/11/2011 09:22 AM, Charles Moulliard wrote:
The WAR contains the spec and the implementation.
Oh well... a good thing is that no one will use hibernate to actually
persist anything here.
It's JUST that this legacy thing has a few classes that I need to use (Address,
Country...) that actually implement some Hibernate interfaces (or extend some
Hibernate classes) -do not ask me why :)
So
Hi Manuel,
I did a webinar on deploying web services with CXF into ServiceMix
(which of course, is using Karaf as it's core). You can get access to
the archived webinar at:
http://fusesource.com/resources/video-archived-webinars/
Some sample code should be up there as well.
Best,
Ade
that would be fine, too.
As long as someone does this, since searching together all those
dependencies is
just a tedious task :)
2011/2/11 Guillaume Nodet gno...@gmail.com:
Shouldn't we put that in CXF ? Over time, I think it would be better
if that can be maintained inside CXF rather than
I think we should prefer this for all features currently in the enterprise
features file
kind regards,
andreas
On Fri, Feb 11, 2011 at 01:19:09PM +0100, Guillaume Nodet wrote:
Shouldn't we put that in CXF ? Over time, I think it would be better
if that can be maintained inside CXF rather than
One more thing though, since I'm searching for it :)
These Projects like Camel, CXF, Aries and so forth need to place the
URL to the features.xml file
more prominently to show the support and help finding them easier.
As long as it isn't done in another way :)
2011/2/11 Andreas Pieber
