[JBoss JIRA] Created: (JBIDE-1719) Some bugs for <h:selectMany*> components.
by Andrei Scherbovich (JIRA)
Some bugs for <h:selectMany*> components.
-----------------------------------------
Key: JBIDE-1719
URL: http://jira.jboss.com/jira/browse/JBIDE-1719
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.GA
Reporter: Andrei Scherbovich
Assigned To: Maxim Areshkau
Attachments: 1.jpg
<h:selectManyCheckbox>
1) Attributes "dir", "disabled", "disabledClass", "enabledClass" don't work
<h:selectManyListBox> and <h:selectManyMenu>
1) Attributes "dir", "disabled", "disabledClass", "enabledClass", "styleClass", "style" don't work
2) Bad highlighting of selected in VPE elements of these components
<f:selectItem>
1) Attribute "escape" doesn't work
(SEE ATTACHMENT)
--
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, 8 months
[JBoss JIRA] Created: (JBIDE-1410) el resolution in visual editor
by Menashe (JIRA)
el resolution in visual editor
------------------------------
Key: JBIDE-1410
URL: http://jira.jboss.com/jira/browse/JBIDE-1410
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 2.0.0.CR1
Environment: seam2.0
eclipse 3.3.1.1
Reporter: Menashe
When el is used (as image/css source) the visual editor doesn't resolve it.
Here is what I mean (this is part of my template therefor it must be full path, since if it left as relative path it gets resolved based on the path of the page that is using the template and not of the actual template location.)
<img src="#{facesContext.externalContext.requestContextPath}/images/header.gif"/>
Visual editor should be able to figure out that #{facesContext.externalContext.requestContextPath} should be just dropped.
Since
<img src="/images/header.gif"/>
works fine in visual editor but not in the seam2 (unless contextpath is '/')
--
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, 8 months
[JBoss JIRA] Created: (JBIDE-3161) Equinox Transforms plugin for JBDS
by Rob Stryker (JIRA)
Equinox Transforms plugin for JBDS
----------------------------------
Key: JBIDE-3161
URL: https://jira.jboss.org/jira/browse/JBIDE-3161
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.0.0.beta1
Reporter: Rob Stryker
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.0.0.cr1
Develop a plugin which will be able to transform / invalidate other plugins in an installation. First iteration could be just a core with a hard-coded list of plugins / extension points which we want invalidated.
The goal here is to have all appropriate plugins in our installation, but disable the ones we do not want. Currently, JBDS removes the webtools jboss server-tools jar entirely, which makes the update site fail. What we need here is to have the webtools jboss server-tools jar IN hte installation, and loaded as a plugin, but have all of its extension points invalidated so it is effectively an empty non-contributing plugin.
org.eclipse.jst.server.generic.jboss_1.5.205.v200805140145 is the plugin we need invalidated. We need it's plugin.xml to be essentially empty with just base <plugin></plugin> tags.
--
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, 8 months