[JBoss JIRA] Created: (JBIDE-1480) Functionality to enforce the use of IDs of selected JSF components
by Damian Harvey (JIRA)
Functionality to enforce the use of IDs of selected JSF components
------------------------------------------------------------------
Key: JBIDE-1480
URL: http://jira.jboss.com/jira/browse/JBIDE-1480
Project: JBoss Tools
Issue Type: Feature Request
Environment: All
Reporter: Damian Harvey
It would be very handy if the Jboss Tools (RHDS/JBDS) JSF tooling could enforce the use of IDs for selected JSF components. It is best practice to use IDs for most components but if you forget, are lazy or otherwise don't add them, then the rework can be daunting.
Ideally it would be an option on the Eclipse Prefs -> Jboss Tools -> Web -> JSF panel. The user could enter which components to include/exclude. If selected and a component had no ID, an error (or warning depending on the severity selected) would show up in the Eclipse problems view.
--
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
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-1277) Test's can't run when -ds.xml is not on the sourcepath
by Max Andersen (JIRA)
Test's can't run when -ds.xml is not on the sourcepath
------------------------------------------------------
Key: JBIDE-1277
URL: http://jira.jboss.com/jira/browse/JBIDE-1277
Project: JBoss Tools
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.Beta4
Reporter: Max Andersen
Assigned To: Denis Golovin
Priority: Blocker
Fix For: 2.0.0.CR1
the change from having -ds.xml in the classpath to a resources dir breaks the execution of unit tests since the -ds.xml is not found by the deployer.
Since the resources folder where intended for non-classpath relevant things I suggest we put the -ds.xml into the META-INF/ dir since they are special files being picked up by the jboss deployers.
I guess this affect both WAR and EAR.
Test case is simple:
EXECUTE: Create New Seam Project
EXECUTE: Create New Seam Action
EXECUTE:right click the generated test xml and execute TestNG
ASSERT: Green light! and not some error about datasource not being found.
--
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
15 years, 6 months
[JBoss JIRA] Created: (RHDS-334) In GPD - right-click on a task node does not display options to add actions or tasks
by Len DiMaggio (JIRA)
In GPD - right-click on a task node does not display options to add actions or tasks
------------------------------------------------------------------------------------
Key: RHDS-334
URL: http://jira.jboss.com/jira/browse/RHDS-334
Project: Red Hat Developer Studio
Issue Type: Bug
Components: visualeditor
Affects Versions: 1.0.0.CR1
Environment: Red Hat Developer Studio - Build id: 1.0.0.CR1
Designer plugin 3.1.0.sp1
jbpm-jpdl-suite-3.2.2 (for jBPM runtime)
Reporter: Len DiMaggio
Attachments: Screenshot_eclipse.png, Screenshot_RHDS.png
Description of problem:
In the GPD, right-clicking on a task does not display options to add actions or tasks in RHDS CR1.
Contrast - this does work correctly with:
Core and Designer plugin 3.0.13
jbpm-jpdl-suite-3.2.2 (for runtime)
Eclipse Europa - Version: 3.3.1.1
Version-Release number of selected component (IR or RC #, component ver)
Red Hat Developer Studio - Build id: 1.0.0.CR1
How reproducible:
100%
Steps to Reproduce:
1. Access the websale example program - shipped with jbpm-jpdl-suite-3.2.2
2. Edit the processdefinition.xml file with the GPD
3. Right-click on a task node
Actual results:
See RHDS screenshot - attached
Expected results:
See Eclipse screenshot - attached
Additional info: (e.g., stack trace)
Attachments (e.g., server log)
--
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
15 years, 6 months