[JBoss JIRA] Created: (JBIDE-989) Provide hyperlinking in console for property/page errors
by Max Andersen (JIRA)
Provide hyperlinking in console for property/page errors
--------------------------------------------------------
Key: JBIDE-989
URL: http://jira.jboss.com/jira/browse/JBIDE-989
Project: JBoss Tools
Issue Type: Feature Request
Components: JBoss Tools Core
Affects Versions: 2.0.0.Beta3, 2.0.0.Beta4
Reporter: Max Andersen
Fix For: 2.0.0.CR1
If a property is wrong an exception like this is shown in the console of JBoss AS:
Caused by: javax.el.PropertyNotFoundException: /anotherPing.xhtml @20,52 action="#{thirdPing.anotherPing}": Target Unreachable, identifier 'thirdPing' resolved to null
at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:70)
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77)
The class names and stacktrace locations are highlighted.
We should add support for linking /anotherPing.xhtml @20,52 (there might be multiple matches since the as can contain multiple projects so if we can't decide between them we need to show a list of the possible matches)
--
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
16 years, 8 months
[JBoss JIRA] Created: (RHDS-209) WebProjects view ends in a NullPointer
by Remo Liechti (JIRA)
WebProjects view ends in a NullPointer
--------------------------------------
Key: RHDS-209
URL: http://jira.jboss.com/jira/browse/RHDS-209
Project: Red Hat Developer Studio
Issue Type: Bug
Components: visualeditor
Affects Versions: 1.0.0.beta1
Environment: Windows Xp SP2 EN
MyEclipse 6.0
Reporter: Remo Liechti
Priority: Blocker
I installed the RedHat Editor into a MyEclipse 6.0 installation by downloading ONYL "RichFaces-VPE-win32-2.0.0.beta3.zip".
After restart of MyEclipse, the editor was installed correctly and I was able to open my JSF pages with it.
The Palette was also showing properly. So I tried to import a TLD, but no one was shown, so I wanted to take a look at the Web Project properties and opened therefor the Web Project View, which turned into a NullPointer.
How can I fix this? That way I'm not able to use the Palette with our TLD file which is very bad, so I have to write the code still manually...
--
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
16 years, 8 months
[JBoss JIRA] Created: (JBIDE-813) java.lang.NullPointerException after replace code in Editor with Local History
by Anton Klimkovich (JIRA)
java.lang.NullPointerException after replace code in Editor with Local History
------------------------------------------------------------------------------
Key: JBIDE-813
URL: http://jira.jboss.com/jira/browse/JBIDE-813
Project: JBoss Tools
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.Beta3
Reporter: Anton Klimkovich
JSFKickStart
Open inputUserName.jsp
In Editor right mouse click and select Format
Save and close Editor
Open Editor
Right mouse click and select Replace With -> Local History
Press Replace button
java.lang.NullPointerException
at org.eclipse.jst.jsp.core.internal.validation.JSPActionValidator.getTaglibPrefixes(JSPActionValidator.java:157)
at org.eclipse.jst.jsp.core.internal.validation.JSPActionValidator.performValidation(JSPActionValidator.java:215)
at org.eclipse.jst.jsp.core.internal.validation.JSPActionValidator.performValidation(JSPActionValidator.java:193)
at org.eclipse.jst.jsp.core.internal.validation.JSPBatchValidator.performValidation(JSPBatchValidator.java:377)
at org.eclipse.jst.jsp.core.internal.validation.JSPBatchValidator.validateFile(JSPBatchValidator.java:428)
at org.eclipse.jst.jsp.core.internal.validation.JSPBatchValidator.doValidate(JSPBatchValidator.java:190)
at org.eclipse.jst.jsp.core.internal.validation.JSPBatchValidator$1.run(JSPBatchValidator.java:452)
at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:720)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4466)
at org.eclipse.jst.jsp.core.internal.validation.JSPBatchValidator.validateInJob(JSPBatchValidator.java:460)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
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
16 years, 9 months
[JBoss JIRA] Created: (JBIDE-1026) Too many Seam validator jobs
by Max Andersen (JIRA)
Too many Seam validator jobs
----------------------------
Key: JBIDE-1026
URL: http://jira.jboss.com/jira/browse/JBIDE-1026
Project: JBoss Tools
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.Beta4
Reporter: Max Andersen
Fix For: 2.0.0.Beta3
Seem like Seam validator is taking its time to do its validation ...and for some reason multiple ones are started on the same project.
I'll attach screenshot showing it.
If the validation will take so long time then:
a) we should actaully report to the progresmonitor what it is currently working on
b) make sure we are actually synchronized correctly with the eclipse Job api (or whatever that the WTP validation framework requires)
--
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
16 years, 9 months
[JBoss JIRA] Created: (JBIDE-899) faces-config does not recognise redirect in navigation case
by Oleg Varaksin (JIRA)
faces-config does not recognise redirect in navigation case
-----------------------------------------------------------
Key: JBIDE-899
URL: http://jira.jboss.com/jira/browse/JBIDE-899
Project: JBoss Tools
Issue Type: Bug
Components: JSF
Affects Versions: 2.0.0.Beta1
Environment: Windows XP, JDK 1.4.10, JSF 1.1, Red Hat Developer Studio Beta 1
Reporter: Oleg Varaksin
My faces-config begins with
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config>
In the 'tree' or 'source' view I can add <redirect /> as follows
<navigation-rule>
<from-view-id>*</from-view-id>
<navigation-case>
<from-outcome>logout</from-outcome>
<to-view-id>/index.xhtml</to-view-id>
<redirect />
</navigation-case>
</navigation-rule>
But Red Hat Dev. Studio says then "0:0 Unallowed child redirect of navigation-case". 'Redirect' element should be allowed in the faces config !
Thanks.
Oleg Varaksin.
--
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
16 years, 9 months