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.
Actually, it seems that attribute 'namespace' of 'import' element not used by bpel compiler and runtime as well. Steps to reproduce: - Create Synchronous sample project. - Open bpel source editor. - Change import namespace to some incorrect value, for example: <import namespace="http://www.mycomp.org/ChangedSynchronousSample" location="SynchronousSample.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/> - Save, build and deploy Synchronous project. - Run test. Result: Project works fine after change namespace in import to incorrect, but should not be.
venkat, maybe this is runtime issue?
are we ignoring the namespace in the engine?
I verfied and we do show errors if namespace points to wrong namespace. This looks like fixed in bpel validation not sure about runtime. assigning to different subcomponent.
Mei - could you verify whether the engine uses the namespace value correctly - does it fail with the incorrect namespace?
It should get fixed in Bpel validation because it is one of the static checks to ensure a valid bpel is packaged. Runtime does not use that attribute, so it should not spend another cycle of validation which is already done in Bpel validation, otherwise, it will be a duplication of validation in bpel engine at runtime which is inefficient.
fixed in static validator