Generic Service Control WSDL

Okay, so we are running into a little problem on my program. I will do my best to explain how it is all put together without being too confusing.
We are designing a WebService for WLS 9.2 that will be used to start JPDs on WLI. These JPDs will be modeled after a generic JPD that will have a "start" method. We used this JPD to create a WSDL that was then used to generate a ServiceControl for our WebService. The actual JPDs will be registered with ALSR and will not be necessarily know until runtime.
Hence, our service will lookup the endpoint for the JPD from the registry using some search criteria. This works!!! The WebService will then set the endpoint for the generic control to the endpoint the was retrieved from the registry. Finally, the WebService will use the control to call the "start" method on the control.
Okay, so we have gotten this working when deploying to the server from Workshop. And we were able to get it to work when we export the EAR from Workshop and upload the ear. However, dude to some CM requirements and the way we are handling that aspect of deployment, we were using Ant to build the EAR. We figured out that our Ant script was ignoring some steps in creating the files.
We then tried to use the Workshop exported Ant script, but those don't work for us. There is some classpath problem, and such that makes it not work.
So to make a long story even longer. Has anyone else tried to develop a generic WSDL to a "class" of services and call those services by setting the endpoint for the service via a control? It appears that this may or may not be supported in WLS 9.2.
Any thoughts?

Hi Debbie,
When you created the service control did you choose the option to generate xmlbean types for the service or did you generate jax/rpc types ?
Can you send the service, wsdl and control to me via email at akraj_at_yahoo.com ?
cheers
Raj

Similar Messages

Not able to generate Service control from WSDL in Weblogic Workshop9.2

Hi All,
I am not able to create Service control from my WSDL in Weblogic workshop9.2. It was working fine in Weblogic 8.1.
I am getting the following error. Please help me out.
Types analysis failed for both JAX-RPC and XmlBeans.
BEGIN JAX-RPC CAUSE
com.bea.control.servicecontrol.internal.validation.BindingsCheckException: Failed to generate the JSService with the endpoint builder
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.setupJsService(BindingsClassNameReference.java:573)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadJsService(BindingsClassNameReference.java:321)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getJsService(BindingsClassNameReference.java:362)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadTypeNamesForService(BindingsClassNameReference.java:398)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getTypeNamesForService(BindingsClassNameReference.java:383)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeNamesForService(BindingsCheckUtility.java:210)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingTypeInfoForService(BindingsCheckUtility.java:131)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingInfoForServiceByBindingsDataSourceType(BindingsCheckUtility.java:104)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.initializeTypesForTheService(BindingsCheckUtility.java:273)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.findMatchingBindingsDataSources(BindingsCheckUtility.java:434)
at com.bea.wlw.controls.service.ui.util.BindingsChecker.<init>(BindingsChecker.java:55)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.checkForCompatibleBindings(SelectSCInfoPage.java:304)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.<init>(SelectSCInfoPage.java:98)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.getPageList(GenerateSCWizard.java:150)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.addPages(GenerateSCWizard.java:136)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:499)
at org.eclipse.jface.window.Window.create(Window.java:418)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:996)
at org.eclipse.jface.window.Window.open(Window.java:776)
at com.bea.wlw.controls.service.ui.actions.NewSCGenAction.run(NewSCGenAction.java:101)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
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:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.IllegalArgumentException: unable to find java type for t=String@http://www.w3.org/2001/XMLSchema
at weblogic.wsee.bind.buildtime.internal.TylarBuildtimeBindings.getClassFromXmlType(TylarBuildtimeBindings.java:693)
at weblogic.wsee.bind.buildtime.internal.TylarBuildtimeBindings.getClassFromSchemaType(TylarBuildtimeBindings.java:182)
at weblogic.wsee.tools.source.EndpointBuilder.getJavaClassName(EndpointBuilder.java:735)
at weblogic.wsee.tools.source.EndpointBuilder.addPart(EndpointBuilder.java:664)
at weblogic.wsee.tools.source.EndpointBuilder.createParams(EndpointBuilder.java:591)
at weblogic.wsee.tools.source.EndpointBuilder.addMethod(EndpointBuilder.java:521)
at weblogic.wsee.tools.source.EndpointBuilder.buildEndpoint(EndpointBuilder.java:475)
at weblogic.wsee.tools.source.EndpointBuilder.buildJsService(EndpointBuilder.java:252)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.setupJsService(BindingsClassNameReference.java:549)
... 43 more
END JAX-RPC CAUSE
BEGIN XMLBEANS CAUSE
com.bea.control.servicecontrol.internal.validation.BindingsCheckException: Could not create buildtime bindings with ClientGenUtil
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadBuildtimeBindings(BindingsClassNameReference.java:242)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getBindings(BindingsClassNameReference.java:161)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadJsService(BindingsClassNameReference.java:307)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getJsService(BindingsClassNameReference.java:362)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadTypeNamesForService(BindingsClassNameReference.java:398)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getTypeNamesForService(BindingsClassNameReference.java:383)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeNamesForService(BindingsCheckUtility.java:210)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingTypeInfoForService(BindingsCheckUtility.java:131)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingInfoForServiceByBindingsDataSourceType(BindingsCheckUtility.java:104)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.initializeTypesForTheService(BindingsCheckUtility.java:253)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.findMatchingBindingsDataSources(BindingsCheckUtility.java:434)
at com.bea.wlw.controls.service.ui.util.BindingsChecker.<init>(BindingsChecker.java:55)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.checkForCompatibleBindings(SelectSCInfoPage.java:304)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.<init>(SelectSCInfoPage.java:98)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.getPageList(GenerateSCWizard.java:150)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.addPages(GenerateSCWizard.java:136)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:499)
at org.eclipse.jface.window.Window.create(Window.java:418)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:996)
at org.eclipse.jface.window.Window.open(Window.java:776)
at com.bea.wlw.controls.service.ui.actions.NewSCGenAction.run(NewSCGenAction.java:101)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
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:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: weblogic.wsee.tools.WsBuildException: com.bea.xml.XmlException: Exception while compiling org apache xmlbeans: C:\R4WorkSpace\TestEWS\src\controls\EWSDeal.wsdl:0: error: src-resolve: type 'Array@http://schemas.xmlsoap.org/soap/encoding/' not found.
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBuildtimeBindings(ClientGenUtil.java:217)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBuildtimeBindings(ClientGenUtil.java:174)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadBuildtimeBindings(BindingsClassNameReference.java:228)
... 44 more
Caused by: com.bea.xml.XmlException: Exception while compiling org apache xmlbeans: C:\R4WorkSpace\TestEWS\src\controls\EWSDeal.wsdl:0: error: src-resolve: type 'Array@http://schemas.xmlsoap.org/soap/encoding/' not found.
at weblogic.wsee.bind.buildtime.internal.XmlBeansApacheBindingsBuilderImpl.createBuildtimeBindings(XmlBeansApacheBindingsBuilderImpl.java:262)
at weblogic.wsee.bind.buildtime.internal.XmlBeansBaseBindingsBuilderImpl.createBuildtimeBindings(XmlBeansBaseBindingsBuilderImpl.java:119)
at weblogic.wsee.tools.source.EndpointBuilder.setupBindingProviderWithServices(EndpointBuilder.java:836)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBindingProvider(ClientGenUtil.java:458)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBuildtimeBindings(ClientGenUtil.java:211)
... 46 more
Caused by: org.apache.xmlbeans.XmlException: C:\R4WorkSpace\TestEWS\src\controls\EWSDeal.wsdl:0: error: src-resolve: type 'Array@http://schemas.xmlsoap.org/soap/encoding/' not found.
at weblogic.wsee.bind.buildtime.internal.XmlBeansApacheBindingsBuilderImpl.compileXmlBeans(XmlBeansApacheBindingsBuilderImpl.java:361)
at weblogic.wsee.bind.buildtime.internal.XmlBeansApacheBindingsBuilderImpl.createBuildtimeBindings(XmlBeansApacheBindingsBuilderImpl.java:257)
... 50 more
END XMLBEANS CAUSE

