December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1462) Cannot open struts-config.xml

by Alex Titov (JIRA)

Cannot open struts-config.xml ----------------------------- Key: JBIDE-1462 URL: http://jira.jboss.com/jira/browse/JBIDE-1462 Project: JBoss Tools Issue Type: Bug Components: struts/shale Affects Versions: 2.0.0.CR1 Environment: Linux, Eclipse 3.3.1.1 Reporter: Alex Titov When I try to open struts-config.xml with JBoss XML editor the fillowing error appears in .log file: !ENTRY org.eclipse.ui 4 0 2007-12-07 01:05:43.142 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NoSuchFieldError: ATTR_REGISTER_IN_TOMCAT at org.jboss.tools.struts.StrutsPreference.<clinit>(StrutsPreference.java:28) at org.jboss.tools.struts.ui.editor.StrutsConfigEditor.doCreatePages(StrutsConfigEditor.java:57) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:234) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:178) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2739) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651) at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574) at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340) at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328) at org.eclipse.ui.actions.OpenWithMenu$3.handleEvent(OpenWithMenu.java:226) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3196) change the genereted wsdl file's location

by Feng Qian (JIRA)

change the genereted wsdl file's location ----------------------------------------- Key: JBIDE-3196 URL: https://jira.jboss.org/jira/browse/JBIDE-3196 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.0.cr1 Environment: Now the wsdl file is in ./Webcontext/wsdl/. Because this genenreted wsdl file is sample file, not to be used by server, put it in the project root directory. Reporter: Feng Qian Assignee: Feng Qian Fix For: 3.0.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

13 years, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-2200) Implement top down service creation with JbossWS Web Service runtime

by Denny Xu (JIRA)

Implement top down service creation with JbossWS Web Service runtime -------------------------------------------------------------------- Key: JBIDE-2200 URL: http://jira.jboss.com/jira/browse/JBIDE-2200 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Webservices Affects Versions: 2.0.0.GA Reporter: Denny Xu Assigned To: Denny Xu Fix For: 2.2.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3286) Wrong "Key Type"

by Juergen Zimmermann (JIRA)

Wrong "Key Type" ---------------- Key: JBIDE-3286 URL: https://jira.jboss.org/jira/browse/JBIDE-3286 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.beta1 Environment: Eclipse 3.4.1, WTP 3.0.3, JBossTools 3.0beta1 Reporter: Juergen Zimmermann There are 2 wrong entries in the XML catalog: 1) Key "http://www.jboss.com/ws-security/config". This should be "http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd" 2) Key "urn:jboss:jaxws-config:2.0". This should be "jaxws-config_2_0.xsd" Both keys have the "Key Type": "Schema Location". The key type should be "Namespace Name". Have a look at other entries regarding xsd files e.g. http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd -- 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

13 years, 12 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2955) a error occurs when an jboss ws classpath entry named jarName doesn't exist

by Feng Qian (JIRA)

a error occurs when an jboss ws classpath entry named jarName doesn't exist --------------------------------------------------------------------------- Key: JBIDE-2955 URL: https://jira.jboss.org/jira/browse/JBIDE-2955 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.0.beta1 Reporter: Feng Qian Assignee: Feng Qian Priority: Critical Fix For: 3.0.0.beta1 -- 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

13 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1004) Update site errors after a new install of JBDS 2.1.0.GA

by Jeff (JIRA)

Update site errors after a new install of JBDS 2.1.0.GA ------------------------------------------------------- Key: JBDS-1004 URL: https://jira.jboss.org/jira/browse/JBDS-1004 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Environment: Mac OS X 10.6.2 Reporter: Jeff Do a new install and start up JBDS. Choose Help -> Software Updates and then click the Update button. Answer Yes to the question "The software items you selected may not be valid with your current installation. Do you want to open the wizard anyway to review the selections?". Then you'll see a rather long list of available updates with each one as far as I can tell having the same message: Cannot complete the request. See the details. Cannot find a solution satisfying the following requirements org.eclipse.ui.ide.application [1.0.101.M20090826-0800]. -- 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

13 years, 12 months

4
19
0 / 0

[JBoss JIRA] Created: (JBIDE-3862) Add JUnit tests for Generate Seam Entities wizard

by Denis Golovin (JIRA)

Add JUnit tests for Generate Seam Entities wizard ------------------------------------------------- Key: JBIDE-3862 URL: https://jira.jboss.org/jira/browse/JBIDE-3862 Project: Tools (JBoss Tools) Issue Type: Task Components: Seam Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 it can use HSQL employee DB from https://svn.jboss.org/repos/jbosstools/trunk/documentation/development/us... -- 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

14 years

2
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2850) Run JUnit tests for relevant Seam Distributions

by Denis Golovin (JIRA)

Run JUnit tests for relevant Seam Distributions ------------------------------------------------ Key: JBIDE-2850 URL: https://jira.jboss.org/jira/browse/JBIDE-2850 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.0.0.alpha Reporter: Denis Golovin Assignee: Denis Golovin Priority: Blocker Fix For: 3.0.0.beta1 1.2.1.GA with path, 2.0.2.SP1, 1.2.1.GA with patch from JB EAP, 2.0.0 fp form JB EAP and 2.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

14 years

2
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5109) Allow regular jboss servers to use remote deployment as well (instead of just SSH Server)

by Rob Stryker (JIRA)

Allow regular jboss servers to use remote deployment as well (instead of just SSH Server) ----------------------------------------------------------------------------------------- Key: JBIDE-5109 URL: https://jira.jboss.org/jira/browse/JBIDE-5109 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.1.0.M3 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.1.0.CR1 5) Expand this logic to be accessible from standard JBoss server types. See JBIDE-5048 -- 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

14 years

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3971) Add option to transform a POJO into a WebService

by Joao Paulo Viragine (JIRA)

Add option to transform a POJO into a WebService ------------------------------------------------ Key: JBIDE-3971 URL: https://jira.jboss.org/jira/browse/JBIDE-3971 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.0.0.CR2 Environment: JBDS 2.0.0.CR2 Reporter: Joao Paulo Viragine Priority: Minor It would be nice if we could add WebServices annotations to an existing POJO (as we have the option to add Hibernate/JPA annotations to an existing POJO) A wizard could expose the methods in the POJO, so we could choose which methods will be exposed as a "WebMethod". Further, JBDS could update the web.xml to map the class as a Servlet. -- 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

14 years

6
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2009