[jira] Created: (CXF-2239) codegen fails to create classes, whereas wsimport succed

[Valerio Schiavoni (JIRA)]

codegen fails to create classes, whereas wsimport succed


 Key: CXF-2239
 URL: https://issues.apache.org/jira/browse/CXF-2239
 Project: CXF
  Issue Type: Bug
Affects Versions: 2.2.1
 Environment: Maven version: 2.0.10
Java version: 1.6.0_07
OS name: "mac os x" version: "10.5.7" arch: "x86_64" Family: "mac"

Reporter: Valerio Schiavoni


The wsdl is at http://api.microsofttranslator.com/V1/Soap.svc?WSDL

This works fine:
wsimport -keep http://api.microsofttranslator.com/V1/Soap.svc?WSDL

Instead, running the profile -Pbuild:wsdl in the attached pom produces:

Caused by: java.lang.RuntimeException: 
org.apache.ws.commons.schema.XmlSchemaException: An imported schema was 
announced to have the namespace http://tempuri.org/, but has the namespace 
http://api.microsofttranslator.com/v1/soap.svc
at 
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1907)
at 
org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1615)
at 
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:224)
at 
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:523)
at 
org.apache.cxf.common.xmlschema.SchemaCollection.read(SchemaCollection.java:176)
at org.apache.cxf.wsdl11.SchemaUtil.extractSchema(SchemaUtil.java:133)
at org.apache.cxf.wsdl11.SchemaUtil.getSchemas(SchemaUtil.java:73)
at 
org.apache.cxf.tools.validator.internal.WSDLRefValidator.getSchemas(WSDLRefValidator.java:115)
at 
org.apache.cxf.tools.validator.internal.WSDLRefValidator.processSchemas(WSDLRefValidator.java:127)
... 29 more
Caused by: org.apache.ws.commons.schema.XmlSchemaException: An imported schema 
was announced to have the namespace http://tempuri.org/, but has the namespace 
http://api.microsofttranslator.com/v1/soap.svc
at 
org.apache.ws.commons.schema.SchemaBuilder$1.validate(SchemaBuilder.java:1605)
at 
org.apache.ws.commons.schema.SchemaBuilder.setNamespaceAttributes(SchemaBuilder.java:369)
at 
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:134)
at 
org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:121)
at 
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:509)
at 
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:382)
at 
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1901)
... 37 more
[INFO] 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CXF-2239) codegen fails to create classes, whereas wsimport succed

[Valerio Schiavoni (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Valerio Schiavoni updated CXF-2239:
---

Attachment: translate.wsdl
pom.xml

The files to reproduce the problem. Simply put them in the same directory and 
run:

mvn -Pbuild:wsdl



> codegen fails to create classes, whereas wsimport succed
> 
>
> Key: CXF-2239
> URL: https://issues.apache.org/jira/browse/CXF-2239
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: Maven version: 2.0.10
> Java version: 1.6.0_07
> OS name: "mac os x" version: "10.5.7" arch: "x86_64" Family: "mac"
>Reporter: Valerio Schiavoni
> Attachments: pom.xml, translate.wsdl
>
>
> The wsdl is at http://api.microsofttranslator.com/V1/Soap.svc?WSDL
> This works fine:
> wsimport -keep http://api.microsofttranslator.com/V1/Soap.svc?WSDL
> Instead, running the profile -Pbuild:wsdl in the attached pom produces:
> Caused by: java.lang.RuntimeException: 
> org.apache.ws.commons.schema.XmlSchemaException: An imported schema was 
> announced to have the namespace http://tempuri.org/, but has the namespace 
> http://api.microsofttranslator.com/v1/soap.svc
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1907)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1615)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:224)
>   at 
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:523)
>   at 
> org.apache.cxf.common.xmlschema.SchemaCollection.read(SchemaCollection.java:176)
>   at org.apache.cxf.wsdl11.SchemaUtil.extractSchema(SchemaUtil.java:133)
>   at org.apache.cxf.wsdl11.SchemaUtil.getSchemas(SchemaUtil.java:73)
>   at 
> org.apache.cxf.tools.validator.internal.WSDLRefValidator.getSchemas(WSDLRefValidator.java:115)
>   at 
> org.apache.cxf.tools.validator.internal.WSDLRefValidator.processSchemas(WSDLRefValidator.java:127)
>   ... 29 more
> Caused by: org.apache.ws.commons.schema.XmlSchemaException: An imported 
> schema was announced to have the namespace http://tempuri.org/, but has the 
> namespace http://api.microsofttranslator.com/v1/soap.svc
>   at 
> org.apache.ws.commons.schema.SchemaBuilder$1.validate(SchemaBuilder.java:1605)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.setNamespaceAttributes(SchemaBuilder.java:369)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:134)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:121)
>   at 
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:509)
>   at 
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:382)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1901)
>   ... 37 more
> [INFO] 
> 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (CXF-2240) add ibmjdk profile for cxf-codegen-plugin

[Freeman Fang (JIRA)]

add ibmjdk profile for cxf-codegen-plugin
-

 Key: CXF-2240
 URL: https://issues.apache.org/jira/browse/CXF-2240
 Project: CXF
  Issue Type: Improvement
Affects Versions: 2.2.1, 2.1.5, 2.0.11
Reporter: Freeman Fang
Assignee: Freeman Fang


cxf-codegen-plugin need xercesImp dependency with IBM JDK, so if other project 
use cxf-code-plugin with IBM JDK, need add IBM JDK pofile to change default 
cxf-codegen-plugin dependency, like what already done in 
https://issues.apache.org/activemq/browse/CAMEL-939
https://issues.apache.org/activemq/browse/SMX4-149
We can add ibm jdk profile in cxf-codegen-plugin pom to avoid this
like add 
+
+
+ibmjdk
+
+
+java.vendor
+IBM Corporation
+
+
+
+
+xerces
+xercesImpl
+2.8.1
+
+
+
+


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (CXF-2223) Proxy authentication failure with SSL tunneling

[Mathieu Chauvin (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713010#action_12713010
 ] 

Mathieu Chauvin commented on CXF-2223:
--

The problem is still there with the 2.1.5 release.

I started from the very simple wsdl_first sample to show this issue. You will 
find attached the cxf.xml configuration that I updated to get the following 
exception:
 [java] Invoking sayHi...
 [java] Exception in thread "Main Thread" 
javax.xml.ws.soap.SOAPFaultException: Could not send Message.
 [java] at 
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:145)
 [java] at $Proxy41.sayHi(Unknown Source)
 [java] at demo.hw.client.Client.main(Client.java:61)
 [java] Caused by: org.apache.cxf.interceptor.Fault: Could not send Message.
 [java] at 
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
 [java] at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:226)
 [java] at 
org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:469)
 [java] at 
org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:299)
 [java] at 
org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:251)
 [java] at 
org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
 [java] at 
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
 [java] ... 2 more
 [java] Caused by: java.io.IOException: Unable to tunnel through proxy. 
Proxy returns "HTTP/1.0 407 Proxy Authentication Required"
 [java] at 
sun.net.www.protocol.http.HttpURLConnection.doTunneling(HttpURLConnection.java:1350)
 [java] at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:164)
 [java] at 
sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:857)
 [java] at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
 [java] at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1904)
 [java] at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.onFirstWrite(HTTPConduit.java:1859)
 [java] at 
org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:42)
 [java] at 
org.apache.cxf.io.AbstractThresholdOutputStream.write(AbstractThresholdOutputStream.java:69)
 [java] at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1922)
 [java] at 
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
 [java] at 
org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:626)
 [java] at 
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
 [java] ... 8 more
 [java] Java Result: 1

