August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1252) Update version in Splash.bmp to 4.0.1.M1

by Denis Golovin (JIRA)

Update version in Splash.bmp to 4.0.1.M1 ---------------------------------------- Key: JBDS-1252 URL: https://jira.jboss.org/browse/JBDS-1252 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: ui/branding Affects Versions: 4.0.0.M1 Reporter: Denis Golovin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
9
0 / 0

[JBoss JIRA] Updated: (JBIDE-6464) Running a SeamTest when multiple projects are open in the Eclipse workspace fails

by Alexey Kazakov (JIRA)

[ https://jira.jboss.org/browse/JBIDE-6464?page=com.atlassian.jira.plugin.s... ] Alexey Kazakov updated JBIDE-6464: ---------------------------------- Fix Version/s: 3.3.x (was: 3.2.x) > Running a SeamTest when multiple projects are open in the Eclipse workspace fails > --------------------------------------------------------------------------------- > > Key: JBIDE-6464 > URL: https://jira.jboss.org/browse/JBIDE-6464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam > Environment: XP, JBoss 5.1.0 GA, Seam 2.2.0 GA, JBoss Tools 3.1.0 GA > Reporter: Shu-Wei Tan > Assignee: Alexey Kazakov > Fix For: 3.3.x > > > My eclipse workspace contains 2 JBoss Tools generated Seam projects: > - Project1.war > - Project1.ear > - Project1.ejb > - Project1.test > - Project2.war > - Project2.ear > - Project2.ejb > - Project2.test > Project2.ear depends on both Project1.ejb and Project2.ejb. > Project2.test contains a SeamTest test case. When running that test case, I get an exception saying TimerServiceDispatcher already deployed. This is because jboss-seam.jar seems to be picked up twice by the bootstrap process, once from Project1.ear and once from Project2.ear. > If I close the Project1.ear project in Eclipse then rerun the test, it works. > Here's the exception (the actual project name is different from my simplified example above): > ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfsjar:file:/E:/gbahn/SeamProjects/General/General-ear/EarContent/jboss-seam.jar!/ state=PostClassLoader mode=Manual requiredState=Real > org.jboss.deployers.spi.DeploymentException: Error deploying jboss-seam.jar: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:158) > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:88) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45) > at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) > at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127) > at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289) > at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:19) > at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024) > at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915) > at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58) > 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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:607) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:417) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:154) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:88) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:284) > at org.testng.SuiteRunner.run(SuiteRunner.java:204) > at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:877) > at org.testng.TestNG.runSuitesLocally(TestNG.java:842) > at org.testng.TestNG.run(TestNG.java:751) > at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) > at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) > Caused by: org.jboss.deployers.spi.DeploymentException: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:540) > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:486) > at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:468) > at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:434) > at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:376) > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:145) > ... 36 more > Caused by: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:128) > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:536) > ... 41 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-6359) Unable to add NotifyEmail target to Notifier

by Libor Zoubek (JIRA)

Unable to add NotifyEmail target to Notifier -------------------------------------------- Key: JBIDE-6359 URL: https://jira.jboss.org/browse/JBIDE-6359 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Libor Zoubek Assignee: Brian Fitzpatrick Attachments: esb.emailnotify.log -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-6696) Seam 2.2 DVD Store example not working with EAP 5.1

by Martin Malina (JIRA)

Seam 2.2 DVD Store example not working with EAP 5.1 --------------------------------------------------- Key: JBIDE-6696 URL: https://jira.jboss.org/browse/JBIDE-6696 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.1.0.GA Reporter: Martin Malina Assignee: Snjezana Peco Steps: 1. create a new Example project and choose Seam 2.2 DVD Store example 2. deploy to a running EAP 5.1 server The deployment of dvdstore22-ear.ear fails due to failure to deploy dvdstore22.war. This in turn fails because of this error: 13:41:57,403 ERROR [[/seam-dvdstore]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.RuntimeException: Could not create Component: org.jboss.seam.bpm.jbpm ... Caused by: java.lang.NoClassDefFoundError: org/hibernate/lob/ReaderInputStream ... Caused by: java.lang.ClassNotFoundException: org.hibernate.lob.ReaderInputStream from BaseClassLoader@12e6c13f{vfszip:/home/rasp/jbossqa/EAP5/EnterprisePlatform-5.1.0/jboss-eap-5.1/jboss-as/server/all/deploy/jboss-seam-dvdstore.ear/} See JBPAPP-4643 for more info. The example needs to be upgraded to this version: http://repository.jboss.org/maven2-brew/org/jboss/seam/examples/jboss-sea... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6609) Support for BPELInvoke action

by Libor Zoubek (JIRA)

Support for BPELInvoke action ----------------------------- Key: JBIDE-6609 URL: https://jira.jboss.org/browse/JBIDE-6609 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Libor Zoubek ESB Editor should support BPELInvoke ESB action, since it is an integration point between esb and riftsaw. Details of it can be found here http://docs.jboss.com/riftsaw/2.0.0.Final/userguide/html/esb.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6787) Seam wizard creates a project named null-ear

by Alexey Kazakov (JIRA)

Seam wizard creates a project named null-ear -------------------------------------------- Key: JBIDE-6787 URL: https://jira.jboss.org/browse/JBIDE-6787 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Priority: Critical Fix For: 3.2.0.M2 1. Create any EAR Seam project via New Web Seam Project wizard. This step is needed to initialize default values (project type - EAR, Seam runtime) 2. Open New Web Seam Project wizard again. Type any project name and press Finish (This button is supposed to be enabled in this case). 3. Look at the generated projects. Only war project has correct name. Ear, EJB, Test projects looks like null-ear, null-ejb, null-test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6667) NPE in org.jboss.tools.seam.core

by Snjezana Peco (JIRA)

NPE in org.jboss.tools.seam.core -------------------------------- Key: JBIDE-6667 URL: https://jira.jboss.org/browse/JBIDE-6667 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.x Reporter: Snjezana Peco Assignee: Alexey Kazakov Steps to reproduce: - create some project (it doesn't have to be a Java project) - close it You will get the following exception: !ENTRY org.eclipse.ui.ide 2 4 2010-07-20 22:33:43.046 !MESSAGE Problems occurred closing the selected resources. !SUBENTRY 1 org.eclipse.core.resources 2 566 2010-07-20 22:33:43.046 !MESSAGE Problems occurred during save. !STACK 0 java.lang.NullPointerException at org.jboss.tools.seam.core.SeamCorePlugin$1.saving(SeamCorePlugin.java:84) at org.eclipse.core.internal.resources.SaveManager.executeLifecycle(SaveManager.java:361) at org.eclipse.core.internal.resources.SaveManager$1.run(SaveManager.java:170) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.resources.SaveManager.broadcastLifecycle(SaveManager.java:173) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1108) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1087) at org.eclipse.core.internal.resources.Project.close(Project.java:190) at org.eclipse.ui.actions.CloseResourceAction.invokeOperation(CloseResourceAction.java:129) at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:162) at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:483) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6610) seam components defined in custom component.xml files not recognized

by Marcel Sebek (JIRA)

seam components defined in custom component.xml files not recognized -------------------------------------------------------------------- Key: JBIDE-6610 URL: https://jira.jboss.org/browse/JBIDE-6610 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.1 Environment: seam version 2.2.0.GA, icefaces, ear-type of project Reporter: Marcel Sebek Assignee: Alexey Kazakov The component defined in custom ???.component.xml is not recognized by jboss tools. When I inject the component, I get a warning about unknown context variable name 'xyz'. However, pasting the content of custom component.xml into global components.xml hides the warnings. The injection works, therefore the code should be correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6686) Hibernate platform names for JPA Facet are misleading/incorrect

by Max Rydahl Andersen (JIRA)

Hibernate platform names for JPA Facet are misleading/incorrect --------------------------------------------------------------- Key: JBIDE-6686 URL: https://jira.jboss.org/browse/JBIDE-6686 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.M1 Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Fix For: 3.2.0.M2 We seem to provide two platform names under JPA Facet: "Hibernate" & "Hibernate jpa 2.0" 1) Both shows up no matter if I choose JPA 1 or JPA 2 on the facet page, that does not sound correct to me. 2) Why is "jpa" lower case ? 3) Why does one has a version and the on none ? 4) Shouldn't these be named after the main Hibernate version they target ? i.e. Hibernate 3.3-3.4 and Hibernate 3.5 ? Or simply Hibernate EntityManager 3.4, Hibernate EntityManager 3.5 ? (need to check the version numbers if they are correct, since i'm just speaking of memory here) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6541) code assist does not show Seam components when Eclipse first starts (until you 'refresh' or clean project)

by Vadim Berezniker (JIRA)

code assist does not show Seam components when Eclipse first starts (until you 'refresh' or clean project) ---------------------------------------------------------------------------------------------------------- Key: JBIDE-6541 URL: https://jira.jboss.org/browse/JBIDE-6541 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.1 Reporter: Vadim Berezniker Relevant forum post is here: https://community.jboss.org/message/549587#549587 As the title says, if I restart Eclipse and open a .xhtml file and try to perform EL code assist, I do not see any Seam components in the list. If I refresh the project, clean the project or expand the project in the 'Seam Components' window then it starts to work. I tried it with a clean workspace with JBoss Tools 3.1.1 with the same results. Tried it on another machine with JBoss Tools 3.1.0 with the same results. I noticed that Eclipse doesn't appear to run builders if the project is in 'pristine' state. That is if the project is built when you close Eclipse, it won't try to build it when you reopen Eclipse. Eclipse version is 3.5.2 It's a pretty minor issue as it's relatively easy to resolve, but it may be confusing to new users if they encounter it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
3
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 August 2010