March 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-1946) Double click on <ui:composition> elements in VPE doesn't redirect to template page.

by Andrei Scherbovich (JIRA)

Double click on <ui:composition> elements in VPE doesn't redirect to template page. ----------------------------------------------------------------------------------- Key: JBIDE-1946 URL: http://jira.jboss.com/jira/browse/JBIDE-1946 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 2.1 Reporter: Andrei Scherbovich Assigned To: Maxim Areshkau Double click on <ui:composition> elements in VPE should redirect to template page. -- 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

18 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1258) Actually auto-complete resource bundle keys for org.jboss.seam.international.messages (and resource bundles in faces-confg)

by Gavin King (JIRA)

Actually auto-complete resource bundle keys for org.jboss.seam.international.messages (and resource bundles in faces-confg) --------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1258 URL: http://jira.jboss.com/jira/browse/JBIDE-1258 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King Max tells my that, today, when a resource bundle is defined using f:loadBundle, we can actually look inside the .properties file and find the keys. Well, thats awesome, except that f:loadBundle is semi-deprecated, and the following approaches are preferred: * For Seam projects, use the built-in component, and do #{messages.foo} to get "foo" from messages_xx.properties * For any JSF project, look at resource bundles defined in faces-config.xml By the way, at present it looks like the resource bundle stuff is a bit confused about the classpath, and thinks that if the bundle.properties file is in src/model, then the name of it is "model.bundle", when in fact it is just "bundle". This is a bug. -- 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

18 years, 2 months

5
17
0 / 0

[JBoss JIRA] Created: (JBDS-232) Update information about the palette

by Anatoly Fedosik (JIRA)

Update information about the palette ------------------------------------- Key: JBDS-232 URL: http://jira.jboss.com/jira/browse/JBDS-232 Project: Developer Studio Issue Type: Task Components: Doc - JSFTools Affects Versions: 1.0.0.GA Reporter: Anatoly Fedosik Assigned To: Yauheniya kryvinchanka Fix For: 1.0.1 1) Now most palette wizards have title. Update the screenshots if it is necessary. Related bug is: JBIDE-1471 2) 'Properties' menu Item is removed from Palette editor popup menu. Update text and screenshots if it is necessary. Related bug is: JBIDE-1472 -- 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

18 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (RHDS-339) Discuss the differences between WAR deployment and EAR deployment.

by Svetlana mukhina (JIRA)

Discuss the differences between WAR deployment and EAR deployment. ------------------------------------------------------------------ Key: RHDS-339 URL: http://jira.jboss.com/jira/browse/RHDS-339 Project: Red Hat Developer Studio Issue Type: Task Components: Doc - Seam Affects Versions: 1.0.0.CR1 Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Fix For: 1.1 Update the guide according to this remark: "Ch#3 needs some improvement: We need to discuss what are the differences between WAR deployment and EAR deployment. The WAR is for deployment on Tomcat + Embedded JBoss We need to discuss the directories inside the directories you have shown. We need to explain where are the xhtml files, java files, web.xml, etc etc. " Waiting for Max blog update where it will be written about it. -- 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

18 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1890) java.io.EOFException when make DnD button from Visual part to Source part of visual editor.

by Anton Klimkovich (JIRA)

java.io.EOFException when make DnD button from Visual part to Source part of visual editor. ------------------------------------------------------------------------------------------- Key: JBIDE-1890 URL: http://jira.jboss.com/jira/browse/JBIDE-1890 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1 Reporter: Anton Klimkovich Attachments: DnD from visulToSource.PNG EXECUTE: Create JSF1.2 kickstart project EXECUTE: Open inputUserName.jsp on Visual/Source tab EXECUTE: Make DnD button from Visual part to Source part of visual editor FAILURE: java.io.EOFException -- 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

18 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-1918) User unable to edit value attribute in VPE for <h:inputTextarea> tag and selection of this tag in vpe should select (highlight) this tag in source editor.

by Andrei Scherbovich (JIRA)

