[JBoss JIRA] Created: (JBIDE-8601) Hyperlinks throw assertions for undefined data types
by Robert (Bob) Brodt (JIRA)
Hyperlinks throw assertions for undefined data types
----------------------------------------------------
Key: JBIDE-8601
URL: https://issues.jboss.org/browse/JBIDE-8601
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.0.CR1
Environment: all
Reporter: Robert (Bob) Brodt
Assignee: Robert (Bob) Brodt
Fix For: 3.2.1
Whilst investigating JBIDE-8064 I ran across a problem with hyperlinks that are supposed to open the WSDL or XSD editor for message or schema definitions. The BPELUtil#openEditor() method will simply throw an assertion if the hyperlink points to an unknown object. This will happen if, for example, the user enters an incorrect message type for a variable using the editor's Source tab, or if a message type has been removed from a WSDL, etc.
The editor should display an error dialog if the object is undefined instead of simply ignoring the user gesture.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8637) Move VPE to Eclipse 3.7
by Yahor Radtsevich (JIRA)
Move VPE to Eclipse 3.7
-----------------------
Key: JBIDE-8637
URL: https://issues.jboss.org/browse/JBIDE-8637
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Visual Page Editor core
Affects Versions: 3.3.0.M1
Reporter: Yahor Radtsevich
Assignee: Yahor Radtsevich
Fix For: 3.3.0.M1
Issue to aggregate all efforts to move VPE to Eclipse 3.7.
What needs to be done (on all supported systems):
# Run VPE on Eclipse 3.7
# Make VPE build to be green on Eclipse 3.7
# Test VPE compatibility with Eclipse 3.7, move to a newer XULRunner if necessary
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8097) JBoss Tools Docbook editor is missing in JBT/JBDS
by Vlado Pakan (JIRA)
JBoss Tools Docbook editor is missing in JBT/JBDS
-------------------------------------------------
Key: JBIDE-8097
URL: https://issues.jboss.org/browse/JBIDE-8097
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.CR1
Environment: Linux 32bit, Java Sun 1.6
Reporter: Vlado Pakan
Assignee: Maxim Areshkau
Create new .xml file. It's not possible to open this file with JBoss Docbook editor.
There was context menu when right clicked on this .xml Open With > JBoss Tools Docbook and also when dialog with all available editors Open With > Other... contained JBoss Tools Docbook item.
It's not working neither in JBT 2011-01-11_22-57-02-H898 nor JBDS 201101071424N-H660-CR1.
It's working in JBDS 201012161657N-H584-CR1.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8049) *.inc content type JSP clash with PDT
by Sylvain Lecoy (JIRA)
*.inc content type JSP clash with PDT
-------------------------------------
Key: JBIDE-8049
URL: https://issues.jboss.org/browse/JBIDE-8049
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: Eclipse Helios
Windows 7 x64
Reporter: Sylvain Lecoy
I'm using eclipse 3.6.1, and among other things have a few j2ee plugins and php.
In the content types (under text) both the jsp type and php type both have ".inc" in the file association.
The workspace in which I work with php is a different one than the one I'm using for jsp (or java for that matter) and so in the php workbench I defaulted the php editor to handle .inc files.
When I open a .inc file in the editor though all of the text is one big error (all red underlined) and in the Problems view all of the errors are from type "JSP Problem", also when I view the properties of the file I get Type: File (JSP).
This bug originally reported on eclipse.org : http://www.eclipse.org/forums/index.php?t=msg&goto=647203&S=21af02ce175ae...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months