As the proxy fails client authentication, it is not even necessary to deploy 
the target server with an SSL listener. That's the reason why I started from 
the basic sample instead of the https one.
The wsdl_first client works fine with this configuration (assuming the proxy 
configuration is correct of course) using http, but setting the protocol to 
'https' within the wsdl leads to this issue.

Let me know if any additional information is required.

Mathieu.

> Proxy authentication failure with SSL tunneling
> ---
>
> Key: CXF-2223
> URL: https://issues.apache.org/jira/browse/CXF-2223
> Project: CXF
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 2.1.2
>Reporter: Mathieu Chauvin
>
> We are facing the very same issue as the one described at the following URL:
> http://www.mail-archive.com/us...@cxf.apache.org/msg06422.html
> Https transport appears not to send proxy-authorization within the CONNECT 
> operation as it should.
> Olivier Billard's workaround works just fine but requires java programming, 
> and makes it impossible to configure proxy related properties in a simple 
> manner.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (CXF-2230) details & faultactor are issing from webservice response

[Ashwin Kondhalkar (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713011#action_12713011
 ] 

Ashwin Kondhalkar commented on CXF-2230:


Daniel,

Good morning. This is regarding one more issue as "WSDL2Java does not generate 
the setter method of a List of objects". When I searched over the net I found 
the below link,

http://www.mail-archive.com/cxf-u...@incubator.apache.org/msg06395.html

In this link you have updated that this behavior is as per the JAXB 
specification. I wanted to know does this still holds true or its changed? Also 
is there any way of making use of option -xjc to pass some plugin to generate 
the setter methods?

Kindly let me know.

Thanks & Regards
 Ashwin



> details & faultactor are issing from webservice response
> 
>
> Key: CXF-2230
> URL: https://issues.apache.org/jira/browse/CXF-2230
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-WS Runtime, JAXB Databinding
>Affects Versions: 2.1
> Environment: ECLIPSE,XP,CXF 2.1
>Reporter: amit rathi
>Priority: Critical
> Fix For: 2.1.5
>
> Attachments: jar file set 1.zip, jar file set 2.zip, jar file set 
> 3.zip, please download these jar files from net & inculde in project.txt, 
> Sample_CXF_Project.zip, screenshot.zip
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> details & faultactor are missing from webservice response 
> This issue look identical to "  SOAPFaultException built programmatically and 
> thrown in a JAX-WS handler are not correctly populated " in this link 
> <<>>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CXF-2223) Proxy authentication failure with SSL tunneling

