[JBoss JIRA] Created: (JBIDE-5143) ClassCastException when create f:selectItem inside h:selectManyListBox
by Yura Zhishko (JIRA)
ClassCastException when create f:selectItem inside h:selectManyListBox
----------------------------------------------------------------------
Key: JBIDE-5143
URL: https://jira.jboss.org/jira/browse/JBIDE-5143
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.1.0.M4
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
Priority: Minor
1) Open attached page with VPE.
2) Find any line that contains f:selectItem and comment it.
RESULT: During visual DOM building next exception occurs:
java.lang.ClassCastException: $Proxy26
at org.jboss.tools.jsf.vpe.jsf.template.selectitem.AbstractSelectItemTemplate.processOutputAttribute(AbstractSelectItemTemplate.java:99)
at org.jboss.tools.jsf.vpe.jsf.template.selectitem.AbstractOptionSelectItemTemplate.create(AbstractOptionSelectItemTemplate.java:67)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:489)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:689)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:601)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:235)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.rebuildDom(VpeVisualDomBuilder.java:263)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:987)
at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:661)
at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:489)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
--
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, 1 month
[JBoss JIRA] Created: (JBIDE-5642) Taglibs defined in JAR files as facelets *.taglib.xml are not recognized in Web Projects View in Tag Libraries folder.
by Oleg Varaksin (JIRA)
Taglibs defined in JAR files as facelets *.taglib.xml are not recognized in Web Projects View in Tag Libraries folder.
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-5642
URL: https://jira.jboss.org/jira/browse/JBIDE-5642
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.1.0.CR1
Environment: Eclipse 3.5 and higher, JBossTools 3.1.0.CR1, OS Windows XP and higher
Reporter: Oleg Varaksin
If we have some JAR files in classpath of web project which contain *.taglib.xml files (under META-INF) they will be not recognized by JBoss Tools. I have imported such JAR as described in the related issue https://jira.jboss.org/jira/browse/JBIDE-4213. TLDs have been well recognized (displayed under Tag Libraries folder), but *.taglib.xml files not. There are no chances to add them to the JBoss Tools Palette.
Note 1: *.taglib.xml files from external JARs don't have to be added in web.xml. That means, javax.faces.FACELETS_LIBRARIES is not needed in web.xml. JSF scans automatically META-INF folder of all JARs in classpath.
Note 2: *.taglib.xml files should be also recognized in JAR project itself if we implement JSF 2 custom components in this JAR project (which reside under META-INF/resources/...) and want to add xmlns namespaces from *.taglib.xml's in some *.xhtml files. At the moment it's not possible and there isn't code autocompletion.
This issue is very important for JSF 2.x.
--
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, 1 month
[JBoss JIRA] Created: (JBIDE-5984) JSF 2 composite components autocomplete works partailly
by Vadim Gerassimov (JIRA)
JSF 2 composite components autocomplete works partailly
-------------------------------------------------------
Key: JBIDE-5984
URL: https://jira.jboss.org/jira/browse/JBIDE-5984
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, jsp/jsf/xml source editing
Affects Versions: 3.1.0.CR2
Environment: Windows XP SP2, Eclipse 3.5 SR2, JBoss Tools 3.1.0 CR2 (installed: JBoss Maven integration, Context and Dependency Injection Tools, JBoss Tools RichFaces, XULRunner), Glassfish v3 runtime
Reporter: Vadim Gerassimov
Just installed JBoss Tools CR2 (JSF support, CDI support, maven integration). I played a little bit with JSF 2. JBoss Tools CR2 has partial composite component support - it sees composite components (autocomplete does work), but it does not see composite component attributes (i.e. attributes autocomplete does not work). Also inside composite component cc.attr. autocomplete does not work and IDE gives warning: "cc cannot be resolved". From response in http://in.relation.to/Bloggers/JBossTools31CR2CDILessTypingAndTheLastPolish such features should work.
Maybe I'm doing something wrong or something is not installed.
Regards,
Vadim
--
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, 1 month