March 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-3582) Wrong provider name

by Nick Boldt (JIRA)

Wrong provider name ------------------- Key: JBIDE-3582 URL: https://jira.jboss.org/jira/browse/JBIDE-3582 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.0.0.CR2 Reporter: Nick Boldt Attachments: JBIDE-3582.wrong.provider.jbpm.png As of N200901181220 build, the provider for jBPM is listed as "JBoss Inc." rather than "JBoss, a division of Red Hat" -- 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

17 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3898) Update to jbpm_jpdl_gpd_3_1_7 tag for jbpm

by Max Rydahl Andersen (JIRA)

Update to jbpm_jpdl_gpd_3_1_7 tag for jbpm ------------------------------------------ Key: JBIDE-3898 URL: https://jira.jboss.org/jira/browse/JBIDE-3898 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.0.0.GA Reporter: Max Rydahl Andersen Assignee: Nick Boldt Priority: Blocker Fix For: 3.0.0.GA jbpm have done a set of updates and need to move tag to jbpm_jpdl_gpd_3_1_7 -- 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

17 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3367) Exception occurs during an import existing seam projects into worksspace

by Denis Golovin (JIRA)

Exception occurs during an import existing seam projects into worksspace ------------------------------------------------------------------------ Key: JBIDE-3367 URL: https://jira.jboss.org/jira/browse/JBIDE-3367 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Reporter: Denis Golovin Assignee: Denis Golovin https://bugs.eclipse.org/bugs/show_bug.cgi?id=257251 java.lang.NullPointerException at org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory.createModuleDelegates(J2EEDeployableFactory.java:82) at org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory.createModules(J2EEDeployableFactory.java:68) at org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory.createModules(J2EEDeployableFactory.java:56) at org.eclipse.wst.server.core.util.ProjectModuleFactoryDelegate.cacheModules(ProjectModuleFactoryDelegate.java:59) at org.eclipse.wst.server.core.util.ProjectModuleFactoryDelegate.getModules(ProjectModuleFactoryDelegate.java:255) at org.eclipse.wst.server.core.internal.ModuleFactory.getModules(ModuleFactory.java:131) at org.eclipse.wst.server.core.ServerUtil.getModules(ServerUtil.java:96) at org.eclipse.wst.server.core.internal.ResourceManager.publishHandleProjectChange(ResourceManager.java:965) at org.eclipse.wst.server.core.internal.ResourceManager$ServerResourceChangeListener$1.visit(ResourceManager.java:122) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48) at org.eclipse.wst.server.core.internal.ResourceManager$ServerResourceChangeListener.resourceChanged(ResourceManager.java:116) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:288) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:282) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148) at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:297) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-3839) JBDS2.0.0 CR2 with Project Examples for ESB problems

by Stelios Koussouris (JIRA)

JBDS2.0.0 CR2 with Project Examples for ESB problems ---------------------------------------------------- Key: JBIDE-3839 URL: https://jira.jboss.org/jira/browse/JBIDE-3839 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Reporter: Stelios Koussouris Priority: Minor Trying to use in JBDS 2.0.0 CR2 The "ESB Tools" In documentation http://download.jboss.org/jbosstools/nightly-docs/en/esb_ref_guide/html_s... 2.3. Creating ESB Project using JBoss Tools Project Examples Wizard The result show on the following figure is not what I get ... Figure 2.7. JBoss ESB Project Examples: helloworld and helloworld_testclient I wanted to use my own Runtime (which exists outside the JBDS) but it automatically gives me (as shown in the "Java Build Path") - JBoss ESB Runtime (jbossesb-server-4.4GA) - Server Library [jboss-eap-Runtime (unbound) - plus the version of JDK Now, I cannot see any way of changing the JBoss ESB Runtime it is given as 4.4 and therefore have not changed it. I have though modified the "Server Library [jboss-eap-Runtime (unbound)" to point to a SOA-P server configuration which I want my services to be deployed in. I have also removed the "jboss-eap-runtime", which is the default Target Runtime, from my "Targeted Runtimes" instead I am pointing to the runtime that I have assigned also to "Server Library [jboss-eap-Runtime (unbound)". Now my "Java Build Path" looks like - JBoss ESB Runtime (jbossesb-server-4.4GA) - Server Library [jboss-eap-Runtime (MY ASSIGNED RUNTIME) - plus the version of JDK This has not resolved issues with imports to do so both in the helloworld and hellorworld client I used from quick fixes the "fix project setup" to import the jbossesb-rosetta.jar from a SOA-P server (not even my own one was given as an option) which has resolved now the import etc. I have discussed some of this with Max and suggested I raise a JIRA so here is.. -- 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

17 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3590) Seam 12 project with JBossesb-server-4.4.GA

by Aliaksey Nis (JIRA)

