December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5224) Some Plugins and Features has wrong or missing License or Copyright text.

by Vlado Pakan (JIRA)

Some Plugins and Features has wrong or missing License or Copyright text. ------------------------------------------------------------------------- Key: JBIDE-5224 URL: https://jira.jboss.org/jira/browse/JBIDE-5224 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Vlado Pakan Some of the plugins and features has wrong or missing License and Copyright text. Details: Features ( Choose Menu Help > About > Installation Details > Features Tab. > License Button): JBoss Archive Tools - org.jboss.ide.eclipse.archives.feature JBoss AS Tools - org.jboss.ide.eclipse.as.feature Hibernate Tools - org.hibernate.eclispe.feature JBoss Tools Rich Faces - org.jboss.tools.richfaces.feature Installed software (Choose Menu Help > About > Installation Details > Installed Software Tab. > Properties Button): wrong or missing copyright and license text: Common tools for jBPM 3 and jBPM - org.jboss.tools.jbpm.common.feature.feature.group Common tools for jBPM 3 and jBPM 4 Sources - org.jboss.tools.jbpm.common.source.feature.feature.group Flow Language Common Tools Sources - org.jboss.tools.flow.common.source.feature.feature.group JBoss BPEL Editor Sources - org.jboss.tools.bpel.source.feature.feature.group JBoss Maven Integration Source - org.jboss.tools.maven.source.feature.feature.group JBoss Maven Seam Integration Source - org.jboss.tools.maven.seam.source.feature.feature.group JBoss WebServices Tools - org.jboss.tools.ws.feature.feature.group jBPM 4 Graphical Editor and Tools Sources - org.jboss.tools.flow.jpdl4.source.feature.feature.group jBPM Convert - org.jboss.tools.jbpm.convert.feature.feature.group Project Examples - org.jboss.tools.project.examples.feature.feature.group Smooks Tools - org.jboss.tools.smooks.feature.feature.group wrong or missing license text Flow Languages Common Tools - org.jboss.tools.flow.common.feature.feature.group JBoss BPEL Editor - org.jboss.tools.bpel.feature.feature.group JBoss BPEL Editor SDK - org.jboss.tools.bpel.sdk.feature.feature.group JBoss ESB Tools - org.jboss.tools.esb.feature.feature.group JBoss Portlet - org.jboss.tools.portlet.feature.feature.group jBPM 4 Graphical Editor and Tools - org.jboss.tools.flow.jpdl4.feature.feature.group jBPM 4 Tools SDK - org.jboss.tools.jbpm4.sdk.feature.feature.group JMX Console - org.jboss.tools.jmx.feature.feature.group JMX Console SDK - org.jboss.tools.jmx.sdk.feature.feature.group JMX Console Source - org.jboss.tools.jmx.source.feature.feature.group Struts Tools - org.jboss.tools.struts_feature.feature.group wrong or missing copyright text JBoss Profiler - org.jboss.tools.profiler.feature.feature.group jBPM jPDL Tools - org.jbpm.gd.jpdl.feature.feature.group -- 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 months

3
14
0 / 0

[JBoss JIRA] Created: (JBDS-1021) Richfaces libs are updated

by Svetlana mukhina (JIRA)

Richfaces libs are updated --------------------------- Key: JBDS-1021 URL: https://jira.jboss.org/jira/browse/JBDS-1021 Project: JBoss Developer Studio Issue Type: Task Components: Doc - VisualWebTools, Doc - RHDS GSG Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc check RF versions in guides -- 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 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5033) JUnit Tests fail on Hudson x86_64 platforms

by Denis Golovin (JIRA)

JUnit Tests fail on Hudson x86_64 platforms ------------------------------------------- Key: JBIDE-5033 URL: https://jira.jboss.org/jira/browse/JBIDE-5033 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Assignee: Nick Boldt Fix For: 3.1.0.M4, 3.1.0.CR1 It seems to work for me locally on x86_64 linux but throws exception on hudson [java] !STACK 0 > [java] org.eclipse.swt.SWTError: XPCOM error -2147467259 > [java] at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2068) > [java] at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:457) > [java] at org.eclipse.swt.browser.Browser.<init>(Browser.java:119) > [java] at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:87) > [java] at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135) > [java] at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$10.<init>(MozillaEditor.java:521) > [java] at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:521) > [java] at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:911) > [java] at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:210) > [java] at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:400) > [java] at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) > [java] at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662) > [java] at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462) > [java] at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) > [java] at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313) > [java] at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) > [java] at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) > [java] at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) > [java] at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) > [java] at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256) > [java] at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209) > [java] at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1608) > [java] at org.eclipse.ui.internal.PartStack.add(PartStack.java:499) > [java] at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103) > [java] at org.eclipse.ui.internal.PartStack.add(PartStack.java:485) > [java] at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112) > [java] at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) > [java] at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225) > [java] at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213) > [java] at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:778) > [java] at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:677) > [java] at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638) > [java] at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2854) > [java] at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762) > [java] at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754) > [java] at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705) > [java] at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > [java] at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701) > [java] at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685) > [java] at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2676) > [java] at org.jboss.tools.vpe.ui.test.VpeTest.openEditor(VpeTest.java:222) > [java] at org.jboss.tools.jsf.vpe.facelets.test.FaceletsComponentTest.performTestForFaceletComponent(FaceletsComponentTest.java:347) > [java] at org.jboss.tools.jsf.vpe.facelets.test.FaceletsComponentTest.testDebug(FaceletsComponentTest.java:54) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:585) > [java] at junit.framework.TestCase.runTest(TestCase.java:164) > [java] at junit.framework.TestCase.runBare(TestCase.java:130) > [java] at junit.framework.TestResult$1.protect(TestResult.java:106) > [java] at junit.framework.TestResult.runProtected(TestResult.java:124) > [java] at junit.framework.TestResult.run(TestResult.java:109) > [java] at junit.framework.TestCase.run(TestCase.java:120) > [java] at junit.framework.TestSuite.runTest(TestSuite.java:230) > [java] at junit.framework.TestSuite.run(TestSuite.java:225) > [java] at junit.framework.TestSuite.runTest(TestSuite.java:230) > [java] at junit.framework.TestSuite.run(TestSuite.java:225) > [java] at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) > [java] at junit.extensions.TestSetup$1.protect(TestSetup.java:21) > [java] at junit.framework.TestResult.runProtected(TestResult.java:124) > [java] at junit.extensions.TestSetup.run(TestSetup.java:25) > [java] at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > [java] at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) > [java] at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) > [java] at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > [java] at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) > [java] at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) > [java] at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) > [java] at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) > [java] at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) > [java] at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) > [java] at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) > [java] at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > [java] at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) > [java] at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > [java] at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > [java] at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) > [java] at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) > [java] at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) > [java] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) > [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) > [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:585) > [java] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) > [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) > [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311) > [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287) > [java] 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

