[JBoss JIRA] Created: (JBIDE-6687) New XHTML Template/New XHTML Page mechanism inconcistencies
by Max Rydahl Andersen (JIRA)
New XHTML Template/New XHTML Page mechanism inconcistencies
-----------------------------------------------------------
Key: JBIDE-6687
URL: https://jira.jboss.org/browse/JBIDE-6687
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.M1
Reporter: Max Rydahl Andersen
Fix For: 3.2.0.M2
Tried the new template wizards (JBIDE-6131)
Works great, but the logic of the new XHTML Page which is using this are a bit weird.
1) Why don't we enable "Use XHTML Template" by default ?
2) Why is the file generated filled with some unknown template when I did not enable templates ? (shouldn't it be blank ?)
3) Is this coded via the builtin HTML wizard in Helios or duplication ? (it's good we have XHTML separated out from HTML ..makes it easier instead of tons of 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, 7 months
[JBoss JIRA] Created: (JBIDE-6475) [Bpel] Several class loader related unsafe places in JBoss Tools
by Brian Fitzpatrick (JIRA)
[Bpel] Several class loader related unsafe places in JBoss Tools
----------------------------------------------------------------
Key: JBIDE-6475
URL: https://jira.jboss.org/browse/JBIDE-6475
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.x, 3.1.x
Reporter: Brian Fitzpatrick
Assignee: Robert (Bob) Brodt
Fix For: 3.2.x
This originally came from JBIDE-6466
I find several unsafe places which are related with Thread.currentThread().getContextClassLoader() and Thread.currentThread().setContextClassLoader(). These places in code could have dramatic outcome during JBoss Tools normal work.
5) \jbosstools\trunk\bpel\plugins\org.eclipse.bpel.ui\src\org\eclipse\bpel\ui\util\BPELEditorUtil.java
- here is potential unsafe code commented;
--
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, 7 months
[JBoss JIRA] Created: (JBIDE-6360) Need to validate view-id locations in pages.xml
by Samuel Mendenhall (JIRA)
Need to validate view-id locations in pages.xml
-----------------------------------------------
Key: JBIDE-6360
URL: https://jira.jboss.org/browse/JBIDE-6360
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Affects Versions: 3.1.0.GA
Reporter: Samuel Mendenhall
Assignee: Alexey Kazakov
Priority: Minor
Currently one can put a wrong view-id in a navigation in pages.xml and JBoss Tools does not complain about it. It would be nice to have a compile time checking so that
<page view-id="/home.xhtml" action=
"#{identity.isLoggedIn}">
<navigation>
<rule if="#{identity.loggedIn}">
<redirect view-id="/man.xhtml"/>
</rule>
</navigation>
</page>
for example is flagged as /man.xhtml is spelled wrong, it should be /main.xhtml
--
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, 7 months