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.
Desc: The default values for JMS operation created during the WSDL genaration are <jms:operation destination="DefaultQueue" destinationType="Queue"/> <wsdl:input name="input1"> <jms:message messageType="TextMessage" textPart="change me"/> But when we add JMS operation later to the created WSDL,JMS operation is created as follows <jms:operation destination="Provide value for this required attribute" destinationType="Topic"/> <wsdl:input name="input1"> This should be creates with destination typ Queue & text part is also missing.
Will see if wsdl editor allows custom plug in.
Set target to "future" - to be fixed in component pack release for JMS BC
This will be fixed in the component pack release for JMS BC
this is fixed now in the latest glassfish esb 2.2
Verified in the latest build(GFESB:20091116-0720:2.2). Still getting the same result:when we add JMS operation later to the created WSDL,JMS operation is created as follows <jms:operation destination="Provide value for this required attribute" destinationType="Topic"/> <wsdl:input name="input1"> This should be creates with destination typ Queue & text part is also missing. It could be fine if we provide the default values while adding jms:binding also
ok I see the expectation here, the current option is specifying the details using the property sheet, the issue is some of the details would require user input, like the message part can not be put automatically ( there could be more than one message part which one to put ?) possibly this can be best served by making an enhancement request, like adding an operation would take the user through a wizard where user can specify the details, Changing this to an enhancement.