[jira] [Assigned] (CXF-4452) NullPointerException when trying to customize the package name for a service definition without customizing the class name.
[
https://issues.apache.org/jira/browse/CXF-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CXF-4452:
-
Assignee: Freeman Fang
> NullPointerException when trying to customize the package name for a service
> definition without customizing the class name.
> ---
>
> Key: CXF-4452
> URL: https://issues.apache.org/jira/browse/CXF-4452
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.6.1
> Environment: JDK v1.7
> Maven v3.0.4
> cxf-codegen-plugin v2.6.1
>Reporter: Sandy Perez
>Assignee: Freeman Fang
>Priority: Minor
>
> Hello
> When I try to use jax-ws customization to customize the package name without
> customizing the class name, for example using the following XML code
> xmlns="http://java.sun.com/xml/ns/jaxws";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
>
>
>
>
> I get the following exception:
> [WARNING] WSDLToJava Error: java.lang.NullPointerException
> [WARNING]
> [WARNING] org.apache.cxf.tools.common.ToolException:
> java.lang.NullPointerException
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:294)
> [WARNING] at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:184)
> [WARNING] Caused by: java.lang.NullPointerException
> [WARNING] at
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.ServiceProcessor.processService(ServiceProcessor.java:207)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.ServiceProcessor.process(ServiceProcessor.java:100)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.WSDLToJavaProcessor.wsdlDefinitionToJavaModel(WSDLToJavaProcessor.java:91)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.WSDLToJavaProcessor.process(WSDLToJavaProcessor.java:60)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:253)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:139)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:286)
> [WARNING] ... 4 more
> The problem is in the class named
> ‘org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.
> ServiceProcessor’ in line 207:
> if (serviceBinding2.getJaxwsClass().getComments() != null) {
> …
> }
> If you don’t customize the class name, serviceBinding2.getJaxwsClass() will
> returns null so calling getComments() results in a NullPointerException .
> A possible quick solution could be to change the condition as follows:
> if (serviceBinding2.getJaxwsClass() != null &&
> serviceBinding2.getJaxwsClass().getComments() != null) {
> …
> }
> On the other hand, a possible workaround is to customize the class name. For
> example, the following XML code will work fine.
> xmlns="http://java.sun.com/xml/ns/jaxws";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
>
>
>
>
>
> Best regards,
>
> Sandy Pérez González
> Indaba Consultores S.L.
> http://www.indaba.es/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
issue with jquery client
how to send the response to jquery client as josn data.
this is my jquery code for getting data to client
*var url=
'http://10.163.14.56:9000/customerservice/renderdetails?callback=?';
$(document).ready(function(){
$('#getData').click(function() {
$.ajax({
type: 'GET',
url: url,
async: false,
crossDomain:true,
jsonpCallback: 'jsonCallback',
contentType: "application/json",
dataType: 'jsonp',
success: function(json) {
alert("success") ;
alert(json.name);
//console.dir(json.sites);
},
error: function(e) {
alert("error"+e.toString());
}
});
});
});*
i have used jax-rs 2.6.1 framework in restfull for server side code
*@GET
@Produces(MediaType.APPLICATION_JSON)
@Path("/renderdetails")
public Response get_Det(){
//String json ="{symbol: 'IBM', price: 91.42}";
String data="{"
+"\"age\":100,"
+"\"name\":\"otcnic\" "
+"}";
System.out.println("JSON Data:"+data);
return Response.ok(data, MediaType.APPLICATION_JSON).build();
}*
please let me know what i made mistake,
i am getting the following in client side :
error[object Object]
Timestamp: 08/08/2012 09:58:02 AM
Error: SyntaxError: invalid label
Source File:
http://10.163.14.56:9000/customerservice/renderdetails?callback=jsonCallback&_=1344400082000
Line: 1, Column: 1
Source Code:
{"age":100,"name":"otcnic" }
if any body having server side and cient side code..
please share it
it would be help for me
thanks in advance
G.Lenin
Research Scientist
OTC-NIC
--
View this message in context:
http://cxf.547215.n5.nabble.com/issue-with-jquery-client-tp5712166.html
Sent from the cxf-issues mailing list archive at Nabble.com.
[jira] [Created] (CXF-4459) i am getting timout error while creating webservice client using jaxWsProxyFactoryBean using spring
jai created CXF-4459: Summary: i am getting timout error while creating webservice client using jaxWsProxyFactoryBean using spring Key: CXF-4459 URL: https://issues.apache.org/jira/browse/CXF-4459 Project: CXF Issue Type: New Feature Components: JAX-WS Runtime Affects Versions: 2.6.1 Environment: jdk 1.6, spring 3.0, cxf 2.6 Reporter: jai i have intergrated cxf with spring and trying to consume external webservice. everything works fine i have direct internet access. but when i try to run using my corporate proxy server which basically authenticated me using domain\userid,password via proxy.corporate.com i am getting timeout exception while client bean is invoked. share necessary code. dmain\userid password http://www.xxx.com/services/XXXService?wsdl"; /> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4454) JSSE KeyManagers and TrustManager XML configurations are ignored if they contain no keystore element.
[ https://issues.apache.org/jira/browse/CXF-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-4454. -- Resolution: Fixed Fix Version/s: 2.7.0 2.6.2 2.5.5 2.4.9 > JSSE KeyManagers and TrustManager XML configurations are ignored if they > contain no keystore element. > - > > Key: CXF-4454 > URL: https://issues.apache.org/jira/browse/CXF-4454 > Project: CXF > Issue Type: Bug > Components: Configuration >Affects Versions: 2.6.1 > Environment: all >Reporter: Sven Staible >Assignee: Aki Yoshida >Priority: Minor > Fix For: 2.4.9, 2.5.5, 2.6.2, 2.7.0 > > > The XSD for JSSE KeyManagers and TrustManagers allows them to not include a > keystore (or certstore) element (which is correct). However the configured > key and trust manager configurations are ignored and not applied if they > contain no keystore configuration element (see TLSParameterJaxBUtils.java:239 > and TLSParameterJaxBUtils.java:275). > For a Trust- or KeyManager to not require a keystore configuration is a valid > scenario. I'm currently using a JCE provider that does not require a > keystore. With the current implementation I can not use this provider with > the XML configuration feature. If I set the key and trust managers of this > provider manually in the TLSClientParametersConfig using java code it works > as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-2451) Unable to call no-arg methods when using implicit headers - getting params [null]
[ https://issues.apache.org/jira/browse/CXF-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431366#comment-13431366 ] Robert Oliver commented on CXF-2451: I believe I am running into this issue (or one that very closely matches the description) using CXF 2.6.1. Has this not been addressed yet in that version? I am using -exsh true to include the header as a parameter for my no-arg methods but it is still being omitted from the SOAP payload. If I step into the WrapperClassOutIntercepter.handleMessage() (client-side) and force MessageContentList.hasValue() to return true for the header param it is correctly included in the SOAP payload. My guess is that this has something to do with the MessagePartInfo.getIndex() (it is returning 1 even though it is the first item in the message parts list) but I'm not yet familiar enough with CXF to know if I'm barking up the wrong tree. > Unable to call no-arg methods when using implicit headers - getting params > [null] > - > > Key: CXF-2451 > URL: https://issues.apache.org/jira/browse/CXF-2451 > Project: CXF > Issue Type: Bug >Affects Versions: 2.2.3 > Environment: ALL >Reporter: Arik Gorelik >Assignee: Daniel Kulp > Fix For: 2.1.7, 2.2.4 > > > Hello, > I am a developer using CXF 2.2.3. I am currently running into an issue when > trying to call a NO-ARG method getFoo() > while using implicit headers defined ONLY at the wsdl:binding section. > Each header has a SEPARATE wsdl:message defined and headers elements are NOT > part of the getFooRequest wsdl:message. > The generated code looks correct (using wsdl2java); however, invoking the > method results in the error message in the following soap fault message: > wrong number of arguments while invoking public > com.test.services.v29.FooResponse > com.test.services.v29.TestServiceImpl.getFoo() throws > com.test.services.v29.TestException with params [null]. > Here is the stack trace: > WARNING: Application has thrown exception, unwinding now > org.apache.cxf.interceptor.Fault: wrong number of arguments while invoking > public com.test.services.v29.FooResponse > com.test.services.v29.TestServiceImpl.getFoo() throws > com.test.services.v29.TestException with params [null]. > at > org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:152) > at > org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(AbstractJAXWSMethodInvoker.java:83) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:126) > at > org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:55) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:68) > at > org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) > at > org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:98) > at > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) > at > org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:104) > at > org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99) > at > org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:452) > at > org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:196) > at > org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:220) > at > org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCXFServlet.java:153) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > > Caused by: java.lang.IllegalArgumentException: wrong number of arguments > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:166) > at > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:82) > ... 33 more > Request is: > http://sch
[jira] [Created] (CXF-4460) Support static claims globally and per endpoint
Oliver Wulff created CXF-4460: - Summary: Support static claims globally and per endpoint Key: CXF-4460 URL: https://issues.apache.org/jira/browse/CXF-4460 Project: CXF Issue Type: New Feature Components: Services Affects Versions: 2.6.1 Reporter: Oliver Wulff Assignee: Oliver Wulff User independent claims information can be added to an issued saml token. there are two options, either global claims which are independent of the endpoint (appliesto) and endpoint specific claims. Example: company name (global claim) application id (endpoint specific claim) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4461) ClaimsHandler is called only if a requested claim is supported
Oliver Wulff created CXF-4461: - Summary: ClaimsHandler is called only if a requested claim is supported Key: CXF-4461 URL: https://issues.apache.org/jira/browse/CXF-4461 Project: CXF Issue Type: Improvement Components: Services Affects Versions: 2.6.1 Reporter: Oliver Wulff ClaimsManager calls all configured ClaimsHandler and passes all requested claims for processing. This can be improved to call a ClaimsHandler only if it can support the requested claim. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4462) Support caching for claim values
Oliver Wulff created CXF-4462: - Summary: Support caching for claim values Key: CXF-4462 URL: https://issues.apache.org/jira/browse/CXF-4462 Project: CXF Issue Type: Improvement Reporter: Oliver Wulff Claims are usually provided by remote systems like LDAP, Web Services, etc. When a user logs into applications, the performance can be improved if the claims are cached. Ehcache should be used and maybe another option is hazelcast in a clustered environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4463) Support caching for mapped principals/identites
Oliver Wulff created CXF-4463: - Summary: Support caching for mapped principals/identites Key: CXF-4463 URL: https://issues.apache.org/jira/browse/CXF-4463 Project: CXF Issue Type: Improvement Components: Services Affects Versions: 2.6.1 Reporter: Oliver Wulff Within a login process like WS-Federation, several requests must be processed by the STS which can involve identity mapping. Identity mapping information are usually provided by remote systems like LDAP, Web Services, etc. The performance can be improved if the mapped principals/identites are cached. Ehcache should be used and maybe another option is hazelcast in a clustered environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4384) ClaimsAttributeStatementProvider only supports principal in WSS header but not OnBehalfOf
[ https://issues.apache.org/jira/browse/CXF-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff resolved CXF-4384. --- Resolution: Duplicate Fix Version/s: 2.6.2 Duplicate of CXF-4395 > ClaimsAttributeStatementProvider only supports principal in WSS header but > not OnBehalfOf > - > > Key: CXF-4384 > URL: https://issues.apache.org/jira/browse/CXF-4384 > Project: CXF > Issue Type: Bug > Components: Services >Affects Versions: 2.6.1 >Reporter: Oliver Wulff >Assignee: Oliver Wulff > Fix For: 2.6.2 > > > If an intermediary requests a token onbehalfof the > ClaimsAttributeStatementProvider ignores the principal of onbehalfof but > instead uses the one of the requestor or null if requestor hasn't passed a > token in WSS header. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4464) Support ClaimsHandler per realm
Oliver Wulff created CXF-4464: - Summary: Support ClaimsHandler per realm Key: CXF-4464 URL: https://issues.apache.org/jira/browse/CXF-4464 Project: CXF Issue Type: New Feature Components: Services Affects Versions: 2.6.1 Reporter: Oliver Wulff A ClaimsHandler is independent of the STS realm. Example: The LdapClaimsHandler is configured to support the claims firstname and lastname. The principal (ws-sec header, onbehalfof, actas) is mapped to the STS realm. But you must use another principal to access the claims data from the LDAP directory. Thus a claimshandler must know which principal of which realm must be used to retrieve the claims. Therefore, the ClaimsHandler must provide the information in which realm he is applicable thus the ClaimsManager can map the identity before calling retrieveClaimValues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4459) i am getting timout error while creating webservice client using jaxWsProxyFactoryBean using spring
[ https://issues.apache.org/jira/browse/CXF-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431507#comment-13431507 ] Freeman Fang commented on CXF-4459: --- Hi, You really should post this kind question on CXF users mailling list first but not create a jira directly. Freeman > i am getting timout error while creating webservice client using > jaxWsProxyFactoryBean using spring > --- > > Key: CXF-4459 > URL: https://issues.apache.org/jira/browse/CXF-4459 > Project: CXF > Issue Type: New Feature > Components: JAX-WS Runtime >Affects Versions: 2.6.1 > Environment: jdk 1.6, spring 3.0, cxf 2.6 >Reporter: jai > Original Estimate: 24h > Remaining Estimate: 24h > > i have intergrated cxf with spring and trying to consume external webservice. > everything works fine i have direct internet access. > but when i try to run using my corporate proxy server which basically > authenticated me using domain\userid,password via proxy.corporate.com i am > getting timeout exception while client bean is invoked. > share necessary code. > >ProxyServerPort="8080" Connection="Keep-Alive" MaxRetransmits="1" > AllowChunking="false" /> > > > dmain\userid > password > > > > > factory-bean="XXXWsClientclientFactory" factory-method="create" > /> > >value="com.genie4me.services.couponservice.CouponServicePortType" /> >value="http://www.xxx.com/services/XXXService?wsdl"; /> > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4452) NullPointerException when trying to customize the package name for a service definition without customizing the class name.
[
https://issues.apache.org/jira/browse/CXF-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CXF-4452.
---
Resolution: Fixed
Fix Version/s: 2.7.0
2.6.2
2.5.5
2.4.9
commit fix
http://svn.apache.org/viewvc?rev=1370687&view=rev for trunk
http://svn.apache.org/viewvc?rev=1370704&view=rev for 2.6.x branch
http://svn.apache.org/viewvc?rev=1371023&view=rev for 2.5.x branch
http://svn.apache.org/viewvc?rev=1371025&view=rev for 2.4.x branch
@Sandy,
Thanks for pointing out this issue!
> NullPointerException when trying to customize the package name for a service
> definition without customizing the class name.
> ---
>
> Key: CXF-4452
> URL: https://issues.apache.org/jira/browse/CXF-4452
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.6.1
> Environment: JDK v1.7
> Maven v3.0.4
> cxf-codegen-plugin v2.6.1
>Reporter: Sandy Perez
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 2.4.9, 2.5.5, 2.6.2, 2.7.0
>
>
> Hello
> When I try to use jax-ws customization to customize the package name without
> customizing the class name, for example using the following XML code
> xmlns="http://java.sun.com/xml/ns/jaxws";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
>
>
>
>
> I get the following exception:
> [WARNING] WSDLToJava Error: java.lang.NullPointerException
> [WARNING]
> [WARNING] org.apache.cxf.tools.common.ToolException:
> java.lang.NullPointerException
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:294)
> [WARNING] at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:184)
> [WARNING] Caused by: java.lang.NullPointerException
> [WARNING] at
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.ServiceProcessor.processService(ServiceProcessor.java:207)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.ServiceProcessor.process(ServiceProcessor.java:100)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.WSDLToJavaProcessor.wsdlDefinitionToJavaModel(WSDLToJavaProcessor.java:91)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.WSDLToJavaProcessor.process(WSDLToJavaProcessor.java:60)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:253)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:139)
> [WARNING] at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:286)
> [WARNING] ... 4 more
> The problem is in the class named
> ‘org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.
> ServiceProcessor’ in line 207:
> if (serviceBinding2.getJaxwsClass().getComments() != null) {
> …
> }
> If you don’t customize the class name, serviceBinding2.getJaxwsClass() will
> returns null so calling getComments() results in a NullPointerException .
> A possible quick solution could be to change the condition as follows:
> if (serviceBinding2.getJaxwsClass() != null &&
> serviceBinding2.getJaxwsClass().getComments() != null) {
> …
> }
> On the other hand, a possible workaround is to customize the class name. For
> example, the following XML code will work fine.
> xmlns="http://java.sun.com/xml/ns/jaxws";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
>
>
>
>
>
> Best regards,
>
> Sandy Pérez González
> Indaba Consultores S.L.
> http://www.indaba.es/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
