July 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Moved: (JBIDE-553) Automatic refreshing of deployed app in app server

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-553?page=all ] Max Andersen moved RHDS-30 to JBIDE-553: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-553 (was: RHDS-30) > Automatic refreshing of deployed app in app server > -------------------------------------------------- > > Key: JBIDE-553 > URL: http://jira.jboss.com/jira/browse/JBIDE-553 > Project: JBoss Tools > Issue Type: Feature Request > Reporter: Michael Neale > > Nice to have. Seam gen produces a build.xml which is able to "restart" a web app by touching the web.xml (presumably when deployed in exploded mode). Would be nice if this could be part of a autosave build task when any pertinent java code is saved and autocompiled by eclipse (presumably also exploded deployment could be used). Obviously the aim is to not have any perceived deployment cycle when developing, simply refresh the browser/client and changes will be visible. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-554) [validation] validation for @Remove/@Destroy

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-554?page=all ] Max Andersen moved RHDS-4 to JBIDE-554: --------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-554 (was: RHDS-4) > [validation] validation for @Remove/@Destroy > -------------------------------------------- > > Key: JBIDE-554 > URL: http://jira.jboss.com/jira/browse/JBIDE-554 > Project: JBoss Tools > Issue Type: Feature Request > Reporter: Max Andersen > > from seam docs: > "All stateful session bean Seam components must have a method marked @Remove @Destroy to ensure that Seam will remove the stateful bean when the Seam context ends, and clean up any server-side state." -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-555) Typiing non US characters in the Visual editor or JSP code editor ( like Cyrilic characters ) the fail cannot be saved

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-555?page=all ] Max Andersen moved RHDS-38 to JBIDE-555: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-555 (was: RHDS-38) Affects Version/s: (was: ExadelStudioPro4) > Typiing non US characters in the Visual editor or JSP code editor ( like Cyrilic characters ) the fail cannot be saved > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-555 > URL: http://jira.jboss.com/jira/browse/JBIDE-555 > Project: JBoss Tools > Issue Type: Feature Request > Reporter: Naiden Gochev > Priority: Optional > > when i try to type a non US - Bulgarian ( Cirilic Charracters ) in a JSP (Visual or Editor area ) file and click CTRL+S (save) im using cp1251 encoding ( windows-1251) under Windows XP i get an error. > Will be nice if non unicode characters entered in visual editor are replaced with unicode characters in jsp source editor somethink like the feature of yours properties editor. > i was unable to atach the attachments ( i dont have idea why the applet started but not workign ) check the fallowing screenshots : > http://isy-dc.com/~naiden/exadel/cirilicJSP.JPG - this is the bug > http://isy-dc.com/~naiden/exadel/propEditor.JPG - example showing resource bundle file after typing cyrilic characters in properties 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-556) warn/show when an EL expression has non-existing variable

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-556?page=all ] Max Andersen moved RHDS-6 to JBIDE-556: --------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-556 (was: RHDS-6) > warn/show when an EL expression has non-existing variable > --------------------------------------------------------- > > Key: JBIDE-556 > URL: http://jira.jboss.com/jira/browse/JBIDE-556 > Project: JBoss Tools > Issue Type: Feature Request > Reporter: Max Andersen > > #{nonexistingvariable.name} could get a warn > #{existingvariable.nonexistingproperty} could also (maybe even an error) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-557) Xmodel classloading should "obey" osgi classloading

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-557?page=all ] Max Andersen moved RHDS-55 to JBIDE-557: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-557 (was: RHDS-55) > Xmodel classloading should "obey" osgi classloading > --------------------------------------------------- > > Key: JBIDE-557 > URL: http://jira.jboss.com/jira/browse/JBIDE-557 > Project: JBoss Tools > Issue Type: Task > Reporter: Max Andersen > > currently xmodel keeps a global cache of classes in ClassLoaderUtil and has a hidden binding to other plugins. > e..g it refers to jsf.web.ui via strings. That is a bad coupling; should be the other way around. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-542) Creating KickStart Projects - wrong default face-config dtd version on creation

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-542?page=all ] Max Andersen moved RHDS-57 to JBIDE-542: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-542 (was: RHDS-57) Affects Version/s: ExadelStudioPro4 > Creating KickStart Projects - wrong default face-config dtd version on creation > ------------------------------------------------------------------------------- > > Key: JBIDE-542 > URL: http://jira.jboss.com/jira/browse/JBIDE-542 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Environment: WindowsXP SP2 > Red Hat Enterprise Linux 5.0 > rhds-win32-1.0.0.ALPHA.jar > Red Hat Developer Studio > Version: 1.0.0 > Build id: 1.0.0 > Reporter: Aliaksey Nis > Priority: Trivial > > Create next KickStart projects: > 1. JSF 1.0 - Reference Implementation > 2. MyFaces 1.1.4 > For both projects open faces-config.jsp, switch to tab Source. > For JSF 1.0 dtd is "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">, > must be "http://java.sun.com/dtd/web-facesconfig_1_0.dtd"> > For MyFaces 1.1.4 dtd is "http://java.sun.com/dtd/web-facesconfig_1_0.dtd">, > must be "http://java.sun.com/dtd/web-facesconfig_1_1.dtd"> -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-543) Bad "Current Global Section" view in Red Hat Xml editor for Validation files on RHEL 5

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-543?page=all ] Max Andersen moved RHDS-56 to JBIDE-543: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-543 (was: RHDS-56) Fix Version/s: (was: 1.0.0.GA) Affects Version/s: ExadelStudioPro4 (was: 1.0.0.GA) > Bad "Current Global Section" view in Red Hat Xml editor for Validation files on RHEL 5 > --------------------------------------------------------------------------------------- > > Key: JBIDE-543 > URL: http://jira.jboss.com/jira/browse/JBIDE-543 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Environment: RHEL 5 > Reporter: Anton Klimkovich > Priority: Optional > Attachments: Current global Section.PNG > > > Bad "Current Global Section" view in Red Hat Xml editor for Validation files on RHEL 5 > Look at screenshoot -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-544) When registering project to JBoss server Progress bar shows "Register to Tomcat".

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-544?page=all ] Max Andersen moved RHDS-45 to JBIDE-544: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-544 (was: RHDS-45) Affects Version/s: ExadelStudioPro4 > When registering project to JBoss server Progress bar shows "Register to Tomcat". > --------------------------------------------------------------------------------- > > Key: JBIDE-544 > URL: http://jira.jboss.com/jira/browse/JBIDE-544 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Environment: Windows XP > RHDS build-333 > Reporter: Anton Klimkovich > Priority: Trivial > Attachments: Register JBoss.PNG > > > 1 Add JBoss server > 2 On Web Projects View select Create New JSF project > 3 Input name for project and click Next button > 4 In Target Server select JBoss server > 5 Click Finish > Look at Screenshoot. Progress bar shows "Register to Tomcat" instead of "Register to JBoss" -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-545) Exadel not using EFS properly - creates errors not finding linked resources with struts-config

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-545?page=all ] Max Andersen moved RHDS-43 to JBIDE-545: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-545 (was: RHDS-43) Affects Version/s: ExadelStudioPro4 (was: ExadelStudioPro4) > Exadel not using EFS properly - creates errors not finding linked resources with struts-config > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-545 > URL: http://jira.jboss.com/jira/browse/JBIDE-545 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Environment: Eclipse 3.2.1 > Reporter: Stek Finch > > ExadelStudio appears to bypass the Eclipse file system (at least when validating the struts-config) so as to not find link resources. > I setup /StrutsHello/WebContent/pages/greeting.jsp to be a linked resource > <link> > <name>WebContent/pages/greeting.jsp</name> > <type>1</type> > <location>C:/dev/tmp/greeting.jsp</location> > </link> > This file is referenced in my struts-config like this > <forward name="sayHello" path="/pages/greeting.jsp"/> > ExadelStudio marks that with an error "Forward sayHello of Action /greeting path attribute reference to non-existent page" > This is incocorrect, this file is there, albeit a linked resource. When I run the webapp in Eclipse+Exadel, the page does work as it should - so WST or something must be using the EFS properly unlike the part of Exadel validating the struts-config. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-546) Content Assist for JSP in jsf 1.1 is shown hints for jsf 1.2

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-546?page=all ] Max Andersen moved RHDS-59 to JBIDE-546: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-546 (was: RHDS-59) Affects Version/s: ExadelStudioPro4 > Content Assist for JSP in jsf 1.1 is shown hints for jsf 1.2 > ------------------------------------------------------------ > > Key: JBIDE-546 > URL: http://jira.jboss.com/jira/browse/JBIDE-546 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Reporter: Anton Klimkovich > Attachments: screenshort1.jpg > > > 1. Project on jsf 1.1 > 2. Content Assist for JSP in jsf 1.1 with facelets project is shown hints for jsf 1.2. See screenshot 1: footerClass and headerClass attributes for h:column is not from jsf 1.1, but from jsf 1.2 -- 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, 9 months

1
0
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 July 2007