You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "DiFrango, Ronald" <Ro...@capitalone.com> on 2015/11/06 22:51:47 UTC
CMIS-917
All,
We ran into the issue describe in the follow JIRA ticket with the same setup [JDK8]:
https://issues.apache.org/jira/browse/CMIS-917
The interesting thing is that we set the binding to ATOMPUB but it seems to get in the way of all of our other SOAP calls:
cmisParams.put(SessionParameter.BINDING_TYPE, BindingType.ATOMPUB.value());
Is there anyway to prune this out or is a patch forthcoming?
Thanks,
Ron
________________________________________________________
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: CMIS-917
Posted by Florian Müller <fm...@apache.org>.
Hi Ron,
The OpenCMIS 0.13.0 client does not reference JAX-WS libraries directly.
It relies on the JAX-WS implementation in the JDK. So, there is nothing
that can be excluded via Maven.
Previous OpenCMIS versions required additional JAX-WS JARs. Please check
if they are still in you project.
If not, please provide more details about your issue.
- Florian
> Florian,
>
> I wonder if y¹all could use Maven¹s compile optional scope so that they
> aren¹t included by default in order to prevent this. I think this is what
> Spring does, it would then put the onus on the consumers to include
> explicitly what they need.
>
> Being a little lazy here, but here are the dependencies we include, so
> which ones have SOAP libraries requirements:
>
> <dependency>
> <groupId>org.apache.chemistry.opencmis</groupId>
> <artifactId>chemistry-opencmis-client-api</artifactId>
> <version>0.13.0</version>
> </dependency>
> <dependency>
> <groupId>org.apache.chemistry.opencmis</groupId>
> <artifactId>chemistry-opencmis-client-impl</artifactId>
> <version>0.13.0</version>
> </dependency>
> <dependency>
> <groupId>org.apache.chemistry.opencmis</groupId>
> <artifactId>chemistry-opencmis-commons-api</artifactId>
> <version>0.13.0</version>
> </dependency>
> <dependency>
> <groupId>org.apache.chemistry.opencmis</groupId>
> <artifactId>chemistry-opencmis-commons-impl</artifactId>
> <version>0.13.0</version>
> </dependency>
>
>
> Thanks,
>
> Ron DiFrango
>
>
>
>
>
>
> On 11/7/15, 7:25 AM, "Florian Müller" <fm...@apache.org> wrote:
>
>> Hi Ron,
>>
>> The AtomPub binding code should not affect any SOAP calls.
>> If you don't use the Web Services binding, remove the Web Service
>> related JARs and their dependencies. They may interfere with other SOAP
>> libraries even if OpenCMIS doesn't use them.
>>
>>
>> - Florian
>>
>>
>>> All,
>>>
>>> We ran into the issue describe in the follow JIRA ticket with the same
>>> setup [JDK8]:
>>>
>>> https://issues.apache.org/jira/browse/CMIS-917
>>>
>>> The interesting thing is that we set the binding to ATOMPUB but it
>>> seems to get in the way of all of our other SOAP calls:
>>>
>>> cmisParams.put(SessionParameter.BINDING_TYPE,
>>> BindingType.ATOMPUB.value());
>>>
>>> Is there anyway to prune this out or is a patch forthcoming?
>>>
>>> Thanks,
>>>
>>> Ron
>>> ________________________________________________________
>>>
>>> The information contained in this e-mail is confidential and/or
>>> proprietary to Capital One and/or its affiliates and may only be used
>>> solely in performance of work or services for Capital One. The
>>> information transmitted herewith is intended only for use by the
>>> individual or entity to which it is addressed. If the reader of this
>>> message is not the intended recipient, you are hereby notified that any
>>> review, retransmission, dissemination, distribution, copying or other
>>> use of, or taking of any action in reliance upon this information is
>>> strictly prohibited. If you have received this communication in error,
>>> please contact the sender and delete the material from your computer.
>>>
>
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
>
Re: CMIS-917
Posted by "DiFrango, Ronald" <Ro...@capitalone.com>.
Florian,
I wonder if y¹all could use Maven¹s compile optional scope so that they
aren¹t included by default in order to prevent this. I think this is what
Spring does, it would then put the onus on the consumers to include
explicitly what they need.
Being a little lazy here, but here are the dependencies we include, so
which ones have SOAP libraries requirements:
<dependency>
<groupId>org.apache.chemistry.opencmis</groupId>
<artifactId>chemistry-opencmis-client-api</artifactId>
<version>0.13.0</version>
</dependency>
<dependency>
<groupId>org.apache.chemistry.opencmis</groupId>
<artifactId>chemistry-opencmis-client-impl</artifactId>
<version>0.13.0</version>
</dependency>
<dependency>
<groupId>org.apache.chemistry.opencmis</groupId>
<artifactId>chemistry-opencmis-commons-api</artifactId>
<version>0.13.0</version>
</dependency>
<dependency>
<groupId>org.apache.chemistry.opencmis</groupId>
<artifactId>chemistry-opencmis-commons-impl</artifactId>
<version>0.13.0</version>
</dependency>
Thanks,
Ron DiFrango
On 11/7/15, 7:25 AM, "Florian Müller" <fm...@apache.org> wrote:
>Hi Ron,
>
>The AtomPub binding code should not affect any SOAP calls.
>If you don't use the Web Services binding, remove the Web Service
>related JARs and their dependencies. They may interfere with other SOAP
>libraries even if OpenCMIS doesn't use them.
>
>
>- Florian
>
>
>> All,
>>
>> We ran into the issue describe in the follow JIRA ticket with the same
>>setup [JDK8]:
>>
>> https://issues.apache.org/jira/browse/CMIS-917
>>
>> The interesting thing is that we set the binding to ATOMPUB but it
>>seems to get in the way of all of our other SOAP calls:
>>
>> cmisParams.put(SessionParameter.BINDING_TYPE,
>>BindingType.ATOMPUB.value());
>>
>> Is there anyway to prune this out or is a patch forthcoming?
>>
>> Thanks,
>>
>> Ron
>> ________________________________________________________
>>
>> The information contained in this e-mail is confidential and/or
>>proprietary to Capital One and/or its affiliates and may only be used
>>solely in performance of work or services for Capital One. The
>>information transmitted herewith is intended only for use by the
>>individual or entity to which it is addressed. If the reader of this
>>message is not the intended recipient, you are hereby notified that any
>>review, retransmission, dissemination, distribution, copying or other
>>use of, or taking of any action in reliance upon this information is
>>strictly prohibited. If you have received this communication in error,
>>please contact the sender and delete the material from your computer.
>>
________________________________________________________
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: CMIS-917
Posted by Florian Müller <fm...@apache.org>.
Hi Ron,
The AtomPub binding code should not affect any SOAP calls.
If you don't use the Web Services binding, remove the Web Service
related JARs and their dependencies. They may interfere with other SOAP
libraries even if OpenCMIS doesn't use them.
- Florian
> All,
>
> We ran into the issue describe in the follow JIRA ticket with the same setup [JDK8]:
>
> https://issues.apache.org/jira/browse/CMIS-917
>
> The interesting thing is that we set the binding to ATOMPUB but it seems to get in the way of all of our other SOAP calls:
>
> cmisParams.put(SessionParameter.BINDING_TYPE, BindingType.ATOMPUB.value());
>
> Is there anyway to prune this out or is a patch forthcoming?
>
> Thanks,
>
> Ron
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
>