Web Service application - migrating to Glassfish

Hello!
I've a WebService app. which now runs on Tomcat 5.5.23 and was written using JAX-WS. I've install Sun Java System App. Server 9.0 and I intend to migrate our app. here.
The application is delivered as a war file which I've already deployed in glassfish using admin GUI of asadmin. I can see our app. at WebApplications section but I can't see it under WebServices section, although it seems at a first view that the application works and respond to client's request.
I'd like to ask you if I need to use a special tool for migrating our aplication or what I did is enough and there is no need for other changes.
Thank you very much
With best regards,
Sorin

I found how to do this in an excellent TechEd Europe document presented by some guy from SAP AG (I think) from a few years back.
Unfortunately, I didn't save the link. I had only a paper printout and I can't find the document again.  It was buried in some article I read on some SAP web page.
Thomas Jung also has a presentation on this that can be found with search, but I was not able to follow that completely.  The TechEd Europe piece could be followed line by line and had the necessary code examples (function modules)  to demonstrate that the the Web Service was consumed.  If I remember correctly, anything that is remote enabled in 6.20 can consume the service.
WebService in WebAS 6.20 is absolutely unique; implementing a web service in WebAS/Basis versions before and after are entirely different from WebAS 6.20.

Similar Messages

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

  • 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

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

  • 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

  • SOAP vs. XML-RPC for synchronous Web Services applications

    Hi everyone, I have to finish one project soon and I have to make a decision. Because I don't have much time I want to ask if anyone can answer me, what are the major differences bettween SOAP vs. XML-RPC for synchronous Web Services applications. I'll be very grateful if you help me!
    Thanks in advance!

    Come on guys i know you can help me, please don't hesitate to write some row

  • Jax-WS 2.2 web service instances management on Glassfish 3

    Hi all, I'm studying Jax-WS specification in general and its implementation on Glassfish 3.1.2. I built a simple standard example where a jax-ws soap based web service is called from a jsp page by using the artifacts generated through wsimport (the webservice and the jsp page are both deployed on Glassfish in the same EAR but in 2 different wars).
    Everything works as expected but I have a question: looking at the application log, it seems that Glassfish creates a new instance of the webservice each time it is called. I would like to know where Java offically defines how a web container should manage webservice instances and if developers can customize this behaviour.
    I read jax-ws 2.1 specification here
    http://download.oracle.com/otndocs/jcp/jaxws-2.1-mrel2-eval-oth-JSpec/
    but I found only a clue when speaking about how to publish a webservice using the Endpoint class by hand (section 5.2.2 "Publishing", page 69):
    "An endpoint consists of an object that acts as the Web service implementation (called here implementor) plus some configuration information...
    An Endpoint will be typically invoked to serve concurrent requests, so its implementor should be written so as to support multiple threads. The synchronized keyword may be used as usual to control access to critical sections of code. For finer control over the threads used to dispatch incoming requests, an application can directly set the executor to be used..."
    This note is present even in Jax-WS 2.2 specification (used by Glassfish 3).
    Actually, if I build a webservice using only JavaSE 7 (which includes Jax-WS 2.2), this description is true because there is only one instance of the webservice. Is there any reason why JavaEE doesn't follow this policy?
    Thanks a lot for your help,
    Nico

    Hi, I found the answers on this specification (JSR-109):
    http://jcp.org/aboutJava/communityprocess/mrel/jsr109/index3.html
    It describes how Jax-WS works on JavaEE:
    "4.1 Client Programming model (page 18)
    a client must assume that the methods of a Web service have no state that is persistent across multiple Web service method invocations. A client can treat the Web service implementation as stateless.
    The client has no control over the life cycle of the Web service implementation on the server. A client does not create or destroy instances of a Web service, which is referred to as a Port. The client only accesses the Port. The life cycle of the Ports, or instances of a Web service implementation, are managed by the run-time that hosts the Web service. A Port has no identity. This means that a client cannot compare a Port to other Ports to see if they are the same or identical, nor can a client access a specific Port instance.
    5.3.2.4.2 Web container programming model for JAX-WS (page 42)
    A Service Implementation must be a stateless object. A Service Implementation Bean must not save client specific state across method calls either within the bean instance’s data members or external to the instance. A container may use any bean instance to service a request.
    5.3.4 Service Implementation Bean Life Cycle (page 43)
    Before a request can be serviced, the container must instantiate a Service Implementation Bean and ready it for method requests.
    A container may pool method ready instances of a Service Implementation Bean and dispatch a method request on any instance in a method ready state."
    Moreover, the specification states that JavaEE must not use the Endpoint class to publish a webservice:
    "5.3.3 Publishing Endpoints – javax.xml.ws.Endpoint (page 43)
    JAX-WS provides functionality for creating and publishing Web Service endpoints dynamically using javax.xml.ws.Endpoint API. The use of this functionality is considered non-portable in a managed environment. It is required that both the Servlet and the EJB container disallow the publishing of the Endpoint dynamically, by not granting the publishEndpoint security permission."

  • Seeking advice with concept / design of a Java Web Services Application

    Hi all,
    After a week of searching the internet I'm not sure how which projects, services, etc. I should use to develop my application. Please could someone offer some advice?
    Application outline (Java application running on Linux):
    1. Wait for an instruction from a Windows WCF application. Instruction contains a list of domain names and one or two other parameters.
    2. Perform queries upon those domain names (find if they are registered, etc. - takes 10-20 mins to do complete list)
    3. Send back results to WCF application.
    Solution 1 (first idea):
    1. Create SOAP web service using Java Web Services / Apache to listen for requests. Executes a Java Client Application upon request.
    2. Java Client Application performs the queries...
    3. Java Client Application sends results to the Windows web service.
    Solution 1 Problems:
    a) Using 2 applications, they won't be able to share the same memory.
    b) The whole process will be slow (having to pass the domain names from the service to application and execute the application each time) - A quick response is critical.
    c) Would like is for the whole process to be done under one application, sharing the same memory.
    Solution 2:
    1. Create a Java Daemon from scratch listening for an incoming SOAP message (no web service like Apache/Tomcat involved).
    2. Query the domain names in a new thread inside the Java Daemon
    3. Send the results back via SOAP.
    Solution 2 Problems:
    Cannot find examples of how to create a SOAP service from scratch. E.g. creating a WSDL file based on my application; converting application methods to SOAP-callable methods easily (without writing a framework).
    With all the Java tools and projects out there - Java EE, Glassfish Project - there must be a very easy way to achieve this seemingly simple task. Please can someone offer some advice?
    Many thanks for reading this.
    Richard
    Edited by: jazzinbrazil on Mar 30, 2009 4:58 AM

    You just need an app server like Tomcat.If I'm not wrong, Tomcat is a Servlet container.
    Servlets aren't deactivated when they don't receive
    any request for some time?
    How can I deploy an application to Tomcat in order to
    keep it always active?I don't know what you mean. Tomcat is an application that is always running. In what way are the Servlets deactivated?
    Apache Axis: http://ws.apache.org/axis/
    Yes I'm collecting some info about this... let's see
    it!
    Finally, to be more clearer... I don't want to start
    a new application at each invocation (something like
    getting the request, instantiating the necessary
    classes and executing them) but to call an already
    running app at each invocation (so, getting request
    and invoking, in a manner that I don't know, the
    running application).The container manages this. If you have data that must remain loaded, you can associate it with the class (use a static modifier.) This will complicate threading, however.
    I can use Axis to get the request, but it also grants
    me that my app will always be active?I think you are just using the wrong terminology here. What I think you are asking is whether the resources will be loded into memory at all times. If you want to ensure this behavior, you need to associate the data with a class. I'm not 100% positive, but I don't think Tomcat will unload classes in normal circumstances.

  • Problen when using log4j.jar in my web service application

    Hi, i have a little problem. I have to migrate an existing java application to web services, and this application uses log4j.jar. So i put that jar file in the lib dir in WEB-INF. However, when i try to deploy the application, i get an error saying
    org.apache.commons.LoggingException: No suitable Log constructor [LJava.lang.Class;c492c8 for org.apache.commons.logging.impl.Log4JLogger
    And of course if i remove that jar from the lib dir, the app deploys ok, but it crashes because it can't find the class Logger (located in that jar)
    Any ideas how to solve this?????
    Thank you                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    When is the log4j constructor invoked ?....you said you moved the java application to webservice....in the java application they might have initialized the log4j with the log4j properties file some where when they start the application..
    Have a start up servlet which initializes the lof4j.

  • Can't Export/Archive Web Services for Migration

    We have several web services that I'd like to copy from one
    server to another. I tried creating a ColdFusion Archive but the
    web services that I selected are not included in the CAR file. Is
    this a known issue?
    Is there any other way to migrate web services from one
    server to another? Are the entries stored in an XML file?
    Thanks for any help,
    Glenn

    Bill:
    Welcome to the Apple Discussions. Try the following:download and run BatChmod on the iPhoto Library folder with the settings shown here, putting your administrator login name, long or short, in the owner and group sections. You can either type in the path to the folder or just drag the folder into that field. See if this will help.
    Next, log into another account or boot into Safe Mode and see if you can export to a web page. If so then there's something amiss with your account. If not, then a reinstall of iPhoto seems appropriate.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • How to access Portal Logged in user in Web Service application

    Hi Experts,
    I have created one Deployable Proxy and based on that i have created Web Based (WAR) project. to consume the proxy i have created Servlet based java file which invokes Web services. Based on this WAR project i created EAR application which deploys on J2EE server.
    I am facing issue while accessing Portal Logged in user in my Servlet Class in WAR project so can  you please provide inputs for how we can access Portal Logged in user in our Servlet class? also how we can access LDAP detailes of portal Logged inuser ?
    I tried to fetch the Logged in user from servlet request but i can't access it giving me null value. Following is the method details that i am using in my servlet.
    protected void doGet(HttpServletRequest request,HttpServletResponse response)throws ServletException, IOException                
    IUser user = UMFactory.getAuthenticator().getLoggedInUser();
    String strName = user.getFirstName();
             If I checked in LDAP values First name for logged in user is present but in my code its giving Null value.
    Can you please provide your inputs on above issue.
    Regards,
    Rahul

    have you found a solution this problem yet?

  • Spring web-service application in weblogic 9.1

    Hi,
    Iam trying to port the sample application given with Spring Web Services download(It works great with tomcat) to Weblogic 9.1. There were some issues doing it. You can see the discussion here. [url http://forum.springframework.org/showthread.php?t=26205]
    I did that accordingly and Iam getting a [org.springframework.ws.soap.axiom.AxiomSoapMessageFactory]: Constructor threw exception; nested exception is java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:451)
            at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
            at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
            at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
            at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
            Truncated. see log file for complete stacktrace
    org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.ws.soap.axiom.AxiomSoapMessageFactory]: Constructor threw exception; nested exception is java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
            at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:759)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:724)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:387)
            Truncated. see log file for complete stacktrace
    java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
            at org.springframework.ws.soap.axiom.AxiomSoapMessageFactory.<init>(AxiomSoapMessageFactory.java:97)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            Truncated. see log file for complete stacktrace error.
    Look at this page for the settings i have done. [url http://forum.springframework.org/showthread.php?t=40051]
    Please help me resolve this issue.
    Thanks
    Vignesh

    Well, in the web.xml for the app we have it set up as BASIC authentication, and list the roles that are allowed at that particular site. In order to sign in, another app would have to set the authorization property in the URLConnection.
    The problem is, using AXIS to connect, I have no way to set this property in the connection, since it is wrapped up by axis. (Call)
    I have reached a potential solution of constructing the soap message with the client using means other than the AXIS API, which I am implementing now and praying it will work!
    Everything I have read suggests using SSL to connect to the web service, but I can't figure out how to set up SSL so that my host/axisweb directory needs HTTPS but host/ doesn't...
    Does this make sense? Any suggestions?

  • Start ABAP Debug in Web Services Application - won't take non-Dialog user

    Hello all. We are trying to Replicate Employees from SuccessFactors to SAP ECP/ERP with a delivered integration from SAP, but we''re having trouble interpreting some of the errors we're getting in the Application Log
    As shown in the Web Services Utilities Message Monitor - our message is successfully Delivered - we would like to set a break-point in Class CL_PAOCF_EC_EE_MDR_IMPL and run our test. Unfortunately we have to use a Technical User in our middleware connector to consume the Service (to connect to the Java Application Server?) and setting External Breakpoints or enabling Debugging in SICF will only permit Dialog users. Does anyone know how we can run our Web Service and invoke an External Breakpoint in our application posting Class?

    Hello Keith,
    What is the "user type" for this user? In our system we have the user for the middleware defined as "Service type" and external debugging is possible with that user.
    BR,
    Suhas
    PS - Read the documentation of the data element XUUSTYP for further details.

Maybe you are looking for