September 2008 - jbosstools-issues

[JBoss JIRA] Created: (RHDS-334) In GPD - right-click on a task node does not display options to add actions or tasks

by Len DiMaggio (JIRA)

In GPD - right-click on a task node does not display options to add actions or tasks ------------------------------------------------------------------------------------ Key: RHDS-334 URL: http://jira.jboss.com/jira/browse/RHDS-334 Project: Red Hat Developer Studio Issue Type: Bug Components: visualeditor Affects Versions: 1.0.0.CR1 Environment: Red Hat Developer Studio - Build id: 1.0.0.CR1 Designer plugin 3.1.0.sp1 jbpm-jpdl-suite-3.2.2 (for jBPM runtime) Reporter: Len DiMaggio Attachments: Screenshot_eclipse.png, Screenshot_RHDS.png Description of problem: In the GPD, right-clicking on a task does not display options to add actions or tasks in RHDS CR1. Contrast - this does work correctly with: Core and Designer plugin 3.0.13 jbpm-jpdl-suite-3.2.2 (for runtime) Eclipse Europa - Version: 3.3.1.1 Version-Release number of selected component (IR or RC #, component ver) Red Hat Developer Studio - Build id: 1.0.0.CR1 How reproducible: 100% Steps to Reproduce: 1. Access the websale example program - shipped with jbpm-jpdl-suite-3.2.2 2. Edit the processdefinition.xml file with the GPD 3. Right-click on a task node Actual results: See RHDS screenshot - attached Expected results: See Eclipse screenshot - attached Additional info: (e.g., stack trace) Attachments (e.g., server log) -- 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

17 years, 4 months

6
13
0 / 0

[JBoss JIRA] Created: (JBDS-427) Seam EARs are not correctly deployed on windows

by Jeronimo Ginzburg (JIRA)

Seam EARs are not correctly deployed on windows ----------------------------------------------- Key: JBDS-427 URL: https://jira.jboss.org/jira/browse/JBDS-427 Project: Developer Studio Issue Type: Bug Affects Versions: 1.1.0.GA Environment: Windows only (2000 & XP), Seam 2.0.2SP1, Sun JDK 1.5.0_16 Reporter: Jeronimo Ginzburg Assignee: Max Rydahl Andersen JBDS often doesn't include or update some files when deploying Seam EARs. This only happens on the JBDS 1.1.0GA win32 version. We couldn't reproduce this wrong behavior neither in RHEL version nor in JBoss Tools 2.1.2 over eclipse 3.3.2-win32 using WTP 2.0.3. At the same time the error is not *always* exactly reproducible. The missing or not updated files are not always the same. In one occasion a jar was deployed with 0 kb size. Following is a more detailed description of the steps performed in the customer environment and later reproduced in my machine with *more or less* similar problems. 1) Windows 2000 and the JBDS win32 1.1.0 GA distribution (in my case I installed Win 2000 SP4, but the customer has XP). I was using Sun JDK 1.5.0_16. 2) I generated a new Seam Web Project called "aProject" using Seam 2.0.2SP1 with the EAR packaging option. 3) I published the new blank application to the JBoss EAP 4.3 (included in the JBDS distribution) The first thing I noticed was that the EJB files (in this case Authenticator.class and others) WERE NOT COPIED. (This didn't happened at the customer) I tried stoping/restarting the AS/deleting the ear folder, redeploying the application several times. Finally the files were deployed. (Note that I hadn't changed the project settings for getting it done) 4) I removed jboss-seam.jar from the EJB manifest file. I added it as an external jar to the ejb project. (this is because of a reported bug) 5) I created a new Java project called "core". I included an external jar file ("model.jar") on the build path of this project and I checked "model.jar" to be exported to other dependant projects. I coded a reference to a model.jar class in the "core" project. Later I coded a reference to a class from core project inside Authenticator class login method. I made "aProject-ejb" and "aProject-ear" to depend on "core" (in the project references) In the J2EE module dependencies of core project I checked core.jar and model.jar I the build path of aProject-ejb I included core. I also checked it for export In the aProject-ear J2EE module dependencies I checked core.jar (model.jar is automatically included) (Note: Perhaps I'm forgetting to write any substep here. The result must be that the ear package must contain model.jar and core.jar) 5) I published the seam application to the AS. In this case all the files were copied but on the customer, sometimes core.jar or model.jar were not copied or copied with 0 kb size 6) I logged in. A class not found exception was thrown because I forgot to include core.jar and model.jar in the EJB Manifest file classpath. I added it to the manifest file. I saved the file. I published the application again. The deployed manifest file is not updated. I made some retries and nothing happened. Then I realized the manifest file date was about 30 minutes later than the local time of my machine. So I changed the time (+35 minutes) and then after republishing the file was updated. Errors: *** ERROR ***: Wed Sep 17 17:34:13 ART 2008 No IModelProvider exists for virtual component P/aProject-ear aProject-ear/EarContent/jboss-seam.jar of version: null (An exception stack trace is not available.) /////////////////////////////// (other error only in the case of the 0kb deployed jar): unable to assemble module java.util.zip.ZipException: ZIP file must have at least one entry at java.util.zip.ZipOutputStream.finish(Unknown Source) at java.util.zip.DeflaterOutputStream.close(Unknown Source) at java.util.zip.ZipOutputStream.close(Unknown Source) at org.jboss.ide.eclipse.as.core.server.xpl.ModulePackager.finished(ModulePackager.java:58) at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.packModuleIntoJar(JstPublisher.java:332) at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.fullPublish(JstPublisher.java:138) at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:112) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:132) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:835) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72) 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2494) File rich.tld openes in TLD Editor with unsaved marker.