Hi
I have not seen the wsdl yet but your xmlbean types generation looks familiar.
This is one reason why you could get the error with the xmlbeans type.
error: src-resolve: type 'Array@http://schemas.xmlsoap.org/soap/encoding/' not found.
Workaround: To allow the XmlBeans to be built from this type of WSDL correctly, add the schemaLocation attribute. For example, if the original WSDL had an import such as:
<s:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
It should be changed to the following:
<s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" schemaLocation="http://schemas.xmlsoap.org/soap/encoding/"/>
After this change you should not see the error.
Vimala-

Service Control Not Being Generated Correctly from WSDL

Hello,
I am using BEA Workshop for WebLogic Platform 9.2.0 for development. I created a web service in Workshop, which exposes 3 methods... one of the methods, putPlan(), accepts two parameters.
After generating the WSDL from the web service class, I ran the Web Service Client Wizard. I was able to successfully access and test the web service with the generated client code.
However, in another project, I generated a service control from the WSDL. Although the service control was created without any errors, the control itself does not appear to be correct: it defines the putPlan() method as accepting only one parameter instead of the expected two.
The WSDL itself looks good, as it clearly defines two input parameters to the putPlan() method. And, the Web Service Client wizard had no problems generating valid client code from the WSDL. So, I am confused as to why the generated service control is not right.
Any help with this problem would be greatly appreciated.
Thanks!

Hi Debbie,
When you created the service control did you choose the option to generate xmlbean types for the service or did you generate jax/rpc types ?
Can you send the service, wsdl and control to me via email at akraj_at_yahoo.com ?
cheers
Raj

Workshop 10.0.1 - Generating service control from a WSDL file

Hi!
I've been familiarising myself with Workshop (version 10.0.1).
There is a feature that allows the generation of a web service control by right-clicking a WSDL file (Web Services > Generate Service Control).
This process creates a jar file containing the WSDL's complex type.
My only problem with this is that the jar uses the namespaces as package names (for example: www.openuri.org will be converted into an org.openuri package).
I've been searching for a way to customize the package names, but I've been unable to find it. We previously used Axis to generate a web service client, and we ran an Ant task that could map namespaces to packages.
Would there be a way to achieve this in Workshop?
Thank you!

