generating web services client codes in .apt_src folder..

[aupres]

Hello!

I try to develope web services by using jboss 7.0.2 and jbossws-cxf 4.0.2. Deployment is successful. But the problem is generating client codes.

When "src" folder is choosen, client codes are generated like below,

And when ".apt_src" folder is choosen, client codes are like this :

What i want is generating "clientsample" codes in ".apt_src" folder. But those codes are not generated. In JBoss 5 version "com.aaa.ws", "com.aaa.ws.jaxws" and

"com.aaa.ws.clientsample" package were generated in .apt_src folder.

Is it bug? or do i miss any option? Pls, inform me.

Best regards,

Joseph

[maxandersen]

what wizard are you using that puts # in the paths instead of / ?

[aupres]

Thank you for your reply, Max.

My previous reference was http://docs.jboss.org/tools/3.1.0.GA/en/ws_ref_guide/html/client.html .

[bfitzpat]

Create a JIRA for this and we can look at it. Please be as specific as you can with any steps and example code/wsdl you can provide.

[aupres]

Thanks, Brian. I created JIRA.And I am writing the bug on this page.

1. I made simple web services codes on Eclipse Indigo and JBoss 7. And I deployed it. My reference was http://docs.jboss.org/tools/3.1.0.GA/en/ws_ref_guide/html/topdown.html.

    Deploment was successful.

2. I tried to generate client sample codes. But it failed.

  

As shown above, no clientsample package was generated in .apt_src folder.In previous JBoss version, clientsamples package was generated in .apt_src folder and I used it.

I hope this bug will be solved on next JBossTools version. Thank you for your reply..

[aupres]

I created JIRA, Brian! Any comments?

[bfitzpat]

Sorry, haven't gotten back to this yet. On my list!

[aupres]

That's ok, Brian. When you solve this issue, pls leave the comment.

[bfitzpat]

I have had a chance to try this out and hit upon the issue you indicated. With AS 7.1 I'm seeing the following as the broken code. Note the notes about different constructors requiring different versions of JAX-WS. The workaround is to simply comment out the broken constructors and then it compiles fine even if generated in the .apt_src alternate source directory.

//This constructor requires JAX-WS API 2.2. You will need to endorse the 2.2

//API jar or re-run wsdl2java with "-frontend jaxws21" to generate JAX-WS 2.1

//compliant code instead.

public AreaService_Service(WebServiceFeature ... features) {

   super(WSDL_LOCATION, SERVICE, features);

}

//This constructor requires JAX-WS API 2.2. You will need to endorse the 2.2

//API jar or re-run wsdl2java with "-frontend jaxws21" to generate JAX-WS 2.1

//compliant code instead.

public AreaService_Service(URL wsdlLocation, WebServiceFeature ... features) {

   super(wsdlLocation, SERVICE, features);

}

//This constructor requires JAX-WS API 2.2. You will need to endorse the 2.2

//API jar or re-run wsdl2java with "-frontend jaxws21" to generate JAX-WS 2.1

//compliant code instead.

public AreaService_Service(URL wsdlLocation, QName serviceName, WebServiceFeature ... features) {

   super(wsdlLocation, serviceName, features);

}

I will continue to poke around, but the workaround at least seems pretty obvious.