[JBoss JIRA] Created: (JBIDE-4304) Autoconfigure datasources from JBoss in DTP
by Max Rydahl Andersen (JIRA)
Autoconfigure datasources from JBoss in DTP
-------------------------------------------
Key: JBIDE-4304
URL: https://jira.jboss.org/jira/browse/JBIDE-4304
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Max Rydahl Andersen
Fix For: 3.1.0.M1, 3.1.0.M2
It would be great if DTP would automatically (or semi-automatically) could be configured to pickup the -ds.xml in a server runtime so users didn't have to set it up.
Not sure where in the ui we should have this, a couple of options come to my mind:
1) At AS Server/runtime creation have a checkbox saying "Configure -ds.xml automatically in DTP" and then we will keep DTP informed about the -ds.xml files for it to pick up
2) In DTP's ui have a way to add or maybe only import a -ds.xml and have it preconfigured.
The biggest issue will be to know which drivers we should be using for -ds.xml...
Things that should be considered:
If users changes the -ds.xml how does DTP learn about it ?
If the users remove the -ds.xml how does DTP react ?
If the users add .?
Needs investigation into if DTP have extensions point that allows for this kind of 'monitored' resources to update the connections; or if it is better to simply just have a way to "import" settings from ds.xml's (and then possibly have a manual refresh to pickup changes)
Or have both.
The usecase for this is to be able to use already existing and newly added -ds.xml files from within Eclipse with minimal setup, i.e. for Seam and Dali projects.
(I think this is a duplicate, but couldn't find it ;(
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Created: (JBIDE-6384) Clean up JstJspAllTests form tests that actuallytests functionality injected by client plugins
by Denis Golovin (JIRA)
Clean up JstJspAllTests form tests that actuallytests functionality injected by client plugins
----------------------------------------------------------------------------------------------
Key: JBIDE-6384
URL: https://jira.jboss.org/browse/JBIDE-6384
Project: Tools (JBoss Tools)
Issue Type: Task
Components: testing
Affects Versions: 3.2.0.M1
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 3.2.0.M1
Example:
JstJspJbide1759Test fails in tycho build because o.j.t.jsf plug-in is not declared as dependency of jst.jsp.tests plug-in.JstJspJbide1759Test tests actually functionality provided by o.j.t.jsf through extension points.
Tests that should be moved down along the hierarchy to jsf, seam or even vpe components are:
suite.addTestSuite(CAForUnclosedELTest.class);
suite.addTestSuite(CAForCompositeComponentTest.class);
suite.addTestSuite(MissingKBBuilderTest.class);
suite.addTestSuite(JsfJspJbide1807Test.class);
suite.addTestSuite(CAForIDTest.class);
suite.addTestSuite(JsfJspJbide1813Test.class);
suite.addTestSuite(JstJspJbide1759Test.class);
suite.addTestSuite(JsfJspJbide2437Test.class);
suite.addTestSuite(JsfJspJbide2016Test.class);
suite.addTestSuite(CAForELinStyleTest.class);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Created: (JBIDE-6301) Rename Source and Visutal Templates preferences
by Maxim Areshkau (JIRA)
Rename Source and Visutal Templates preferences
------------------------------------------------
Key: JBIDE-6301
URL: https://jira.jboss.org/browse/JBIDE-6301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.next
Reporter: Maxim Areshkau
Assignee: Maxim Areshkau
Fix For: 3.2.next
Now in exists two vpe preferences with simular name, but different sence.
We can specify source templates using JBoss Tools->Web->Editors->Visual Page Editor->Templates.
And we can specify visual templates via JBoss Tools->Web->Editors->Visual Page Editor->Templates Tab.
So better to rename JBoss Tools->Web->Editors->Visual Page Editor->Templates to Code Templates
and Visual Page Editor->Templates Tab to Visual Templates
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months