[JBoss JIRA] Created: (JBIDE-2021) Visual Editor for pages.xml and *.pages.xml files
by Ashish Kulkarni (JIRA)
Visual Editor for pages.xml and *.pages.xml files
-------------------------------------------------
Key: JBIDE-2021
URL: http://jira.jboss.com/jira/browse/JBIDE-2021
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Environment: All
Reporter: Ashish Kulkarni
Currently there is no way to visually edit the pages.xml and *.pages.xml files generated by Seam Gen. As a result, we cannot add params and/or navigation/conditional navigation between pages visually.
This needs to be done manually and is a painful and error-prone process.
Could we have a visual editor for this please?
This should have the following functionality:
1. Add params based upon the source page's input parameters. This can be auto-scanned and then the user can be asked to select the parameters from a list.
2. Editing the navigation here should work in similar way as the faces-config.xml editor. However, in addition, this should also allow for seam's conditional navigation.
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-1788) Extend XML Catalog to support jboss.dtd, jboss-app.dtd, and jboss-web.xml
by Juergen Zimmermann (JIRA)
Extend XML Catalog to support jboss.dtd, jboss-app.dtd, and jboss-web.xml
-------------------------------------------------------------------------
Key: JBIDE-1788
URL: http://jira.jboss.com/jira/browse/JBIDE-1788
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml source editing
Affects Versions: 2.0.1
Environment: Eclipse 3.3.2RC2, WTP 2.0.2RC2, JBossTools nightly 20080201
Reporter: Juergen Zimmermann
When a project has jboss.xml, jboss-app.xml, or jboss-web.xml, then the XML validator of WTP shows warnings regarding a missing dtd, e.g. when the internet connection is broken.
Workaround is to extend the XML catalog (Preferences -> Web and XML -> XML catalog) so that there are entries like
* -//JBoss//DTD JBOSS 4.2//EN
* -//JBoss//DTD J2EE Application 4.2//EN
* -//JBoss//DTD Web Application 4.2//EN
These entries are mapped to a local DTD just like Hibernate Tools are already doing it with
* -//Hibernate/Hibernate Configuration DTD 3.0//EN
* -//Hibernate/Hibernate Mapping DTD 3.0//EN
* -//Hibernate/Hibernate Reverse Engineering DTD 3.0//EN
I'd appreciate to also have mappings for JBoss' XML files.
--
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, 11 months
[JBoss JIRA] Created: (JBDS-343) Project loaded into JBoss DevStudio can't be opened, causes NullPointerException in "EJB3ClasspathContainer.getClasspathEntries()"
by David Tonhofer (JIRA)
Project loaded into JBoss DevStudio can't be opened, causes NullPointerException in "EJB3ClasspathContainer.getClasspathEntries()"
----------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-343
URL: http://jira.jboss.com/jira/browse/JBDS-343
Project: Developer Studio
Issue Type: Bug
Affects Versions: 1.0.0.GA
Environment: Linux Fedora 8, 2.6.24.7-92.fc8
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)
Reporter: David Tonhofer
Assigned To: Max Rydahl Andersen
A project exported from subversion into JBoss DevStudio cannot be opened. The Eclipse log shows NullPointerException, either at startup or later. Here is the one at startup:
!ENTRY org.eclipse.core.jobs 4 2 2008-05-23 15:25:55.615
!MESSAGE An internal error occurred during: "Initializing Java Tooling".
!STACK 0
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.classpath.core.ejb3.EJB3ClasspathContainer.getClasspathEntries(EJB3ClasspathContainer.java:113)
at org.eclipse.jdt.internal.core.JavaModelManager.containerPutIfInitializingWithSameEntries(JavaModelManager.java:547)
at org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation(SetContainerOperation.java:49)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:720)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
....
Speculation on what went wrong: The .classpath of the project has a Windows-Nature Absolute Path (a Bad Thing in our mixed environment), somehow created on an Eclipse with manually loaded-in JBoss Tools:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src"/>
<classpathentry kind="src" path="test"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry combineaccessrules="false" kind="src" path="/jb_seam_demox-ejb"/>
<classpathentry kind="lib" path="D:/jboss-seam-2.0.0.GA/lib/testng.jar"/>
<classpathentry kind="con" path="org.jboss.ide.eclipse.as.classpath.core.ejb3.classpathContainer/JBoss 4.2 Server"/>
<classpathentry kind="output" path="bin"/>
</classpath>
--
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, 11 months