December 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-482) Installer should name the icons/launchers JBoss Developer Studio 2

by Max Rydahl Andersen (JIRA)

Installer should name the icons/launchers JBoss Developer Studio 2 ------------------------------------------------------------------ Key: JBDS-482 URL: https://jira.jboss.org/jira/browse/JBDS-482 Project: Developer Studio Issue Type: Task Affects Versions: 2.0.0.beta1 Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 2.0.0.cr1 The goal is to not blindly overwrite existing JBDS icons/launchers. Today we get a warning if the user already has an existing c:/jbdevstudio folder. That is fine and the user can change the install directory to c:/jbdevstudio2 if he wishes. But if he does he ends up with 2 JBoss Developer Studio launchers/uninstallers. Thus I suggest that our launcher should be named "JBoss Developer Studio <major version name>", i.e. "JBoss Developer Studio 2". Same goes for the uninstaller, it should not just be called "Uninstaller", it should be "Uninstall JBoss Developer Studio 2" I thought about using the full version name ("JBoss Developer Studio 2.0.0.GA") but what would then happen when the user installs 2.0.1.GA ....can we update the launcher ? If we can we should only do that if the user decided to install into the same directory. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-487) make ui tests run on a different UI thread (eg., using xvfb) so they can run locally without accidental user interaction

by Nick Boldt (JIRA)

make ui tests run on a different UI thread (eg., using xvfb) so they can run locally without accidental user interaction ------------------------------------------------------------------------------------------------------------------------ Key: JBDS-487 URL: https://jira.jboss.org/jira/browse/JBDS-487 Project: Developer Studio Issue Type: Sub-task Reporter: Nick Boldt Assignee: Nick Boldt -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3369) jboss server runtime build in jboss tools hasnt tracked late shift in JBOSS AS5 GA move of libraries to /common/lib

by William Woodman (JIRA)

jboss server runtime build in jboss tools hasnt tracked late shift in JBOSS AS5 GA move of libraries to /common/lib ------------------------------------------------------------------------------------------------------------------- Key: JBIDE-3369 URL: https://jira.jboss.org/jira/browse/JBIDE-3369 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Environment: JBOSS AS 5 GA and JBOSS tools CR1 - JBossTools-3.0.0.CR1-N200812051203-ALL-win32.zip Reporter: William Woodman Priority: Minor download eclipse, and install latest nightly build of jboss tools. download latest new jboss AS5.0.0.GA server from download site download SEAM 2.1.1CR1 (not required to show the problem really but is part of my code base). start eclipse and create a new jboss 5 server runtime and point at the jboss 5 AS install directories (in passing my pristine copies of jboss as5/server/default has no /lib directory which casues this to fail. You have to create an empty /lib under the server/default and then it works) howevver, what used to happen is that various hibernate jars would be included in the runtime library lists as well as <home>/client and <home>/lib directories. with the shift in AS5.0.0 GA to the use of the <home>/common/lib model, this doesnt seem to be tracked in the server runtime library lookups. Code used to work in JBOSS AS5.0.0CR2 and below which picked up the hibernate jars for validation etc, now dont compile under server runtime pointed at new jboss As5.0.0.GA build work around. Manually create a new user library - add the <home>/common/lib jars to that and include into the seam ejb project as an extra user library to get compiliation to complete properly. -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3408) [For Now] JBoss 5.0 servers must start off deploying to standard location

by Rob Stryker (JIRA)

[For Now] JBoss 5.0 servers must start off deploying to standard location ------------------------------------------------------------------------- Key: JBIDE-3408 URL: https://jira.jboss.org/jira/browse/JBIDE-3408 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Priority: Blocker Fix For: 3.0.0.cr1 Start / Stop / Deploy must work and output folder must be the standard /server/{conf}/deploy folder. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-3400) JBDS 2.0 Beta creates wrong

by Aaron Pestel (JIRA)

