February 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5847) Cannot install Hibernate Tools on Eclipse Galileo SR2 M5

by Krasimir Goutcev (JIRA)

Cannot install Hibernate Tools on Eclipse Galileo SR2 M5 -------------------------------------------------------- Key: JBIDE-5847 URL: https://jira.jboss.org/jira/browse/JBIDE-5847 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Win Srvers 2003 x64 eclipse-jee-helios-M5-win32 Reporter: Krasimir Goutcev 1. Install eclipse-jee-helios-M5-win32 2. Add update link http://download.jboss.org/jbosstools/updates/nightly/trunk/ 3. check Hibernate tools 4 Click "Next" Result: Cannot complete the install because one or more required items could not be found. Software being installed: Hibernate Tools 3.3.0.v201002130332N-H23-CR3 (org.hibernate.eclipse.feature.feature.group 3.3.0.v201002130332N-H23-CR3) Missing requirement: Hibernate Jdt Core 3.3.0.v201002130332N-H23-CR3 (org.jboss.tools.hibernate.jpt.core 3.3.0.v201002130332N-H23-CR3) requires 'bundle org.eclipse.jpt.core [2.2.0,2.2.2)' but it could not be found Cannot satisfy dependency: From: Hibernate Tools 3.3.0.v201002130332N-H23-CR3 (org.hibernate.eclipse.feature.feature.group 3.3.0.v201002130332N-H23-CR3) To: org.jboss.tools.hibernate.jpt.core [3.3.0.v201002130332N-H23-CR3] -- 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

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5897) "targer" instead of "target" used in properties view

by Max Rydahl Andersen (JIRA)

"targer" instead of "target" used in properties view ---------------------------------------------------- Key: JBIDE-5897 URL: https://jira.jboss.org/jira/browse/JBIDE-5897 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Assignee: Vitali Yemialyanchyk Fix For: 3.1.1 "targer" shown in all the screenshots of the whatsnew and noteworthy for CR2 -- 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

15 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5501) Move AS support for specific facets out of AS ?

by Max Rydahl Andersen (JIRA)

Move AS support for specific facets out of AS ? ----------------------------------------------- Key: JBIDE-5501 URL: https://jira.jboss.org/jira/browse/JBIDE-5501 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Optional Fix For: 3.1.0.GA, 3.2.next Looking at JBIDE-5229, is it not possible to move such support *outside* of AS module and let it be defined by the esb module or some integration module ? Or should as.core really have *all* knowledge and create a kind of logical circular dependency ? ESB needs AS, but AS needs ESB too ? -- 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

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5924) Intermittent issue with generating Web Service classes from WSDL

by Brian Fitzpatrick (JIRA)

Intermittent issue with generating Web Service classes from WSDL ---------------------------------------------------------------- Key: JBIDE-5924 URL: https://jira.jboss.org/jira/browse/JBIDE-5924 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 2.1.1 Reporter: Brian Fitzpatrick https://enterprise.redhat.com/issue-tracker/536423 ******** [JBOSS] Failed to Generate Web Service Classes from WSDL ******** This case was originally submitted on the Redhat Support site and transferred here to the JBoss Support site. Apologies for the initial lack of information; that information was not transferred over. This is a problem that is happening inside JBoss's Developer's Studio. Here are the technologies being used: Operating System: Fedora 12 JBoss Developer's Studio v2.1.1.GA JBoss Application Server v5.1.0.GA JBoss WS Tools v3.2.2.GA Java SDK 1.6.0_17 I have been creating "Top Down Java Bean Web Services" from a WSDL file using the File->New->Web Service wizard. After the installation of JBoss Dev Studio, this function worked perfectly and created all the necessary classes in the package that I was specifying. After a few weeks, this function seemed to become slightly broken. All of a sudden, going through the same process, I started to receive a "Failed to generate implementation class" error when hitting Finish at the end of the wizard. It stopped creating the Implementation class of the Web Service, but it created the other classes. This wasn't a huge deal because I have been developing the Implementation class myself and it was still providing the other supporting classes for the web service. Just recently, this function has stopped working completely. It no longer creates ANY of the classes and I still get the "Failed to generate implementation class" error when I hit Finish at the end of the Wizard. When I originally created this ticket on the Redhat Support site, the wizard started to work again while I was taking screen shots to show the errors, but it has stopped working again. *************** In addition to the problem above: In my WSDL file, I have a function called validLogin that returns a complex object UserBean. UserBean.java is a java object that I created. It resides in another project called "Commons" inside of JBoss Dev Studio under the package "com.beans" When I first created this WSDL file, I believe it worked fine by just putting in "com.beans.UserBean". The wsdl file seemed to pick up the UserBean object automatically because I have the Commons project linked to the accessdb project through the Build Path. Now this function doesn't seem to be working anymore. When the "web service wizard" was working or if I do the "create web client from wsdl wizard", it doesn't seem to recognize the UserBean class in the Commons project. It tries to make a new object called ComBeansUserBean as well as UserBean. Can you instruct me on the best way to tell my WSDL file to return a complex object residing in a different project using the Design view of the wsdl creator? -- 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

15 years, 10 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-5841) JstJspAllTests.testCAForCompositeComponent fails: Content Assistant returned no proposals