Hi
This is a known issue and a limitation. Service controls doesn't honor xsdconfig files when generated from wsdl file.
We have an enhancement request CR307698 pending to address this issue. It looks like it's a big change in code to get this working so it is being looked at in the next release.
Also, you can call BEA support / create a case in future and request status on this CR anytime.
Vimala-

Generate Service Control for WSDL: NullPointerException

Steps to demonstrate the problem: in Platform Workshop (8.1.4) in Integration mode, create a Tutorial Process Application, then for RequestQuote.jpd, Generate WSDL file, then for that WSDL, Generate Service Control.
<pre>ERROR: requestquote/RequestQuoteContract.wsdl Line 0, Col 0: java.lang.NullPointerException
</pre>
The WSDL is valid (Axis WSDL2Java and Eclipse-Webtools are both okay with it, assuming I delete some cw and http namespaces they don't understand).
The problem is when the XSD is too deeply nested giving XML like /one/two/three, whereas /one/two is okay for WLI. This is valid XSD, but apparently too deep for WLI to understand.
Any help debugging this more or working around it would be appreciated. Is there a way to run this process from the command line, so I might debug this more on my own? I'd like to give the stackTrace for the NPE, but WLI Workshop doesn't show that.
Thanks,
Mike

Hi guys,
I had the same problem and what I had to do was import the Schema project that holds all schemas included in the WSDL that I was trying to generate a control from. In my case I had the Schema project because I was the one that developed the WebService too, in your case it's possible that you have to create an Schema project and somehow extract the schemas from de WSDL and create .xsd files to put in the project.
After doing this you will see the popup window (when you try to generate a service control from the WSDL file) asking if you want to use the XMLBeans generated from the xsd files in your Schema project otherwise it will generate inner classes based in the WSDL's schemas, you must choose YES (use the existing XMLBeans) and that should be it for creating a Service Control based on a WSDL file.
Hope this helps in most cases.
Regards,
Israel Williams
Software Architect
JWM Solutions
[email protected]

Error generating Web Service control in Workshop 9.2 from any wsdl

When trying to generate web service control from service control wizard I get the following error:
An error was encountered while generating types: null
The full stack trace is:
<pre>java.lang.reflect.InvocationTargetException
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:327)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830)
     at com.bea.wlw.controls.service.ui.GenerateSCWizard.performFinish(GenerateSCWizard.java:213)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349)
     at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
     at org.eclipse.jface.window.Window.open(Window.java:787)
     at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:110)
     at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
     at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
     at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
     at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
     at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
     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:585)
     at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
     at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
     at org.eclipse.core.launcher.Main.run(Main.java:973)
     at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.NullPointerException
     at com.bea.wlw.controls.service.ui.GenerateSCWizard$Finisher.run(GenerateSCWizard.java:501)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
</pre>
I have tried different wsdls simple and complex and still getting the same error. What could be the problem? Is it a bug or my misconfiguration? Has anybody succeded to generate service control in workshop 9.0 and above?

Did you also get a CrashWeb dialog?
Andrey Adamovich wrote:
When trying to generate web service control from service control wizard I get the following error:
An error was encountered while generating types: null
The full stack trace is:
<pre>java.lang.reflect.InvocationTargetException
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:327)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830)
     at com.bea.wlw.controls.service.ui.GenerateSCWizard.performFinish(GenerateSCWizard.java:213)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349)
     at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
     at org.eclipse.jface.window.Window.open(Window.java:787)
     at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:110)
     at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
     at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
     at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
     at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
     at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
     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:585)
     at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
     at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
     at org.eclipse.core.launcher.Main.run(Main.java:973)
     at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.NullPointerException
     at com.bea.wlw.controls.service.ui.GenerateSCWizard$Finisher.run(GenerateSCWizard.java:501)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
</pre>
I have tried different wsdls simple and complex and still getting the same error. What could be the problem? Is it a bug or my misconfiguration? Has anybody succeded to generate service control in workshop 9.0 and above?

An error when testing a web service control that takes a complexType argument

