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.

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.

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.

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

Warning when building a web dynpro application

Hi,
Am getting the following warning when trying to build a web dynpro applications( DTR perspective - FPM application).
Kind     Status     Priority     Description     Resource     In Folder     Location
Warning               [Warning]: Path in Classpath for file SapMetamodelWebdynproContent.zip not found.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Version for file SapMetamodelWebdynproContent.zip not found.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_admin.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_clientserver.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_model_dynamicrfc.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_modelimpl.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_progmodel.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_runtime_designtime_coupling_api.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_runtime_designtime_coupling.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_runtime_repository_pmr.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_runtime_repository.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Warning               [Warning]: Versions of '_webdynpro_services.jar' have different prefix.     DJI_ZPOSMGMT_DZFPManalog.com
Info               TextView DefaultTextView: UIElement does not have a label     CcposView.wdview
I am trying to build the apllication.
Does a warnning stop the web dynpro appliucation from been "build". If the applciation is built. Where can I get the .EAR file on my local machine. I want to pass the .EAR to the basis team for them to deploy.
Does warning message prevent from getting the .EAR files from been generated???
Please advise
regadrs
Sam

Hi Sam,
Have you a DC inside the JDI (Track)? - then it could be that you have an older Version from the files that you check-in into your Track - SAP_JEE.sca , SAP_BUILDT.
If you have an older version of this files in your DC you must check-in this files again from the new Patchlevel and sync the DS's of your project!
Carsten

A problem with building a web service with netbeans

always a problem occurs when i try to build a web service server side.
build is perfect .but when i said run the project there is an error occurs:
"Deployment error:null. See the server log file for details."
error link goes me to this row in the build-impl.xml file of the project:
<nbdeploy forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" debugmode="false"/>
i am waiting for your help.

Being a total novice on the https/SSL configuration side of things, I've finally managed to dig down to the fact that our external partner of course needs to have a certificate installed in order to run https.
I guess the browser did not prompt and ask for acceptance of this, because it was already verified through one of the standard issuers - VeriSign.
So was then able to export the certificate through IE's Properties>Certificate>Details>Copy To File...
Will then try to import this into the correct domain on the WebLogic server.
(A quick test of the web service from the EM console worked fine. Strange then that executing the service through a partner link in bpel does not work, but I guess it may have to do with a local bpel being exposed as a web service in itself, and that security on both sides is called for... maybe... :-) )
-Haakon-

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

Into which AppServer directory are web service files deployed?

Assume I compile Web Services (in JDeveloper) and deploy them to the Oracle AppServer.
into which directory are the web service archives physically deployed?
How can I find this out?
Can I change this folder?
Peter

If for instance you deployed to the default domain then it would be in $ORACLE_HOME/bpel/domains/default/tmp directory. It will be prefixed with a dot in front of it so using ls command will not show it, but use ls -al.

Please give me your opinion... about tools for develop web service

If you would like to choose the tool for develop web service.
what is the most important feature that you will consider,
Please help me to order these topic from the most to the least
a. creating web service
b. creating web service client
c. searching web service to UDDI registry
d. publish web service to UDDI registry
e. connecting to database management systems.
f. license fee
g.system requirements
h. Installation procedures
thank you very much for your opinion. I will keep your information for my research....
:)

Hi Fangnaka,
You can use JWDSP2.0 + Tomcat 5.X +Jdk1.5 to develop and deploy webservice.
Better IDEA are Intellij or Eclipse for webservice code development.
Cheers
Rajesh R

Difference between building/consuming web service in ERP vs. XI (PI)

Hi All,
Can someone direct me to the pros and cons of whether to build/consume a web service in ERP (ABAP - SE80, etc.) versus in XI? We have ECC 6.0 and the latest version of Web AS running - so no issues with that. I'm just wondering - if we can build and consume everything in ERP, why even waste our time with XI (for web services)? What gives?
Thanks,
Matt

Hi there,
There are three main aspects in using XI for Enterprise Services:
1. The ESR - Enterprise Service Repository (based on Integration Repository)
2. The Service Registry (coming as part of latest XI release: PI 7.1)
3. The need for asynchronous services
1. The ESR
This one should be used for designing your services -ESR is design-time-, defining object data model, interfaces, operations and so on based on Global Data Types.
The use of Global Data Types allows to ensure that when we speak of e.g. an amount being 1,000.52, it will be understood correctly from the other side thanks to a common set of data types.
Furthermore, the ESR comes with pre-defined content (interfaces and others) that makes the building of new services faster.
Note that once you've defined your service in XI, you'll have to generate a proxy (ABAP or JAVA) in your ERP (in case ABAP) where you'll need to implement your code, this means that at run-time your're not obliged to pass through XI to run the service.
2. The SR
The Service Registry is the ultimate place where all enterprise services of your company will be published. This will really be your ES yellow pages where you can get services WSDL and location so that you can integrate them easily in any of your applications. Services available in the SR are (should) be "released" services, so in contrary to what you can find in the ESR (where you can have work in progress), here you'll only have services that are completed and ready to use.
3. Asynchronous ES
The ERP does not allow you to create real asynchronous services, and this is true as well when you call a service from your ERP as when you provide a service in your ERP to external calls (proxy client).
In case you need to work with asynchronous scenario, you'll have to go through XI.
Of course in an ERP system, there are many ways of making a "kind of" asynchronous behaviour with coding, workflow and so on, but in this case the other party (the external service provider or caller) will probably have also to be adapted which is not always possible.
Well, these are from my point of view the most important elements; so, if you don't need asynchronous behaviour and you don't have to many services to manage you can certainly work without XI.
Now, if you start having services from different systems, and you build a complete enterprise SOA based infrastructure, XI/PI becomes a necessity.
Rgds,
Karim

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.

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.

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?

Which tools build a web service application

Similar Messages

Maybe you are looking for