[JBoss JIRA] Created: (JBIDE-8467) Remove debug message from RichFacesInplaceSelectTemplate.java
by Vlado Pakan (JIRA)
Remove debug message from RichFacesInplaceSelectTemplate.java
-------------------------------------------------------------
Key: JBIDE-8467
URL: https://issues.jboss.org/browse/JBIDE-8467
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.2.x
Reporter: Vlado Pakan
Assignee: Denis Maliarevich
Priority: Minor
/trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesInplaceSelectTemplate.java contains forgotten debug message in createSelectedList(...) method:
System.out.println(" dropDownListSizesStyle = " //$NON-NLS-1$
+ dropDownListSizesStyle);
Please remove it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 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, 10 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, 10 months
[JBoss JIRA] Created: (JBIDE-8342) top-down ws does not honour user selected JAX-WS spec version
by Lukas Jungmann (JIRA)
top-down ws does not honour user selected JAX-WS spec version
-------------------------------------------------------------
Key: JBIDE-8342
URL: https://issues.jboss.org/browse/JBIDE-8342
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.CR1
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
-register JBossAS 6 in the IDE
-create new dynamic web module (version 3.0)
-open new web service wizard
-set the type to top down, use some arbitrary WSDL, press next
-see that JAX-WS spec version is set to 2.0
-finish the wizard
-open generated *Service.java file
=> generated file contains among others following constructor:
public EchoWSService(WebServiceFeature ... features) {
super(WSDL_LOCATION, SERVICE, features);
}
problem is that the WebServiceFeature class has been introduced in JAX-WS 2.1 hence the mismatch of the "user" selected JAX-WS version in the wizard - 2.0 - and the version of sources generated by wsconsume - they're actually of version 2.2
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months