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.
Try to create Mobile client (JSR 172 support) from WSDLs generated by NB Ent pack. Observe there is a warning message from WSDL retriver which says the given WSDL is not WS-I coplient. See also this issue for more details. http://www.netbeans.org/issues/show_bug.cgi?id=88148
As this is breaking end to end application development betweeb Mobile and SOA apps I am increasing priority of this issue.
Can you provide steps and how to set up the environment for mobility. I am not sure from the bug why the wsdl is not WS-I compliant.
Created attachment 43571 [details] WSDL validator
Here are the steps to reproduce this issue. Create Synchronous sample and deploy. Create Mobile application (File -> New -> Mobility -> Mobile Application. Select Mobile application -> Add -> J2ME Webservice client Select Existing WSDL file and browse to Synchronous sample/src folder and select "SynchronousSample.wsdl" Observe Two dialogs appear. 1 Schema file not found 2 WSDL is not WS-I complient. (See attached screen capture for details). If you have questions about the validation you may contact Michal Skvor. He is the owner of this wizard.
I think this is a problem with the mobility pack and not related to wsdl editor. The WSDL validates fine. Currently the wsdl editor does not claim to produce WS-I compliant wsdls. The primary error that I see is that the imported schema is not accessed by the mobility wizard. Also the error message is not clear on what is not WS-I compliant that the mobility wizard needs. Also, it would be great if Michal can be added as cc onto this issue.
The WSDL validator should open the dialog with explanation that the schema file is not found. I fixed the issue with inaccessible schema about 2 months ago in http://www.netbeans.org/issues/show_bug.cgi?id=102213. Keep in mind that if you would like to create the client the application have to be deployed on application server and accessible from the IDE. PCM could you confirm that the schema file is unaccessible and your proxies in the IDE are properly set? I'm decreasing the priority to P3.
This application is running on bundled appserver. If you install using "Full installer" you can reproduce this scenario. I tried with the latest build and I saw the following two dialogs. 1 Schema file not found 2 WSDL is not WS-I complient. (See attached screen capture for details). Are you sure this issue is fixed for M10? With the priority P3?
Created attachment 43868 [details] xsd not dound error
the locally stored WSDL doesn't point to a valid location of XSD therefore it cannot be reached by the JSR172 mobilew webservices wizard. Because it isn't reachable there is the "schema file not found report" However when I point the wizard to the WSDL at the localhost (http://localhost:18181/SynchronousSample?WSDL) then it validates correctly. I'm reassigning back to xml. Please, generate valid wsdl. Or is it an unsupported use case? Anyway ball is on your side ;)
what do you mean "generate valid wsdl"? The wsdl editor is able to find the xsd file and validates fine. There is no problem with the wsdl editor other than the ws-i compliance stuff. I still dont know what is not WS-I compliant, and you guys didnt clarify that. Just because you pointed the wizard to the url does not substantiate the bug. reassigning back to mobility.
Maybe the WS-I compliance message is wrong and should be changed to JSR-172 or Mobile Web Services Compliance but the reason why the wsdl does not pass is still the same. JSR-172 specification restricts usage of wsdl and schema elements to simplify client stacks in the mobile. The restriction is combination of WS-I Basic Profile (http://www.ws-i.org) and additional JSR-172 restrictions (http://www.jcp.org/en/jsr/detail?id=172). I made some work to specify what is wrong the WSDL or Schema in version 6.0. Maybe I should make review of error messages.
Closing as fixed. Reopen it if necessary to explain some issues.
seems that it is working