You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Chris Owens <ct...@chris-owens.com> on 2014/09/29 14:18:21 UTC

Re: Failure like OPENEJB-2063 bug, but with jax-Ws service

I'm getting the same stack trace; I just verified that I am running 1.7.0 and
cxf 2.6.14





--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Failure-like-OPENEJB-2063-bug-but-with-jax-Ws-service-tp4667209p4672025.html
Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Failure like OPENEJB-2063 bug, but with jax-Ws service

Posted by Romain Manni-Bucau <rm...@gmail.com>.
it is fixed now. Was the same without being the same ;) (not the same
call actually, I missed this one, sorry)


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-10-02 22:58 GMT+02:00 Chris Owens <ct...@chris-owens.com>:
> I just tried with 1.7.2 and same issue?
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/Failure-like-OPENEJB-2063-bug-but-with-jax-Ws-service-tp4667209p4672096.html
> Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Failure like OPENEJB-2063 bug, but with jax-Ws service

Posted by Chris Owens <ct...@chris-owens.com>.
I just tried with 1.7.2 and same issue?





--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Failure-like-OPENEJB-2063-bug-but-with-jax-Ws-service-tp4667209p4672096.html
Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Failure like OPENEJB-2063 bug, but with jax-Ws service

Posted by Romain Manni-Bucau <rm...@gmail.com>.
PS: https://issues.apache.org/jira/browse/TOMEE-1366


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-09-29 21:44 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> right, this one never has been fixed. You can open a jira for it
> (either on tomee or on cxf, both are relevant).
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-09-29 14:18 GMT+02:00 Chris Owens <ct...@chris-owens.com>:
>> I'm getting the same stack trace; I just verified that I am running 1.7.0 and
>> cxf 2.6.14
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://tomee-openejb.979440.n4.nabble.com/Failure-like-OPENEJB-2063-bug-but-with-jax-Ws-service-tp4667209p4672025.html
>> Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Failure like OPENEJB-2063 bug, but with jax-Ws service

Posted by Romain Manni-Bucau <rm...@gmail.com>.
well it is fixed so I don't want to create a thread about it but the
real bug is in cxf since they don't support the API they use. Instead
of throwing an exception they should System.err or log a warning
saying it is ignored IMHO.

Last point: another point is surely using commons-logging which is
only in maintenance mode today - we even didn't really integrate it in
TomEE/OpenEJB but we support slf4j and log4j2 out of the box.


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-10-04 17:16 GMT+02:00 romych <ro...@mail.ru>:
> Yes I am report about success too early.
> The error was not corrected at the time.
> Latter I am remove throw statement from AbstractDelegatingLogger.java source
> file and recompile cxf-api.
> Then overwrite cxf-api library at catalina-home/lib directory. But I think
> it is not an cxf bug, problem in openejb-cxf.
>
>>it is fixed now. Was the same without being the same ;) (not the same
>>call actually, I missed this one, sorry)
>
> Thanks mans, for your job.
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/Failure-like-OPENEJB-2063-bug-but-with-jax-Ws-service-tp4667209p4672130.html
> Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Failure like OPENEJB-2063 bug, but with jax-Ws service

Posted by romych <ro...@mail.ru>.
Yes I am report about success too early. 
The error was not corrected at the time.
Latter I am remove throw statement from AbstractDelegatingLogger.java source
file and recompile cxf-api.
Then overwrite cxf-api library at catalina-home/lib directory. But I think
it is not an cxf bug, problem in openejb-cxf.

>it is fixed now. Was the same without being the same ;) (not the same
>call actually, I missed this one, sorry)

Thanks mans, for your job.



--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Failure-like-OPENEJB-2063-bug-but-with-jax-Ws-service-tp4667209p4672130.html
Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Failure like OPENEJB-2063 bug, but with jax-Ws service

Posted by Romain Manni-Bucau <rm...@gmail.com>.
right, this one never has been fixed. You can open a jira for it
(either on tomee or on cxf, both are relevant).


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-09-29 14:18 GMT+02:00 Chris Owens <ct...@chris-owens.com>:
> I'm getting the same stack trace; I just verified that I am running 1.7.0 and
> cxf 2.6.14
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/Failure-like-OPENEJB-2063-bug-but-with-jax-Ws-service-tp4667209p4672025.html
> Sent from the TomEE Users mailing list archive at Nabble.com.