[Mathieu Chauvin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mathieu Chauvin updated CXF-2223:
-

Attachment: cxf.xml

Configuration file taken from the wsdl_first sample to illustrate how to 
reproduce this issue (in conjunction with the https protocol with the wsdl's 
endpoint).

> Proxy authentication failure with SSL tunneling
> ---
>
> Key: CXF-2223
> URL: https://issues.apache.org/jira/browse/CXF-2223
> Project: CXF
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 2.1.2
>Reporter: Mathieu Chauvin
> Attachments: cxf.xml
>
>
> We are facing the very same issue as the one described at the following URL:
> http://www.mail-archive.com/us...@cxf.apache.org/msg06422.html
> Https transport appears not to send proxy-authorization within the CONNECT 
> operation as it should.
> Olivier Billard's workaround works just fine but requires java programming, 
> and makes it impossible to configure proxy related properties in a simple 
> manner.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (CXF-2241) wsdl2java produces code with compile error, trying to instantiate abstract class

[Christopher Marshall (JIRA)]

wsdl2java produces code with compile error, trying to instantiate abstract class


 Key: CXF-2241
 URL: https://issues.apache.org/jira/browse/CXF-2241
 Project: CXF
  Issue Type: Bug
Affects Versions: 2.2.1
 Environment: Linux, Eclipse 3.5RC1
Reporter: Christopher Marshall


For wsdl that includes abstract complex types as:

  

  
  
  
  
  
  
  

  

an abstract class will be generated and the sample client will include code 
that tries to instantiate this class which of course causes a complile error.

The sample above is from the Google AdWords API and the full WSDL can be 
downloaded from:

https://adwords.google.com/api/adwords/v13/ReportService?wsdl

Chris Marshall

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (CXF-2173) ClassCastException with Declarative Services

[Josh Holtzman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Holtzman closed CXF-2173.
--


> ClassCastException with Declarative Services
> 
>
> Key: CXF-2173
> URL: https://issues.apache.org/jira/browse/CXF-2173
> Project: CXF
>  Issue Type: Bug
>  Components: Distributed-OSGi
>Reporter: Josh Holtzman
>Assignee: David Bosschaert
> Attachments: dosgi-ds.patch
>
>
> When trying to configure a DOSGI service using declarative services, the 
> following exception is thrown:
> Exception in thread "pool-1-thread-2" java.lang.ClassCastException: 
> [Ljava.lang.String; cannot be cast to java.lang.String
>   at 
> org.apache.cxf.dosgi.dsw.OsgiUtils.getPublishableInterfaces(OsgiUtils.java:470)
>   at 
> org.apache.cxf.dosgi.dsw.hooks.CxfPublishHook.publishEndpoint(CxfPublishHook.java:68)
>   at org.apache.cxf.dosgi.dsw.Activator$1.run(Activator.java:143)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
>   at java.lang.Thread.run(Thread.java:637)
> The OSGI/sample.xml file contains:
> 
> 
>   
>   
>   *
>   SOAP.1_2
>   pojo
>name="osgi.remote.configuration.pojo.httpservice.context">/samplews
>   
> 
>   
> 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (CXF-2239) codegen fails to create classes, whereas wsimport succed

[Benson Margulies (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benson Margulies resolved CXF-2239.
---

   Resolution: Invalid
Fix Version/s: 2.2.2
 Assignee: Benson Margulies

When I fetch the WSDL from the ? URL, I don't get the same thing that you do.

Your file copy contains:


http://tempuri.org/Imports";>
http://api.microsofttranslator.com/V1/Soap.svc?xsd=xsd0";
namespace="http://tempuri.org/"; />
http://api.microsofttranslator.com/V1/Soap.svc?xsd=xsd1";
namespace="http://schemas.microsoft.com/2003/10/Serialization/"; 
/>
http://api.microsofttranslator.com/V1/Soap.svc?xsd=xsd2";

namespace="http://schemas.microsoft.com/2003/10/Serialization/Arrays"; />


Note that 'tempuri.org' URLs. These are invalid, since they contradict what the 
served XSD states.

When I fetch from the ? URL, I get the following, and this works fine.


http://api.microsofttranslator.com/v1/soap.svc/Imports";>
http://api.microsofttranslator.com/V1/Soap.svc?xsd=xsd0"; 
namespace="http://api.microsofttranslator.com/v1/soap.svc"/>
http://api.microsofttranslator.com/V1/Soap.svc?xsd=xsd1"; 
namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
http://api.microsofttranslator.com/V1/Soap.svc?xsd=xsd2"; 
namespace="http://schemas.microsoft.com/2003/10/Serialization/Arrays"/>


> codegen fails to create classes, whereas wsimport succed
> 
>
> Key: CXF-2239
> URL: https://issues.apache.org/jira/browse/CXF-2239
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: Maven version: 2.0.10
> Java version: 1.6.0_07
> OS name: "mac os x" version: "10.5.7" arch: "x86_64" Family: "mac"
>Reporter: Valerio Schiavoni
>Assignee: Benson Margulies
> Fix For: 2.2.2
>
> Attachments: pom.xml, translate.wsdl
>
>
> The wsdl is at http://api.microsofttranslator.com/V1/Soap.svc?WSDL
> This works fine:
> wsimport -keep http://api.microsofttranslator.com/V1/Soap.svc?WSDL
> Instead, running the profile -Pbuild:wsdl in the attached pom produces:
> Caused by: java.lang.RuntimeException: 
> org.apache.ws.commons.schema.XmlSchemaException: An imported schema was 
> announced to have the namespace http://tempuri.org/, but has the namespace 
> http://api.microsofttranslator.com/v1/soap.svc
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1907)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1615)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:224)
>   at 
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:523)
>   at 
> org.apache.cxf.common.xmlschema.SchemaCollection.read(SchemaCollection.java:176)
>   at org.apache.cxf.wsdl11.SchemaUtil.extractSchema(SchemaUtil.java:133)
>   at org.apache.cxf.wsdl11.SchemaUtil.getSchemas(SchemaUtil.java:73)
>   at 
> org.apache.cxf.tools.validator.internal.WSDLRefValidator.getSchemas(WSDLRefValidator.java:115)
>   at 
> org.apache.cxf.tools.validator.internal.WSDLRefValidator.processSchemas(WSDLRefValidator.java:127)
>   ... 29 more
> Caused by: org.apache.ws.commons.schema.XmlSchemaException: An imported 
> schema was announced to have the namespace http://tempuri.org/, but has the 
> namespace http://api.microsofttranslator.com/v1/soap.svc
>   at 
> org.apache.ws.commons.schema.SchemaBuilder$1.validate(SchemaBuilder.java:1605)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.setNamespaceAttributes(SchemaBuilder.java:369)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:134)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:121)
>   at 
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:509)
>   at 
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:382)
>   at 
> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1901)
>   ... 37 more
> [INFO] 
> 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CXF-1395) MtoM for text/plain causes bad XML.