i took some wsdl file and generated a web service control in BEA Workshop 8.1.
from the jcx file, i generated the jws test file.
now, the webservice takes in a complex argument as an input. as a result, i added
specialized code in the jws test file to construct the complex type to pass into
the web service control. it compiled/built fine. but when i do the actual testing,
i get the following error:
java.lang.NullPointerException
at com.bea.xml.marshal.AtomicValueMPlan.marshal(AtomicValueMPlan.java:90)
at com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:337)
at com.bea.xml.marshal.MarshalContext.writeElementObjectOrHref(MarshalContext.java:426)
at com.bea.xml.marshal.BaseMPlan.writeValueUsingStrategy(BaseMPlan.java:307)
at com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:349)
at com.bea.xml.marshal.MarshalContext.writeElementObjectOrHref(MarshalContext.java:426)
at com.bea.xml.marshal.BaseMPlan.writeValueUsingStrategy(BaseMPlan.java:307)
at com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:349)
at com.bea.xml.marshal.MethodMPlan.marshal(MethodMPlan.java:260)
at com.bea.wlw.runtime.core.dispatcher.DispMessage.marshalXml(DispMessage.java:386)
at com.bea.wlw.runtime.jws.call.SoapCall.<init>(SoapCall.java:150)
at com.bea.wlw.runtime.jws.call.SoapHttpCall.<init>(SoapHttpCall.java:61)
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:559)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:359)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:387)
at $Proxy8.DocLitQueryByExample(Unknown Source)
at doc_lit_bs.bs_doc_litControlTest.DocLitQueryByExample(bs_doc_litControlTest.jws:31)
i checked the line of code in the jws file and it looks like this:
public doc_lit_bs.bs_doc_litControl.ListOfSampleAccount DocLitQueryByExample(java.lang.String
AccountName)
doc_lit_bs.bs_doc_litControl.ListOfSampleAccount response;
doc_lit_bs.bs_doc_litControl.ListOfSampleAccount ListOfSampleAccount =
new doc_lit_bs.bs_doc_litControl.ListOfSampleAccount();
doc_lit_bs.bs_doc_litControl.Account account = new doc_lit_bs.bs_doc_litControl.Account
account.Name = AccountName;
ListOfSampleAccount.Account = account;
response = bs_doc_litControl.DocLitQueryByExample (ListOfSampleAccount);
/* line 31 */
return (response);
what could be the problem? and how may i resolve this? any help is greatly appreciated.

Hello,
There was an NPE problem reported and resolved (CR117566) concerning
using "mixed" ComplexType, something like:
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";>
<xs:complexType name="fooType" mixed="true"/>
<xs:element name="root" type="fooType"/>
</xs:schema>
Generally speaking, an NPE will be a bug. Can you provide an small
example that generated the NPE to the support team, it would be very
helpful in resolving this issue.
Thanks,
Bruce
Bolei wrote:
>
i took some wsdl file and generated a web service control in BEA Workshop 8.1.
from the jcx file, i generated the jws test file.
now, the webservice takes in a complex argument as an input. as a result, i added
specialized code in the jws test file to construct the complex type to pass into
the web service control. it compiled/built fine. but when i do the actual testing,
i get the following error:
java.lang.NullPointerException
at com.bea.xml.marshal.AtomicValueMPlan.marshal(AtomicValueMPlan.java:90)
at com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:337)
at com.bea.xml.marshal.MarshalContext.writeElementObjectOrHref(MarshalContext.java:426)
at com.bea.xml.marshal.BaseMPlan.writeValueUsingStrategy(BaseMPlan.java:307)
at com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:349)
at com.bea.xml.marshal.MarshalContext.writeElementObjectOrHref(MarshalContext.java:426)
at com.bea.xml.marshal.BaseMPlan.writeValueUsingStrategy(BaseMPlan.java:307)
at com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:349)
at com.bea.xml.marshal.MethodMPlan.marshal(MethodMPlan.java:260)
at com.bea.wlw.runtime.core.dispatcher.DispMessage.marshalXml(DispMessage.java:386)
at com.bea.wlw.runtime.jws.call.SoapCall.<init>(SoapCall.java:150)
at com.bea.wlw.runtime.jws.call.SoapHttpCall.<init>(SoapHttpCall.java:61)
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:559)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:359)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:387)
at $Proxy8.DocLitQueryByExample(Unknown Source)
at doc_lit_bs.bs_doc_litControlTest.DocLitQueryByExample(bs_doc_litControlTest.jws:31)
i checked the line of code in the jws file and it looks like this:
public doc_lit_bs.bs_doc_litControl.ListOfSampleAccount DocLitQueryByExample(java.lang.String
AccountName)
doc_lit_bs.bs_doc_litControl.ListOfSampleAccount response;
doc_lit_bs.bs_doc_litControl.ListOfSampleAccount ListOfSampleAccount =
new doc_lit_bs.bs_doc_litControl.ListOfSampleAccount();
doc_lit_bs.bs_doc_litControl.Account account = new doc_lit_bs.bs_doc_litControl.Account
account.Name = AccountName;
ListOfSampleAccount.Account = account;
response = bs_doc_litControl.DocLitQueryByExample (ListOfSampleAccount);
/* line 31 */
return (response);
what could be the problem? and how may i resolve this? any help is greatly appreciated.

Using WS-Security with Web Service Controls in WLI 8.1 SP3

We have a process that calls a web service hosted on a .NET environment. The technique we have used is to generate a service control from the web service WSDL and call that control from a process. The web service is protected using a WS-Security usernameToken policy. The problem is that the .NET environment requires the wsse:Nonce and wsu:Created elements to be provided along with the token and I cannot see how I can specify this using a wsse policy file in WebLogic workshop. Does anyone have any advice for the best way to add this information to the security element in the SOAP header from within a WLI process? I've seen some example code for a java web service client, but that would not really fit with the control-based approach normally adopted in a WLI environment.

You won't be able to do this using the WSSE file.
An easy way to get around this is to use an XML Bean built from the WS-Security XML Schema. You'll have to read the WS-Security spec to determine how to create the nonce, but you'll be able to convert this XML Bean into the Element[] that the setOutputHeaders() method, which is on the service control you call the .NET Web Service with.
Regards,
Mike Wooten

