cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <sberyoz...@gmail.com>
Subject Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2140
Date Wed, 08 Jun 2011 11:13:07 GMT
Hi Aki

On Wed, Jun 8, 2011 at 12:03 PM, Aki Yoshida <elakito@googlemail.com> wrote:
> Hi Sergey,
> I just dropped SOAPMessage.
>
> Most people would be using Source and the patch that I submitted was
> only supporting the Source usage. It makes sense to drop SOAPMessage.
>
> I had a reference to SOAPMessage in ColocUtil as I though I could
> eventually support the SOAPMessage as well. However, after hearing
> what you mentioned, I think it will be quite ugly (if not practical)
> to support it for coloc. (to support it without using it, we would
> need to convert it to some generic object outside of coloc but since
> this conversion is only necessary in case of using coloc, so it
> doesn't look right).
>
I agree, thanks for this fix.
One thing I need to mention is that I'm only thinking of using the
coloc binding for
JAX-RS coloc invocations so lets revisit this issue if you do get some
production requirements re supporting SOAPMessage in time.

But I hope supporting (Dispatch) Source will do it for most non-POJO cases

Cheers, Sergey

> Regards, aki
>
> 2011/6/8 Sergey Beryozkin <sberyozkin@gmail.com>:
>> Hi Aki
>>
>> On Wed, Jun 8, 2011 at 11:33 AM, Aki Yoshida <elakito@googlemail.com> wrote:
>>> hi,
>>> sorry.
>>> i'll be fixing it.
>>
>> np at all; by the way - I'm not sure I'm right there about dropping
>> explicit SOAPMessages refs, I was just hoping to get the coloc binding
>> reused somehow for JAX-RS tests, etc in time. Hopefully you can hide
>> those refs somehow :-)
>>
>> thanks, Sergey
>>
>>> regards, aki
>>>
>>> 2011/6/8 Sergey Beryozkin <sberyozkin@gmail.com>:
>>>> Hi,
>>>>
>>>>> [INFO] -------------------------------------------------------------
>>>>> [ERROR] COMPILATION ERROR :
>>>>> [INFO] -------------------------------------------------------------
>>>>> [ERROR] <https://builds.apache.org/job/CXF-Trunk-JDK15/ws/trunk/rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocUtil.java>:[31,22]
package javax.xml.soap does not exist
>>>>> [ERROR] <https://builds.apache.org/job/CXF-Trunk-JDK15/ws/trunk/rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocUtil.java>:[185,49]
cannot find symbol
>>>>> symbol  : class SOAPMessage
>>>>> location: class org.apache.cxf.binding.coloc.ColocUtil
>>>>> [ERROR] <https://builds.apache.org/job/CXF-Trunk-JDK15/ws/trunk/rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocUtil.java>:[186,49]
cannot find symbol
>>>>> symbol  : class SOAPMessage
>>>>> location: class org.apache.cxf.binding.coloc.ColocUtil
>>>>> [INFO] 3 errors
>>>>
>>>> I think SOAPMessage should not make it into the coloc binding -
>>>> because that is not a SOAP-specific binding - some users have been
>>>> asking about a coloc support for JAX-RS frontend as well so having a
>>>> javax.xml.soap dep seems problematic to me
>>>>
>>>> cheers, Sergey
>>>>
>>>
>>
>



-- 
Sergey Beryozkin

Application Integration Division of Talend
http://sberyozkin.blogspot.com

Mime
View raw message