Calling a weblogic control from a MDB in 10.3

We have a requirment of calling a weblogic control from a MDB. There is a option to call this using Controls.instantiate. However, the secound level controls are not getting called. It means, I have a Facade, DAO and DB controls [Tipically the Design patern implementation]. I am calling the DAO from Facade and the DAO calls DB.
when i am trying to call a Facade from a MDB using the Controls.instantiate, the facade is getting called but depending controls are not getting called.
Please suggest how we can approch this. Is there any way to call a control from a MDB using anotations?
Thanks,

Hi Srini,
it supports but you need to upgrade correctly.
follow this link
Beehive Applications
after upgrade if you found some error like classnotfound error.
If those are the errors you were also experiencing, then please follow one of these options to resolve this issue:OPTION
1:Identify all the JARs that contain the beehive classes and explicitly add the jar files to the classpathOPTION
2:When you created the domain (if you used the Config Wizard), do you make it a "Workshop" domain? If not, try that.That should deploy the Workshop framework (Beehive controls, NETUI, etc) libraries as shared libraries. Then these libraries should be referenced in your applications weblogic.xml and weblogic-application.xml.
regards,
Kal

Similar Messages

  • Is it possible to call a activeX control from PL/SQL...?

    Hi all,
    Is it possible to call a activeX control from PL/SQL...? If yes, please give me sample code or any link.
    Thanks,
    Pal

    The LoadLibrary() Win32 call is used to find the physical DLL and load it into memory. This API call first look in the current directory for the file, and then uses the PATH environmental variable to try and find the file.
    Thus you need to make sure PATH is properly set. A Win32 process runs in a 32bit VM (Virtual Machine). Been a very long time since I did Windows server side development, but as I recall this VM inherits the default o/s environment (unlike Unix where the parent process environment is inherited).
    You can set the environment using the Properties menu of the System desktop icon (or via Control Panel).
    However.. Oracle does not run as your user. Typically it is installed as the o/s user Oracle and this user owns all the Oracle processes (listener, instance, etc).
    So you will need to make sure that this user's environment is correctly configured... Further more than this, I'm out of my depth. Did a lot of Windows stuff back in the 90's, but for many years now I'm only using Unix/Linux professionally - with Windows being my console platform for playing games at home. :-)
    On the Linux/Unix side, I configure the environment variable via the Listener. E.g. Under the entry SID_LIST_LISTENER, I configure the external procedure handler as follows:
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME=/tjs-dev/app/oracle/product/10.2.0)
    (PROGRAM = extproc)
    (ENVS = "EXTPROC_DLLS=ANY")
    )No idea how this applies and works on the Windows side.

  • Calling a Weblogic Servlet from a CGI

    Hello,
              I need to call a WL servlet from a CGI and having problems with the URL
              enconding.
              It's necessary to add a null character to the URL in the CGI script?
              Thanks in advance
              [email protected]
              

    Hi!
    I believe U can call ur servlet by appending "servlet" just before servlet1 .
    That is
    ur URL should be
    http://<host:port>/servlet/servlet1/<File .........>
    I was facing the same problem and it worked fine..........
    Why JDev9i appends "/servlet" and how to remove this is so that I can have whatever path I can is still a mystery..
    If u have a work around. Do share with me...
    Cheers
    Abhishek
    mail: [email protected]

  • Accessing weblogic controls from pojo classes problem

    Hi,
    I'm planning to use DAO class as a wrapper over the beehive controls , and all of this will be part of the workshop utility project.
    When I try using this way the controls never gets instantiated by the container and end up getting NullPointerException.
    For this to work do I need to sort the programmatic control invocation ? If yes are there samples available ?
    Can you also suggest if this is the right approach?
    Are we stuck with using JPF for invoking beehive controls?
    Thanks,
    Chris

    It is possible for some controls. See http://beehive.apache.org/docs/1.0.2/controls/programming.html#Programmatic+Instantiation, which has some sample code.
    Greg

  • Not able to Call JDBC control from MDB

    I need to call a method in the JDBC control from the Message Driven Bean(MDB). When I try to do so, Weblogic throws an error. I tried to call a Custom Control from MDB and the Custom Control called a method in the JDBC control but that does not work too. Can someone help me solve this?
    Can't we call the JDBC control from MDB? There should be some way around this.
    This is the error I get :
    org.apache.beehive.controls.api.ControlException: Control initialization failure[org.apache.beehive.controls.api.ControlException: Contextual service org.apache.beehive.controls.api.context.ResourceContext is not available]
         at org.apache.beehive.controls.runtime.bean.ControlBean.ensureControl(ControlBean.java:326)
         at com.boehringer.supplier.control.db.ForecastJDBCControlBean.updateSpendWithCMId(ForecastJDBCControlBean.java:2879)
         at com.boehringer.supplier.control.java.SupplierControlImpl.processCustomer(SupplierControlImpl.java:1290)
         at com.boehringer.supplier.control.java.SupplierControlImpl.processSonicInboundMessage(SupplierControlImpl.java:1096)
         at com.boehringer.supplier.control.java.SupplierControlBean.processSonicInboundMessage(SupplierControlBean.java:663)
         at com.boehringer.sonic.SonicVendorInboundMDB.onMessage(SonicVendorInboundMDB.java:45)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
         at weblogic.ejb.container.internal.ContinuousJMSMessagePoller.processOneMessage(ContinuousJMSMessagePoller.java:138)
         at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:404)
         at weblogic.ejb.container.internal.ContinuousJMSMessagePoller.pollForParent(ContinuousJMSMessagePoller.java:213)
         at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:543)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: org.apache.beehive.controls.api.ControlException: Contextual service org.apache.beehive.controls.api.context.ResourceContext is not available
         at org.apache.beehive.controls.system.jdbc.JdbcControlImplInitializer.initServices(JdbcControlImplInitializer.java:50)
         at org.apache.beehive.controls.runtime.bean.ImplInitializer.initialize(ImplInitializer.java:34)
         at org.apache.beehive.controls.runtime.bean.ControlBean.ensureControl(ControlBean.java:321)
         ... 12 more

    Hi,
    I am getting the same error. Did you got any solution for this?
    Please help.
    Any kind of help is appreciated.
    Thanks,
    Dpak

  • Programatically calling Web Service DataControl from App Module

    Hey,
    I've been following the 4GL ADF tutorial recently but have a question regarding initiating a web service call instead of using an entity object. The tutorial I am using is located at:
    http://www.oracle.com/technology/products/adf/learnadf.html
    On Page 102 - Adding Custom Methods to the Application Module there is a little piece of code to transfer some data from a transient view object into an entity object. The code is
    public void createNewServiceRequestFromGlobals() {
    ServiceRequestImpl sr =
    (ServiceRequestImpl)getDBTransaction().createEntityInstance(ServiceReques
    tImpl.getDefinitionObject(),null);
    Row globalsRow = getGlobals().first();
    sr.setProblemDescription((String)globalsRow.getAttribute("ProblemDescript
    ion"));
    sr.setProdId((Number)globalsRow.getAttribute("ProductId"));
    getDBTransaction().commit();
    What I would really like to be able to do is use a web service datacontrol instead of the entity object. Can anyone point me in the right direction?
    Thanks,
    Mark

    I have the same problem
    1. I have a data control what is a web service client to URL https:
    2. JDev 11g build a model
    3. I need to call this data control from java class
    4. My java class simply must call a method of the web service, this method I see in the DAta Control, with the parameter and just return the String,
    5. this is not a Web Application, is swing, I not have a Context
    method in WS
    public String ConsultaPlaca(String arg1);
    How I can implement this?
    Just in Java Class, not in page JSP. the java class is a library of other Java class, I need to build a file .jar

  • Calling a WebLogic web service from a WebLogic web application

    We would like to call a WebLogic web service from WebLogic web application. The current architecture looks like:
    LoadBalancer--->iPlanet-1/iPlanet-2--->Firewall--->WebLogic-AppServer-1/WebLogic-AppServer-2
    The web application and web service are in the same WebLogic cluster. We would prefer that the web services do not get published externally.
    Does the WebLogic web application need to make a call back outside the firewall to the load balancer?
    Is there a way the web services can be called locally with load balancing?
    Can web service calls be made over the t3 protocol?
    Thanks,
    Mike

    I think one solution is to use a Java proxy to call the Web services.
    In the Java proxy you can have a method that accepts the user/pass and sets them correctly for the Web service.
    Then you expose that Java proxy as a data control (right click, create data control) - and then create a page that invokes that method.
    (For the basics of working with a POJO data control see: http://blogs.oracle.com/shay/2009/07/java_class_data_control_and_ad.html )

  • Error in  holder-of-key  : calling a secure webservice from weblogic instan

    Hi,
    I am getting following error . Can somebody decrypt this for me ?
    ava.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [Failed to add Signature.] FaultActor [null]No Detail; nested exception is:
         weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: Failed to add Signature.
         at services.SSOTestHelloWorld_Stub.hello(Unknown Source)
         at deloitte.iit.webservices.CallWebService.callService(CallWebService.java:31)
         at jsp_servlet.__clienttest._jspService(__clienttest.java:82)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: Failed to add Signature.
         at weblogic.wsee.codec.soap11.SoapCodec.decodeFault(SoapCodec.java:355)
         at weblogic.wsee.ws.dispatch.client.CodecHandler.decodeFault(CodecHandler.java:115)
         at weblogic.wsee.ws.dispatch.client.CodecHandler.decode(CodecHandler.java:100)
         at weblogic.wsee.ws.dispatch.client.CodecHandler.handleFault(CodecHandler.java:88)
         at weblogic.wsee.handler.HandlerIterator.handleFault(HandlerIterator.java:309)
         at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:269)
         at weblogic.wsee.ws.dispatch.client.ClientDispatcher.handleResponse(ClientDispatcher.java:213)
         at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:150)
         at weblogic.wsee.ws.WsStub.invoke(WsStub.java:87)
         at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:337)
         ... 18 more
    Caused by: weblogic.xml.crypto.wss.WSSecurityException: Failed to add Signature.
         at weblogic.wsee.security.wss.SecurityPolicyDriver.processIntegrity(SecurityPolicyDriver.java:240)
         at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(SecurityPolicyDriver.java:74)
         at weblogic.wsee.security.WssClientHandler.processOutbound(WssClientHandler.java:71)
         at weblogic.wsee.security.WssClientHandler.processRequest(WssClientHandler.java:55)
         at weblogic.wsee.security.WssHandler.handleRequest(WssHandler.java:74)
         at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
         at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:107)
         at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:132)
         ... 20 more

    Hi Stephen,
    Using a registry, for example UDDI [1], would be one solution. WLS has
    a complete UDDI implementation builtin [2] for this purpose.
    You are correct, you need to pass the service address location found in
    the <service> section of the WSDL.
    Hope this helps,
    Bruce
    [1]
    http://www.uddi.org/
    [2]
    http://e-docs.bea.com/wls/docs81/webserv/uddi.html
    Stephen Kurlow wrote:
    >
    I am not sure what I need to do to be able to call a remote webservice (runs on
    another weblogic server instance running on another machine in the same network)
    from within a webservice. I have 2 wsdl files and I have created webservice controls
    from them. I have successfully written code in the first webservice to instantiate
    the parms to the 2nd webservice and invoked the 2nd webservice when both webservices
    are deployed to the same weblogic server instance. So i can see the params being
    marshalled and unmarshalled in the test browser.
    Now how do I install the 2nd webservice on another weblogic server instance and
    instruct the 1st web service to call the 2nd webservice residing on another weblogic
    server instance? I presume some kind of lookup (url?) is needed and is it via
    what is contained in the wsdl file?
    Thanks in advance,
    Stephen Kurlow

  • Calling Service Control from Page Flow

    In Workshop for Weblogic Platform v10.0, we have a web service control in a page flow.
    Although the web service call succeeds (as evidenced by a TcpMon monitor), the control method always returns null.
    I'm guessing that although the call looks synchronous, it's actually behaving asynchronously - returning immediately with null.
    Is this perhaps related to the particulars of calling controls from a Page Flow environment? Is it a bug in v10 of Workshop (Eclipse-based?
    Thanks for any ideas!
    - Rob
    ps: Here's the control interface and using class:
    package controls;
    import com.bea.control.ServiceControl;
    import org.apache.beehive.controls.api.events.EventSet;
    import org.apache.beehive.controls.api.bean.ControlExtension;
    @ServiceControl.Location(urls = {"http://LECAP1.lan.us.ray.com:9905/xsltTransform_vs0"})
    @ServiceControl.HttpSoapProtocol
    @ServiceControl.SOAPBinding(style = ServiceControl.SOAPBinding.Style.DOCUMENT, use = ServiceControl.SOAPBinding.Use.LITERAL, parameterStyle = ServiceControl.SOAPBinding.ParameterStyle.BARE)
    @ServiceControl.WSDL(resourcePath = "controls/cesXsltTransform.wsdl", service = "xsltTransform_vs0")
    @ControlExtension
    public interface xsltTransform_vs0ServiceControl extends ServiceControl
    static final long serialVersionUID = 1L;
    public java.lang.String xmlTransform(com.raytheon.schemas.ces.transformationservices.xmlschema.schema.TransformInput transformInput_arg);
    /** This event set interface provides support for the onAsyncFailure event.
    @EventSet(unicast=true)
    public interface Callback extends ServiceControl.Callback {};
    @Control
    private xsltTransform_vs0ServiceControl xsltTransform_vs0ServiceControl1;
    com.raytheon.schemas.ces.transformationservices.xmlschema.schema.TransformInput transformInput_arg = form
                        .getTransformInput_arg();
    String xmlTransformResult = xsltTransform_vs0ServiceControl1
                        .xmlTransform(transformInput_arg);

    Strange -- the PageFlowJspFilter adds no-cache headers to the response, so
    if you're forwarding to a JSP from the action, then the browser shouldn't be
    caching the result. What's in the URL bar in the case where your request is
    getting cached?
    "Neeraj Harlalka" <[email protected]> wrote in message
    news:3ff993bd$[email protected]..
    >
    Richard -
    Ok. I dug deeper into the issue and now my problem is that although theaction
    is getting called correctly, it seems to execute from a cache. The actiondoes
    not get executed the second time.
    Any ideas?
    Neeraj
    "Richard Feit" <[email protected]> wrote:
    Hmm... I'm not sure why you'd get that. Can you post the relevant JSP
    code?
    Also, are you able to hit the other page flow directly from a browser?
    Rich
    "Neeraj Harlalka" <[email protected]> wrote in message
    news:[email protected]..
    Hi Richard -
    I get an error saying cannot find the begin.do action.
    Thanks
    Neeraj
    Richard Feit" <[email protected]> wrote:
    Hello Neeraj,
    This should work:
    <netui:anchor
    href="/someOtherFlow/SomeOtherFlowController.jpf">someOtherFlowController.
    j
    p
    f</netui:anchor>
    What happens when you do this?
    Rich
    "Neeraj Harlalka" <[email protected]> wrote in message
    news:3fda39df$[email protected]..
    I read the other posts on how to call one page flow from a jsp
    that
    belongs to
    another pageflow. However the last suggestion posted - use the netuianchor tag
    with href, also does not work.
    Any other solution?
    Thanks
    Neeraj

  • Weblogic call a excel-file from URL doesn't open MSExcel but flat html

    Weblogic call a excel-file from URL doesn't open MSExcel but flat html
    Hi,
    WLS 10.3.5
    Forms 11.1.1.4
    I do migrate from AS10g to WLS 10.3.5 / Forms 11
    I get differences between FORMS 10 g / AS and FORMS 11 / WLS
    when call an excel-file with web.showdocument
    in 10g AS10g
    the call
    web.showdocumen('http://MyAS10_Server/myFormsMapping/myExcelfile.xls, _blank);
    opens a Windows-Box
    to decide
    open with ( MSExcel )
    or
    download and save as File
    in WLS 10.3.5 / FORMS 11.1.1.4
    the call with webcache Port 8090 as well as Port OHS 8888
    web.showdocumen('http://MyWLS_Server:8090/myFormsMapping/myExcelfile.xls, _blank);
    opens promptly the excel-File into the Browser as html-Format
    How to get the same way under WLS as before in AS 10g,
    config OHS ?
    regards
    get answer here :
    Weblogic: when call a excelfile from URL doesn't open MSExcel but flat html
    Edited by: astramare on Sep 12, 2011 11:59 AM

    Weblogic: when call a excelfile from URL doesn't open MSExcel but flat html

  • 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-

  • Calling Oracle Stored Procedure from Weblogic.

    Hi All,
    I am using Oracle 11g R2 and weblogic 10.3.5.0
    Do you know if it is possible to call a stored procedure from Weblogic.
    Basically, what I would like to do is to call the following procedure : EXEC DBMS_SESSION.SET_IDENTIFIER('provider_a') when my application connects to my database, "provider_a" being the user used to connect to the oracle schema.
    Thanks.

    Up !
    Thanks.

  • What the best way to call twenty tuxedo domains from one weblogic server use WTC

    I need to call twenty tuxedo domains from one weblogic server use
    WTC. the Service be called in the twenty tuxdo domains are same, do I need to
    write twenty EJB in the weblogic server to call the same service? who have good
    adea to deal with this problem?

    Hi,
    I have a question on the second case. When the client doesn't care of which
    Tuxedo domain it is hitting. What happens if one of the Tux domain is down ? What
    happens to the client request to that domain ?
    Another question is lets say i have a Tuxedo configuration as MP mode( Multi
    machine mode) how does WTC load balance between the Tuxedo domains.
    Thanks,
    Srinivas
    "A. Honghsi Lo" <[email protected]> wrote:
    Hi xcjing,
    One way to handle your needs is to use local service name to remote
    reservice name translation. For instance,
    (in 6.1,6.0 WLS)
    <T_DM_IMPORT ResourceName="TOUPPER1" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM1">
         <RemoteName>TOUPPER</RemoteName>
    </T_DM_IMPORT>
    <T_DM_IMPORT ResourceName="TOUPPER2" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM2">
         <RemoteName>TOUPPER</RemoteName>
    </T_DM_IMPORT>
    <T_DM_IMPORT ResourceName="TOUPPER3" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM3">
         <RemoteName>TOUPPER</RemoteName>
    </T_DM_IMPORT>
    etc
    With this configuration if your client have to call "TOUPPER" service
    in
    TUX-DOM1 then you code your client to call "TOUPPER1" and the request
    will be routed to TUX-DOM1. The same way for request has to go to
    TUX-DOM3, your client calls "TOUPPER3" service and WTC will route it
    to
    TUX-DOM3. In this remote name translation you may have to write 20 EJB
    although they are almost the same. However, if your EJB can analyze
    your client input to decide which Remote Tuxedo Domain to send the
    service request to then you probably only need one EJB.
    In the case that your client does not care which remote Tuxedo Domain
    provides the service then adding
    <T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM1">
         <RemoteName>TOLOWER</RemoteName>
    </T_DM_IMPORT>
    <T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM2">
         <RemoteName>TOLOWER</RemoteName>
    </T_DM_IMPORT>
    <T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM3">
         <RemoteName>TOLOWEr</RemoteName>
    </T_DM_IMPORT>
    etc
    Will load balance your client "TOLOWER" service request among your 20
    remote Tuxedo Domain.
    However, there is a bug in WTC that causes the Remote Service Name
    translation functionality not working properly. It is fixed in the
    upcoming release of WLS.
    Honghsi :-)
    xcjing wrote:
    Thank you very much! But I still have question, give an example,
    twenty Tuxedo domain is named domain1,domain2,....domain20. The
    same Tuxedo Service: TOUPPER is deploy on those twenty Tuxedo domains,some time
    I need call the TOUPPER Service on domain1,saome time I need call theTOUPPER
    Service on domain3 or
    other domain depend on the input from client. you mean I need to importThe TOUPPER
    Service from twenty Tuxedo domains in the console,then write one EJBto call the
    TOUPPER Service,but how can the EJB know which Tuxedo domain's TOUPPERto call
    from?
    Thank you!
    "A. Honghsi Lo" <[email protected]> wrote:
    hi xcjing,
    You don't have to write 20 beans or deploy 20 beans because there
    are
    20
    remote Tuxedo TDomain you need get the service from. Of course, WLSand
    WTC does not prohibit you from doing it though. Whether you need20
    beans or not depend more on you architecture.
    To access 20 remote Tuxedo Domain from one single WLS with singleWTC
    you can configure 20 remote Tuxedo Domain in the BDMCONFIG (6.1,6.0)
    or
    from the console (7.0). You import 20 services one from each remote
    Tuxedo domain. You write one bean, and deploy one bean. Your WLS
    clients will be able to access THE ejb, the EJB will access the WTC
    service, and WTC will load balanced the service requests among the20
    remote Tuxedo Domain.
    Regards,
    honghsi :-)
    xcjing wrote:
    I need to call twenty tuxedo domains from one weblogic server use
    WTC. the Service be called in the twenty tuxdo domains are same,
    do
    I need to
    write twenty EJB in the weblogic server to call the same service?
    who
    have good
    adea to deal with this problem?

  • Call another WebLogic's EJBs from resource adapter?

              Is it possible to call another WebLogic's EJBs from a resource adapter?
              A call to the javax.naming.InitialContext(Hashtable environment) results in a
              VersioningError:
              weblogic.common.internal.VersioningError: Incompatible service packs in CLASSPATH:
              (BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 , 6.1.4.0)
              not compatible with
              (BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
              at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
              at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
              at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
              at weblogic.kernel.Kernel.initialize(Kernel.java:122)
              at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
              at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
              at java.lang.Class.newInstance0(Native Method)
              at java.lang.Class.newInstance(Class.java:232)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              at javax.naming.InitialContext.init(InitialContext.java:217)
              at javax.naming.InitialContext.<init>(InitialContext.java:193)
              at java.lang.reflect.Constructor.newInstance(Native Method)
              I'm not sure it will always be possible to match the version, although here upgrading
              the SP3 to SP4 will probably be done soon.
              Does anyone have experience with this?
              Or better: is there any documentation on this issue?
              

              Hi Hans,
              Here is the link for Weblogic SP3 / SP4 vulnerability and comparison for
              http://216.239.53.104/search?q=cache:RqqaQ3HZdwoJ:www.nipc.gov/cybernotes/2003/cyberissue2003-06.pdf+Versioning+Error+in+BEA+weblogic+6.1+SP3+and+SP4&hl=en&ie=UTF-8
              Hope this will help you.
              Let me know if u have any further problems.
              rgds
              KSK
              "Hans Bausewein" <[email protected]> wrote:
              >
              >
              >Is it possible to call another WebLogic's EJBs from a resource adapter?
              >
              >A call to the javax.naming.InitialContext(Hashtable environment) results
              >in a
              >VersioningError:
              >
              >weblogic.common.internal.VersioningError: Incompatible service packs
              >in CLASSPATH:
              >(BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 ,
              >6.1.4.0)
              >not compatible with
              >(BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
              > at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
              > at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
              > at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
              > at weblogic.kernel.Kernel.initialize(Kernel.java:122)
              > at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
              > at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
              > at java.lang.Class.newInstance0(Native Method)
              > at java.lang.Class.newInstance(Class.java:232)
              > at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
              > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              > at javax.naming.InitialContext.init(InitialContext.java:217)
              > at javax.naming.InitialContext.<init>(InitialContext.java:193)
              > at java.lang.reflect.Constructor.newInstance(Native Method)
              >
              >
              >
              >I'm not sure it will always be possible to match the version, although
              >here upgrading
              >the SP3 to SP4 will probably be done soon.
              >
              >Does anyone have experience with this?
              >
              >Or better: is there any documentation on this issue?
              >
              

  • Calling Data Control from Session bean

    Is it possible to use workshop data control from with in Session bean.

    If the client code is located in the same "deployment unit" (e.g. EAR
    file) as the EJBs, then you can pass the data by reference.
    Serialization is required when crossing between deployment units. This
    is required to support redeployment.
    Hyung-Jin Kim wrote:
    I recently downloaded WL6.0 and I noticed that when a
    session bean returns data to its client, the data is
    always serialized back the client -- EVEN it the client
    is on the same machine. Ideally, I would prefer that a
    reference to the data simply be returned to the client.
    Does the serialization occur because WL6.0 put session
    beans in its own ClassLoader or does the serialization occur
    because of the way WL6.0 compiles the RMI stubs? Thanks
    for your response.
    -hjk

Maybe you are looking for