JBDS 2.0 Beta creates wrong ---------------------------- Key: JBIDE-3400 URL: https://jira.jboss.org/jira/browse/JBIDE-3400 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Environment: Version: 2.0.0.Beta1 Build id: R200810310645 Build date: 10/31/2008 06:53 - with SOA-P 4.3 Reporter: Aaron Pestel When using jBPM tooling to populate input/output tabs on ESB node properties view, the following XML is generated: ---------------------------------- <jbpmToEsbVars> <mapping jbpm="jbpmName1" esb="esbName1"></mapping> </jbpmToEsbVars> <returnVars> <mapping jbpm="jbpmName1" esb="esbName1"></mapping> </returnVars> ---------------------------------- That will not deploy on SOA-P 4.3 (or 4.2 I don't think). It needs to look like this: ---------------------------------- <bpmToEsbVars> <mapping bpm="jbpmName1" esb="esbName1" /> </bpmToEsbVars> <esbToBpmVars> <mapping esb="esbName1" bpm="jbpmName1" /> </esbToBpmVars> ---------------------------------- Note the "bpm" instead of "jbpm" and the "esbToBpmVars" instead of "returnVars" -- 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

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

15 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-517) Buttons for addig stand-alone Servers are disabled while installation.

by Anton Klimkovich (JIRA)

Buttons for addig stand-alone Servers are disabled while installation. ---------------------------------------------------------------------- Key: JBDS-517 URL: https://jira.jboss.org/jira/browse/JBDS-517 Project: Developer Studio Issue Type: Bug Components: installer Affects Versions: 2.0.0.cr1 Reporter: Anton Klimkovich Assignee: Denis Golovin EXECUTE: Run installer of jbds with EAP EXECUTE: On step 5 select No radiobutton ASSERT: Buttons for addig stand-alone Servers are Enabled EXECUTE: select Yes, and have it ready to use inDev Studio radiobutton ASSERT: Buttons for addig stand-alone Servers are Enabled FAILURE: Buttons for addig stand-alone Servers are disabled. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3322) Remove ancient and outdated snippets contributions in org.jboss.tools.jsf

by Max Rydahl Andersen (JIRA)

Remove ancient and outdated snippets contributions in org.jboss.tools.jsf ------------------------------------------------------------------------- Key: JBIDE-3322 URL: https://jira.jboss.org/jira/browse/JBIDE-3322 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF Affects Versions: 3.0.0.beta1 Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.0.0.cr1 I found that our jsf plugin had *alot* of these keys in its properties: panelForm_oracle_core_label=panelForm panelForm_oracle_core_desc=Syntax\:\n<af\:panelForm>\n</af\:panelForm>\nAttributes\:\nid, rows, maxColumns, width, labelWidth, fieldWidth, shortDesc, styleClass, onclick, ondblclick, onmousedown, onmouseup, onmouseover, onmousemove, onmouseout, onkeypress, onkeydown, onkeyup, inlineStyle, partialTriggers, rendered, binding, attributeChangeListener panelForm_oracle_core_content=<af\:panelForm>\n\t\n</af\:panelForm> And it turned out that there are some 100+ snippets defined which does nothing else but fill up the snippets view with something the tooling palette does anyway. I can't find any reference in docs or anywhere else where this is even mentioned or used thus I'm going to remove it since its outofdate and noisy code annoying to have just lying dead. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-3333) ESB project wizard and deployment doesn't work at all with WTP 3.03

by Denny Xu (JIRA)

ESB project wizard and deployment doesn't work at all with WTP 3.03 ------------------------------------------------------------------- Key: JBIDE-3333 URL: https://jira.jboss.org/jira/browse/JBIDE-3333 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.cr1 Reporter: Denny Xu Assignee: Denny Xu Priority: Blocker -- 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

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3390) add new Drools features to build and expose on update site

by Nick Boldt (JIRA)

add new Drools features to build and expose on update site ---------------------------------------------------------- Key: JBIDE-3390 URL: https://jira.jboss.org/jira/browse/JBIDE-3390 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Nick Boldt Assignee: Nick Boldt -- 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

2
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2008