You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Jean-Sébastien Scrève <je...@atosorigin.com> on 2009/05/19 11:44:40 UTC
CXF migration to version 2.2
Hi all,
I began to migrate to CXF 2.2 revision. I was able to get a first revision
working : https://issues.apache.org/jira/browse/OPENEJB-977
There's still a piece of code I don't like that I try to remove. See posts
on CXF :
http://www.nabble.com/Migrating-to-CXF-2.2-in-OpenEJB-td23518058.html#a23612789
My question : it seems OpenEJB team decided not to use Spring to configure
CXF (Spring libraries not included from CXF and the ExtensionManagerBus
usage). Does anybody know the reason for that ? I guess we wanted to avoid
Spring dependencies.
Thanks in advance,
Jean-Sébastien Scrève.
--
View this message in context: http://www.nabble.com/CXF-migration-to-version-2.2-tp23612958p23612958.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: CXF migration to version 2.2
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
David Blevins wrote:
>
>
> We've so far tried to get by without Spring as a requirement for
> OpenEJB to run. The first library we encountered that used Spring was
> ActiveMQ, but even they don't require Spring to run and it was just an
> option. So for our ActiveMQ integration we support both with the
> default being to not use Spring.
>
> When we did the CXF integration, we took the same route as they also
> didn't require Spring to run and it was just an option; tough I'm not
> sure in our integration if we have a way to turn "spring
> configuration" support on for CXF like we can for ActiveMQ.
>
> There's the history.
>
> If we can continue to get by without it as a requirement, that'd be
> the best option in my opinion at least.
>
That would be definitely great if we can avoid spring dependencies.
The more different dependencies we have the more difficult it will be to
manage incompatibilities (for example, discussion around ASM) .
We will do our best to avoid using Spring.
Jean-Louis
--
View this message in context: http://www.nabble.com/CXF-migration-to-version-2.2-tp23612958p23655251.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: CXF migration to version 2.2
Posted by Jean-Sébastien Scrève <je...@atosorigin.com>.
All right.
What createBindingInfo() does is, among other things, to define the
transport factory linked to a namespace. When a namespace is read for the
very first time, CXF read a configuration file named bus-extensions.xml. At
that point, Jetty registers as a factory for some namespaces. So what I did
was simply to override the settings read by CXF right after the file
reading.
createEndPointInfo() calls createBindingInfo() and then actually retrieves
the transport factory linked to the input namespace. As Jetty was overriden
by our transport factory, createEndPointInfo() is then able to call our own
transport factory.
I'll provide a patch with cleaner code as soon as all my tests are done.
David Blevins wrote:
>
>
> On May 19, 2009, at 2:44 AM, Jean-Sébastien Scrève wrote:
>
>> I began to migrate to CXF 2.2 revision. I was able to get a first
>> revision
>> working : https://issues.apache.org/jira/browse/OPENEJB-977
>>
>> There's still a piece of code I don't like that I try to remove. See
>> posts
>> on CXF :
>> http://www.nabble.com/Migrating-to-CXF-2.2-in-OpenEJB-td23518058.html#a23612789
>
> In that thread you mention that overriding createBindingInfo() solves
> the problem. Not very CXF aware, can you tell me more about that?
>
>> My question : it seems OpenEJB team decided not to use Spring to
>> configure
>> CXF (Spring libraries not included from CXF and the
>> ExtensionManagerBus
>> usage). Does anybody know the reason for that ? I guess we wanted to
>> avoid
>> Spring dependencies.
>
> We've so far tried to get by without Spring as a requirement for
> OpenEJB to run. The first library we encountered that used Spring was
> ActiveMQ, but even they don't require Spring to run and it was just an
> option. So for our ActiveMQ integration we support both with the
> default being to not use Spring.
>
> When we did the CXF integration, we took the same route as they also
> didn't require Spring to run and it was just an option; tough I'm not
> sure in our integration if we have a way to turn "spring
> configuration" support on for CXF like we can for ActiveMQ.
>
> There's the history.
>
> If we can continue to get by without it as a requirement, that'd be
> the best option in my opinion at least.
>
> -David
>
>
>
--
View this message in context: http://www.nabble.com/CXF-migration-to-version-2.2-tp23612958p23704340.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: CXF migration to version 2.2
Posted by Jean-Sébastien Scrève <je...@atosorigin.com>.
Hi,
Patch has been submitted in OPENEJB-977.
Best regards,
Jean-Sébastien Scrève.
David Blevins wrote:
>
>
> On May 19, 2009, at 2:44 AM, Jean-Sébastien Scrève wrote:
>
>> I began to migrate to CXF 2.2 revision. I was able to get a first
>> revision
>> working : https://issues.apache.org/jira/browse/OPENEJB-977
>>
>> There's still a piece of code I don't like that I try to remove. See
>> posts
>> on CXF :
>> http://www.nabble.com/Migrating-to-CXF-2.2-in-OpenEJB-td23518058.html#a23612789
>
> In that thread you mention that overriding createBindingInfo() solves
> the problem. Not very CXF aware, can you tell me more about that?
>
>> My question : it seems OpenEJB team decided not to use Spring to
>> configure
>> CXF (Spring libraries not included from CXF and the
>> ExtensionManagerBus
>> usage). Does anybody know the reason for that ? I guess we wanted to
>> avoid
>> Spring dependencies.
>
> We've so far tried to get by without Spring as a requirement for
> OpenEJB to run. The first library we encountered that used Spring was
> ActiveMQ, but even they don't require Spring to run and it was just an
> option. So for our ActiveMQ integration we support both with the
> default being to not use Spring.
>
> When we did the CXF integration, we took the same route as they also
> didn't require Spring to run and it was just an option; tough I'm not
> sure in our integration if we have a way to turn "spring
> configuration" support on for CXF like we can for ActiveMQ.
>
> There's the history.
>
> If we can continue to get by without it as a requirement, that'd be
> the best option in my opinion at least.
>
> -David
>
>
>
--
View this message in context: http://www.nabble.com/CXF-migration-to-version-2.2-tp23612958p23739232.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: CXF migration to version 2.2
Posted by David Blevins <da...@visi.com>.
On May 19, 2009, at 2:44 AM, Jean-Sébastien Scrève wrote:
> I began to migrate to CXF 2.2 revision. I was able to get a first
> revision
> working : https://issues.apache.org/jira/browse/OPENEJB-977
>
> There's still a piece of code I don't like that I try to remove. See
> posts
> on CXF :
> http://www.nabble.com/Migrating-to-CXF-2.2-in-OpenEJB-td23518058.html#a23612789
In that thread you mention that overriding createBindingInfo() solves
the problem. Not very CXF aware, can you tell me more about that?
> My question : it seems OpenEJB team decided not to use Spring to
> configure
> CXF (Spring libraries not included from CXF and the
> ExtensionManagerBus
> usage). Does anybody know the reason for that ? I guess we wanted to
> avoid
> Spring dependencies.
We've so far tried to get by without Spring as a requirement for
OpenEJB to run. The first library we encountered that used Spring was
ActiveMQ, but even they don't require Spring to run and it was just an
option. So for our ActiveMQ integration we support both with the
default being to not use Spring.
When we did the CXF integration, we took the same route as they also
didn't require Spring to run and it was just an option; tough I'm not
sure in our integration if we have a way to turn "spring
configuration" support on for CXF like we can for ActiveMQ.
There's the history.
If we can continue to get by without it as a requirement, that'd be
the best option in my opinion at least.
-David
Re: CXF migration to version 2.2
Posted by Jean-Sébastien Scrève <je...@atosorigin.com>.
All right !
As mentionned here : https://issues.apache.org/jira/browse/OPENEJB-977, I
did not achieve to get something "clean" working without Spring. So I
attached a patch with Spring.
I'll do some more tests and keep you informed if I see any bug.
So now it's up to you to get the Spring patch or the non Spring patch !
Best regards,
Jean-Sébastien Scrève.
Jacek Laskowski wrote:
>
> On Tue, May 19, 2009 at 11:44 AM, Jean-Sébastien Scrève
> <je...@atosorigin.com> wrote:
>
>> My question : it seems OpenEJB team decided not to use Spring to
>> configure
>> CXF (Spring libraries not included from CXF and the ExtensionManagerBus
>> usage). Does anybody know the reason for that ? I guess we wanted to
>> avoid
>> Spring dependencies.
>
> Exactly. The less the better, but if it's CXF requirement to have it,
> we'll have it - the cost of being laid upon different frameworks.
> If/when we're OSGi, it's going to be as simple as turning a CXF bundle
> on and off without having to worry about the deps burden.
>
> Jacek
>
> --
> Jacek Laskowski
> Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
>
>
--
View this message in context: http://www.nabble.com/CXF-migration-to-version-2.2-tp23612958p23638253.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: CXF migration to version 2.2
Posted by David Blevins <da...@visi.com>.
On May 19, 2009, at 3:48 AM, Jacek Laskowski wrote:
> On Tue, May 19, 2009 at 11:44 AM, Jean-Sébastien Scrève
> <je...@atosorigin.com> wrote:
>
>> My question : it seems OpenEJB team decided not to use Spring to
>> configure
>> CXF (Spring libraries not included from CXF and the
>> ExtensionManagerBus
>> usage). Does anybody know the reason for that ? I guess we wanted
>> to avoid
>> Spring dependencies.
>
> Exactly. The less the better, but if it's CXF requirement to have it,
> we'll have it - the cost of being laid upon different frameworks.
> If/when we're OSGi, it's going to be as simple as turning a CXF bundle
> on and off without having to worry about the deps burden.
We've intentionally not required Spring in the OpenEJB core and it
would be great if we could get this to work without it.
-David
Re: CXF migration to version 2.2
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Tue, May 19, 2009 at 11:44 AM, Jean-Sébastien Scrève
<je...@atosorigin.com> wrote:
> My question : it seems OpenEJB team decided not to use Spring to configure
> CXF (Spring libraries not included from CXF and the ExtensionManagerBus
> usage). Does anybody know the reason for that ? I guess we wanted to avoid
> Spring dependencies.
Exactly. The less the better, but if it's CXF requirement to have it,
we'll have it - the cost of being laid upon different frameworks.
If/when we're OSGi, it's going to be as simple as turning a CXF bundle
on and off without having to worry about the deps burden.
Jacek
--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl