December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1035) IDE not displaying the s:link includePageParams attribute in code completion

by Tihomir Surdilovic (JIRA)

IDE not displaying the s:link includePageParams attribute in code completion ---------------------------------------------------------------------------- Key: JBDS-1035 URL: https://jira.jboss.org/jira/browse/JBDS-1035 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Reporter: Tihomir Surdilovic Since Seam 2.1.1.CR1 attribute "includePageParams" was added to the s:link component (see JIRA https://jira.jboss.org/jira/browse/JBSEAM-3609. This attribute however is not available in the IDE when doing code completion and displaying all attributes of this 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5580) OpenOns don't work for complex ELs.

by Alexey Kazakov (JIRA)

OpenOns don't work for complex ELs. ----------------------------------- Key: JBIDE-5580 URL: https://jira.jboss.org/jira/browse/JBIDE-5580 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.CR2 For example, create a page with #{(game.value == 'foo' and game.value == 'foo') ? game.value == 'foo' : false} where "game" is resolvable managed bean, seam context variable or CDI bean. OpenOns should be work. But now it doesn't. -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5579) NullPointerException in EclipseUIUtil.getActiveEditor().

by Victor Rubezhny (JIRA)

NullPointerException in EclipseUIUtil.getActiveEditor(). -------------------------------------------------------- Key: JBIDE-5579 URL: https://jira.jboss.org/jira/browse/JBIDE-5579 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.0.CR2 JUnit testing log contains NullPointerException: Stack Trace: java.lang.NullPointerException at org.jboss.tools.common.util.EclipseUIUtil.getActiveEditor(EclipseUIUtil.java:45) at org.jboss.tools.common.util.EclipseUIUtil.isOpenInActiveEditor(EclipseUIUtil.java:62) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:331) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:179) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:169) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.searchInCach(RefactorSearcher.java:191) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scanForJava(RefactorSearcher.java:174) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scanForJava(RefactorSearcher.java:135) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scanForJava(RefactorSearcher.java:133) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.findELReferences(RefactorSearcher.java:105) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.renameComponent(SeamRenameProcessor.java:386) at org.jboss.tools.seam.internal.core.refactoring.RenameSeamContextVariableProcessor.checkFinalConditions(RenameSeamContextVariableProcessor.java:71) at org.jboss.tools.seam.core.test.refactoring.SeamContextVariableRefactoringTest.renameContextVariable(SeamContextVariableRefactoringTest.java:47) at org.jboss.tools.seam.core.test.refactoring.SeamContextVariableRefactoringTest.testSeamContextVariable_Component_Rename(SeamContextVariableRefactoringTest.java:132) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) at org.eclipse.core.launcher.Main.main(Main.java:34) -- 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

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5573) Changes to JSP and XHTML files are not saved if the files are opened from linked WEB-ROOT folder

by Yahor Radtsevich (JIRA)

Changes to JSP and XHTML files are not saved if the files are opened from linked WEB-ROOT folder ------------------------------------------------------------------------------------------------ Key: JBIDE-5573 URL: https://jira.jboss.org/jira/browse/JBIDE-5573 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Yahor Radtsevich Priority: Critical Fix For: 3.1.0.CR2 STEPS TO REPRODUCE: 1. Click New Project->Web/Dynamic Web Project. 2. Enter a name for the project, unselect 'Use default Project contents' , enter a custom directory for the project contents not in the workspace. 3. Click Finish. 4. Select the created project in the Package Explorer, right click it and select Configure->Add JSF Capabilities. 5. Linked 'WEB-ROOT' folder is appeared in the project. 6. Create file index.jsp in the 'WEB-ROOT'. 7. Open the file with JBoss Tools JSP Editor and type anything into it. 8. Save the file and close the editor. 9. Reopen index.jsp. ACTUAL BEHAVIOR: All changes are lost. EXPECTED BEHAVIOR: The changes are saved. -- 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

14 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5540) New ESB Project Wizard - Late Error Message: "Please specify the project primary target runtime"

by Burr Sutter (JIRA)

New ESB Project Wizard - Late Error Message: "Please specify the project primary target runtime" ------------------------------------------------------------------------------------------------- Key: JBIDE-5540 URL: https://jira.jboss.org/jira/browse/JBIDE-5540 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Environment: jbdevstudio-win32-3.0.0.v200912111227M-H41-RC1 Reporter: Burr Sutter Attachments: New_ESB_Project_Target_Runtime_Issue.pdf The error message "Please specify the project primary target runtime" shows up late in the wizard flow, it should have shown up on the first screen that asked for the primary target runtime. If the Primary Target Runtime was going to be mandatory, it should have stopped me on the first screen. It could have been defaulted as well, since I had obviously been working with a particular server & runtime in my session. The attached PDF illustrates the workflow. -- 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

14 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-1025) JBDS 2.1 "Seam Booking Example - EAR mavenized" does not build from commandline

by Tihomir Surdilovic (JIRA)