User unable to edit value attribute in VPE for <h:inputTextarea> tag and selection of this tag in vpe should select (highlight) this tag in source editor. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1918 URL: http://jira.jboss.com/jira/browse/JBIDE-1918 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1 Reporter: Andrei Scherbovich Assigned To: Sergey Dzmitrovich Priority: Minor User unable to edit value attribute in VPE for <h:inputTextarea> tag and selection of this tag in vpe should select (highlight) this tag in source editor. Steps: 1. EXECUTE: Try to edit value of <h:inputTextarea value="Lorem ipsum dolor sit amet..." /> tag in VPE. (jsp, xhtml files) 2. FAILURE: unable to edit 3. EXECUTE: Click on <h:inputTextarea value="Lorem ipsum dolor sit amet..." /> in VPE for the first time (focus on this component) 4. ASSERT: component selected (highlighted) in source editor 5. FAILURE: component is not selected (highlighted) in source editor -- 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

18 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-1947) Selection after resizing of <h:input*> in VPE broken in some case.

by Andrei Scherbovich (JIRA)

Selection after resizing of <h:input*> in VPE broken in some case. ------------------------------------------------------------------ Key: JBIDE-1947 URL: http://jira.jboss.com/jira/browse/JBIDE-1947 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1 Reporter: Andrei Scherbovich Assigned To: Sergey Dzmitrovich Priority: Minor Selection after resizing of <h:input*> in VPE broken in some case. If user tries to resize <h:input*> elements in VPE then selection breakes right after resizing. Steps: 1. EXECUTE: Select <h:inputText> element in VPE 2. ASSERT: Element is selected and highlighted in the source 3. EXECUTE: Resize <h:inputText> element (make huge resizement) 4. ASSERT: Element still selected and highlighted in source and visual editors 5. FAILURE: Selection breakes -- 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

18 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-1917) User unable to edit value attribute in VPE for <h:inputText> tag.

by Andrei Scherbovich (JIRA)

User unable to edit value attribute in VPE for <h:inputText> tag. ----------------------------------------------------------------- Key: JBIDE-1917 URL: http://jira.jboss.com/jira/browse/JBIDE-1917 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1 Reporter: Andrei Scherbovich Assigned To: Sergey Dzmitrovich Priority: Minor User unable to edit "value" attribute in VPE for <h:inputText> tag. -- 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

18 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1355) [unittest] ASClasspath test failure because of weird NPE on hudson

by Max Andersen (JIRA)

[unittest] ASClasspath test failure because of weird NPE on hudson ------------------------------------------------------------------ Key: JBIDE-1355 URL: http://jira.jboss.com/jira/browse/JBIDE-1355 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.CR1 Reporter: Max Andersen Fix For: 2.0.1 testClasspathAvailable fails - most likely because of this hidden stack trace inside the console output. Seems like the jvm type is unknown for some reason. [java] !ENTRY org.eclipse.wst.common.project.facet.core 4 0 2007-11-21 15:58:22.089 [java] !MESSAGE null [java] !STACK 0 [java] java.lang.NullPointerException [java] at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossServerRuntime.getVM(AbstractJBossServerRuntime.java:75) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadJREClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:178) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadClasspathEntries2(WebtoolsProjectJBossClasspathContainerInitializer.java:148) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.loadClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:141) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.WebtoolsProjectJBossClasspathContainerInitializer$WebtoolsProjectJBossClasspathContainer.getClasspathEntries(WebtoolsProjectJBossClasspathContainerInitializer.java:111) [java] at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider.getClasspathEntries(ProjectRuntimeClasspathProvider.java:69) [java] at org.eclipse.jst.common.project.facet.core.internal.RuntimeClasspathProvider.getClasspathEntries(RuntimeClasspathProvider.java:51) [java] at org.eclipse.jst.common.project.facet.core.ClasspathHelper.addClasspathEntries(ClasspathHelper.java:148) [java] at org.eclipse.jst.common.project.facet.JavaFacetUtils.resetClasspath(JavaFacetUtils.java:229) [java] at org.eclipse.jst.common.project.facet.JavaFacetRuntimeChangedDelegate.execute(JavaFacetRuntimeChangedDelegate.java:44) [java] at org.eclipse.wst.common.project.facet.core.events.internal.LegacyEventHandlerAdapter.handleEvent(LegacyEventHandlerAdapter.java:100) [java] at org.eclipse.wst.common.project.facet.core.events.internal.ListenerRegistry.notifyListeners(ListenerRegistry.java:76) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1088) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.setTargetedRuntimesInternal(FacetedProject.java:692) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$4(FacetedProject.java:613) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$3.run(FacetedProject.java:595) [java] at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) [java] at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.setTargetedRuntimes(FacetedProject.java:605) [java] at org.jboss.ide.eclipse.as.test.ASClasspathTest.setTargetRuntime(ASClasspathTest.java:141) [java] at org.jboss.ide.eclipse.as.test.ASClasspathTest.testClasspathAvailable(ASClasspathTest.java:98) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at junit.framework.TestCase.runTest(TestCase.java:164) -- 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

