[jira] Commented: (CXF-2725) "local part cannot be "null" when creating a QName"
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848594#action_12848594 ] Sidhartha Priye commented on CXF-2725: -- Dan, With the help of this link - http://cwiki.apache.org/confluence/display/CXF20DOC/Application+Server+Specific+Configuration+Guide I can now endorse SAAJ1.3.2 libraries on WAS 6.1. The trick is to add the jsr173_api-1.0.jar. So for any one's reference here are the jars in WAS endorsed directory. Make sure your application and webapp-classloaders are parent-last saaj-impl-1.3.2.jar saaj-api-1.3.jar jsr173_api-1.0.jar jaxp-ri-1.4.2.jar Once I got this then I copied CXF2.2.7 jars on both the client app and the server app (both deployed on the same node). Restarted the server and that was it. For anyone who run into this problem, here are the list of jars I have assembled that gave me a working solution - Apache Commons Jars: commons-codec-1.3.jar commons-collections-3.2.1.jar commons-logging-1.1.1.jar commons-pool-1.5.2.jar commons-configuration-1.5.jar commons-lang-2.4.jar CXF jars/supporting jars: geronimo-activation_1.1_spec-1.0.2.jar geronimo-annotation_1.0_spec-1.1.1.jar geronimo-javamail_1.4_spec-1.6.jar geronimo-jaxws_2.1_spec-1.0.jar geronimo-stax-api_1.0_spec-1.0.1.jar geronimo-ws-metadata_2.0_spec-1.1.2.jar jaxb-api-2.1.jar jaxb-impl-2.1.12.jar jaxb-xjc-2.1.12.jar cxf-2.2.7.jar FastInfoset-1.2.7.jar jetty-6.1.21.jar jetty-util-6.1.21.jar stax2-api-3.0.1.jar velocity-1.6.2.jar woodstox-core-asl-4.0.7.jar wss4j-1.5.8.jar wstx-asl-3.2.9.jar xmlbeans-2.4.0.jar xml-resolver-1.2.jar XmlSchema-1.4.5.jar xmlsec-1.4.3.jar xmltooling-1.2.1.jar if you are using OpenSAML then you would need: opensaml-2.3.0.jar openws-1.3.0.jar slf4j-api-1.5.10.jar slf4j-jdk14-1.5.10.jar velocity-1.6.2.jar xmlsec-1.4.3.jar xmltooling-1.2.1.jar My endorsed library on WAS6.1 (/java/jre/lib/endorsed) is: jaxp-ri-1.4.2.jar jsr173_api-1.0.jar resolver-2.9.1.jar saaj-api-1.3.jar saaj-impl-1.3.2.jar serializer-2.9.1.jar wsdl4j-1.6.2.jar xalan-2.7.1.jar xercesImpl-2.9.1.jar xml-apis-2.9.1.jar Thank you very much for the fix to 2.2.7. Hope to stay in touch!!! thanks Sid > "local part cannot be "null" when creating a QName" > --- > > Key: CXF-2725 > URL: https://issues.apache.org/jira/browse/CXF-2725 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding >Affects Versions: 2.2.6 > Environment: Websphere 6.1, CXF 2.2.6 OR 2.2.7-snapshot, OpenSAML > libraries, Spring 2.5.6 libraries, JAX WS Client >Reporter: Sidhartha Priye >Priority: Critical > Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip > > > The entire discussion on this issue can be read here > http://old.nabble.com/local-part-cannot-be-%22null%22-when-creating-a-QName-td27714287.html#a27872480 > On Dan's suggestion, I am entering this track item as he mentioned he will > take a shot at it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2725) "local part cannot be "null" when creating a QName"
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-2725. -- Resolution: Fixed Fix Version/s: 2.2.7 Assignee: Daniel Kulp > "local part cannot be "null" when creating a QName" > --- > > Key: CXF-2725 > URL: https://issues.apache.org/jira/browse/CXF-2725 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding >Affects Versions: 2.2.6 > Environment: Websphere 6.1, CXF 2.2.6 OR 2.2.7-snapshot, OpenSAML > libraries, Spring 2.5.6 libraries, JAX WS Client >Reporter: Sidhartha Priye >Assignee: Daniel Kulp >Priority: Critical > Fix For: 2.2.7 > > Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip > > > The entire discussion on this issue can be read here > http://old.nabble.com/local-part-cannot-be-%22null%22-when-creating-a-QName-td27714287.html#a27872480 > On Dan's suggestion, I am entering this track item as he mentioned he will > take a shot at it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2725) "local part cannot be "null" when creating a QName"
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848691#action_12848691 ] Sidhartha Priye commented on CXF-2725: -- Dan, I am just curious what was the issue that was causing this and what did you fix. Should I look for this in the release notes. thanks Sid > "local part cannot be "null" when creating a QName" > --- > > Key: CXF-2725 > URL: https://issues.apache.org/jira/browse/CXF-2725 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding >Affects Versions: 2.2.6 > Environment: Websphere 6.1, CXF 2.2.6 OR 2.2.7-snapshot, OpenSAML > libraries, Spring 2.5.6 libraries, JAX WS Client >Reporter: Sidhartha Priye >Assignee: Daniel Kulp >Priority: Critical > Fix For: 2.2.7 > > Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip > > > The entire discussion on this issue can be read here > http://old.nabble.com/local-part-cannot-be-%22null%22-when-creating-a-QName-td27714287.html#a27872480 > On Dan's suggestion, I am entering this track item as he mentioned he will > take a shot at it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2718) JAX-RS OSGi doesn't support relative path from annotation
[
https://issues.apache.org/jira/browse/CXF-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848708#action_12848708
]
Sergey Beryozkin commented on CXF-2718:
---
I recall having some issues with a pax web extender 'losing' the context after
a cxf bundle was refreshed or restarted. It refreshes itself whenever a cxf
jaxrs demo restarts, possibly to do with the fact it has some optional
dependencies(jettison related, etc). I actually submitted a patch, just can't
find a link at the moment, but I know it was applied by Alin Dreghiciu. It was
a transient thread-safety related issue.
> JAX-RS OSGi doesn't support relative path from annotation
> -
>
> Key: CXF-2718
> URL: https://issues.apache.org/jira/browse/CXF-2718
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.2.6
> Environment: Ubuntu 9
> servicemix-4.2.0-fuse-01-00
>Reporter: george.goodrich
> Attachments: configuration-status-20100318-1258-0700.txt
>
>
> I tried to use CXF JAX-RS in ServiceMix 4.2/Fuse ESB.
> Somehow I had to prefix /cfx/server-address in the @Path of the resource
> class.
> For example:
> I used the following Spring bean xml
>
>
> />
>
>
>
>
>
>
>
> Then I had to use /cxf/hello EXACTLY in resource class like below:
> @Path("/cxf/hello")
> public class EquipmentRegistryService {
>
>@GET
>@Produces("text/html")
>public String getXml() {
> return "Hello World!";
>}
> }
> If I changed the path to anything else(such as @Path("/greeting")), I got
> http 404.
> In the non-OSGi environment, I am able to use relative path in the path
> annotation.
> For example: if the @Path("/greeting") is used, I can use
> /cxf/rest/hello/greeting to reach the resource in non-OSGi environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1764) No support for attributes in JavaScript code generator
[ https://issues.apache.org/jira/browse/CXF-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CXF-1764: - Labels: gsoc (was: ) > No support for attributes in JavaScript code generator > -- > > Key: CXF-1764 > URL: https://issues.apache.org/jira/browse/CXF-1764 > Project: CXF > Issue Type: Bug > Components: JavaScript Client >Affects Versions: 2.1 >Reporter: Benson Margulies >Assignee: Benson Margulies > > We don't support @XmlAttribute and it's xsd equivalent. We should. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