16 years, 5 months

6
42
0 / 0

[JBoss JIRA] Created: (JBDS-868) Add XSLT tooling to JBDS

by Max Rydahl Andersen (JIRA)

Add XSLT tooling to JBDS ------------------------ Key: JBDS-868 URL: https://jira.jboss.org/jira/browse/JBDS-868 Project: JBoss Developer Studio Issue Type: Feature Request Components: integration Affects Versions: 3.0.0.M2 Reporter: Max Rydahl Andersen Priority: Critical Fix For: 3.0.0.M3 The XSLT tooling from Galileo should be included to assist the SOA runtimes that has xslt support. -- 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 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5308) New JBPM3 Project - sample process definition missing

by Dominik Pospisil (JIRA)

New JBPM3 Project - sample process definition missing ----------------------------------------------------- Key: JBIDE-5308 URL: https://jira.jboss.org/jira/browse/JBIDE-5308 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Environment: Linux x86_64 Reporter: Dominik Pospisil When creating new JBPM3 Project with sample process definiton, test case for process execution is created but the referenced process definition simple/processdefinition.xml is missing. The referenced file is not created at all. -- 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 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5529) jBPM GPD xml can't be open or gain focus when process xml is open

by Jiri Peterka (JIRA)

jBPM GPD xml can't be open or gain focus when process xml is open ----------------------------------------------------------------- Key: JBIDE-5529 URL: https://jira.jboss.org/jira/browse/JBIDE-5529 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.CR1 Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.GA 1. Create jBPM project and a jBPM process 2. Open process definition xml 3. Try to open gdp.xml by double clicking on in Project Explorer FAILURE: gdp.xml isn't open FAILURE2: If it's already open, it didn't gain focus -- 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 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5309) JBPM 3.2.6 runtime - missing lib/activation.jar

by Dominik Pospisil (JIRA)

JBPM 3.2.6 runtime - missing lib/activation.jar ----------------------------------------------- Key: JBIDE-5309 URL: https://jira.jboss.org/jira/browse/JBIDE-5309 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.M4 Environment: Linux x86_64 Reporter: Dominik Pospisil A JBPM3 project configured with JBPM 3.2.6 runtime can not be compiled, since the required lib/activation.jar is missing in JBPM 3.2.6 runtime. -- 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 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5530) Missing message element in jBPM code assistant of process definition

by Jiri Peterka (JIRA)

Missing message element in jBPM code assistant of process definition -------------------------------------------------------------------- Key: JBIDE-5530 URL: https://jira.jboss.org/jira/browse/JBIDE-5530 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.CR1 Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.GA 1. Have jBPM project and a default process 2. Switch to Source tab of default process definition to be able modify process xml directly CC works, but CC doesn't offer message element ( try to remove it and add it with using CC ) <state name="first"> <transition name="to_end" to="end2"> <action name="action" class="com.sample.action.MessageActionHandler"> <message>About to finish!</message> </action> </transition> </state> Note: Message isn't available in Design tab functionality as well -- 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 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5533) Default folder for new jBPM process definition

by Jiri Peterka (JIRA)

Default folder for new jBPM process definition ---------------------------------------------- Key: JBIDE-5533 URL: https://jira.jboss.org/jira/browse/JBIDE-5533 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jbpm Affects Versions: 3.1.0.CR1 Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.GA When creating new jBPM3 process definition with selected project name (root node), src/main/jpdl should be source folder by default -- 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 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5417) New Hibernate XML Mapping file (hbm.xml) - for files in "test" folder -> generate files into src folder

by Vitali Yemialyanchyk (JIRA)

New Hibernate XML Mapping file (hbm.xml) - for files in "test" folder -> generate files into src folder ------------------------------------------------------------------------------------------------------- Key: JBIDE-5417 URL: https://jira.jboss.org/jira/browse/JBIDE-5417 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Vitali Yemialyanchyk Assignee: Dmitry Geraskov Priority: Minor Fix For: 3.1.0.GA Attachments: screenshot-1.jpg "src" & "test" are the source folders for the project. -- 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 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5534) Republish does not work for ESB actions nor jboss-esb.xml

by Burr Sutter (JIRA)

Republish does not work for ESB actions nor jboss-esb.xml --------------------------------------------------------- Key: JBIDE-5534 URL: https://jira.jboss.org/jira/browse/JBIDE-5534 Project: Tools (JBoss Tools) Issue Type: Bug Environment: jbdevstudio-win32-3.0.0.v200912111227M-H41-RC1 with Java 1.6 on Windows Vista 64bit Reporter: Burr Sutter Attachments: Replublish_Issue.pdf I have a .esb archive created via JBoss Tools, deployed in SOA Platform 5 Beta 1 (ER5), changes to the action source or changes to the jboss-esb.xml are not picked up, not deployed, even though the actual files were updated in the deploy directory. The server was started via the "Servers" tab in JBDS. I have found that this works if I have started the server in debug mode. See attached PDF for the flow of events. -- 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 months

