[JBoss JIRA] Created: (JBIDE-5509) Seam Portlet Project - datasource deployment not available
by Dominik Pospisil (JIRA)
Seam Portlet Project - datasource deployment not available
----------------------------------------------------------
Key: JBIDE-5509
URL: https://jira.jboss.org/jira/browse/JBIDE-5509
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal
Affects Versions: 3.1.0.CR1
Reporter: Dominik Pospisil
Project created using "New Dynamic web Project" wizard with "JBoss Seam Portlet Project v2.0" configuration does not expose associted datasource for deployment. As a result deployment of the project fails.
Steps to reproduce:
1) File -> New -> Dynamic Web Project
2) Select "JBoss Seam Portlet Project v2.0" configuration
3) Choose propper runtimes, finish.
4) Right click project, choose Run as -> Run on server
5) Run as resource deployment configuration dialog does not contain project datasource as expected.
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBIDE-5468) Server instance not allways created when creating new runtime
by Dominik Pospisil (JIRA)
Server instance not allways created when creating new runtime
-------------------------------------------------------------
Key: JBIDE-5468
URL: https://jira.jboss.org/jira/browse/JBIDE-5468
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR1
Reporter: Dominik Pospisil
Assignee: Rob Stryker
When creating new server runtime, associated server instance is not allways created as expected (even if create local server checkbox is selected).
Steps to reproduce:
1. Create new runtime (e.g. JBoss EAP 4.3 Runtime) with non-default name (e.g. JBoss EPP 4.3 Runtime)
2. Rename created server to non-default name (JBoss EPP 4.3 Runtime Server)
3. Now we have EPP runtime and EPP server
4. Create new runtime of the same type (JBoss EAP 4.3 Runtime)
5. Corresponding server is not created (JBoss EAP 4.3 Runtime Server)
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBIDE-4880) Open-on doesn't work for custom tags packed in jar file from taglib.xml
by Yura Zhishko (JIRA)
Open-on doesn't work for custom tags packed in jar file from taglib.xml
-----------------------------------------------------------------------
Key: JBIDE-4880
URL: https://jira.jboss.org/jira/browse/JBIDE-4880
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.M3
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
1) Import attached project
2) Open pages -> index.xhtml
3) Make Open-on, for example, on ma:paginator in VPE
ASSERT: mareshkau.taglib.xml is opened by Web XML editor.
4) Choose Source tab.
5) Make open-on for <source>/components/echo.xhtml</source>
ASSERT: The page components/echo.xhtml with tag definition is opened.
ASSERT FAILED: Open-on doesn't work at all.
P. S. We could open xml files from jars only by standard XML Editor. So open-on works fine in this situation. But after Step 3 XML file is opened by Web XML Editor, which shouldn't work with XML files from jars for now. So I think, that the root of problem lies near these conditions.
--
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
16 years, 4 months