July 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-2577) <rich:panel> component invisible in VPE if "style" attribute has complex arguments

by Andrei Scherbovich (JIRA)

<rich:panel> component invisible in VPE if "style" attribute has complex arguments ---------------------------------------------------------------------------------- Key: JBIDE-2577 URL: https://jira.jboss.org/jira/browse/JBIDE-2577 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 3.0.0.alpha Reporter: Andrei Scherbovich Assignee: Maxim Areshkau <rich:panel> component invisible in VPE if "style" attribute has complex arguments Try to run TEST FILE ATTACHED on server. It works fine but in VPE I can't find <rich:panel> component. -- 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

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-1536) Strange selection of text inside <rich:panel> .

by Anton Klimkovich (JIRA)

Strange selection of text inside <rich:panel> . ----------------------------------------------- Key: JBIDE-1536 URL: http://jira.jboss.com/jira/browse/JBIDE-1536 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.0.1 Environment: WinXP JBossTools-200712181613-nightly Reporter: Anton Klimkovich Priority: Minor Attachments: panel2.xhtml, StrangeSelection1.PNG, StrangeSelection2.PNG Open attached test page on Visual/Source tab Try to select text in different panels. The result of selection will be also different. Look at screenshot. -- 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
16
0 / 0

[JBoss JIRA] Created: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.

by Mario Balaban (JIRA)

AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings. ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2050 URL: http://jira.jboss.com/jira/browse/JBIDE-2050 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.0.1 Environment: Linux 2.6.22-14-generic, Eclipse Europa Version: 3.3.2, JbossToolsPlugin 2.0.1GA-ALL linux, JbossAS 4.2.2.GA Reporter: Mario Balaban On the same machine I had to create 2 instances of JbossAS, one for testing and another for development. The instance used for testing is using the "default" configuration. The test (default) instance I am able to start and to stop correctly from the Eclipse IDE. The "devel" instance that is a copy of the "default" configuration but has different port bindings (modified jboss-service.xml by uncommenting the tag <mbean code="org.jboss.services.binding.ServiceBindingManager"..../> ) has problems when starting and stopping from eclipse IDE. In the console window of IDE I see " [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 15s:993ms" but the state of the server in the "Servers" window of the IDE is Starting... It remains "Starting..." till an OutOfMemory is visualized in the IDE. This error happens even when no applications are deployed to the deploy directory of the "devel" configuration. It seems that the problem is associated to different port bindings used by "devel" configuration. -- 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

5
15
0 / 0

[JBoss JIRA] Created: (JBDS-358) Screenshots

by Svetlana mukhina (JIRA)

Screenshots ------------ Key: JBDS-358 URL: http://jira.jboss.com/jira/browse/JBDS-358 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assigned To: Anatoly Fedosik Priority: Minor Fix For: 2.0.0.alpha Sometime screen name (title in guide) doesn't correspond its content, plz try to make titles more informative -- 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

2
10
0 / 0

[JBoss JIRA] Created: (JBIDE-816) Resource bundle completion don't work in template clients

by Adrian Mitev (JIRA)

Resource bundle completion don't work in template clients --------------------------------------------------------- Key: JBIDE-816 URL: http://jira.jboss.com/jira/browse/JBIDE-816 Project: JBoss Tools Issue Type: Bug Components: JSF Environment: rhds beta1, jdk 1.5_0.12, windows XP Reporter: Adrian Mitev I have facelets template page and template client page. If i define <f:loadBundle> in the template page i get code completion for the bundle in it, but i don't get it in the template client page. If i redefine the same <f:loadBundle> in the template client i get completion in it, but this means that i'll have the same component defined twice in the component tree. I guess that the template should be traversed too. -- 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

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1712) In JBDS 1.0 - jBPM deployment - to a local file - does not recognize $HOME

by Len DiMaggio (JIRA)

In JBDS 1.0 - jBPM deployment - to a local file - does not recognize $HOME -------------------------------------------------------------------------- Key: JBIDE-1712 URL: http://jira.jboss.com/jira/browse/JBIDE-1712 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 2.0.0.GA Environment: JBDS 1.0 RHEL5 Reporter: Len DiMaggio Attachments: Screenshot.png In JBDS 1.0 - jBPM deployment - to a local file - does not recognize $HOME See attached screen shot -- 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, 1 month

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-1552) Seeing some screen display corruption running JBDS 1.0 on RHEL5 - see attachments

by Len DiMaggio (JIRA)

Seeing some screen display corruption running JBDS 1.0 on RHEL5 - see attachments --------------------------------------------------------------------------------- Key: JBIDE-1552 URL: http://jira.jboss.com/jira/browse/JBIDE-1552 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 2.0.0.GA Environment: JBoss Developer Studio Build id: 1.0.0.GA RHEL5 Sun 1.5.0_13 JVM Reporter: Len DiMaggio Priority: Minor See the attached screenshots -- 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, 1 month

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-374) hotkey methods for project archiver description

by Svetlana mukhina (JIRA)

hotkey methods for project archiver description ----------------------------------------------- Key: JBDS-374 URL: http://jira.jboss.com/jira/browse/JBDS-374 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assigned To: OLga Chikvina Fix For: 2.0.0.alpha describe new hotkey methods for project archiver -- 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, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-386) ESB Editor is Extended

by Svetlana mukhina (JIRA)

ESB Editor is Extended ---------------------- Key: JBDS-386 URL: https://jira.jboss.org/jira/browse/JBDS-386 Project: Developer Studio Issue Type: Task Components: Doc - ESB Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.alpha Update the guide according to https://jira.jboss.org/jira/browse/JBIDE-2022 -- 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

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-2550) Preliminary support for JSF 2.0

by Juergen Zimmermann (JIRA)

Preliminary support for JSF 2.0 ------------------------------- Key: JBIDE-2550 URL: https://jira.jboss.org/jira/browse/JBIDE-2550 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 3.0.0.alpha Reporter: Juergen Zimmermann JSF 2.0 EDR1 is available. I tested it with my up and found only one issue: https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=748 I tested the fix with Mojarra r5055 and it works fine. However, the VPE cannot support previewing. There are only a couple of changes: 1) There is also <h:head> and <h:body> instead of plain <head> and <body> 2) Images can be included this way: <h:graphicImage value="#{resource['hskaCore:myImg.jpg']}" /> The default implementation will look for resources in two locations and in the following order: a) /resources this location represents resources in the webapp itself and if present, must be in the root of the web application b) /META-INF/resources this location represents resources on the classpath -- 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

4
20
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2008