4
17
0 / 0

[JBoss JIRA] Created: (JBDS-648) Distribution should support updatesite or install into base eclipse

by Mark Diskin (JIRA)

Distribution should support updatesite or install into base eclipse -------------------------------------------------------------------- Key: JBDS-648 URL: https://jira.jboss.org/jira/browse/JBDS-648 Project: Developer Studio Issue Type: Feature Request Components: installer Environment: Windows Reporter: Mark Diskin The JBOSS tools is not not offered under development support options, but JBOSS Developer Studio is only provided as a standalone product. As a user of the base eclipse and Spring STS eclipse I'm used to be able to install JBOSS tools into those environments, but this is not covered by support for issues/patching. Could Developer Studio be provided as an update site offering or as a archive that could be installed into an existing eclipse environment. -- 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 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDS-628) WTP's 3.0.3 EAR lib support is broken, need 3.0.4 to work

by Max Rydahl Andersen (JIRA)

WTP's 3.0.3 EAR lib support is broken, need 3.0.4 to work --------------------------------------------------------- Key: JBDS-628 URL: https://jira.jboss.org/jira/browse/JBDS-628 Project: Developer Studio Issue Type: Task Components: 3rdParty Affects Versions: 2.0.0.GA Reporter: Max Rydahl Andersen Priority: Blocker Fix For: 2.0.0.GA https://bugs.eclipse.org/bugs/show_bug.cgi?id=255243 prevents users from having empty and clean manifest.mf files https://bugs.eclipse.org/bugs/show_bug.cgi?id=263918 is related but not as bad since there is a workaround. -- 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 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5401) java.lang.reflect.InvocationTargetException is occured when seam component is renaming after Save dialog confirmation.

by Anton Klimkovich (JIRA)

java.lang.reflect.InvocationTargetException is occured when seam component is renaming after Save dialog confirmation. ---------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5401 URL: https://jira.jboss.org/jira/browse/JBIDE-5401 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Reporter: Anton Klimkovich Assignee: Alexey Kazakov EXECUTE: Create Seam web project EXECUTE: components.xml EXECUTE: Rename <persistence:managed-persistence-context name="entityManager" to "entityManager23" EXECUTE: Open Seam Components View EXECUTE: Select Authenticator -> Rename Seam Component ASSERT: Save dialog appeares EXECUTE: Confirm Save action. EXECUTE: Rename component to entityManager35 EXECUTE: Press Next button FAILURE: java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:944) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.createChange(RefactoringWizard.java:583) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.computeUserInputSuccessorPage(RefactoringWizard.java:422) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.computeSuccessorPage(UserInputWizardPage.java:74) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.getNextPage(UserInputWizardPage.java:114) at org.jboss.tools.seam.ui.wizard.RenameComponentWizard$RenameComponentWizardPage.getNextPage(RenameComponentWizard.java:120) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:823) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:143) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:155) at org.jboss.tools.seam.ui.refactoring.SeamRefactorContributionFactory.invokeRenameComponentWizard(SeamRefactorContributionFactory.java:423) at org.jboss.tools.seam.ui.views.actions.RenameComponentAction.run(RenameComponentAction.java:49) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) 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.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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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) Caused by: java.lang.NullPointerException at org.jboss.tools.seam.internal.core.refactoring.SeamRefactorSearcher.<init>(SeamRefactorSearcher.java:44) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor$SeamSearcher.<init>(SeamRenameProcessor.java:442) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.getSearcher(SeamRenameProcessor.java:79) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.renameComponent(SeamRenameProcessor.java:382) at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.checkFinalConditions(RenameComponentProcessor.java:63) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Root exception: java.lang.NullPointerException at org.jboss.tools.seam.internal.core.refactoring.SeamRefactorSearcher.<init>(SeamRefactorSearcher.java:44) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor$SeamSearcher.<init>(SeamRenameProcessor.java:442) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.getSearcher(SeamRenameProcessor.java:79) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.renameComponent(SeamRenameProcessor.java:382) at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.checkFinalConditions(RenameComponentProcessor.java:63) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-906) Demos update

by Svetlana mukhina (JIRA)

Demos update ------------ Key: JBDS-906 URL: https://jira.jboss.org/jira/browse/JBDS-906 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc It's necessary to look though all demos, try to follow the steps and update them if necessary. -- 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 months

2
13
0 / 0

[JBoss JIRA] Created: (JBIDE-4937) birt - Seam component always null with birt embed

by Gonzalez Adrian (JIRA)

birt - Seam component always null with birt embed ------------------------------------------------- Key: JBIDE-4937 URL: https://jira.jboss.org/jira/browse/JBIDE-4937 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt Reporter: Gonzalez Adrian I'm using a Seam component in birt report (from a scripted datasource). Seam component is in conversation (or even session scope - same result). When I try to access a Seam Component from a birt report and when I use embed mode(designType="embed"), Seam component is always null (I'm accessing seam component with Component.getInstance("sampleReportList", false);). When I use designType="run", or frameset everything works fine. Tthe issue is due to the session that isn't propagated in embed mode. UIDocument class creates a new URLConnection to call JBossBirtServlet without propagating session cookie JSESSIONID (or the session id parameter if session is propagated with url rewriting). JBossBirtServlet then calls birt engine, but in a new session context. So the scripted source in birt engine cannot get a reference to any object stored in the original session. -- 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 months

4
24
0 / 0

[JBoss JIRA] Created: (JBDS-934) Automatic value and wire binding implemented

by Svetlana mukhina (JIRA)

