November 2012 - jbosstools-issues

[JBoss JIRA] (JBDS-2404) JBDS crashes at startup when a BPEL diagram was open upon previous shutdown

by Maurice de Chateau (JIRA)

Maurice de Chateau created JBDS-2404: ---------------------------------------- Summary: JBDS crashes at startup when a BPEL diagram was open upon previous shutdown Key: JBDS-2404 URL: https://issues.jboss.org/browse/JBDS-2404 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.0.GA, 5.0.1.GA Environment: Linux (Ubuntu 12.10, 64-bit), Oracle JVM (1.7.0_09, 64-bit) Reporter: Maurice de Chateau Assignee: Douglas Palmer In JBDS 5.0.x with ´SOA and Data Services Tooling´ installed, the IDE cannot be started up once it was previously closed with a BPEL diagram still opened. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
19
0 / 0

[JBoss JIRA] (JBIDE-11493) Create standalone Browsersim Eclipse based application

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-11493: ------------------------------------- Summary: Create standalone Browsersim Eclipse based application Key: JBIDE-11493 URL: https://issues.jboss.org/browse/JBIDE-11493 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.3.0.Beta3 Reporter: Denis Golovin Assignee: Yahor Radtsevich Wen I was looking for other Browser Simulator implementations I could not found andything downloadable for personal consumption :) would be good to provide eclipse based application for anyone to run. Because now to run it as standalone one need to know java and go with something like {code} java -cp /path/with/browsersim/jars;/path/to/platform/dependent/swt.jar org.jboss.tools.vpe.browsersim.ui.BrowserSim {code} In case of application it would need just a little: # Download archive # Unpack it # Run browsersim(.exe) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
25
0 / 0

[JBoss JIRA] (JBIDE-13159) gwt-kitchensink fails to deploy - class not found

by Martin Malina (JIRA)

Martin Malina created JBIDE-13159: ------------------------------------- Summary: gwt-kitchensink fails to deploy - class not found Key: JBIDE-13159 URL: https://issues.jboss.org/browse/JBIDE-13159 Project: Tools (JBoss Tools) Issue Type: Bug Components: GWT, maven Affects Versions: 4.0.0.CR1 Environment: JBDS 6.0.0.CR1a B133 JBT 4.0.0.CR1a B97 Reporter: Martin Malina Assignee: Denis Golovin Fix For: 4.0.0.CR1 When you try to deploy the gwt project from Central, it fails to deploy with the following error: {code} 15:27:18,698 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-gwt-webapp.war in deployment directory. To trigger deployment create a file called jboss-gwt-webapp.war.dodeploy 15:27:18,713 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jboss-gwt-webapp.war" 15:27:20,830 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for primary 15:27:20,978 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice. 15:27:20,979 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice. 15:27:21,021 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jboss-gwt-webapp.war 15:27:21,301 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-gwt-webapp.war 15:27:21,332 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71) 15:27:21,364 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-gwt-webapp.war#primary' 15:27:21,461 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final} 15:27:21,467 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH000412: Hibernate Core {4.0.1.Final} 15:27:21,469 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000206: hibernate.properties not found 15:27:21,473 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000021: Bytecode provider name : javassist 15:27:21,490 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [ name: primary ...] 15:27:21,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/Users/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/jboss-gwt-webapp.war/WEB-INF/classes/ at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] ... 3 more Caused by: java.lang.RuntimeException: JBAS011431: Could not load entity class 'org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30' with PersistenceUnitInfo.getClassLoader() at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:175) at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851) ... 9 more Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30 from [Module "deployment.jboss-gwt-webapp.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171) ... 11 more 15:27:21,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-gwt-webapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}} 15:27:21,742 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment jboss-gwt-webapp.war in 27ms 15:27:21,743 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service 15:27:21,745 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}}} {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
10
0 / 0

[JBoss JIRA] (JBDS-2358) GWT example generates warnings

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2358: ---------------------------------- Summary: GWT example generates warnings Key: JBDS-2358 URL: https://issues.jboss.org/browse/JBDS-2358 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 6.0.0.Alpha2 Environment: Version: 6.0.0.Alpha2 Build id: Alpha2-v20121004-2330-B40 Build date: 20121004-2330 Reporter: Len DiMaggio Assignee: Snjezana Peco Fix For: 6.0.0.CR1 The GWT project generates these warnings: No connection specified for project. No database-specific validation will be performed. jboss-gwt-webapp Overriding managed version 1.0.0.GA for validation-api pom.xml /jboss-gwt-webapp line 240 No bean is eligible for injection to the injection point [JSR-299 §5.2.1] KitchenSinkApp.java /jboss-gwt-webapp/src/main/java/org/jboss/tools/gwt/kitchensink/client/local line 41 Unnecessary @SuppressWarnings("unused") Resources.java /jboss-gwt-webapp/src/main/java/org/jboss/tools/gwt/kitchensink/util line 24 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
9
0 / 0

[JBoss JIRA] (JBIDE-13059) test the RichFaces Kitchensink archetype upgrade

by Brian Leathem (JIRA)

