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.
I get the attached warning msg when mapping complex type nodes in the bpel mapper. (First noticed in OpenESB but also happens in todays Alaska installer drop) - create a BPEL BP based on a simple request-reply WSDL. The wsdl imports two external xml schemas for the input and output msgs. - create an EJB project. - create a new WSDL which imports the exact same schemas documents and uses the same namespace I used for the WSDL which represents the bpel request/response partner. - From this wsdl, create an EJB webservice and deploy. - import the WSDL for the EJB webservice into the bpel project, create new PL, and invoke the service. - map the input variable of the business process to the input variable for the EJB webservice at the root node Everything deploys and runs correctly but should I be getting this warning msg if I'm using the same xsds and namespaces?
Created attachment 38196 [details] image to demostrate the issue
I do not recall seeing such a warning before. There was an RE from Josh that involved adding more "type checking" to the mapper. My first reaction is that this message must come from new work in this area. But, I am a bit confused because I thought that Josh had said he did not actually do anything in this area because he had no time. I think we should ask Josh to clarify whether this was pre-existing functionality that is only now being exposed, or whether it is new functionality, that may be buggy.
Yes I haven't worked on the mapper for a while (I'm now on a different project). This message is new to me. Perhaps alexey or supernikita could provide more info than I could...
We discussed something similar today.
It was in old BPEL mapper, now it doesn't show the warning.