Automatic value and wire binding implemented --------------------------------------------- Key: JBDS-934 URL: https://jira.jboss.org/jira/browse/JBDS-934 Project: JBoss Developer Studio Issue Type: Task Components: Doc - Smooks Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc see what's new, find the related dev jira tickets -- 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 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5245) Create FreeMarker Template builder for generating XML messages (from an XML Sample)

by Tom Fennelly (JIRA)

Create FreeMarker Template builder for generating XML messages (from an XML Sample) ------------------------------------------------------------------------------------ Key: JBIDE-5245 URL: https://jira.jboss.org/jira/browse/JBIDE-5245 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.1.0.CR1 -- 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 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-3720) Add new server runtime lists additional servers.

by Aliaksey Nis (JIRA)

Add new server runtime lists additional servers. ------------------------------------------------ Key: JBIDE-3720 URL: https://jira.jboss.org/jira/browse/JBIDE-3720 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.GA Environment: WindowsXP SP2 JBoss Tools Version: 3.0.0.GA Build id: JBossTools-ALL-win32-3.0.0.GA-N200902020001-H1393 JRE 1.5_08 Reporter: Aliaksey Nis Priority: Minor JBoss Tools (installed on Eclipse + plugins) EXECUTE: Open Preferences > Server > Installed Runtimes. Press Add. Look at screenshot. Duplicated servers appears in list. -- 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 months

7
43
0 / 0

[JBoss JIRA] Created: (JBDS-1014) EAP 5 version not recognised

by Joshua Wulf (JIRA)

EAP 5 version not recognised ---------------------------- Key: JBDS-1014 URL: https://jira.jboss.org/jira/browse/JBDS-1014 Project: JBoss Developer Studio Issue Type: Bug Components: installer Affects Versions: 3.0.0.CR1 Environment: Mac OS X Reporter: Joshua Wulf Attachments: Picture 3.png During installation if EAP 5 is added as a server it produces an error message that "Version is not valid for selected Type". Versions available for EAP are 4.2 and 4.3. -- 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 months

3
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5470) Add "Add" button to the VPE templates for unknown tags preferences page.

by Denis Maliarevich (JIRA)

Add "Add" button to the VPE templates for unknown tags preferences page. ------------------------------------------------------------------------ Key: JBIDE-5470 URL: https://jira.jboss.org/jira/browse/JBIDE-5470 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.1.0.CR1 Reporter: Denis Maliarevich Assignee: Denis Maliarevich Priority: Minor Fix For: 3.1.0.GA Attachments: VPE Templates Preferences Page.png "Add" button should be added to existed "Edit" and "Remove" buttons. Now it's possible to add new template for unknown tags only via VPE context menu. Having all three buttons on the one page is very convenient. Also "Global EL Expressions" preferences page has such a behavior. -- 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 months

2
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5364) Make namespace prefix consistent

by Tom Fennelly (JIRA)

Make namespace prefix consistent -------------------------------- Key: JBIDE-5364 URL: https://jira.jboss.org/jira/browse/JBIDE-5364 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Assignee: Xue Peng Fix For: 3.1.0.GA Seems like the namespace prefixes come from the EMF generate code, so I didn't modify them :) At present, they tend to include schema version numbers etc as part of the prefix. Can we have them generated such that they are consistent with what existing Smooks users i.e. without version numbers etc. Some are already OK, but I'll list the ones (relevant to this release) I can think of anyway... - EDI - "edi" - CSV - "csv" - JSON - "json" - Javabean - "jb" - FreeMarker - "ftl" I think that's all that's relevant for this release :) -- 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 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5483) ConcurrentModificationException throws when open xhtml page

by Maxim Areshkau (JIRA)

ConcurrentModificationException throws when open xhtml page ----------------------------------------------------------- Key: JBIDE-5483 URL: https://jira.jboss.org/jira/browse/JBIDE-5483 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.GA Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.1.0.GA Attachments: concurentModification.log #1 copy page into web project https://jira.jboss.org/jira/secure/attachment/12325794/components.xhtml #2 try to open couple times from time to time I have ConcurentModificationException -- 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 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5432) Issue found while testing smooks example edi-with-import-to-java

by Brian Fitzpatrick (JIRA)

Issue found while testing smooks example edi-with-import-to-java ---------------------------------------------------------------- Key: JBIDE-5432 URL: https://jira.jboss.org/jira/browse/JBIDE-5432 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.1.0.GA While testing today, I ran into an issue testing the milyn-smooks-example-edi-with-import-to-java example from the Smooks examples. You can download Smooks from here: http://www.smooks.org/mediawiki/index.php?title=Downloads Grab Smooks v.1.2.2 "ALL", and it will include binaries, examples and so on. You can have maven create the eclipse projects and import them directly. In the root of the smooks-examples directory, type "mvn eclipse:eclipse". Then you can import each example individually. Do this and import the milyn-smooks-example-edi-with-import-to-java example. Using this example, when I specify the edi sample message file I get this error in the editor: "Check Reader Configuration. Error creating Input Model from Input Data. Error: "Error parsing EDI mapping model [file]. Target Profile(s) [org.milyn.profile.profile#default_profile]." And this in my console: 2009-12-09 09:04:23.276::INFO: Logging to STDERR via org.mortbay.log.StdErrLog java.lang.NullPointerException at org.jboss.tools.smooks.configuration.editors.ModelPanelCreator.markPropertyUI(ModelPanelCreator.java:179) at org.jboss.tools.smooks.configuration.editors.ModelPanelCreator.createModelPanel(ModelPanelCreator.java:160) at org.jboss.tools.smooks.configuration.editors.SmooksReaderFormPage.createReaderPanel(SmooksReaderFormPage.java:763) at org.jboss.tools.smooks.configuration.editors.SmooksReaderFormPage.initReaderConfigSection(SmooksReaderFormPage.java:440) at org.jboss.tools.smooks.configuration.editors.SmooksReaderFormPage.createReaderConfigSection(SmooksReaderFormPage.java:395) at org.jboss.tools.smooks.configuration.editors.SmooksReaderFormPage.createFormContent(SmooksReaderFormPage.java:210) at org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150) at org.jboss.tools.smooks.graphical.editors.SmooksProcessGraphicalEditor.createTaskPage(SmooksProcessGraphicalEditor.java:1008) at org.jboss.tools.smooks.graphical.editors.SmooksProcessGraphicalEditor$5.run(SmooksProcessGraphicalEditor.java:964) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:179) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4113) at org.jboss.tools.smooks.graphical.editors.SmooksProcessGraphicalEditor.showTaskControl(SmooksProcessGraphicalEditor.java:927) at org.jboss.tools.smooks.graphical.editors.SmooksProcessGraphicalEditor$2.selectionChanged(SmooksProcessGraphicalEditor.java:353) at org.eclipse.zest.core.viewers.GraphViewer$1.widgetSelected(GraphViewer.java:96) at org.eclipse.zest.core.widgets.Graph.fireWidgetSelectedEvent(Graph.java:723) at org.eclipse.zest.core.widgets.Graph.access$4(Graph.java:715) at org.eclipse.zest.core.widgets.Graph$DragSupport.mousePressed(Graph.java:682) at org.eclipse.draw2d.Figure.handleMousePressed(Figure.java:873) at org.eclipse.draw2d.SWTEventDispatcher.dispatchMousePressed(SWTEventDispatcher.java:214) at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseDown(LightweightSystem.java:513) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) 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.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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) 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) -- 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 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5564) Duplicate items of Child's type list when creating new features