by Anton Klimkovich (JIRA)

File rich.tld openes in TLD Editor with unsaved marker. ------------------------------------------------------- Key: JBIDE-2494 URL: http://jira.jboss.com/jira/browse/JBIDE-2494 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: Anton Klimkovich Assigned To: Alexey Kazakov Priority: Minor EXECUTE: Create Seam web project EXECUTE: Open rich.tld FAILURE: File is opened in TLD Editor with unsaved marker. -- 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

17 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2108) Double click on filtered file should open it for edit

by Galder Zamarreno (JIRA)

Double click on filtered file should open it for edit ----------------------------------------------------- Key: JBIDE-2108 URL: http://jira.jboss.com/jira/browse/JBIDE-2108 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.0.beta1 Reporter: Galder Zamarreno After creating a File Filter in the JBoss Server View, double clicking any files that match the filter should by default open them for edit. Currently, it does nothing so you have to right click and select "Edit File" Thoughts? -- 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

17 years, 4 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2627) Add "Server Locations" option to JBoss WTP Adapter to prevent JBoss contamination

by Francisco Jose Peredo Noguez (JIRA)

Add "Server Locations" option to JBoss WTP Adapter to prevent JBoss contamination --------------------------------------------------------------------------------- Key: JBIDE-2627 URL: https://jira.jboss.org/jira/browse/JBIDE-2627 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.2 Reporter: Francisco Jose Peredo Noguez When doing development of serveral independent applications over the JBoss AS, that JBoss AS installation get contaminated by those applications If I create workspaces1, and inside it I create dynamic webproject 1, and run it on JBoss, then I switch to workspace2, and create dynamic webproject 2, and run it on JBoss, since it is the same JBoss instance, both dynamic webproject 1 and dynamic webproject 2 will start (and there is no way, from inside eclipse to undeploy dynamic webproject 1 unless I go back to workspaces1 and undeploy it. But, if one is working with Tomcat, there is no problem, applications do not "contaminate" the shared Tomcat, why is that? well the Tomcat WTP Adapter has a configuration option enabled by default under "Server Location", that reads: "Use workspace metadata (does not modify Tomcat installation)". I would like to have an option like that for JBoss AS. -- 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

17 years, 4 months

5
20
0 / 0