URGENT: Error while deploying ear with weblogic service control

We have build an ear within workshop and deployed to another server. When accessing the application we are getting the following error:
'com.bea.control.ServiceControlException: Could not find service ref in jndi: java:comp/env/service/hhs_wc_controls_SearchServiceControl[javax.naming.NameNotFoundException: While trying to look up comp/env/service/hhs_wc_controls_SearchServiceControl in /app/webapp/WCWeb/5120123.; remaining name 'comp/env/service/hhs_wc_controls_SearchServiceControl'] '
The service control is connecting a WSDL to consume a web service.
Does the service control create a JNDI entry or some file is not getting built into the ear?
We are using WLP 10.3
Your help is much appreciated.
Thanks,
- Shankar
Edited by: user1269940 on Nov 6, 2009 12:39 PM

Hi Shankar
When a WebService Control is created based on .wsdl file, it generates a .JAR file with all jaxb generated classes and .java files with service and port classes. This .jar file will be under web-inf/lib folder. Then I guess you are using this WebService control in your Pageflow and invoke webservice operations. So do you have like a portlet for this pageflow and testing from a portal. I have a similar scenario but I did not get any error that you are seeing. I consume SOA BPEL webservices in one of my pageflows using Service Controls.
To debug, first test if the wsdl is working by directly invoking the wsdl operations using a utility servlet by name "wls_utc" which you can invoke from any of your wls/wlp domain. Start your domain assuming localhost and port is 7001. The url for testing webservices is:
http://localhost:7001/wls_utc. This works if domain is in Dev Mode only. This page opens a jsp page, where you can type your wsdl url (http://host:port/context/a/b/xyx?wsdl). This page parses that wsdl and shows all operations and for each operation the fields for input parameters. See if this wsdl works fine.
As for deployment, there is no additional step required. Just ear your application that has .war file and that has web-inf/lib folder with actual webservice control generate .jar file. I did no tconfigure any additional JNDI lookups like that.
Thanks
Ravi Jegga

Cluster resource 'Analysis Services' of type 'Generic Service' in clustered role 'SQL Server' failed.

Windows Server 2012 R2
SQL Server 2012
After a recent cluster failover from node 1 to node 2, the Analysis Services role is in a failed state, with the service stopped. When attempting to start the service, there are two error messages captured in Failover Cluster Manager:
Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          4/10/2014 11:48:49 AM
Event ID:      1042
Task Category: Generic Service Resource
Level:         Error
Keywords:
User:          SYSTEM
Computer:      HQ-HASQL-1.sbgnet.int
Description:
Generic service 'Analysis Services (HASQL)' failed with error '1067'. Please examine the application event log.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
    <EventID>1042</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>16</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-10T15:48:49.752168200Z" />
    <EventRecordID>26212</EventRecordID>
    <Correlation />
    <Execution ProcessID="9036" ThreadID="14748" />
    <Channel>System</Channel>
    <Computer>HQ-HASQL-1.sbgnet.int</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="ResourceName">Analysis Services (HASQL)</Data>
    <Data Name="Status">1067</Data>
</EventData>
</Event>
Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          4/10/2014 11:48:49 AM
Event ID:      1069
Task Category: Resource Control Manager
Level:         Error
Keywords:
User:          SYSTEM
Computer:      HQ-HASQL-1.sbgnet.int
Description:
Cluster resource 'Analysis Services (HASQL)' of type 'Generic Service' in clustered role 'SQL Server (HASQL)' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
    <EventID>1069</EventID>
    <Version>1</Version>
    <Level>2</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-10T15:48:49.752168200Z" />
    <EventRecordID>26213</EventRecordID>
    <Correlation />
    <Execution ProcessID="6464" ThreadID="9076" />
    <Channel>System</Channel>
    <Computer>HQ-HASQL-1.sbgnet.int</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="ResourceName">Analysis Services (HASQL)</Data>
    <Data Name="ResourceGroup">SQL Server (HASQL)</Data>
    <Data Name="ResTypeDll">Generic Service</Data>
</EventData>
</Event>
With just these generic error messages being present, this has been difficult to diagnose. Some research has yielded possible resolutions of the Event Viewer log being full, .NET corruption, missing registry entries, but none of those seem to be the issue
(Event Viewer logs cleared, Analysis services is working on the same physical servers in a different cluster, and the registry entries was only a supported issue for SQL Server 2008 and 2008 R2).
Any help would be greatly appreciated.

Bring up Configuration Manager, look at binary path for SSAS. Make sure BOTH folders exist. Sometimes with failovers mappings get screwed up.

When to use Java Web Service from WSDL, Webservice proxy, Web Service DataControl -- JDeveloper 11.1.1.7

Hi Experts!
I am having confusion among these 3 services provided in Oracle ADF. When to use and what service needs to be used?
Once we generate Webservice WSDL. With the WSDL we have 3 options in Jdeveloper to invoke this service.
1. Java Web Service From WSDL.
2. Web Service proxy,
3. Web Service Data Control.
Can anyone give us some brief description of these 3 services when do we need to use and which service is to be used for which scenario ?
Please give me your valuable inputs.
Thanks & Regards,
Guravaiah Tata.