by Jiri Peterka (JIRA)

Duplicate items of Child's type list when creating new features --------------------------------------------------------------- Key: JBIDE-5564 URL: https://jira.jboss.org/jira/browse/JBIDE-5564 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.CR2 Attachments: select-childs-type.png Steps: 1. Create Java Project 2. Create smooks configuration file 3. Click on Input Task 4. Select Input type : CSV 5. Input configuration : Binding 6. Add new feature FAILURE: Content of the list -- 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 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5379) Suport adding the CSV field names as the first record produced by a CSV template

by Tom Fennelly (JIRA)

Suport adding the CSV field names as the first record produced by a CSV template -------------------------------------------------------------------------------- Key: JBIDE-5379 URL: https://jira.jboss.org/jira/browse/JBIDE-5379 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.1.0.GA CSV messages often define their field set in the first record of the message e.g. Name,Address,Age Joe Blogs,France,21 Mary Murphy,Ireland, 30 Add a simple "Add Field Names to Message" checkbox in the CSV template creation 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

16 years, 5 months

2
15
0 / 0

[JBoss JIRA] Created: (JBDS-933) Seam components templates

by Svetlana mukhina (JIRA)

Seam components templates -------------------------- Key: JBDS-933 URL: https://jira.jboss.org/jira/browse/JBDS-933 Project: JBoss Developer Studio Issue Type: Task Components: Doc - Seam Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.1.0-doc Update templating section of Seam guide, see the linked tasks, what's new and wiki articles: http://docs.jboss.org/tools/whatsnew/vpe/vpe-news-3.1.0.M2.html - Templates http://www.jboss.org/community/docs/DOC-12834 -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-926) Maven WTP 3.1 Library Providers are added

by Svetlana mukhina (JIRA)

Maven WTP 3.1 Library Providers are added ------------------------------------------ Key: JBDS-926 URL: https://jira.jboss.org/jira/browse/JBDS-926 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc update the guides see the linked tasks and what's new http://docs.jboss.org/tools/whatsnew/maven/maven-news-1.0.0.M3.html - Maven WTP 3.1 Library Providers -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-798) "Map" / "Resource List" actions are added to root elements

by Svetlana mukhina (JIRA)

"Map" / "Resource List" actions are added to root elements ---------------------------------------------------------- Key: JBDS-798 URL: https://jira.jboss.org/jira/browse/JBDS-798 Project: Developer Studio Issue Type: Task Components: Doc - Smooks Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0 Check the screens, theymust be up-to-date -- 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, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBDS-935) Adding map or resource list

by Svetlana mukhina (JIRA)

Adding map or resource list --------------------------- Key: JBDS-935 URL: https://jira.jboss.org/jira/browse/JBDS-935 Project: JBoss Developer Studio Issue Type: Task Components: Doc - Smooks Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc see what's new and find the related dev jira for guide update http://docs.jboss.org/tools/whatsnew/smooks/smooks-news-1.1.0.M2.html -- 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, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4030) java.lang.NullPointerException when edit default Connection Profile

by Anton Klimkovich (JIRA)

java.lang.NullPointerException when edit default Connection Profile ------------------------------------------------------------------- Key: JBIDE-4030 URL: https://jira.jboss.org/jira/browse/JBIDE-4030 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich Attachments: exception.txt EXECUTE: Install JBDS. New workspace EXECUTE: New Seam Web Project EXECUTE: Press Edit button on Seam Facet wizard FAILURE: Drivers list is empty. EXECUTE: Press Test Connection FAILURE: Test connection failed EXECUTE: Press Ok button. FAILURE2: java.lang.NullPointerException at org.eclipse.datatools.connectivity.ui.wizards.ProfilePropertyPage.performOk(ProfilePropertyPage.java:114) log attached. -- 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, 6 months

6
12
0 / 0

[JBoss JIRA] Created: (JBIDE-2687) Exception during configuratiob

by Aliaksey Nis (JIRA)

Exception during configuratiob ------------------------------ Key: JBIDE-2687 URL: https://jira.jboss.org/jira/browse/JBIDE-2687 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Aliaksey Nis -- 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, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5291) Generalize the code used to handle source to target template mappings

by Tom Fennelly (JIRA)

