[JBoss JIRA] Created: (JBIDE-1967) Editor do not recognize .jsf extension for the JSF files
by Antoine Herzog (JIRA)
Editor do not recognize .jsf extension for the JSF files
--------------------------------------------------------
Key: JBIDE-1967
URL: http://jira.jboss.com/jira/browse/JBIDE-1967
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 2.0.1
Environment: Eclipse 3.3.2 and JB Tools 2.0.1
Reporter: Antoine Herzog
Fix For: 2.1.0.beta1
in JBoss Tools : the .jsf files are recognized for global editor features.
Every things works fine with .xhtml , but not with .jsf.
Even if the file association is set.
What does not work ? : With a .jsf file, I do not get the toolTips, the code completion, the drag and drop of new components...
(but all these features works fine with .xhtml files)
See the forum post.
To check this problem :
- I create a new file (simple new file), with .jsf extension
- I copy into it the exact whole content of a .xhtml file that works well.
=> the file is set as a JSP (the icon is jsp, the default editor is JBoss Tool JSP editor).
if I open it with "open with", and choose JBoss Tool HTML editor.
idem : no code completion, no code validation etc...
note : the icon of the editor window is "green with htm"... and not "blue with jsp". So it is really the JBoss Tool HTML editor.
so, it seems there is something that prevent the editor to run with this file (".jsf") as a jsf file.
The editor do not take into account the .jsf file, as a JSF...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months
[JBoss JIRA] Created: (JBIDE-1542) Empty "Driver Class" property for modified connection profiles
by Alexandros Karypidis (JIRA)
Empty "Driver Class" property for modified connection profiles
--------------------------------------------------------------
Key: JBIDE-1542
URL: http://jira.jboss.com/jira/browse/JBIDE-1542
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam, seam-gen
Affects Versions: 2.0.0.GA
Environment: 32-bit Ubuntu Linux 7.10, Eclipse 3.3.1.1 (M20071023-1652), WTP 2.0.1 (v200709110510), DTP 1.5.1
Reporter: Alexandros Karypidis
Priority: Minor
The Seam Web Project wizard complains that "Driver Class proberty is empty for selected 'x' connection profile" on the Seam Facet page and will not proceed. This occurs for perfectly valid connection profiles, when they have been modified since their creation. To reproduce:
1) Open the Database Development perspective
2) Create a connection profile. Type an incorrect JDBC connection URL.
3) Edit the connection profile. Fix the JDBC connection URL.
4) Start the Seam Web Project wizard and select the connection profile.
5) The wizard does not accept the connection and will not move forward from the "Seam Facet" page.
If you skip step 3 and not modify the connection profile, the problem does not occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
by Viacheslav Kabanovich (JIRA)
Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months