Hi,
Can you share your WSDL.
You can send it to me at [email protected]
-Vishal

Document/literal web service with WSDL

Hi
I is so hard to get an easily written example of how to do a Document/literal web service in java, to generate a WSDL descripbing it and then deploying it on Apache.
I first belived that I should use JAXM. But I think it is just SOAP and there is no way to generate a WSDL file for the JAXM service, or??
It seems that u can to document/literal style using JAX-RPC, but this is VERY strange since RPC style is the direct opposite of Document style.
well, well
I would be very greatful for information here.
regards
/Rassol

JWSDP 1.2 includes the WS-I sample application in JWSDP_HOME/wsi-sampleapp. Several components of
this application use document-literal operations. The architecture of the application is described
here http://ws-i.org/SampleApplications/SupplyChainManagement/2003-04/SCMArchitecture1.0-BdAD.pdf
The WSDL for the services is availabe from URLs in the document.
As you say, the trick is generating the WSDL for a new service. You have two options: 1. Modify
existing WSDL yourself. This might be fairly easy, since the only major changes will be in the
schema. Then use a tool to generate Java source code from the WSDL. 2. Use a tool to generate WSDL
from source files.
I prefer option 1 myself, since that gives me total control over the schema. It allows me to
serialize certain parts of the SOAP message as body elements, others as attributes, and others as
header elements. Then I use the Apache Axis tool WSDL2Java with the "-s" option to generate skeleton
service files. One big advantage to this approach is that WSDL2Java generates JavaBean class for the
types in the WSDL schema, so I don't need to build the SOAP message with SAAJ. A service client
generates stubs and calls the service exactly as it would for an rpc/encoded service.
wscompile also generates service files from WSDL if you give the "-gen:server" option, but I've only
used Axis for my services.
Here's a sample WSDL for a document/literal service you can modify as you need. I checked it with
the WS-I testing tools to be sure it conforms to the WS-I Basic Profile 1.0a (available at www.ws-
i.org). Notice that the processPo operation is a request-response type operation, even though it has
a document/literal style. This follows the recommendations in the Basic Profile.
Cheers,
Mike
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://www.ltree.com/wsdl/po" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:impl="http://www.ltree.com/wsdl/po" xmlns:intf="http://www.ltree.com/wsdl/po" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://www.ltree.com/types/po" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns:tns1="http://www.ltree.com/types/po"
          xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
          targetNamespace="http://www.ltree.com/types/po"
          elementFormDefault="qualified">
     <xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/"
                 location="http://schemas.xmlsoap.org/soap/envelope/"/>
     <xsd:complexType name="LineItem">
         <xsd:sequence>
             <xsd:element name="itemId" type="xsd:string"/>
             <xsd:element name="quantity" type="xsd:int"/>
         </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="PurchaseOrder">
         <xsd:sequence>
             <xsd:element name="customerName" type="xsd:string"/>
             <xsd:element name="lineItem" type="tns1:LineItem"
                      minOccurs="1" maxOccurs="unbounded" />
         </xsd:sequence>
         <xsd:attribute name="purchaseOrderId" type="xsd:string" use="required"/>
     </xsd:complexType>
     <xsd:element name="purchaseOrder" nillable="true" type="tns1:PurchaseOrder"/>
     <xsd:complexType name="CallbackEndpoint">
         <xsd:attribute name="location" type="xsd:anyURI" use="required"/>
     </xsd:complexType>
     <xsd:element name="callbackEndpoint" nillable="false" type="tns1:CallbackEndpoint"/>
     <xsd:complexType name="PurchaseOrderAck">
         <xsd:sequence>
             <xsd:element name="poId" type="xsd:string"/>
         </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="purchaseOrderAck" nillable="true" type="tns1:PurchaseOrderAck"/>
     <xsd:complexType name="InvalidCustomerNameException">
      <xsd:sequence>
       <xsd:element name="message" nillable="true" type="xsd:string"/>
       <xsd:element name="customerName" type="xsd:string"/>
      </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="invalidCustomerNameException" nillable="true"
                  type="tns1:InvalidCustomerNameException"/>