Generalize the code used to handle source to target template mappings --------------------------------------------------------------------- Key: JBIDE-5291 URL: https://jira.jboss.org/jira/browse/JBIDE-5291 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1 I'm wondering can we generalize the editor parts that handle the mappings between the Java Mappings and the target templating model. I probably didn't lay out my thoughts clearly enough on this, but what I was hoping for was that the target model parts would be agnostic of target message format (CSV, XML etc) and the templating technology used - FreeMarker only now, but I've structured the templating API to allow us add other TemplateBuilder impls e.g. for XSLT. What I see at the moment in the editor is that when I attempt to make a mapping connection, I see the FreemarkerCSVNodeGraphicalModel and FreemarkerCSVContentGenerator editor model parts on the call stack. I may be reading the code incorrectly, but I would only expected to see totally generic editor parts at play here... imo, this mapping part of the process should be totally generic i.e. exactly the same, no matter what the target message format and templating tech. I know I might just be reading the code incorrectly and I don't really understand the EMF process, but I thought I should add this JIRA anyway so as to allow it be tracked ... if I'm talking rubbish, we can just reject this JIRA :) -- 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, 6 months

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-5289) Don't re-scan all ELs every time when user invokes class/method/field refactoring.

by Alexey Kazakov (JIRA)

Don't re-scan all ELs every time when user invokes class/method/field refactoring. ---------------------------------------------------------------------------------- Key: JBIDE-5289 URL: https://jira.jboss.org/jira/browse/JBIDE-5289 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.GA Use PageContextFactory.createContext().getELReference() to get EL references which could be cached. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5581) XML catalog not complete for JBossAS 6.0.0.M1

by Juergen Zimmermann (JIRA)

XML catalog not complete for JBossAS 6.0.0.M1 --------------------------------------------- Key: JBIDE-5581 URL: https://jira.jboss.org/jira/browse/JBIDE-5581 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Juergen Zimmermann JBossAS 6.0 supports JPA 2.0 which requires persistence_2_0.xsd. This schema file can be found in docs/schema and should be added to plugins\org.jboss.ide.eclipse.as.core_...jar within the subdirectory dtd. -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5510) Not show references on assembly page that is not possible for a specific project

by Max Rydahl Andersen (JIRA)

Not show references on assembly page that is not possible for a specific project -------------------------------------------------------------------------------- Key: JBIDE-5510 URL: https://jira.jboss.org/jira/browse/JBIDE-5510 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.1.0.GA Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.1.0.GA At least until we get to WTP 3.2 can we at least Warn or even remove the option for adding reference types that default WTP 3.2 module types does not support ? -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5560) Wrong version of smooks in configuration file

by Jiri Peterka (JIRA)

Wrong version of smooks in configuration file --------------------------------------------- Key: JBIDE-5560 URL: https://jira.jboss.org/jira/browse/JBIDE-5560 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.CR2 Attachments: smooks-version.png There is smooks platform version always 1.2 (disabled combo) even when using 1.1.x Steps to reproduce: 1. Create java project 2. Add Smooks 1.1 jars into Java Build Path 3. Create smooks configuration, see wrong version in options tab Additional question: 1. Why platform version is disabled? 2. Why can't I set version in creation 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

16 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4613) Do not load ConsoleConfiguration by default.

by Dmitry Geraskov (JIRA)

Do not load ConsoleConfiguration by default. -------------------------------------------- Key: JBIDE-4613 URL: https://jira.jboss.org/jira/browse/JBIDE-4613 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.1.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Critical Fix For: 3.1.0.M4 This should be done as completion proposal -- 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, 6 months

3
22
0 / 0

[JBoss JIRA] Created: (JBIDE-5570) Keep hibernate.properties for proper Seam/Hibernate integration

by Max Rydahl Andersen (JIRA)

Keep hibernate.properties for proper Seam/Hibernate integration --------------------------------------------------------------- Key: JBIDE-5570 URL: https://jira.jboss.org/jira/browse/JBIDE-5570 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Priority: Blocker Fix For: 3.1.0.CR1 >From JBIDE-4985: hibernate.properties file still need to get generated. the provider class and datasource and manager lookup class is needed to override what is stated in persistence.xml. Without them hibernate query console and critiera editor not work. Suggestion for cR1, continue to create hibernate.properties so things are still overridden and usable from ant. -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5561) Changed smooks configuration file name isn't reflected in editor

by Jiri Peterka (JIRA)

Changed smooks configuration file name isn't reflected in editor ---------------------------------------------------------------- Key: JBIDE-5561 URL: https://jira.jboss.org/jira/browse/JBIDE-5561 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.CR2 Steps: 1. Create smooks configuration file 2. Open it 3. Change the name FAILURE: Name isn't reflected in editor and there are some related errors after that (like when saving, etc.) -- 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, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5562) Strange smooks apply template message type selection

by Jiri Peterka (JIRA)

Strange smooks apply template message type selection ---------------------------------------------------- Key: JBIDE-5562 URL: https://jira.jboss.org/jira/browse/JBIDE-5562 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.CR2 Steps: 1. Have smoke configuration (Input task -> Java Mapping) 2. Click on Java Mapping -> Apply template Only selectable Message type is CSV. 1. Why only CSV can be selected? 2. If only one item is available, why to select? 3. Bad layout ( control is very strange ) 4. When clicked selection is thin inside thick original control -- 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, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4889) JBoss Tools server runtime responds as capable of providing libraries for portlet facets although it doesn't provide them

by Snjezana Peco (JIRA)

JBoss Tools server runtime responds as capable of providing libraries for portlet facets although it doesn't provide them ------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4889 URL: https://jira.jboss.org/jira/browse/JBIDE-4889 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M3 Reporter: Snjezana Peco Assignee: Rob Stryker The problem is in the ProjectRuntimeClasspathProvider.getClasspathEntries() method that returns libraries for every facet. For more details see http://www.jboss.org/community/wiki/PortletFacetLibraries -- 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, 6 months

