Disabling transactions from WLI Workshop Web Service application?

I need to disable the transactions from a Workshop generated Web Service for WLI (Workshop 8.1.6).
I can accomplish this by changing and repackaging the builded EAR-package by altering the ejb-jar.xml:s in the .workshop directory and setting the transactions from Required to NotSupported. It would be much more convenient, if I could do that change from the Workshop.
Actual question: is there a way to disable transactions from a Web Service in Workshop? I have not found any place to change this property.

Hi
You have 2 options.
As you mentioned you can modify the generated ejb descriptors. Unfortunately this attribute is not exposed as a property in the workshop, so you cannot change there.
Other option is to suspend the transaction created by workshop so that your webservice functionality or any control called within that won't be part of the workshop transaction.
More info at http://forums.bea.com/bea/message.jspa?messageID=600045134&tstart=0
Thanks
Vimala

Similar Messages

  • How to disable default logging for workshop web services

    Hi there,
    We have created a web service using WL Workshop that we want to deploy to a production server. The problem is that the destination server is not using a default log4j library for the server, but each application initiates its own library.
    When we try to deploy the web service onto the production server, we are getting an error of a log4j/Appender class not found. We can solve the problem by adding any log4j library to the class path at the beginning, but that will cause compatilibity problems with existing applications.
    Is there any way to disable the default web services logging? It looks like the knex library is trying to instantiate this class at deployment. Any way we can disable that option?
    Thanks

    Thanks David for your reply,
    That is indeed what I am trying to do: to add all required libraries within my web-inf folder.
    But it seems that the server itself expects the log4j library to be loaded when the server is initiated. It looks to me that some server-level listener for the web services is starting together with the domain and tries to access the log4j library. This library is not found because it is inside the web-inf folder of my application.
    I do not see any error while starting the server. The error only appears when trying to deploy the application (ear) with the web service. It seems that I am forgetting something, but unless I include the log4j.jar in the classpath when I start the server, i will not be able to avoid the error.
    Suggestions and tests are much welcome.
    thanks!

  • (266758030) Can WebLogic Workshop Web Services be deployed on a different Application Server?

    (266758030) Q(asked by Lalit Sudan): Can WebLogic Workshop Web Services be deployed
    on a different Application Server?
    A(by Adam Fitzgerald): .jws files are not yet an accepted standard so you can expect
    that the WebLogic Workshop Web Services cannot be ported to other Application Servers,
    however, it is a general goal to expand the functionality of the Workshop tool for
    other App Servers.

    Just so you'll know Oracle9iAS also includes apache as the HTTP server.
    As Suncan said, if you want to use Forms on the Web you need the Forms Server engine, and it comes bundled in Oracle9iAS. You'll save yourself a lot of headache if you just install Oracle9iAS and have everything pre-configured for you thus reducing maintanance costs.

  • Web service application instance

    I am building a LV2009 web services application (main.exe + web services).  The web service VI's share globals with the main.exe.  I think that the web services run under a separate application instance, therefore using globals will not work directly.  My idea was to wrap the global calls on the web service side inside of VI server calls to main.exe.
    Here's what I was thinking:
    So, to get this to work properly, I open an application reference (default port 3363) and VI reference (VI is in memory in the main.exe).  I read the global control value, close the references, and convert the control value into the correct data type.
    From all that I read, I should be able to do all this within the LabVIEW development environemnt with the service deployed to the local machine. My LV has both the web server and VI server (port 3363) enabled.
    I built and deployed the service VI after first disabling the VI server within the service's project (I'm not really sure that this really matters).
    I run my main.exe (.vi) and attempt to call the service, but I get error 1004 (Open VI Reference - VI not in memory).
    I guess my problem seems to lay around the "Open Application"...how should I open an application reference from a web services VI?
    TIA,
    James
    Solved!
    Go to Solution.

    Even though it's on the local machine, you need to supply the machine name or IP address ("localhost" should work).  Otherwise you'll just get a connection to the local application instance (see the help), which, of course, doesn't help you communicate across instances.

  • Problem in deploying Web Service Application on Weblogic Server

    Hi,
    I am trying to develop a web service application with eclipse, all things goes correct and wsdl also gets formed but the problem occurs when the EAR is deployed. It gives error in publishing the EAR file.
    Here is the error i am getting:
    Module named 'ftooldev1EAR' failed to deploy. See Error Log view for more detail.
    *weblogic.application.ModuleException: [HTTP:101064][WebAppModule(ftooldev1EAR:/ftooldev1)] Error parsing descriptor in Web appplication "D:\eclipse_wspace1\ftooldev1\build\jws\weboutput"*
    *com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    *     at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)*
    *     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)*
    *     at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)*
    *     at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)*
    *     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)*
    *     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)*
    *     at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)*
    *     at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)*
    *     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)*
    *     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)*
    *     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)*
    *     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)*
    *     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)*
    *     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)*
    *     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)*
    *     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)*
    *     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)*
    *     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)*
    *     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)*
    *     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)*
    *     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)*
    *     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)*
    *     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)*
    *     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)*
    *     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)*
    *     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)*
    *     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)*
    *     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)*
    *     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)*
    *     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)*
    *     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)*
    *     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)*
    *     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)*
    *     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)*
    *     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)*
    *     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)*
    *     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)*
    *     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)*
    *     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)*
    *     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)*
    *     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)*
    *     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)*
    *     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
    *invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1566)
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1346)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:803)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:623)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:516)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
    at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
    at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1075)
    at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:132)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
    *Caused by: weblogic.application.ModuleException: [HTTP:101064][WebAppModule(ftooldev1EAR:/ftooldev1)] Error parsing descriptor in Web appplication "D:\eclipse_wspace1\ftooldev1\build\jws\weboutput"*
    *com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    *invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    at weblogic.servlet.internal.WebAppModule.createModuleException(WebAppModule.java:1511)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1247)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    *Caused by: com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
    Here is the web.xml of my application:
    *<?xml version="1.0" encoding="UTF-8"?>*
    *<web-app xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"*
    xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    *<servlet>*
    *<servlet-name>action</servlet-name>*
    *<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>*
    *<init-param/>*
    *</servlet>*
    *<servlet>*
    *<javaee:display-name>Apache-Axis Servlet</javaee:display-name>*
    *<servlet-name>AxisServlet</servlet-name>*
    *<servlet-class>org.apache.axis.transport.http.AxisServlet</servlet-class>*
    *</servlet>*
    *<servlet-mapping>*
    *<servlet-name>AxisServlet</servlet-name>*
    *<url-pattern>/servlet/AxisServlet</url-pattern>*
    *</servlet-mapping>*
    *<servlet-mapping>*
    *<servlet-name>AxisServlet</servlet-name>*
    *<url-pattern>*.jws</url-pattern>*
    *</servlet-mapping>*
    *<servlet-mapping>*
    *<servlet-name>AxisServlet</servlet-name>*
    *<url-pattern>/services/*</url-pattern>*
    *</servlet-mapping>*
    *<servlet>*
    *<javaee:display-name>Axis Admin Servlet</javaee:display-name>*
    *<servlet-name>AdminServlet</servlet-name>*
    *<servlet-class>org.apache.axis.transport.http.AdminServlet</servlet-class>*
    *<load-on-startup>100</load-on-startup>*
    *</servlet>*
    *<servlet-mapping>*
    *<servlet-name>AdminServlet</servlet-name>*
    *<url-pattern>/servlet/AdminServlet</url-pattern>*
    *</servlet-mapping>*
    *</web-app>*
    Edited by: 925692 on Apr 5, 2012 1:38 AM
    Edited by: 925692 on Apr 5, 2012 1:40 AM
    Edited by: 925692 on Apr 5, 2012 1:40 AM

    This behavior might be attributed to Axis inclusion.
    Web service actions and wizards supported by Weblogic can be found at:
    File->New->Other->Oracle->WebLogic->Web Services
    Can you provide more detail about your starting point wsdl? or JWS? and information around what generation actions you used?
    Thanks

  • ServletException When Deploying Web Service Application to WL 10.3.1

    I'm attempting to deploy a web service application to WebLogic 10.3.1 built using the ANT jwsc task. The majority of the build is being done by Maven to produce and EAR file which contains the web service application WAR file, but I'm using ANT for the jwsc task due to classpath issues in Maven. Here is my task definition from by ANT build script:
    <jwsc srcdir="src" destdir="${basedir}/target"
    classpathref="weblogic.jar.classpath" verbose="on" debug="on"
    keepgenerated="yes">
    <module contextpath="testapp" name="TestWSApp" explode="true">
    <jws type="JAXWS" file="test/src/TestWSImpl.java"/>
    <descriptor file="${basedir}/src/main/webapp/WEB-INF/web.xml"/>
    <descriptor file="${basedir}/src/main/webapp/WEB-INF/weblogic.xml"/>
    </module>
    </jwsc>
    When the process completes, within the WAR file is the web.xml, which has been modified by the jwsc process to contain a servlet definition and mapping:
    <servlet>
    <servlet-name>TestWSAppServlethttp</servlet-name>
    <servlet-class>test.src.TestWSImpl</servlet-class>
    <load-on-startup>0</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>TestWSAppServlethttp</servlet-name>
    <url-pattern>/TestWSAppServlethttp</url-pattern>
    </servlet-mapping>
    The problem comes when I try to deploy to WebLogic. The deployment fails and I get errors. The stack track is really long, but here is the main problem:
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "DataIntegrityServiceServlethttp" failed to preload on startup in Web application: "/testapp".
    javax.servlet.ServletException: Servlet class: 'test.src.TestWSImpl' does not implement javax.servlet.Servlet
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:276)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    This error actaully makes sense if I was trying to deploy a servlet and not a web service class. If I manually remove the <load-on-startup>0</load-on-startup> element from the web.xml, then this deploys fine. I've tried to define the servlet in the web.xml permenantly, but jwsc throws an error saying the context is already in use.
    So what I need to do is either have jwsc skip the modification of the web.xml or just not have it create the <load-on-startup>0</load-on-startup> element. Any ideas?

    Nevermind, I figured it out.
    I had to change the name of my JWS class (the one that implements the web service methods) and then it worked fine.
    Thanks to all who responded.

  • Open client socket from within a Web Service

    Hello,
    I need to open a client TCP/IP socket from within a Web Service-type WebLogic
    Workshop app. When I try to read from the socket, the socket read operation hangs.
    When I use the same code in a J2SE Java app on the same machine using Eclipse
    everything works fine. It also works fine from within WebLogic, if I use a "URL"
    object instead of a "Socket" object. (However, I cannot use this type of connection.)
    Can anyone tell me how to work with raw TCP/IP sockets in this situation?

    Hi Udi,
    I have tested my code from within a Servlet and it works fine.
    The Servlet and the Web Service both call the same simple JAVA class. This class wants to access a DB, and therefor, I am using the Data Source.
    When the Servlet calls the class, everything works fine. But when I use the Web Service to call this class, I get the Exception "No attributes are implemented".
    I hope this information helps you understanding my problem?
    Thank you very much for your help.
    Kind regards,
         Nadine

  • Creating web service application in JDeveloper 11.1.2

    Hi all,
    I had use the JDeveloper 11.1.2 . And i want create a new web service application using the JDeveloper 11.1.2. Please give some steps and document for creating the web service application .
    Also give some steps for accessing the web service application from j2ee 1.4 application using JDeveloper 11.1.2.
    thanks
    Prabu

    Hi all,
    i had installed the J2ee 1.4 application in oracle apps 11i (Linux server). I had executing the web service process in Linux server and its working fine.
    And i need to call the web service from externally. I.e Web service code is executed in Linux server. I need to call the web service from Jdeveloper .
    Please give steps and document screen shots for invoking the web service application from the External java application(i.e jdevloper).
    Please help,
    Thanks
    Prabu

  • Pulling Data from an imported web service into a data grid - Flex 3.0

    Hi all,
    I have created a web service from Oracle using JDeveloper and imported it into my Fex 3 project, and I am trying to populate a data grid with the data from the web service.  I was trying to emulate the example found in my Adobe Flex 3.0 for Dummies book (see http://dougmccune.com/flexfordummies/chapter14/srcview/index.html), and while the code from the book with that data service works fine, I can't get my application to work.  My issue is with the part of code mx:DataGrid dataProvider="(service)"  - I do not know how to specify what to use for the data source to populate the data grid from my imported web service.  Any suggestions or examples would be helpful, as I am a newcomer to Adobe Flex.  My code is as follows:
    <?xml version="1.0" encoding="utf-8"?><mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"xmlns:webservices="
    generated.webservices.*">
     <mx:Script>
    <![CDATA[
     private function getData():void {service.getPdRec(ageDt.text);
    ]]>
    </mx:Script>
     <webservices:PD_Pct_Web_Service id="service" />
     <mx:VBox>
     <mx:HBox width="100%">
     <mx:TextInput id="ageDt" width="100%" />
     <mx:Button id="submitButton" label="Search" click="getData()" />
     </mx:HBox>
     <mx:DataGrid dataProvider="(service.getPdRec_lastResult
    " rowHeight="
    58" width="100%" height="300">
     <mx:columns>
     <mx:DataGridColumn dataField="creditManager" headerText="Credit Manager" width="40" />
     <mx:DataGridColumn dataField="pdTarget" headerText="PD Target" width="40" />
     <mx:DataGridColumn dataField="totalPd" headerText="Total PD" width="40" />
     <mx:DataGridColumn dataField="pdPct" headerText="PD Percent" width="50" />
     </mx:columns>
     </mx:DataGrid>
     </mx:VBox>
     </mx:Application>
    My web service returns the following when invoked:
    <env:Envelope
      xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:ns0="http://erec_db/PD_Pct_Web_Service.wsdl/types/">
    <env:Body>
      <ns0:getPdRecResponseElement>
       <ns0:result>
        <ns0:creditManager>Cobb</ns0:creditManager>
        <ns0:pdTarget>10</ns0:pdTarget>
        <ns0:totalPd>147.65</ns0:totalPd>
        <ns0:pdPct>26.77</ns0:pdPct>
       </ns0:result>
       <ns0:result>
        <ns0:creditManager>Collova</ns0:creditManager>
        <ns0:pdTarget>10</ns0:pdTarget>
        <ns0:totalPd>27.71</ns0:totalPd>
        <ns0:pdPct>21.67</ns0:pdPct>
       </ns0:result>
       <ns0:result>
        <ns0:creditManager>Lee</ns0:creditManager>
        <ns0:pdTarget>10</ns0:pdTarget>
        <ns0:totalPd>33.61</ns0:totalPd>
        <ns0:pdPct>72.38</ns0:pdPct>
       </ns0:result>
       <ns0:result>
        <ns0:creditManager>Maynard</ns0:creditManager>
        <ns0:pdTarget>10</ns0:pdTarget>
        <ns0:totalPd>74.19</ns0:totalPd>
        <ns0:pdPct>33.69</ns0:pdPct>
       </ns0:result>
       <ns0:result>
        <ns0:creditManager>Ong</ns0:creditManager>
        <ns0:pdTarget>10</ns0:pdTarget>
        <ns0:totalPd>13.26</ns0:totalPd>
        <ns0:pdPct>46.06</ns0:pdPct>
       </ns0:result>
      </ns0:getPdRecResponseElement>
    </env:Body>
    </env:Envelope>

    Use data binding. <mx:DataGrid dataProvider="{service.getPdRec_lastResult}"
    -Radhakrishna

  • Could not run the bookstore1 example from the Java Web Services Tutorial

    The bookstore1 servlets example from the Java Web Services Tutorial (issue Aug 1, 2002) was built and deployed successfully by using the deploytool (following the steps described on pages 498ff of the tutorial).
    After deploying the application the Tomcat Web Application Manager shows the entry:
    /bookstore1:stopped:0:D:\Programme\Java\tomcat\jakarta-tomcat-4.1.8\work\Standalone\localhost\manager\bookstore1.war
    when entering the command: http://localhost:8080/manager/list.
    After entering the command: http://localhost:8080/manager/start?path=/bookstore1, the (uncomplete) message appears:
    FAIL - Application at context path /bookstore1 could not
    It should be noted that I was able to build and deploy the application GSApp (chapter 3 of the tutorial) successfully.

    Did you set up the database as described in
    http://java.sun.com/webservices/docs/1.0/tutorial/doc/WebApp13.html#69868

  • How to send a XML file from  SAP    to   WEB SERVICE

    Hi folks,
    i m creating a XML file with purchase order data, while saving the purchase order.now i need to send this XML file to some WEB SERVICE i.e to some perticular address in WEB.
    can anyone give the step by step procedure to do this web service configuration? it's really urgent.
    points must be awarded.
    Thanks & Regards
      pabitra

    Hi all,
    i need to send some purchase order data from SAP to WEB SERVICE. while saving the purchase order, i want to send some data from SAP to WEB SERVICE ( a perticular address in WEB).
    i want to see those datas in xml format in WEB.
    Now i am using SAP 4.7 version. Is this web service configuration is possible or not?
    In SE37, i can not see the CREATE WEB SERVICE option in utilitities--> More utilities menu.is it possible in 4.7???
    can anyone give any suggestion ? it's very urgent.
    Thnaks
    pabitra

  • Which tools build a web service application

    i am a greenhorn in web services.
    i want to build a the example " <INSTALL>/javaeetutorial5/examples/jaxws/helloservice/"
    This are the steps am following
    -open the cmd prompt;
    -type cd C:\Documents and Settings\Guest\Desktop\francis\sun\tutorials\jwstutorial20\jwstutorial20\examples\jaxws\helloservice
    -type asant build
    i get the message : asant is not recognised as a batch command.................
    i get the problem is that i have not set the classpath, but i need to now what builds the web service application or the directory which has the tool.

    If you want to create web service in java then you can use Apache Soap or Weblogic web services using EJBs.

  • MBAM 2.5 Web Applications installation - "Web service application pool account is not valid"

    Hi,
    I've created a Server 2012R2 installation to install MBAM 2.5. When installing the Web Applications I keep getting "The web service application pool account is not valid". 
    The account I am using is a standard domain account with admin rights on the Server and I've also set the SPN (both netbios and FQDN) and Delegation.
    This account is also a member of the group that is defined as RW of the SQL databases (which were setup without any problem and are on a separate  Server 2008R2, SQL 2008R2 installation.
    I am also getting an error with the SSRS URL , stating "SQL Server Reporting Services URL that points to the MBAM reports is not valid", despite being able to browse to the http://[FQDN]/ReportServer_MBAM location.
    Thanks.

    I got this kind of error when I revert back my virtual machine a lot to my previous checkpoints. I hope this can't be an issue for you.
    Make sure the application pool account must have the following login roles on the SQL server and have following rights on the reporting instance:-
    Required SQL Server permissions
    The user responsible for installing MBAM database and reporting feature must have the local administrator privileges and the following log in permission:-
    SQL Server instance login server roles:
    dbcreator
    processadmin
    SQL Server Reporting Services instance rights:
    Create Folder
    Publish Reports
    SQL Server Database Engine Services: SQL Server Database Engine Services must be installed and running during MBAM Server installation.
    SQL Server Reporting Services (SSRS): SSRS must be installed and running during the MBAM Server installation. Configure SSRS in "native" mode and not in "SharePoint" mode.
    Gaurav Ranjan

  • How to access  complex data type from a soap web services?

    hello
    can u please tell me how can i access complex data type from a soap web service from jdeveloper 10g
    Jdeveloper generates 3 classes
    serviceStub
    getproperties
    response
    i have to retreview the data which is a complex data type it gives some
    unknown type. and the return value is a key-value pair data type .
    regards
    vs

    After you create the partner link and the invoke (to create the variables), change the element type of the response message to the complex type definition of your collection that appears in the XSD. You can do the same thing if you want to change the element type of the payload of the request message as well.

  • Workshop Web Service Security

    We have a Workshop Web service, where we want to use digital signature for a particular soap header element. SO if any SOAP REQUEST used digital signature for this particular node them only webservices will be executed.
    Initially we are planning to use WSSE policy file for the web services using the "<b><additionalSignedElements></b>" in "<wsSecurityOut>" tag for Web service control to sign the soap message and "<wsSecurityIn>" tag for WEB SERVICE policy file to verify it. But it is signing the whole soap body and it was unable to verify the signature of particular node because we can not mention a particular element in "<wsSecurityIn>".
    Is it possible to implement this type of scenario using WSSE POLICY file or we have to write WEB SERVICE handler for verification ?
    What is the use of <additionalSignedElements> in "wsSecurityOut" tag because we can not use it in "wsSecurityIn" element to verify it.

    Why do you want to do that? Any specific use case? I think for SOA services, you have to use OWSM. You may refer -
    http://download.oracle.com/docs/cd/E17904_01/web.1111/b32511/intro_ws.htm#BACBBDIB
    Regards,
    Anuj

Maybe you are looking for