</xsd:schema>
</wsdl:types>
   <wsdl:message name="processPoRequest">
      <wsdl:part name="callbackEndpoint" element="tns1:callbackEndpoint"/>
      <wsdl:part name="purchaseOrder" element="tns1:purchaseOrder"/>
   </wsdl:message>
   <wsdl:message name="processPoResponse">
      <wsdl:part name="purchaseOrderAck" element="tns1:purchaseOrderAck"/>
   </wsdl:message>
   <wsdl:message name="invalidCustomerNameException">
      <wsdl:part name="fault" element="tns1:invalidCustomerNameException"/>
   </wsdl:message>
   <wsdl:portType name="PurchaseOrderHandler">
      <wsdl:operation name="processPo">
         <wsdl:input message="impl:processPoRequest" name="processPoRequest"/>
         <wsdl:output message="impl:processPoResponse" name="processPoResponse"/>
         <wsdl:fault message="impl:invalidCustomerNameException" name="invalidCustomerNameException"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="PurchaseOrderHandlerPortSoapBinding" type="impl:PurchaseOrderHandler">
      <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="processPo">
         <wsdlsoap:operation soapAction="" style="document"/>
         <wsdl:input name="processPoRequest">
            <wsdlsoap:header message="impl:processPoRequest" part="callbackEndpoint" use="literal"/>
            <wsdlsoap:body parts="purchaseOrder" use="literal"/>
         </wsdl:input>
         <wsdl:output name="processPoResponse">
            <wsdlsoap:body use="literal"/>
         </wsdl:output>
         <wsdl:fault name="invalidCustomerNameException">
            <wsdlsoap:fault name="invalidCustomerNameException" use="literal"/>
         </wsdl:fault>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="PurchaseOrderHandlerService">
      <wsdl:port binding="impl:PurchaseOrderHandlerPortSoapBinding" name="PurchaseOrderHandlerPort">
         <wsdlsoap:address location="http://localhost:8080/po/services/PurchaseOrderHandlerService"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

Confusing Service Control in Workshop Tutorial

When you are adding a Service Control, Workshop Tutorial recommends to drug-and-drop
the control descriptor – the .ctrl file from another project – onto your Service
Component in the Design View. This operation confuses me because it contradicts
the Web Services principles. If the author of this tutorial intended to demonstrate
an ability of the tool to accept pre-built 3-rd party control descriptors, I think,
it would be better to demonstrate this for an Application View Control.
For Web Services, an application/user, who wants to establish communication with
a Web Service, is assumed to obtain ( find in UDDI or on a Web Site or in a Repository
) related WSDL and, then, create/build appropriate helpers to support this communication.
So, for the tutorial purposes, I suggest, the right scenario has to
1)     find the WSDL
2)     create local ( for the current project ) control descriptor, not a control
descriptor packaged into another project as it appears in existing Tutorial implementation
3)     automatically generate helper components for SOAP marshalling/unmarshalling
I have tested this scenario by copying the WSDL - CreditCardReportContract.wsdl
- into my “financialservices” project, performed WSDL-to-CTRL conversion and successfully
run it in the debugger.
I do invite your opinions on this subject!
- Michael Poulin

Since Workshop is recommended by BEA as a Web Services development tool, I think,
this topic may be shared between Web Services and Workshop newsgroups.
Point in my comment is not about ability or disability of Workshop of copying
CTRL files into your project. I tried to explain that this feature is inadequate
to Web Services in general if it substitutes WSDL.
I would certainly agree with and appreciate a feature that allows me, as a developer,
to reuse already existing Control Descriptor available in MY environment. However,
the Tutorial does not teach “to copy the control's CTRL file to a common folder”.
Instead, it follows the statement: “If the control will be used only by a single
web service in your project, you may choose to copy the CTRL file to the same
folder as your web service”. I doubt that the statement represents Best Practices
– it couples projects by a derivative, not by the resource. That is, if WSDL has
been changed, the 3-rd project can re-build CTRL file for itself, you project
gets into troubles ( it is obvious, right ? ).
Using Workshop, I am trying to understand how BEA recommends working with Web
Services. I recognize the power of Connector architecture and common approach
to resources accessibility represented by CTRL files. At the same time, I see
that a repository of CTRL files for Web Services can shield developers from Web
Services in WebLogic environment. If this is an accidental consequence, it has
to be clearly explained, if not fixed; if it is an intention, I would like to
hear the BEA comments on how this relates to known WSDL repositories, other standards,
and reliability of Web Services in the enterprise environment, at least.
Thank you,
- Michael
"Anurag Pareek" <[email protected]> wrote:
Michael,
For questions regarding Workshop, I will suggest you to post to the
'weblogic.developer.interest.workshop' newsgroup.
Regarding this query, the docs do state explicitly the following, which
I
guess addresses your concern:
If the CTRL file for the control you wish to use is not in your project,
you
must copy it to your project. The destination to which you copy the control
depends on your expected usage. If the control will be used only by a
single
web service in your project, you may choose to copy the CTRL file to
the
same folder as your web service. If multiple web services in different
folders in your project may use the control, you may wish to copy the
control's CTRL file to a common folder. Remember that the CTRL file must
be
in your WebLogic Workshop project.
Wherever you decide to place the control's CTRL file, it must be in your
WebLogic Workshop project.
Do let me know if you have further inputs.
Regards,
Anurag
"Michael Poulin" <[email protected]> wrote in message
news:[email protected]...
When you are adding a Service Control, Workshop Tutorial recommendsto
drug-and-drop
the control descriptor - the .ctrl file from another project - ontoyour
Service
Component in the Design View. This operation confuses me because itcontradicts
the Web Services principles. If the author of this tutorial intendedto
demonstrate
an ability of the tool to accept pre-built 3-rd party control descriptors,I think,
it would be better to demonstrate this for an Application View Control.
For Web Services, an application/user, who wants to establishcommunication with
a Web Service, is assumed to obtain ( find in UDDI or on a Web Siteor in
a Repository
) related WSDL and, then, create/build appropriate helpers to supportthis
communication.
So, for the tutorial purposes, I suggest, the right scenario has to
1) find the WSDL
2) create local ( for the current project ) control descriptor, nota
control
descriptor packaged into another project as it appears in existingTutorial implementation
3) automatically generate helper components for SOAPmarshalling/unmarshalling
I have tested this scenario by copying the WSDL -CreditCardReportContract.wsdl
- into my "financialservices" project, performed WSDL-to-CTRL conversionand successfully
run it in the debugger.
I do invite your opinions on this subject!
- Michael Poulin

