[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, 7 months
[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, 7 months
[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, 7 months
[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, 7 months
[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, 7 months
[JBoss JIRA] Created: (JBIDE-6242) EPP 5, JBDS, JSR 168 Portlet Deploy
by Gary Lamperillo (JIRA)
EPP 5, JBDS, JSR 168 Portlet Deploy
-----------------------------------
Key: JBIDE-6242
URL: https://jira.jboss.org/jira/browse/JBIDE-6242
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Gary Lamperillo
Several issues with deploying a simple JSR 168 Portlet, I will outline the steps first.
1) Create a Dynamic Web Project
2) to the Facets, I have added just "JBoss Core Portlet"
3) To the Build Path, I added portlet-api-2.0.jar from deploy/gatein.ear/lib
4) Create a Portlet (com.jboss.test.Portlet)
5) Add a server with the launch config param.
6) Started the Server, it starts fine.
7) add the Dynamic Web Project to the Server, and it blows up with a cast from com.jboss.test.Portlet cannot be cast to javax.portlet.Portlet
Here is the stack trace:
14:54:49,125 INFO [TomcatDeployment] deploy, ctxPath=/TestPortal
14:54:49,218 ERROR [LifeCycle] Cannot start object
org.gatein.pc.portlet.container.PortletInitializationException: The portlet Portlet threw a runtime exception during init
at org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl.start(PortletContainerImpl.java:289)
at org.gatein.pc.portlet.impl.container.PortletContainerLifeCycle.invokeStart(PortletContainerLifeCycle.java:76)
at org.gatein.pc.portlet.impl.container.LifeCycle.managedStart(LifeCycle.java:93)
at org.gatein.pc.portlet.impl.container.PortletApplicationLifeCycle.startDependents(PortletApplicationLifeCycle.java:351)
at org.gatein.pc.portlet.impl.container.LifeCycle.managedStart(LifeCycle.java:129)
at org.gatein.pc.mc.PortletApplicationDeployment.install(PortletApplicationDeployment.java:153)
at org.gatein.pc.mc.PortletApplicationDeployer.add(PortletApplicationDeployer.java:216)
at org.gatein.pc.mc.PortletApplicationDeployer.onEvent(PortletApplicationDeployer.java:185)
at org.gatein.wci.impl.DefaultServletContainer.safeFireEvent(DefaultServletContainer.java:147)
at org.gatein.wci.impl.DefaultServletContainer.fireEvent(DefaultServletContainer.java:166)
at org.gatein.wci.impl.DefaultServletContainer.access$400(DefaultServletContainer.java:54)
at org.gatein.wci.impl.DefaultServletContainer$RegistrationImpl.registerWebApp(DefaultServletContainer.java:250)
at org.gatein.wci.tomcat.TC6ServletContainerContext.start(TC6ServletContainerContext.java:283)
at org.gatein.wci.tomcat.TC6ServletContainerContext.lifecycleEvent(TC6ServletContainerContext.java:141)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4388)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
at sun.reflect.GeneratedMethodAccessor355.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
at $Proxy38.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1440)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1158)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1099)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:782)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:371)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:256)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: java.lang.ClassCastException: com.jboss.test.Portlet cannot be cast to javax.portlet.Portlet
at org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl.start(PortletContainerImpl.java:255)
... 75 more
Now this issue can be worked around by refactoring the Java Class and changing the Portlet.xml. However the refactor of the Java Class does not cause refactor of the portlet.xml
--
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, 7 months