3
16
0 / 0

[JBoss JIRA] Created: (JBDS-1007) Debugger does not "see" source by default

by Burr Sutter (JIRA)

Debugger does not "see" source by default ----------------------------------------- Key: JBDS-1007 URL: https://jira.jboss.org/jira/browse/JBDS-1007 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.CR1 Environment: Windows Vista 64-bit, Java 1.6, SOA Platform 5 Beta 1 Reporter: Burr Sutter Attachments: Debugger_Source_not_found.jpg, Edit_Source_Lookup_Path.jpg, MyEsbAction_source.jpg Add a break point to an ESB action does bring up the debugger perspective but the source is not found. Since I am editing the source in JBDS, I would think it can actually find the source. File - New - Project - ESB Project was how the project was constructed. The "test case" is defined here: http://community.jboss.org/wiki/SOA-P43WorkshopLabExamples Screenshots will be uploaded -- 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, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5498) CLONE -Unable to install JBT 3.1.0 GA with Sun 1.5 VM

by Denis Golovin (JIRA)

CLONE -Unable to install JBT 3.1.0 GA with Sun 1.5 VM ----------------------------------------------------- Key: JBIDE-5498 URL: https://jira.jboss.org/jira/browse/JBIDE-5498 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: Linux 32, 64 - Sun JDK 1.5 JBossTools-Update-3.1.0.v200912141523M-H176-RC1.zip Reporter: Jiri Peterka Assignee: Denis Golovin Priority: Blocker Fix For: 3.1.0.CR1 Installation of JBT 3.1.0 CR1 (from JBossTools-Update-3.1.0.v200912141523M-H176-RC1.zip) fails during installation. An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=). Problems downloading artifact: osgi.bundle,org.jboss.tools.flow.common.source,1.2.0.v200912080349. Unpacking fails because intermediate file is empty: /tmp/work8092962226498105926/p2.optimizers.incoming5401691401174022088.jar Problems downloading artifact: osgi.bundle,org.jboss.tools.flow.jpdl4.multipage.source,4.0.0.v200912080349. Unpacking fails because intermediate file is empty: /tmp/work3243820078070021101/p2.optimizers.incoming1825758312005536514.jar Problems downloading artifact: osgi.bundle,org.jboss.tools.flow.jpdl4.source,4.0.0.v200912080349. Unpacking fails because intermediate file is empty: /tmp/work8058464995872764607/p2.optimizers.incoming446867257197025303.jar Problems downloading artifact: osgi.bundle,org.jboss.tools.jbpm.common.source,4.0.0.v200912080327. Unpacking fails because intermediate file is empty: /tmp/work6742735538962259552/p2.optimizers.incoming5740266345540352644.jar Problems downloading artifact: osgi.bundle,org.jbpm.gd.jpdl,3.2.0.v200912080327. Unpacking fails because intermediate file is empty: /tmp/work7385644026415956738/p2.optimizers.incoming1129437408548541227.jar Problems downloading artifact: osgi.bundle,org.jbpm.gd.jpdl.source,3.2.0.v200912080327. Unpacking fails because intermediate file is empty: /tmp/work2030628077411843211/p2.optimizers.incoming2462068408620598661.jar Problems downloading artifact: osgi.bundle,org.pi4soa.cdl.source,3.0.0.v200912051112. Unpacking fails because intermediate file is empty: /tmp/work9173114261359796592/p2.optimizers.incoming4302052898159483087.jar Problems downloading artifact: osgi.bundle,org.pi4soa.common.source,3.0.0.v200912051112. Unpacking fails because intermediate file is empty: /tmp/work6132404903016636406/p2.optimizers.incoming4200457352279481619.jar Problems downloading artifact: osgi.bundle,org.pi4soa.designer.source,3.0.0.v200912051112. Unpacking fails because intermediate file is empty: /tmp/work2594654746023668143/p2.optimizers.incoming6623622469384142388.jar Problems downloading artifact: osgi.bundle,org.pi4soa.scenario.designer.source,3.0.0.v200912051112. Unpacking fails because intermediate file is empty: /tmp/work5032642399328805725/p2.optimizers.incoming8942137205169905617.jar Problems downloading artifact: osgi.bundle,org.pi4soa.scenario.source,3.0.0.v200912051112. Unpacking fails because intermediate file is empty: /tmp/work2879216423901928026/p2.optimizers.incoming2894913774434443637.jar Problems downloading artifact: osgi.bundle,org.pi4soa.service.source,3.0.0.v200912051112. Unpacking fails because intermediate file is empty: /tmp/work1318869065539990110/p2.optimizers.incoming4326185775837742076.jar -- 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, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5586) Fix JstJspAllTests CA-related issue

by Victor Rubezhny (JIRA)

Fix JstJspAllTests CA-related issue ----------------------------------- Key: JBIDE-5586 URL: https://jira.jboss.org/jira/browse/JBIDE-5586 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 3.1.0.CR1 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Priority: Minor Fix For: 3.1.0.CR2 JstJspAllTests Error Message: Proposal #{} not found! Stack Trace: junit.framework.AssertionFailedError: Proposal #{} not found! at org.jboss.tools.jst.jsp.test.ca.ContentAssistantTestCase.checkProposals(ContentAssistantTestCase.java:89) at org.jboss.tools.jst.jsp.test.ca.JsfJspJbide1813Test.testJsfJspJbide1813Test(JsfJspJbide1813Test.java:33) -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5446) Hibernate Configuration 3.0 XML Editor - external update - exceptions

by Vitali Yemialyanchyk (JIRA)