Seam 12 project with JBossesb-server-4.4.GA ------------------------------------------- Key: JBIDE-3590 URL: https://jira.jboss.org/jira/browse/JBIDE-3590 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.CR2 Environment: WindowsXP SP2 JBoss Tools Version: 3.0.0.CR2 Build id: JBossTools-ALL-win32-3.0.0.CR2-N200901190016 JDK 1.5_08 Reporter: Aliaksey Nis EXECUTE: Go to Preferences> Server > Installed runtimes. EXECUTE: Create new Server runtime(and local server) - select path to JBossesb-server-4.4.GA. EXECUTE: Create new Seam 1.2AP EAR project. Select newly created server runtime. FAILURE: In created Ear project error(shown in Problems log) appears. Error points to authentificator.java(multiply validation errors). EXECUTE: Start this project on this server. After loading - press "login" link, input "admin" username, press button. FAILURE: Debug page appears. --------- EXECUTE: Change server runtime for this project to default Server(included in JBDS install pack). Errors disappears. EXECUTE: Change server runtime for this project to JBossesb-server-4.4.GA runtime again. EXECUTE: Create new Entity with name "entity1". FAILURE: Validation errors for Entity1Home.java appears. So, problem is in JBossesb-server-4.4.GA runtime. Is it expected 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

17 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3651) Runtime classpath on ESB Client example results in exception

by Jeff DeLong (JIRA)

Runtime classpath on ESB Client example results in exception ------------------------------------------------------------ Key: JBIDE-3651 URL: https://jira.jboss.org/jira/browse/JBIDE-3651 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.cr1 Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK 1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA). Reporter: Jeff DeLong Problem occurs when running helloworld_testclient. The following exception occurs: Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message [header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors. I can get the exception to go away and the client to run successfully if I add jbossall-client to the FRONT of the Eclipse client application Run Configuration classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime is from SOA-P 4.3). Not sure how to change the order of the libraries. The Run Configuration classpath uses the project default classpath, however the libraries, etc. are listed in the reverse order of how they are listed in the Properties - > Java Build Path -> Libraries, which appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath. -- 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

17 years, 1 month

4
18
0 / 0

[JBoss JIRA] Created: (JBIDE-3886) java.lang.NullPointerException when use OpenOn feature in faces-config.xml from jars opened with JBoss Tools XML Editor.

by Anton Klimkovich (JIRA)

java.lang.NullPointerException when use OpenOn feature in faces-config.xml from jars opened with JBoss Tools XML Editor. ------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-3886 URL: https://jira.jboss.org/jira/browse/JBIDE-3886 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich Assignee: Alexey Kazakov Attachments: exception.txt EXECUTE: Create seam web project EXECUTE: Open Web Projects View EXECUTE: Open faces-config.xml - jboss-seam.jar EXECUTE: Make OpenOn on <message-bundle>org.jboss.seam.core.SeamResourceBundle</message-bundle> FAILURE: Unhandled event loop exception is occured. -- 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

17 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3672) Can't publish the ESB project to the started server from jboss-soa-p.4.3.0.

by Anton Klimkovich (JIRA)

Can't publish the ESB project to the started server from jboss-soa-p.4.3.0. --------------------------------------------------------------------------- Key: JBIDE-3672 URL: https://jira.jboss.org/jira/browse/JBIDE-3672 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.CR2 Reporter: Anton Klimkovich EXECUTE: Download project to workspace http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran... EXECUTE: Add ESB Libraries to the project EXECUTE: Start JBoss AS from jboss-soa-p.4.3.0 ASSERT: Server started. EXECUTE: Add project to the server and press publish button. FAILURE: java.lang.SecurityException: Failed to authenticate principal=, securityDomain=jmx-console Full 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

17 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2739) JBoss Tools icon/logo suggestions

by Max Rydahl Andersen (JIRA)

JBoss Tools icon/logo suggestions --------------------------------- Key: JBIDE-2739 URL: https://jira.jboss.org/jira/browse/JBIDE-2739 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.beta1 Reporter: Max Rydahl Andersen Fix For: 3.0.0.cr1 Attachments: white_balls_in_a_box_1.jpg We would like to have some kind of JBoss Tools identity we can use on website, eclipse aboutbox, wizard etc. Im using this jira to collect the suggestions I receive for JBoss Tools icon/logo's. -- 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

17 years, 1 month

24
126
0 / 0

[JBoss JIRA] Created: (JBDS-634) Console Configuration for new jpa project

by Svetlana mukhina (JIRA)

Console Configuration for new jpa project ----------------------------------------- Key: JBDS-634 URL: https://jira.jboss.org/jira/browse/JBDS-634 Project: Developer Studio Issue Type: Task Components: Doc - Hibernate Affects Versions: 2.0.0.cr2 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.1 Mention in guide that default Console Configuration for new jpa project is created when Hibernate paltform is selected. 1. New jpa project wizard 2 "Target Runtime" is <none>. 3. select Hibernate as a platform 3. Select connection profile(or create new and select) 5. press finish and observe that new console configuration created -- 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

17 years, 1 month

2
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 March 2009