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.
This bug description is copied from the bug http://www.netbeans.org/issues/show_bug.cgi?id=137802 (all messages, which were added there since July 5). ================================================================================================== Product Version: NetBeans IDE Dev (Build 200807030007) Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) ------------------------------------- here are the validation errors I got, attaching new project. XML validation started. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/SynchronousSample.bpel:75,8 WARNING: The variable "OperationIn1" is initialized and not used. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/BPAsyncServiceRecv.wsdl:6,54 ERROR: s4s-elt-schema-ns: The namespace of element 'definitions' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/BPAsyncServiceRecv.wsdl:6,54 ERROR: s4s-elt-invalid: Element 'definitions' is not a valid element in a schema document. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/BPAsyncServiceRecv.wsdl:6,54 ERROR: src-import.2: The root element of document 'BPAsyncServiceRecv.wsdl' has to have the namespace name 'http://www.w3.org/2001/XMLSchema' and the local name 'schema'. C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/WizardCorrelationProperties.wsdl:17,8 ERROR: Can not find the element "ns:simpleElement" at the namespace "http://localhost:12000/repository/repository1/BP10AsyncService/BPAsyncServiceRecv". Expression: "/ns:simpleElement" C:/Documents and Settings/mpottlapelli/My Documents/NetBeansProjects/Correlation/CorrelationInvokeRecv/CorrelationInvokeRecv/src/SynchronousSample.bpel:123,16 ERROR: Property "wzrd_prop_simpleElement_simpleElement" does not have a propertyAlias defined for the message where the correlation set "wzrd_set_Invoke1_Receive1" is being used. 5 Error(s), 1 Warning(s). XML validation finished. In addition I have noted a regression, when "BPAsyncServiceWrapper" WSDL (partnerLinkType associated with two roles) is dropped on BPEL editor it is creating partner link but it is not recognizing the second role. -------------------------------------------------------------------------------------------------- Please follow these steps to reproduce the issue. 1. Create synchronous sample based on Samples/SOA/Synchronous BPEL Process 2. Add BPAsyncServiceRecv.wsdl and BPAsyncServiceInvoke.wsdl to the project 3. Create a WSDL, import BPAsyncServiceRecv and BPAsyncServiceInvoke WSDLs, define a PLT with two roles. 4. DnD WSDL on to BP canvas, create a PL with my role and partner role. 5. DnD Receive and Invoke activities and configure them. 6. Initiate correlation wizard from Recv, and select Invoke as initiating activity. Do the mapping and associate at "simpleElement". 7. Build the project.
Created attachment 65343 [details] new project with build errors
Created attachment 65344 [details] WSDL to be implemented
Created attachment 65345 [details] WSDL to be invoked
Vladimir, please take a look.
Nikita, there is XPath issue: Can not find the element <...> at the namespace "...", please, fix it.
The problem not in the validation. There is an absence of understanding if the schema declarations embedded to a WSDL accessible outside of the WSDL or not. In this case there are 2 WSDL files. One has embedded schema with a type declaration inside. Another WSDL file tries access that type. Any considerations don't make sense until we figure out if it possible and if possible then how if should look.