chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DiFrango, Ronald" <Ronald.DiFra...@capitalone.com>
Subject RE: Part 2: CMIS-917
Date Tue, 17 Nov 2015 12:51:13 GMT
Florian,

We can try that to see if it resolves our issues, but obviously we'd prefer a release version.

Thanks,

Ron

-----Original Message-----
From: Florian Müller [fmui@apache.org<mailto:fmui@apache.org>]
Sent: Tuesday, November 17, 2015 07:11 AM Eastern Standard Time
To: DiFrango, Ronald
Cc: 'dev@chemistry.apache.org'; Sarkar, Avijit
Subject: RE: Part 2: CMIS-917


Hi Ron,

There is no schedule for the next release, yet.
But you can take the source code from SVN, build it, and play with it.

@Gab: Do you have time for a release?


- Florian



> Florian,
>
>  As I mentioned before, we are using the Atom binding so this should
> come into play but for one reason or another it gets picked up in a
> JDK 8 environment.
>
>  That said, it sounds like this will be removed in the next release,
> when is that scheduled to drop?
>
>  Thanks,
>
>  Ron
>
>  -----Original Message-----
>  FROM: Florian Müller [fmui@apache.org]
>  SENT: Tuesday, November 17, 2015 12:44 AM Eastern Standard Time
>  TO: dev@chemistry.apache.org
>  CC: Sarkar, Avijit; DiFrango, Ronald
>  SUBJECT: Re: Part 2: CMIS-917
>
> Hi Ron,
>
>  This is not directly related to CMIS-917.
>  You are using the JAX-WS RI 2.2.10. OpenCMIS only supports the JAX-WS
> RI
>  2.1.7. They are not 100% compatible.
>
>  But this will become irrelevant with the next OpenCMIS release. We
> have
>  moved to Apache CXF.
>
>  - Florian
>
>  > Florian,
>  >
>  > [Note: I’d have added this to the JIRA ticket, but I can’t
> login as my
>  > email has changed since I created the account].
>  >
>  > Our dev team did a little more research and as such they slowly
>  > layered in the Chemistry JAR’s and found that for all the jar’s
> except
>  > the following our application worked fine:
>  >
>  > chemistry-opencmis-commons-impl-0.13.0.jar
>  >
>  > They decompiled the above jar file and noticed the class
>  > WssMUTube.java extends
>  > com.sun.xml.ws.api.pipe.helper.AbstractFilterTubeImpl and based on
> the
>  > stack-trace looks like the JAXWS runtime is using this
> implementation
>  > and that’s creating the issue that ends up with the following
> stack
>  > trace:
>  >
>  > java.lang.NoSuchMethodError:
>  >
> com.sun.xml.ws.api.message.Message.getHeaders()Lcom/sun/xml/ws/api/message/HeaderList;
>  > at
>  >
> org.apache.chemistry.opencmis.commons.impl.tube.client.WssMUTube.processResponse(WssMUTube.java:59)
>  > ~[chemistry-opencmis-commons-impl-0.13.0.jar:0.13.0]
>  > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1147)
>  > ~[jaxws-rt.jar:2.2.10]
>  > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:1050)
>  > ~[jaxws-rt.jar:2.2.10]
>  > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:1019)
>  > ~[jaxws-rt.jar:2.2.10]
>  > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:877)
>  > ~[jaxws-rt.jar:2.2.10]
>  > at com.sun.xml.ws.client.Stub.process(Stub.java:463)
>  > ~[jaxws-rt.jar:2.2.10]
>  > at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:191)
>  > ~[jaxws-rt.jar:2.2.10]
>  >
>  > They then repackaged this jar file after removing this
> WssMUTube.java
>  > class and then the application started running fine without any
> issue.
>  >
>  > Thanks,
>  >
>  > Ron DiFrango
>  >
>  > ________________________________________________________
>  >
>  > 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.


________________________________________________________

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.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message