JBDS 2.1 "Seam Booking Example - EAR mavenized" does not build from commandline ------------------------------------------------------------------------------- Key: JBDS-1025 URL: https://jira.jboss.org/jira/browse/JBDS-1025 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Reporter: Tihomir Surdilovic The parent pom.xml of the "Seam Booking Example - EAR mavenized" built-in example project does not build when running "mvn clean install" from the command-line. This is because the modules section should be defined properly to match the project structure: <modules> <module>../booking-ejb</module> <module>../booking</module> <module>../booking-ear</module> </modules> Also there is a typo for dependency: <dependency> <groupId>oorg.jboss.tools.seam.test</groupId> <artifactId>seamparent</artifactId> <version>${project.version}</version> <type>war</type> </dependency> "oorg" ? Not sure if this dependency should even be used here. -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-978) Option to avoid test project creation is added in "Seam web project" wizard.h

by Svetlana mukhina (JIRA)

Option to avoid test project creation is added in "Seam web project" wizard.h ----------------------------------------------------------------------------- Key: JBDS-978 URL: https://jira.jboss.org/jira/browse/JBDS-978 Project: JBoss Developer Studio Issue Type: Task Components: Doc - RHDS GSG, Doc - Seam Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc retake screens of the wizard -- 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

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5394) BPEL Plugin is not correctly initalizing variables

by Brad Maxwell (JIRA)

BPEL Plugin is not correctly initalizing variables -------------------------------------------------- Key: JBIDE-5394 URL: https://jira.jboss.org/jira/browse/JBIDE-5394 Project: Tools (JBoss Tools) Issue Type: Bug Environment: EAP 5 + Riftsaw 2.0 M2 b61 + JBoss Tools 1.0.0.v200912010817N-H2-RC1 Reporter: Brad Maxwell The BPEL plugin is not correctly initializing the variables. 1) Create a new Process 2) Add an Assign 3) Go to details 4) Click New 5) Select to copy from variable input/payload/inpuy 6) Select to copy to variable HelloWSPartnerLinkRequest.hello/name 7) Click away, it will prompt you to see if you want to create an Initializer 8) Click Yes The code generate is this below. Running this process causes Riftsaw to spit out this error: INFO [org.apache.ode.bpel.runtime.ASSIGN] (ODEServer-29) Assignment Fault: {http://docs.oasis-open.org/wsbpel/2.0/process/executable}selectionFailure,lineNo=80,faultExplanation=No results for expression: {OXPath10Expression name} bpel:copy> <bpel:from> <bpel:literal xml:space="preserve"><tns:hello xmlns:tns="http://jboss.com/examples/ws/Hello" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> </tns:hello> </bpel:literal> </bpel:from> <bpel:to variable="HelloWSPartnerLinkRequest" part="hello"></bpel:to> </bpel:copy> After days of trying various things, I then began comparing my example to the quick starts. I found the issue is 'name' is not being initialized. I hacked the code and added <name xmlns=""/> and it resolved the issue. <bpel:assign validate="no" name="Assign-Input2Request"> <bpel:copy> <bpel:from> <bpel:literal xml:space="preserve"> <tns:hello xmlns:tns="http://jboss.com/examples/ws/Hello" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <name xmlns=""/> </tns:hello> </bpel:literal> </bpel:from> <bpel:to part="hello" variable="HelloWSPartnerLinkRequest"></bpel:to> </bpel:copy> <bpel:copy> <bpel:from part="payload" variable="input"></bpel:from> <bpel:to>$HelloWSPartnerLinkRequest.hello/name</bpel:to> </bpel:copy> </bpel:assign> -- 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

14 years, 9 months

3
16
0 / 0

[JBoss JIRA] Created: (JBIDE-5517) BPEL Editor causing problems installing nightly build

by Jeff DeLong (JIRA)

BPEL Editor causing problems installing nightly build ----------------------------------------------------- Key: JBIDE-5517 URL: https://jira.jboss.org/jira/browse/JBIDE-5517 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Environment: JBossTools-Update-3.1.0.v200912170604N-H64-GA.zip on eclipse-jee-galileo-SR1-linux-gtk.tar.gz on RHEL5 Reporter: Jeff DeLong I installed eclipse-jee-galileo-SR1-linux-gtk.tar.gz and then used the local update archive to install JBossTools-Update-3.1.0.v200912170604N-H64-GA.zip eclipse.buildId=M20090917-0800 java.version=1.5.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product Error Thu Dec 17 10:35:17 MST 2009 An error occurred while collecting items to be installed eclipse.buildId=M20090917-0800 java.version=1.5.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product Error Thu Dec 17 10:35:17 MST 2009 Problems downloading artifact: osgi.bundle,org.eclipse.bpel.wsil.model,0.5.0.v200912120139. eclipse.buildId=M20090917-0800 java.version=1.5.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product eclipse.buildId=M20090917-0800 java.version=1.5.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product Error Thu Dec 17 10:35:17 MST 2009 Unpacking fails because intermediate file is empty: /tmp/work7874/p2.optimizers.incoming7872.jar and thee more similar errors. -- 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

14 years, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4402) Some input files use unchecked or unsafe operations. Recompile with -Xlint:unchecked for details.

by Nick Boldt (JIRA)

Some input files use unchecked or unsafe operations. Recompile with -Xlint:unchecked for details. ------------------------------------------------------------------------------------------------- Key: JBIDE-4402 URL: https://jira.jboss.org/jira/browse/JBIDE-4402 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 3.1.0.M1 Reporter: Nick Boldt http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-2.... [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. Suggest reviewing your sources w/ PDE API Tools and compiling locally to see what these unsafe/unchecked operations are. -- 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

14 years, 9 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2009