18 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1971) Missing entries in the build.properties file

by Snjezana Peco (JIRA)

Missing entries in the build.properties file --------------------------------------------- Key: JBIDE-1971 URL: http://jira.jboss.com/jira/browse/JBIDE-1971 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Snjezana Peco Many plugins have incorrectly set the build.properties file what can cause issues in a build. For instance, - the org.jboss.tools.jst.web plugin catalog, resources & Preferences.xml aren't included in the build.properties. The http://java.sun.com/xml/ns/javaee/ catalog entry is marked with an error in the XML Catalog preference page; JBossTools always downloads web_facesconfig_1_2.xsd from the Internet; OpenOn doesn't work for a JSF configuration file (see JBIDE-1771), etc. These issues occur only in a build, they don't occur in PDE Runtime. - the org.hibernate.eclipse. The branding files aren't included in the build.properties file. The hibernate feature is partially branded. The following is a list of plugins that have entries that aren't included in the build.properties (it is possible that some of the entries aren't required): org.hibernate.eclipse about.html about.ini about.mappings about.properties hibernate_log4j.properties hibernate_icon.gif welcome.xml org.hibernate.eclipse.console schema org.jboss.ide.archives.core schema org.jboss.ide.eclipse.as.ui schema org.jboss.ide.eclipse.as.ui.mbeans schema org.jboss.ide.eclipse.firstrun schema org.jboss.ide.eclipse.jdt.j2ee.xml.ui icons org.jboss.ide.eclipse.jdt.ui icons org.jboss.ide.eclipse.ui resources and icons org.jboss.tools.common.model resources and lib org.jboss.tools.common.model.ui resources, schema, templates org.jboss.tools.common.verification resources org.jboss.tools.esb.core resources org.jboss.tools.hibernate.xml resources org.jboss.tools.jsf Preferences.xml, meta, resources org.jboss.tools.jsf.doc.user all except META-INF org.jboss.tools.common.gef resources org.jboss.tools.common.kb resources org.jboss.tools.common.meta.ui resources org.jboss.tools.jsf.ui resources org.jboss.tools.jsf.verification resources org.jboss.tools.jst.jsp resources org.jboss.tools.jst.web catalog, resources and Preferences.xml org.jboss.tools.jst.web.tiles resources org.jboss.tools.jst.web.tiles.ui resources org.jboss.tools.jst.web.verification resources org.jboss.tools.seam.doc.user all except META-INF org.jboss.tools.seam.xml resources org.jboss.tools.struts Preferences.xml, meta, resources org.jboss.tools.struts.debug resources org.jboss.tools.struts.ui resources org.jboss.tools.struts.verification resources org.jboss.tools.struts.vpe.struts plugin.properties -- 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

18 years, 2 months

3
5
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 March 2008