Brian Leathem created JBIDE-13059: ------------------------------------- Summary: test the RichFaces Kitchensink archetype upgrade Key: JBIDE-13059 URL: https://issues.jboss.org/browse/JBIDE-13059 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Reporter: Brian Leathem RichFaces kitchensink archetype 4.2.3.Final-1 is currently in a JBoss staging repository. The archetype will be promoted out of staging when JBoss tools QA is complete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

6
22
0 / 0

[JBoss JIRA] (JBIDE-12660) tycho-plugins/repository-utils mojo should support parameterized header logo

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12660: ---------------------------------- Summary: tycho-plugins/repository-utils mojo should support parameterized header logo Key: JBIDE-12660 URL: https://issues.jboss.org/browse/JBIDE-12660 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 4.0.0.Alpha2 In order to reuse your index page generator for other components who have their own branding (eg., modeshape) we need to be able to pass in a different URL for the header image, eg. http://www.jboss.org/dms/modeshape/images/modeshape-banner-1180px.png in place of https://www.jboss.org/dms/tools/images/tools-banner.png Note that images may not have the same dimensions (905w x 110h or 1280w x 110h). Wondering why the modeshape banner's filename contains "1180" but the file is in fact 1280px wide shall be left as an exercise for the reader. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
10
0 / 0

[JBoss JIRA] (JBIDE-13131) Beans XML 1.0 Editor throws XModelException: Cannot add new object to model

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-13131: ------------------------------------- Summary: Beans XML 1.0 Editor throws XModelException: Cannot add new object to model Key: JBIDE-13131 URL: https://issues.jboss.org/browse/JBIDE-13131 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 4.0.0.CR1 Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121118-2035-B111.jar Reporter: Daniel Azarov Assignee: Alexey Kazakov Test case: EXECUTE: 1. Create CDI project 2. Open beans.xml in Beans XML 1.0 Editor 3. Select New->Weld->Scan... context menu on beans.xml node in Tree tab 4. Select action "Add Include/Exclude" on Scan node, type name "include" then press button "Finish" 5. Select action "Add System Property" on node "include", type name and value then press button "Finish" 6. Try to Add System Property to System Property FAIL: {code} org.jboss.tools.common.model.XModelException: Cannot add new object to model. at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:182) at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:169) at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:143) at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.executeHandler(DefaultCreateHandler.java:49) at org.jboss.tools.common.meta.action.impl.XActionImpl.executeHandler(XActionImpl.java:65) at org.jboss.tools.common.model.ui.wizards.SpecialWizardSupportOneImpl.action(OneStepWizard.java:54) at org.jboss.tools.common.model.ui.wizards.standard.DefaultStandardWizard.performFinish(DefaultStandardWizard.java:39) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.tools.common.model.ui.wizards.special.DefaultSpecialWizard.execute(DefaultSpecialWizard.java:54) at org.jboss.tools.common.model.ui.wizards.OneStepWizard.execute(OneStepWizard.java:38) at org.jboss.tools.common.model.ui.action.XModelObjectAction.actionPerformed(XModelObjectAction.java:114) at org.jboss.tools.common.model.ui.action.XModelObjectAction$AL.widgetSelected(XModelObjectAction.java:131) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-13170) Validation marker remains in editor

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-13170: ----------------------------------------- Summary: Validation marker remains in editor Key: JBIDE-13170 URL: https://issues.jboss.org/browse/JBIDE-13170 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Affects Versions: 4.0.0.CR1 Reporter: Jaroslav Jankovič Assignee: Alexey Kazakov Fix For: 4.0.0.CR1, 4.1.x -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
10
0 / 0

[JBoss JIRA] (JBDS-2284) Investigate use of Findbugs 2.0.1 in JBoss Central & JBDS Extras sites

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2284: -------------------------------- Summary: Investigate use of Findbugs 2.0.1 in JBoss Central & JBDS Extras sites Key: JBDS-2284 URL: https://issues.jboss.org/browse/JBDS-2284 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, central Affects Versions: 6.0.0.Alpha1 Reporter: Nick Boldt Assignee: Len DiMaggio Fix For: 6.0.0.Beta1 Bits mirrored here: http://download.jboss.org/jbosstools/updates/requirements/findbugs/2.0.1.... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
21
0 / 0

[JBoss JIRA] (JBIDE-13124) Cannot install Findbugs - missing on the server

by Martin Malina (JIRA)

Martin Malina created JBIDE-13124: ------------------------------------- Summary: Cannot install Findbugs - missing on the server Key: JBIDE-13124 URL: https://issues.jboss.org/browse/JBIDE-13124 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 4.0.0.CR1 Environment: JBDS 6.0.0.CR1 B111 JBT 4.0.0.CR1 B78 Reporter: Martin Malina Assignee: Nick Boldt Fix For: 4.0.0.CR1 Findbugs cannot be installed from JBoss Central in both JBT and JBDS: {code} An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Artifact not found: http://findbugs.cs.umd.edu/eclipse-daily/plugins/edu.umd.cs.findbugs.plug.... http://findbugs.cs.umd.edu/eclipse-daily/plugins/edu.umd.cs.findbugs.plug... {code} I checked and it's really not there. But why is it taken from there? I though we had a mirror on dl.jb.org - see JBDS-2284 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2012