August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6943) Template for New BlankRich Faces XHTML file has syntax error.

by Vlado Pakan (JIRA)

Template for New BlankRich Faces XHTML file has syntax error. ------------------------------------------------------------- Key: JBIDE-6943 URL: https://jira.jboss.org/browse/JBIDE-6943 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Environment: JBDS 4.0.0.v201008261621R-H420-M2 Reporter: Vlado Pakan Assignee: Alexey Kazakov Template for New BlankRich Faces XHTML file contains not closed tag rich:panel: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets"> <h:head></h:head> <body> <rich:panel> <f:facet name="header"> Write your own custom rich components with built-in AJAX support </f:facet> <h:outputText value="Panel Body" /> <rich:panel> <----------------------------------- please change it to </rich:panel> </body> </html> -- 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, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6298) BUG: when opens a file with Jboss Tools

by Luan Cestari (JIRA)

BUG: when opens a file with Jboss Tools --------------------------------------- Key: JBIDE-6298 URL: https://jira.jboss.org/browse/JBIDE-6298 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.GA Environment: Windows XP, Eclipse 3.5, CPU:EA4500, RAM memory:2GB, my eclipse uses the subclipse plugin Reporter: Luan Cestari Assignee: Alexey Kazakov After working some time ( e.g. 2 hours) suddenly when I try to open an file (xhtml or xml) occurs the error that make unable to edit the file using jbosstools. Using other tools I can. And only that specific file stay that way (or more than one if I keep using and if the error happen again). I wiped my log and then when the error happen this log appears: http://pastebin.com/scgktb3t . Here is the ss of the error message: http://imagebin.ca/view/AlApbbv.html . -- 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, 6 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6729) Externalize string wizard doesn't work when prop file is in subdirectory

by Krasimir Goutcev (JIRA)

Externalize string wizard doesn't work when prop file is in subdirectory ------------------------------------------------------------------------ Key: JBIDE-6729 URL: https://jira.jboss.org/browse/JBIDE-6729 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Environment: I have a property file in subtirectory and when select it in wizard, table with a content is empty Reporter: Krasimir Goutcev Assignee: Alexey Kazakov Priority: Minor -- 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, 6 months

6
17
0 / 0

[JBoss JIRA] Created: (JBIDE-4921) New Hibernate Reverse Engineering file wizard steps are empty

by Denis Golovin (JIRA)

New Hibernate Reverse Engineering file wizard steps are empty ------------------------------------------------------------- Key: JBIDE-4921 URL: https://jira.jboss.org/jira/browse/JBIDE-4921 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Priority: Minor 'Finish' actually creates the file but all that empty steps look weird :) -- 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, 6 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6827) JUnit Content Assist tests don't work with WTP 3.2.0

by Victor Rubezhny (JIRA)

JUnit Content Assist tests don't work with WTP 3.2.0 ---------------------------------------------------- Key: JBIDE-6827 URL: https://jira.jboss.org/browse/JBIDE-6827 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing, testing Affects Versions: 3.2.0.M2 Environment: Eclipse 3.6+WTP 3.2.0 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.2.0.Beta Content Assist Tests aren't able to work with WTP 3.2.0 because of its changes against the previous version. The CA Tests were proposed to do the following steps while testing: - Find the editors CA Processors from the editor's configuration using the reflection API; - Call computeProposals() method on each CA Processor found to collect proposals - Compare the proposals collected with some template depending on the test For WTP 3.2.0 it is not enough just to call the CA Processor's computeProposals() method to get it work. Some specific initialization things are to be performed before the call to computeProposals(). Without this initialization the following exception appears: !ENTRY org.eclipse.wst.sse.ui 4 4 2010-08-13 14:17:12.114 !MESSAGE null !STACK 0 java.lang.NullPointerException at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.isFirstPage(StructuredContentAssistProcessor.java:741) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:449) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:244) at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:126) at org.jboss.tools.jst.jsp.test.ca.JstJspJbide1585Test.testJstJspJbide1585(JstJspJbide1585Test.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:61) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116) 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:4012) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3631) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2416) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2380) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2229) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:504) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:497) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1406) at org.eclipse.equinox.launcher.Main.main(Main.java:1382) -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6922) Warning marker appears only when we click validate from Context Menu on jsf 2 page

by Maxim Areshkau (JIRA)

Warning marker appears only when we click validate from Context Menu on jsf 2 page ---------------------------------------------------------------------------------- Key: JBIDE-6922 URL: https://jira.jboss.org/browse/JBIDE-6922 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.Beta Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.0.Beta #1 create jsf2 resource page; #2 add some xmlns which refers to non valid resource folder xmlns:t="http://java.sun.com/jsf/composite/test" ASSERT warning message should appear, - ## FAIL #3 add some non existing jsf2 custom tag, <t:test /> ASSERT warning message should appear, - ## FAIL #4 CALL validate from Context Menu, warning will appears. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6939) Code completion for attribute values works only for EL.

by Alexey Kazakov (JIRA)

Code completion for attribute values works only for EL. ------------------------------------------------------- Key: JBIDE-6939 URL: https://jira.jboss.org/browse/JBIDE-6939 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.M2 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Priority: Blocker Fix For: 3.2.0.Beta For example <h:commandButton rendered="|"/> should suggest true/false. <rich:status for="|" .../> should suggest all the available IDs. And so on. -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6945) VPE "Externalize Stings Dialog" violates "Eclipse User Interface Guidelines" Guideline 5.3

by Denis Golovin (JIRA)

VPE "Externalize Stings Dialog" violates "Eclipse User Interface Guidelines" Guideline 5.3 ------------------------------------------------------------------------------------------ Key: JBIDE-6945 URL: https://jira.jboss.org/browse/JBIDE-6945 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Reporter: Denis Golovin Assignee: Denis Maliarevich Fix For: 3.2.0.Beta it is not right to say you have an error in dialog right after it is opened. See Eclipse User Interface Guidelines reference in JBIDE-1312 -- 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, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6949) Auto code completion for EL doesn't work when a user types "."

by Alexey Kazakov (JIRA)

Auto code completion for EL doesn't work when a user types "." -------------------------------------------------------------- Key: JBIDE-6949 URL: https://jira.jboss.org/browse/JBIDE-6949 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.M2 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.2.0.Beta 1. Create any JSF project. 2. Open any xhtml/jsp page. 3. Ctrl+Space in #{|} 4. Select some proposal 5. Type "." Code assist pop-up menu should appear. But now we have to press Ctrl+Space to invoke the code assist. -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5930) Quck fix for creating jsf2 custom page with element name when it not exist

by Maxim Areshkau (JIRA)

Quck fix for creating jsf2 custom page with element name when it not exist -------------------------------------------------------------------------- Key: JBIDE-5930 URL: https://jira.jboss.org/jira/browse/JBIDE-5930 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.next #1 if we specify on page xmlns:mar="http://java.sun.com/jsf/composite/mar #2 then enter mar:table, and table.xthml not exist in resources/mar folder it will be good provide quick fix for creating mar/table.xhtml with jsf2 element structure -- 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, 6 months

6
12
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2010