Invoking a web Service using Service Control

Hi All,
I am getting the below exception when I am trying to execute a process containing a simple Service Control generated using a WSDL file.
Any thoughts/solutions is appreciated.
Exception in getPendingOrdersForApprover
com.bea.control.ServiceControlException: Unexpected exception raised invoking getPendingOrdersForApprover on control com.verisign.controls.MSL_ORDERSoapServiceControl. Use getCause() to see the root cause.[java.rmi.RemoteException: Failed to invoke; nested exception is:
weblogic.wsee.handler.InvocationException: [Client CodecHandler]Failed to decode]
Caused by: java.rmi.RemoteException: Failed to invoke; nested exception is:
weblogic.wsee.handler.InvocationException: [Client CodecHandler]Failed to decode
... 38 more
Caused by: weblogic.wsee.handler.InvocationException: [Client CodecHandler]Failed to decode
... 44 more
Caused by: weblogic.wsee.codec.CodecException: Found more elements in the soap envelope than required by WSDL:{ld:Physical/MSL_ORDER}MSL_ORDER. WSDL Message for this operation is: (WsdlBindingMessage@20764897 <name=> <type=1> <extensionList=(NameValueList@29534392 <list[]{(SoapBody@13827654 <encodingStyle=null> <use=literal> <namespace=null> <parts=null>)}>)>)
... 53 more
at com.bea.control.servicecontrol.impl.ServiceControlImpl.invoke(ServiceControlImpl.java:678)
at com.verisign.controls.MSL_ORDERSoapServiceControlBean.getPendingOrdersForApprover(MSL_ORDERSoapServiceControlBean.java:323)
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:585)
at com.bea.wli.knex.runtime.jcs.container.JcsProxy.invokeBeehiveControl(JcsProxy.java:666)
at com.bea.wli.knex.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:446)
at $Proxy71.getPendingOrdersForApprover(Unknown Source)
at com.verisign.processes.WebServiceInvokeProcess.mSL_ORDERSoapServiceControlGetPendingOrdersForApprover(WebServiceInvokeProcess.jws:48)
Thanks,
Ram

I solved the problem :-)
it happened due to JAVA_HOME env var. It has to point to jdk that comes along with wl812. mine was pointing to sun jdk 1.4.2. However, this is a bug, because, for wlwlbuild task , i was setting the proper bea java home, still it was failing due to system java_home var. And i did not face this problem with WL813. After facing lot of issues with 812, now i feel, 812 is not a stable production version.
Anyways, now the prob;em is solved.

Service Control

Hello,
We've created a proxy service using AquaLogic Service Bus. Using ALSB's test console we've verified that the proxy service works fine when provided XML that conforms to the WSDL's schema.
We then created a page flow portlet in workshop that is supposed to call the proxy service using a service control based on the WSDL just mentioned. So we have a form with all the parameters needed to complete the request. When we actually submit the form, ALSB complains that the SOAP request received does not conform to the WSDL. We looked in ALSBs log, and we found that the request coming in looked quite different from the one that is generated when using ALSBs test console.
Could someone tell me why this is happening and how to solve it? Has anyone successfully called an ALSB proxy service from a portlet using a service control? Are there better ways to achieve this?
Thanks.
Edited by yosri2007 at 04/16/2008 7:43 AM

Hi Oliver,
What I understood is that earlier you were using the wls8.1 to invoke webservice and it was working but when you upgrade it to 9.2 then it is not working. And since you have to use the wsdl generated by your legacy systems so I guess you might be using Ant tasks. If I'm correct then from the exception it seems the client that is created is not able to de-serialize the complex types. I know u wud be knowin but have you checked the client generated by 8.1 and that generated by 9.2. Have you updated your ClientGenTask class because the 8.1 ClientGenTask is available in wls9.2 but it has been deprecated. So BEA recommends to update the class to 9.2 "weblogic.wsee.tools.anttasks.ClientGenTask"
Hope this helps...
http://e-docs.bea.com/wls/docs92/pdf/webserv.pdf
But hey you are using ServiceControl then i think weblogic wud be generating the client for you right. Well I have never used ServiceControl I've also faced a problem in compatibility. So when I used the ant tasks it worked and that too of wls8.1 task. Can you do one thing if you can create your client using ant task and check whether it wud work out(just curious). And pls use either version of the clientgentask. Hope it may work...
If using ant task is not a gud practice in wlp then please correct :) I too need to get myself clear...
Thanks

Generic Service Control WSDL

Similar Messages

Maybe you are looking for