[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Marek Baluch updated JBIDE-8075: -------------------------------- Priority: Critical (was: Major) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8075: --------------------------------------- Fix Version/s: 3.2.x 3.3.x Bob - for you ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Marek Baluch commented on JBIDE-8075: ------------------------------------- Will try the newest build and if I manage to reproduce it then I will attach the project. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Marek Baluch commented on JBIDE-8075: ------------------------------------- Hi Bob, tried it on build: JBT 3.2_trunk.2011-01-19_08-51-02-H962. Follow the steps in how to reproduce just choose HelloMessage.ID. Hope I'm not the only one seeing this problem ... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick updated JBIDE-8075: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 3.2.1 (was: 3.2.x) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Robert (Bob) Brodt commented on JBIDE-8075: ------------------------------------------- Hi Grid. I just checked in a change to fix this but I did not see you had assigned this to yourself - sorry :( The problem was caused by the fact that the editor depends on a processArtifacts.wsdl file because that is where all the <property> and <propertyAlias> elements are created. The project Marek was using was probably imported from somewhere and did not have the processArtifacts.wsdl. The fix was to create the WSDL and add it to the process imports. Again, sorry if I stepped on your toes ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Feng Qian commented on JBIDE-8075: ---------------------------------- Haha, go ahead, Bob! I have noticed this problem. But when I was fixing this issue, I found in the 'Choose type of the variable' wizard, if you choose 'From project', there is a list of Messages. But I think in this case, we can't display these messages because the filters don't include the 'Messages' and if you choose a message, for example 'HelloMessage', it's part: ID, then click on 'ok'. We can't set a Type for the property. I checked the bpel documents, we can't set message part as a property type. Am I right? If right, I think we should filter these messages to avoid displaying them in the 'Choose type of the variable' wizard. Any ideas? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Robert (Bob) Brodt commented on JBIDE-8075: ------------------------------------------- Yes, you are right! The TypeSelectorDialog class is responsible for filtering the types that are displayed in the top selection treeviewer. This is done by creating specialized content providers for XSD types, elements and Messages. The TypeSelectorDialog uses bitflags for each of the XSD type and element checkboxes in the dialog and the xsdTypeProvider has a setFilter() method which tells it what kinds of things to include in its list. The messageTypeProvider has no such method, so it always collects all Messages that it finds and includes them in the selection list. I added a setFilter() to this class also and use the "showMessages" boolean to turn selection on and off when the user clicks the "Messages" checkbox in the dialog. I don't think it's necessary to create another JIRA for this - I'm going to include it as part of this fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8075?page=com.atlassian.jira.plugin... ] Pavol Srna commented on JBIDE-8075: ----------------------------------- Verified on jbdevstudio-product-eap-linux-gtk-4.1.0.v201104171649R-H346-M1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira