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.
Seen with Product Version: NetBeans IDE Dev (Build 200802060003) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 System: SunOS version 5.10 running on x86; ISO646-US; en (nb) Userdir: /Users/lautz/.netbeans/dev 1. Create a new copy of the SynchronousSample application. 2. Open the SynchronousSampleApplication comp app in the CASA editor. 3. Click the Build Project button. 4. DnD a JMS BC into the WSDL ports area. 5. Click the Build Project button. => The build fails. pre-init: init-private: init-userdir: init-user: init-project: do-init: post-init: init-check: init: init-deploy: deps-jar: pre-init: init-private: init-userdir: init-user: init-project: do-init: post-init: init-check: init-taskdefs: init: pre-dist: pre-init: init-private: init-userdir: init-user: init-project: do-init: post-init: init-check: init-taskdefs: init: deps-sub-project: PackageRetrievedFiles: Deleting directory /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7/build/dependentProjectFiles Created dir: /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7/build/dependentProjectFiles dist_se: Building jar: /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7/build/SEDeployment.jar Expanding: /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7/build/SEDeployment.jar into /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7Application/src/jbiServiceUnits/SynchronousSample7 Moving 1 file to /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7Application/src/jbiServiceUnits/SynchronousSample7 deps-javaee-jar: jbi-build: Copying 2 files to /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7Application/src/jbiServiceUnits Building jar: /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7Application/build/BCDeployment.jar Validating CompApp project... validating /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7Application/src/jbiasa/SynchronousSample7Application.wsdl ERROR: /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7Application/src/jbiasa/SynchronousSample7Application.wsdl:20, column:16 Binding operation 'operation1' has an invalid JMS input binding (jms:message) : the input binding 'input1' defines textPart as 'change me' which is a non-existent part in WSDL message '{http://localhost/SynchronousSample/SynchronousSample}requestMessage' ERROR: /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7Application/src/jbiasa/SynchronousSample7Application.wsdl:23, column:16 Binding operation 'operation1' has an invalid JMS output binding (jms:message) : the output binding 'output1' defines textPart as 'change me' which is a non-existent part in WSDL message '{http://localhost/SynchronousSample/SynchronousSample}responseMessage' /Users/lautz/NetBeansProjects/SynchronousSample7/SynchronousSample7Application/nbproject/build-impl.xml:191: Found validation error(s). BUILD FAILED (total time: 0 seconds) It's kind of awkward to require the user to figure out what's broken in a generated document, especially if it's always going to be broken the first time. It would be nicer if it would be possible to tell the user where to set the missing values. I ended up messing around to figure out whether my direct edits to the generated *.wsdl file were going to disappear when I triggered a regeneration of the file (they didn't -- nice! but not obvious). I understand why we don't want to specify defaults in the typical case, but more direction would be nice.
*** Issue 126945 has been marked as a duplicate of this issue. ***
The user has to configure this herself, especially when the message contains multiple parts. In the future, when component provides a customization wizard, it will be easier to configure the component. For now, to configure this, select WSDL Ports/casaPort1/casabinding1/operation1/input1/jms:message in CASA navigator, and choose the appropriate textPart from the dropdown list in the property sheet.