[JBoss JIRA] Created: (JBIDE-2771) <html> teg doesn't close automaticly

by Andrei Scherbovich (JIRA)

<html> teg doesn't close automaticly ------------------------------------ Key: JBIDE-2771 URL: https://jira.jboss.org/jira/browse/JBIDE-2771 Project: Tools (JBoss Tools) Issue Type: Bug Components: XML Structured Editor Affects Versions: 3.0.0.alpha Reporter: Andrei Scherbovich Assignee: Maxim Areshkau Priority: Minor If we write manualy: <html> </ The tag </ should be closed automaticly by adding html>, so the result must be: <html> </html> But it doesn't work and nothing happens. -- 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

17 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2792) Add runtime support for portal

by Snjezana Peco (JIRA)

Add runtime support for portal ------------------------------- Key: JBIDE-2792 URL: https://jira.jboss.org/jira/browse/JBIDE-2792 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Portal Affects Versions: 3.0.0.beta1 Reporter: Snjezana Peco Assignee: Snjezana Peco Now, the portlet plugin uses libraries from the portletbridge distribution. Dependent libraries are copied from the RichFacesPortlet.war example. The portlet-api.jar library is still in the portlet.core plugin. -- 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

17 years, 4 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-1967) Editor do not recognize .jsf extension for the JSF files

by Antoine Herzog (JIRA)

Editor do not recognize .jsf extension for the JSF files -------------------------------------------------------- Key: JBIDE-1967 URL: http://jira.jboss.com/jira/browse/JBIDE-1967 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 2.0.1 Environment: Eclipse 3.3.2 and JB Tools 2.0.1 Reporter: Antoine Herzog Fix For: 2.1.0.beta1 in JBoss Tools : the .jsf files are recognized for global editor features. Every things works fine with .xhtml , but not with .jsf. Even if the file association is set. What does not work ? : With a .jsf file, I do not get the toolTips, the code completion, the drag and drop of new components... (but all these features works fine with .xhtml files) See the forum post. To check this problem : - I create a new file (simple new file), with .jsf extension - I copy into it the exact whole content of a .xhtml file that works well. => the file is set as a JSP (the icon is jsp, the default editor is JBoss Tool JSP editor). if I open it with "open with", and choose JBoss Tool HTML editor. idem : no code completion, no code validation etc... note : the icon of the editor window is "green with htm"... and not "blue with jsp". So it is really the JBoss Tool HTML editor. so, it seems there is something that prevent the editor to run with this file (".jsf") as a jsf file. The editor do not take into account the .jsf file, as a JSF... -- 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

17 years, 4 months

6
14
0 / 0

[JBoss JIRA] Created: (JBIDE-1058) Java Model Exception after calling code completion in scriplet.

by Anton Klimkovich (JIRA)

Java Model Exception after calling code completion in scriplet. --------------------------------------------------------------- Key: JBIDE-1058 URL: http://jira.jboss.com/jira/browse/JBIDE-1058 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta4 Reporter: Anton Klimkovich Attachments: Scriplet error.txt JSFKickStartProject Open hello.jsp Type <%=new java.applet.{call Code Completion} %> (look at screenshot) After callig RHDS hangs up and error appeares. Log with error attached. -- 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

17 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-570) Warning: Detected recursive attempt by part org.jboss.tools.common.model.ui.editor.EditorPartWrapper to create itself (this is probably, but not necessarily, a bug)

by Anton Klimkovich (JIRA)

Warning: Detected recursive attempt by part org.jboss.tools.common.model.ui.editor.EditorPartWrapper to create itself (this is probably, but not necessarily, a bug) -------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-570 URL: http://jira.jboss.com/jira/browse/JBIDE-570 Project: JBoss Tools Issue Type: Bug Components: JSF, Visual Page Editor Environment: WinXp SP2 JDK 1.6 build - 20070702_nightly Reporter: Anton Klimkovich Priority: Minor Create Struts-config.xml file in JSF project Log with error message attached. -- 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

17 years, 4 months

4
6
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 September 2008