by Nick Boldt (JIRA)

JstJspAllTests.testCAForCompositeComponent fails: Content Assistant returned no proposals ----------------------------------------------------------------------------------------- Key: JBIDE-5841 URL: https://jira.jboss.org/jira/browse/JBIDE-5841 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Regression JstJspAllTests.testCAForCompositeComponent Failing for the past 1 build (Since #155 ) Took 8 sec. add description Error Message Content Assistant returned no proposals Stacktrace junit.framework.AssertionFailedError: Content Assistant returned no proposals at org.jboss.tools.jst.jsp.test.ca.ContentAssistantTestCase.checkProposals(ContentAssistantTestCase.java:89) at org.jboss.tools.jst.jsp.test.ca.ContentAssistantTestCase.checkProposals(ContentAssistantTestCase.java:59) at org.jboss.tools.jst.jsp.test.ca.CAForCompositeComponentTest.testCAForCompositeComponent(CAForCompositeComponentTest.java:27) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) at org.eclipse.core.launcher.Main.main(Main.java:34) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-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

15 years, 10 months

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5952) ear dependency jar is wrapped by another jar

by Dmitry Malchikov (JIRA)

ear dependency jar is wrapped by another jar -------------------------------------------- Key: JBIDE-5952 URL: https://jira.jboss.org/jira/browse/JBIDE-5952 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Environment: windows 7 x64, 32-bit JRE, eclipse 3.6 M5 32bit for windows, WTP 3.2 M5, maven 2.2.1, JBossAS Tools 2.1.0.v201002252131N-H17-GA, JBoss Maven Integration 1.0.0.v201002252131N-H17-GA Reporter: Dmitry Malchikov Maven project has ear and ejb modules. Ear module depends on ejb module and includes it in result ear file. When deploying ear some kind of ejb dependencies jars are wrapped into another jar. Example of jars: jtds-1.2.2.jar, jibx-run-1.2.1.jar, mvel2-2.0.10.jar. Don't know really why these jars are wrapped into jar package (for example mvel2-2.0.10.jar contains another mvel2-2.0.10.jar package which contains correct jar content) there are many jars that are deployed correctly. -- 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

15 years, 10 months

6
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5949) JBoss 5.1 Server start not detected

by Andreas Erne (JIRA)

JBoss 5.1 Server start not detected ----------------------------------- Key: JBIDE-5949 URL: https://jira.jboss.org/jira/browse/JBIDE-5949 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.3.GA Environment: Win XP Reporter: Andreas Erne Assignee: Rob Stryker Prepare default install of - JBoss 5.0 - JBoss 5.1 In Eclipse JBoss Server View: - Create JBoss 5.0 server for corresponding 5.0 runtime - Leave default server properties - Start server -> State switches to 'starting' -> State switches to 'started' -> OK - Create JBoss 5.1 server for corresponding 5.1 runtime - Leave default server properties - Start server -> State switches to 'starting' -> State stays in 'starting' state until timeout (450 seconds) -> NOK -- 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

15 years, 10 months

5
11
0 / 0

[JBoss JIRA] Created: (JBDS-1105) Cannot create JbossWS service with client enabled

by Libor Zoubek (JIRA)

Cannot create JbossWS service with client enabled ------------------------------------------------- Key: JBDS-1105 URL: https://jira.jboss.org/jira/browse/JBDS-1105 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 3.0.0.CR2 Reporter: Libor Zoubek creation of new JbossWS cannot be finished when Steps to reproduce : 1. Create new Dynamic project 2. Create new class with javax.jws annotations or use the attached one 3. Create new JbossWS based web service : New -> Other -> Web Service 3.1. Service implementation:select your class 3.2. Web service runtime: JbossWS 3.3. Client type : java Proxy, move slider to 'Develop client' or above 4. Finish or Next, does not matter if you check anything there 5. You get a MessageBox telling : Selection must be WSDL. 6. WSDL seems to get published, web service seems too, but one can' test it btw: How can I retrieve WSDL from jboss as? Jboss-as does not say something like : 'New service is deployed, wsdl is here' -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

5
30
0 / 0

[JBoss JIRA] Created: (JBIDE-5902) Validation not running on CDI project before I enable JSF support

by Max Rydahl Andersen (JIRA)

Validation not running on CDI project before I enable JSF support ----------------------------------------------------------------- Key: JBIDE-5902 URL: https://jira.jboss.org/jira/browse/JBIDE-5902 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Fix For: 3.1.1 Not sure if this is a bug or a feature, but I did not get validation errors for my CDI enabled project before I added JSF support. CDI validation shouldn't require JSF. -- 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

15 years, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (JBDS-702) Tool to replace diffmk

by Svetlana mukhina (JIRA)

Tool to replace diffmk ---------------------- Key: JBDS-702 URL: https://jira.jboss.org/jira/browse/JBDS-702 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Olga Chukhutsina Fix For: 2.1.0 It's necessary to replace diffmk, as it corrupts guides structure and then it should be corrected manually, we need more sophisticated tool to reduce manual work. Investigation of existing appropriate tools is required.. -- 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

15 years, 10 months

4
13
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 February 2010