This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When working with JCAPS6.2 software it seems that web services generated from a web client do not serialize the data correctly. This is the case when accessing a BPEL process (ws based on WSDL of the BPEL process). Testing the BPEL works fine (generated an automatic test case). It only goes wrong when the web application sends a request via the web service. Maybe something is wrong with the Netbeans generated Stub code for the webservice? When finally submitting the request clicking the button it gives a selection failure in BPEL (when checking in the debugger it seems that some XML elements contain other XML elements where they should contain xsd:string. The problem is also described in the url above, or here: http://n2.nabble.com/BPEL-selection-failure-error-in-assign-activity-td3403844.html That said. I found a solution for it. Although I don't know if it is THE solution, meaning maybe it is just an indirect result of something else. Anyhow, what I found is that you need to set a different property for the web application project. Opening the properties for that project and go to Categories: Run, there you have to unselect the 'Deploy on Save' option. After switching this off all works fine when building and deploying it explicitly. Maybe there is some interference between this automatic deployment and the generation of the web service code? So the bug here is: When 'Deploy on Save' option is turned on for web application projects calling a web service is not working correctly.
Have you tried Netbeans 6.8 ? There were few changes in location of generated classes (JAX-WS client stub). Now the the content of build/generated-sources/jax-ws folder should be added to deployment directory (war file) automatically.
(In reply to comment #1) > Have you tried Netbeans 6.8 ? No JCAPS6.2 installs with Netbeans 6.5. It uses specific plugins (for repository based development) that will probably not work under 6.8. I am giving a problem here, with a solution. I just thought, maybe this could be useful information (especially because JCAPS is a commercial product of Sun/Oracle). I can easily deploy explicitly without the 'Deploy on Save' option. Hope it helps, Marcel
Thank you for evaluation. It's the "Deploy on Save" that probably doesn't accept(deploy) generated JAX-WS artifacts. I found similar issue in 6.9. Scenario : - create web application - create a web service client (from wsdl) in web application (http://www.webservicex.net/CurrencyConvertor.asmx) - create a servlet - invoke Insert Code -> Call WS Operation (Conversion Rate) inside servlet - clean project - Run servlet It's probably related to Compile on Save feature (issue 151845). See the attachment
Created attachment 96544 [details] GlassFish exceptions
I cannot replicate this with 3.0.1
this is waiting on the 3.0.1 integration
dev build 201004090201 includes GlassFish Server OSE 3.0.1 bits