[Benson Margulies (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benson Margulies updated CXF-1395:
--

CXF Fields: [Blocked on External]

> MtoM for text/plain causes bad XML.
> ---
>
> Key: CXF-1395
> URL: https://issues.apache.org/jira/browse/CXF-1395
> Project: CXF
>  Issue Type: Bug
>  Components: Soap Binding
>Affects Versions: 2.1
>Reporter: Benson Margulies
>Assignee: Benson Margulies
>
> I just added a test case to ClientMtomXopTest that exercises MtoM where the 
> content type is text/plain rather than application/octet-stream or some other 
> thing.
> The test, when u...@ignored, produces garbage XML that is rejected in the 
> server's parse.
> I don't know where the problem here vis-a-vis CXF or the JAXB-RI. 
> This case is schema first The element type is base64Binary, but the code 
> generator is for some reason declaring as String instead of DataHandler. In 
> fact, this would be fine with me **if-it-worked**.
> Note that I have a related case working, at least client-to-server, in a 
> code-first scenario by declaring a DataHandler and attaching the XmlMimeType 
> annotation for text/plain.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (CXF-2240) add ibmjdk profile for cxf-codegen-plugin

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved CXF-2240.
---

Resolution: Fixed

commit fix
http://svn.apache.org/viewvc?rev=778719&view=rev for trunk
http://svn.apache.org/viewvc?rev=778950&view=rev for 2.1.x branch
http://svn.apache.org/viewvc?rev=778961&view=rev for 2.0.x branch

> add ibmjdk profile for cxf-codegen-plugin
> -
>
> Key: CXF-2240
> URL: https://issues.apache.org/jira/browse/CXF-2240
> Project: CXF
>  Issue Type: Improvement
>Affects Versions: 2.0.11, 2.1.5, 2.2.1
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>
> cxf-codegen-plugin need xercesImp dependency with IBM JDK, so if other 
> project use cxf-code-plugin with IBM JDK, need add IBM JDK pofile to change 
> default cxf-codegen-plugin dependency, like what already done in 
> https://issues.apache.org/activemq/browse/CAMEL-939
> https://issues.apache.org/activemq/browse/SMX4-149
> We can add ibm jdk profile in cxf-codegen-plugin pom to avoid this
> like add 
> +
> +
> +ibmjdk
> +
> +
> +java.vendor
> +IBM Corporation
> +
> +
> +
> +
> +xerces
> +xercesImpl
> +2.8.1
> +
> +
> +
> +

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Reopened: (CXF-2046) Response entity is enclosed in "Result" tags for classes implementing ExceptionMapper

[Gabo Manuel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gabo Manuel reopened CXF-2046:
--


Hi Sergey,

> Hi Gabo - I'm closing this JIRA for now as I can't see a bogus Result tag 
> appearing.
> Feel free to reopen please if you can still see with 2.2.1 or later, ideally 
> with a test case attached :-)

Sorry for the late reply. I have just tested 2.2.1, and the problem is still 
there. Included in the archive is the test case requested. Along with a 
snapshot of the said problem, some logs and class path just in case something 
is wrong with the binaries I am using.

Thanks in advance.

> Response entity is enclosed in "Result" tags for classes implementing 
> ExceptionMapper
> -
>
> Key: CXF-2046
> URL: https://issues.apache.org/jira/browse/CXF-2046
> Project: CXF
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 2.2
> Environment: Java 1.5
> Jetty 6.1
>Reporter: Gabo Manuel
> Fix For: 2.2
>
> Attachments: rtbe-ws4-retest_jira.zip
>
>
> Environment and objects involved is the same as that in another issue: 
> https://issues.apache.org/jira/browse/CXF-2045
> Additional objects involved:
> public class RuntimeExceptionMapper implements 
> ExceptionMapper{
> private static Logger logger = 
> Logger.getLogger(RuntimeExceptionMapper.class);
> public Response toResponse(RuntimeException fault) {
> StringBuffer sb = new StringBuffer();
> sb.append("Generate some custom message to hide the real problem from 
> end user.");
> 
> ResponseBuilder rb = Response.status(500);
> rb.type(MediaType.TEXT_PLAIN_TYPE);
> rb.entity(sb.toString());
> logger.fatal(fault);
> 
> Response resp = rb.build();
> 
> logger.info("entity: " + resp.getEntity().toString());
> 
> return resp;
> }
> }
> Logs captured by TCPMon
> HTTP/1.1 500 Internal Server Error
> Content-Type: text/plain
> Content-Length: 69
> Server: Jetty(6.1.11)
> Generate some custom message to hide the real problem from end 
> user.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CXF-2046) Response entity is enclosed in "Result" tags for classes implementing ExceptionMapper

[Gabo Manuel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gabo Manuel updated CXF-2046:
-

Attachment: rtbe-ws4-retest_jira.zip

Hi Sergey,

I am terribly sorry for the very late reply. There is still that result 
tag with 2.2.1. Attached is the test case requested. Including some 
snapshot and logs during my test. The class path is included in case of 
verification of the jars being used.

Thanks again in advance.

Gabo



> Response entity is enclosed in "Result" tags for classes implementing 
> ExceptionMapper
> -
>
> Key: CXF-2046
> URL: https://issues.apache.org/jira/browse/CXF-2046
> Project: CXF
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 2.2
> Environment: Java 1.5
> Jetty 6.1
>Reporter: Gabo Manuel
> Fix For: 2.2
>
> Attachments: rtbe-ws4-retest_jira.zip, rtbe-ws4-retest_jira.zip
>
>
> Environment and objects involved is the same as that in another issue: 
> https://issues.apache.org/jira/browse/CXF-2045
> Additional objects involved:
> public class RuntimeExceptionMapper implements 
> ExceptionMapper{
> private static Logger logger = 
> Logger.getLogger(RuntimeExceptionMapper.class);
> public Response toResponse(RuntimeException fault) {
> StringBuffer sb = new StringBuffer();
> sb.append("Generate some custom message to hide the real problem from 
> end user.");
> 
> ResponseBuilder rb = Response.status(500);
> rb.type(MediaType.TEXT_PLAIN_TYPE);
> rb.entity(sb.toString());
> logger.fatal(fault);
> 
> Response resp = rb.build();
> 
> logger.info("entity: " + resp.getEntity().toString());
> 
> return resp;
> }
> }
> Logs captured by TCPMon
> HTTP/1.1 500 Internal Server Error
> Content-Type: text/plain
> Content-Length: 69
> Server: Jetty(6.1.11)
> Generate some custom message to hide the real problem from end 
> user.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CXF-2230) details & faultactor are issing from webservice response

[amit rathi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

amit rathi updated CXF-2230:


Attachment: (was: jar file set 1.zip)

> details & faultactor are issing from webservice response
> 
>
> Key: CXF-2230
> URL: https://issues.apache.org/jira/browse/CXF-2230
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-WS Runtime, JAXB Databinding
>Affects Versions: 2.1
> Environment: ECLIPSE,XP,CXF 2.1
>Reporter: amit rathi
>Priority: Critical
> Fix For: 2.1.5
>
> Attachments: please download these jar files from net & inculde in 
> project.txt, Sample_CXF_Project.zip, screenshot.zip
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> details & faultactor are missing from webservice response 
> This issue look identical to "  SOAPFaultException built programmatically and 
> thrown in a JAX-WS handler are not correctly populated " in this link 
> <<>>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CXF-2230) details & faultactor are issing from webservice response

[amit rathi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

amit rathi updated CXF-2230:


Attachment: (was: jar file set 2.zip)

> details & faultactor are issing from webservice response
> 
>
> Key: CXF-2230
> URL: https://issues.apache.org/jira/browse/CXF-2230
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-WS Runtime, JAXB Databinding
>Affects Versions: 2.1
> Environment: ECLIPSE,XP,CXF 2.1
>Reporter: amit rathi
>Priority: Critical
> Fix For: 2.1.5
>
> Attachments: please download these jar files from net & inculde in 
> project.txt, Sample_CXF_Project.zip, screenshot.zip
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> details & faultactor are missing from webservice response 
> This issue look identical to "  SOAPFaultException built programmatically and 
> thrown in a JAX-WS handler are not correctly populated " in this link 
> <<>>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CXF-2230) details & faultactor are issing from webservice response

[amit rathi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

amit rathi updated CXF-2230:


Attachment: (was: jar file set 3.zip)

> details & faultactor are issing from webservice response
> 
>
> Key: CXF-2230
> URL: https://issues.apache.org/jira/browse/CXF-2230
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-WS Runtime, JAXB Databinding
>Affects Versions: 2.1
> Environment: ECLIPSE,XP,CXF 2.1
>Reporter: amit rathi
>Priority: Critical
> Fix For: 2.1.5
>
> Attachments: please download these jar files from net & inculde in 
> project.txt, Sample_CXF_Project.zip, screenshot.zip
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> details & faultactor are missing from webservice response 
> This issue look identical to "  SOAPFaultException built programmatically and 
> thrown in a JAX-WS handler are not correctly populated " in this link 
> <<>>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CXF-2230) details & faultactor are issing from webservice response

[amit rathi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

amit rathi updated CXF-2230:


Attachment: (was: please download these jar files from net & inculde in 
project.txt)

> details & faultactor are issing from webservice response
> 
>
> Key: CXF-2230
> URL: https://issues.apache.org/jira/browse/CXF-2230
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-WS Runtime, JAXB Databinding
>Affects Versions: 2.1
> Environment: ECLIPSE,XP,CXF 2.1
>Reporter: amit rathi
>Priority: Critical
> Fix For: 2.1.5
>
> Attachments: Sample_CXF_Project.zip, screenshot.zip
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> details & faultactor are missing from webservice response 
> This issue look identical to "  SOAPFaultException built programmatically and 
> thrown in a JAX-WS handler are not correctly populated " in this link 
> <<>>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.