Hibernate Configuration 3.0 XML Editor - external update - exceptions --------------------------------------------------------------------- Key: JBIDE-5446 URL: https://jira.jboss.org/jira/browse/JBIDE-5446 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Vitali Yemialyanchyk Assignee: Viacheslav Kabanovich Priority: Minor Fix For: 3.1.0.GA I have Parent.hbm.xml opened in Hibernate Configuration 3.0 XML Editor. I modify file outside and switch into Eclipse. I get exceptions: 1) org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/2deteteproj/src/Parent.hbm.xml'. at org.eclipse.core.internal.resources.File.checkSynchronized(File.java:104) at org.eclipse.core.internal.resources.File.getContentDescription(File.java:268) at org.eclipse.wst.sse.core.internal.modelhandler.ModelHandlerRegistry.getHandlerFor(ModelHandlerRegistry.java:129) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.calculateType(ModelManagerImpl.java:748) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._commonGetModel(ModelManagerImpl.java:507) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getModelForRead(ModelManagerImpl.java:1438) at org.eclipse.wst.xml.ui.internal.validation.MarkupValidator.validateV1File(MarkupValidator.java:993) at org.eclipse.wst.xml.ui.internal.validation.MarkupValidator.validate(MarkupValidator.java:911) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:292) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:258) at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:257) at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:199) at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:221) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor.run(DirtyRegionProcessor.java:641) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) 2) java.lang.NullPointerException at org.eclipse.wst.xml.ui.internal.validation.DelegatingSourceValidator.validate(DelegatingSourceValidator.java:206) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:292) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:258) at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:257) at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:199) at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:221) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor.run(DirtyRegionProcessor.java:641) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) then I click Parent.hbm.xml in Package Explorer - exceptions: 3) org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/2deteteproj/src/Parent.hbm.xml'. at org.eclipse.core.internal.resources.File.checkSynchronized(File.java:104) at org.eclipse.core.internal.resources.File.getContentDescription(File.java:268) at org.eclipse.core.internal.propertytester.FilePropertyTester.testContentType(FilePropertyTester.java:67) at org.eclipse.core.internal.propertytester.FilePropertyTester.test(FilePropertyTester.java:43) at org.eclipse.core.internal.expressions.Property.test(Property.java:58) at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68) at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:21) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:91) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) at org.eclipse.ui.internal.dialogs.RegistryPageContributor.failsEnablement(RegistryPageContributor.java:260) at org.eclipse.ui.internal.dialogs.RegistryPageContributor.isApplicableTo(RegistryPageContributor.java:209) at org.eclipse.ui.internal.dialogs.PropertyPageContributorManager.getApplicableContributors(PropertyPageContributorManager.java:199) at org.eclipse.ui.dialogs.PropertyDialogAction.hasPropertyPagesFor(PropertyDialogAction.java:104) at org.eclipse.ui.dialogs.PropertyDialogAction.isApplicableForSelection(PropertyDialogAction.java:146) at org.eclipse.ui.dialogs.PropertyDialogAction.isApplicableForSelection(PropertyDialogAction.java:126) at org.eclipse.jdt.ui.actions.OpenViewActionGroup.fillContextMenu(OpenViewActionGroup.java:264) at org.eclipse.jdt.ui.actions.NavigateActionGroup.fillContextMenu(NavigateActionGroup.java:105) at org.eclipse.jdt.internal.ui.actions.CompositeActionGroup.fillContextMenu(CompositeActionGroup.java:72) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.fillContextMenu(PackageExplorerActionGroup.java:287) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.menuAboutToShow(PackageExplorerPart.java:780) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:338) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:469) at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:465) at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:491) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1008) at org.eclipse.swt.widgets.Control.WM_INITMENUPOPUP(Control.java:4270) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3974) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1578) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2010) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4589) at org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:254) at org.eclipse.swt.widgets.Display.runPopups(Display.java:3906) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3467) 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.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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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) -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5091) Support JSF2 Composition components packaged into the Web Application Root

by Denis Golovin (JIRA)

Support JSF2 Composition components packaged into the Web Application Root -------------------------------------------------------------------------- Key: JBIDE-5091 URL: https://jira.jboss.org/jira/browse/JBIDE-5091 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Fix For: 3.1.0.M4 VPE discovers components in resources folder of web root and renders them in visual part of editor -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5015) JSF 2.0 composition components support

by Maxim Areshkau (JIRA)

JSF 2.0 composition components support -------------------------------------- Key: JBIDE-5015 URL: https://jira.jboss.org/jira/browse/JBIDE-5015 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core, Visual Page Editor Templates Affects Versions: 3.1.0.M3 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Priority: Critical Fix For: 3.1.0.M4 VPE should support JSF 2.0 composition components. Description of composition components see here: http://www.ibm.com/developerworks/java/library/j-jsf2fu2/index.html?S_TAC... -- 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, 6 months

3
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5100) Support for jsf 2.0 attributes, for example <composite:attribute name="loginPrompt"/>;

by Maxim Areshkau (JIRA)

Support for jsf 2.0 attributes, for example <composite:attribute name="loginPrompt"/>; --------------------------------------------------------------------------------------- Key: JBIDE-5100 URL: https://jira.jboss.org/jira/browse/JBIDE-5100 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core, Visual Page Editor Templates Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.0.CR1 Support for jsf 2.0 attributes, for example <composite:attribute name="loginPrompt"/>; Create composite:attribute empty template. -- 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, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2700) Console view sometimes not showing AS console output

by Galder Zamarreno (JIRA)

Console view sometimes not showing AS console output ---------------------------------------------------- Key: JBIDE-2700 URL: https://jira.jboss.org/jira/browse/JBIDE-2700 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: Galder Zamarreno Attachments: Screenshot-JBoss AS - loadgenerator-LoadGenerator-config-ScenarioConfig.properties - JBoss Developer Studio .png If I open a JBDS workspace and I'm directly in the JBoss AS perspective with the console view opened and then, I start one of the servers, the console shows nothing as you can see from the screenshot. There's a bug somewhere there. -- 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, 6 months

7
24
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 December 2009