Web service deployment problem under sun 8

I am deploying web service under sun8 app server. When I use wscompile to generate wsdl file it puts the following for the the service location:
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
which is replaced on deployment by the actual server name and port. However in my case the local server name and the public name are different. How can I configure what the "REPLACE_WITH_ACTUAL_URL" gets replaced with?

As of now, I don't think you can do that. One ugly workaround is probably to deploy your app, shut down your app server, edit the WSDL present @ install_dir/domains/domain1/.. manually and restart the app server - that might resolve the issue hopefully :(

Similar Messages

  • Web Service deployment problem

    Hi all,
    I'm trying to deploy a Stateless EJB 3.1 as a web service in JBoss 6.0 M5. I'm using maven to build the two projects (one for the ejb jar and one for the ear itself). My ejb looks like this:
    package com.company.testejb;
    import javax.ejb.Stateless;
    import javax.jws.WebService;
    import javax.jws.WebMethod;
    @Stateless
    @WebService
    public class HelloService {
            @WebMethod
            public String hello() {
                    return "Hello, is it me you're looking for?";
    }My problem is that that the endpoint is: http://localhost:8280/testejb-1.0-SNAPSHOT/HelloService?wsdl. Is there a way I can turn it to testejb/HelloService?wsdl ?
    Thanks

    I guess it's your Ejb project issue , just change the project name to testejb, it should be OK

  • Web Services deploy problem

    Hi!
    I am using the latest version of J2EE, and I want to start learning about Web Services. I made a simple example(it has just a method "add"), I created the wsdl and xml required files (as in the article http://java.sun.com/developer/technicalArticles/J2EE/j2ee_ws/) but I got into trouble when I tried to deploy it.
    I am using deploytool, I followed all the steps shown in the tutorial , and when I want to deploy I get the error :
    "distribute: D:\JavaWork\WebServices\basicmath\ws\math.war
    ERROR - Deployment failed - null
    !!! Operation Failed !!!"
    Thanks.

    Hi!
    I can deploy the application if I use the admin console but I can't if I use deploytool. I still get the same errors.
    I tried also to deploy EJBs or JSPs and it didn't work, but if I deploy with admin console it works.
    So, I deployed it with admin-console, but now I got the exception from the client:
    "javax.xml.rpc.soap.SOAPFaultException: JAXRPCSERVLET28: Missing port information
    at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:515)
         at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:294)
         at sstub.MathFace_Stub.add(MathFace_Stub.java:71)
         at sstub.MathClient.main(MathClient.java:25)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)"
    The exception occurs when I call the method "add" of the stub. I searched all the web, but I didn't find anything to help me.
    Thanks again.

  • Web service deployment problem in jboss

    How portals are deloyed inweb-server

    Have you found a solution for this error?
    One way to fix it is to use rpc literal instead of document literal, however, I would like to use document literal and it seems to cause this problem...
    T.

  • Problem generating stubs for Java EJB web service deployed in OAS

    I created an EJB web service and I've successfully deployed it in my Oracle App Server. Some of the methods work fine but others produce the ff error:
    org.apache.soap.SOAPException - java.lang.IllegalArgumentException: No Serializer found to serialize [classname] using encoding style [encoding]It seems that the objects specified as parameters in the web service methods exposed are the only ones that had stubs generated for them. Other objects I use, which are usually wrapped inside a Vector, did not have generated stubs.
    Example:
         public String loginUser(UserDTO userDTO) throws RemoteException, NamingException, SQLException;
    public String addItems (Vector vecItems) throws RemoteException, NamingException, SQLException; // where vecItems is a collection of ItemDTO objects     In this scenario, stubs were generated for the UserDTO class, but not for the ItemDTO class. In effect, calling the addItems method resulted to the exception I mentioned above.
    I did a workaround wherein I declared a dummy method which accepted all the types of objects I needed as parameters so all the necessary stubs can be generated, but this fix doesn't feel like it's the proper solution to my problem.
    If anyone can help me, it would be greatly appreciated. Thanks!

    Crossposted:
    Problem generating stubs for Java EJB web service deployed in OAS

  • BPM Studio call web service deployed by R12 Intergration Repository error

    Hi, I encountered a problem when calling a web service deployed by R12 Intergration Repository (SOA Gateway) w/ username/password authentication.
    It seems that the BPM Studio can not pass the security information to the web service. But using SoapUI it's quite easy to call the service with no error, just set the username and password, and set the password type to PasswordText.
    Under the External Resources catalog, I've set fileds in the Security tab with "Plain" Username Token, "sysadmin" Username and "sysadmin" Password, then changed the Authentication Type to "Username Token Profile". Then create a participant named sysadmin, and use this participant to run the process, but it just can't work.
    Anybody can help? My colleague also posted a topic here: processRemoteException when invoke  webservice from Oracle E-Business Suite but nobody answered. It would be very appreciated if sb. can fix this.

    I've encounter something similar to you're problem and it was resolved by manually creating the object using the web service constructor and inputting user credentials. If you manually instantiate your web service wrapper object and set a a security profile token, it may solve your problem. You can also pass in the web service endPoint URL, if you want.
    Fuego.WebServices.UsernameTokenProfileSecurityPolicy
    I'm not sure how to use UsernameTokenProfileSecurityPolicy, but try something like this:
    Fuego.WebServices.UsernameTokenProfileSecurityPolicy policy = UsernameTokenProfileSecurityPolicy();
    policy.username ="mark";
    policy.password = "password";
    tws = YourWebService();
    response = tws.callWebServiceMethod();
    I realize the security profile isn't tied anywhere to the web service, but try it anyway.
    There is also some fields on the webservice, tws.setRequestHeader() that may allow you to set the username and password on the request, but this doesn't make sense to me. It shouldn't be that hard.
    Edited by: Mark Peterson on Mar 19, 2010 9:14 AM
    Edited by: Mark Peterson on Mar 19, 2010 9:20 AM

  • Error invoking web service deployed in SOA Suite

    I have implemented a stateful web service in Jdeveloper 10.1.3.2.
    I can test succesfully an operation of the web service from the embedeed oc4j of jdeveloper, but i can not succes when i try do the same from the application server control of soa suite.
    The response of the web service in the second case, is the xml of the request.I can not understand.
    I implemented a web service proxy in jdeveloper that invokes the web service deployed in soa suite.When i run it, it gives me an exception like this:
    unexpected element name: expected={http://orclproject/types/}doLoginResponseElement, actual={http://orclproject/types/}doLoginElement
         at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(LiteralObjectSerializerBase.java:231)
         at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:159)
         at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub._deserialize_doLogin(OrclLoginWSSoapHttp_Stub.java:1022)
         at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub._readFirstBodyElement(OrclLoginWSSoapHttp_Stub.java:891)
         at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:333)
         at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
         at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub.doLogin(OrclLoginWSSoapHttp_Stub.java:484)
         at orclproject.OrclLoginWSSoapHttpPortClient.doLogin(OrclLoginWSSoapHttpPortClient.java:65)
         at orclproject.OrclLoginWSSoapHttpPortClient.main(OrclLoginWSSoapHttpPortClient.java:28)
    where doLogin is the operation of the web service.
    any idea?
    thanks in advance...

    Hi,
    almost 8 months passed since this post, but if still actual then look at BUG: Request XML returned as response when result too large thread. It may be the same problem with large data sets.
    Regards,
    Patrik

  • External web services deployment

    Hi,
    I am facing a situation of web services deployment. I am using Jdeveloper 10g and oracle bpel process manager 10.1.3.1.0. I am not able to deploy web services. The following are the steps that I followed to consume that web service called web service called WeatherByCity from xmethods.net.
    Create new Application---> create new empty project( I named it 'projectgt') ----> new 'java web service from wsdl' from wsdl document url (http://ws.strikeiron.com/InnerGears/WeatherByCity2?WSDL ------------->
    --> In the default mapping options for Package Name I put 'projectgt' and root package for generated types I put 'projectgt.types'. All the other options are default. When I right click Webservices.deploy under resources and deploy to the application server, it says failed to deploy with the following message.
    ---- Deployment started. ---- Apr 21, 2006 5:00:07 AM
    Target platform is Standalone OC4J 10g 10.1.3 (AppServerConnection1).
    Wrote WAR file to D:\Application24\Projectgt\deploy\WebServices.war
    Wrote EAR file to D:\Application24\Projectgt\deploy\Application24-Projectgt-WS.ear
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Uploading file Application24-Projectgt-WS.ear ...
    Application Deployer for Application24-Projectgt-WS STARTS.
    Copy the archive to D:\product\10.1.3.1\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications\Application24-Projectgt-WS.ear
    Initialize D:\product\10.1.3.1\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications\Application24-Projectgt-WS.ear begins...
    Unpacking Application24-Projectgt-WS.ear
    Done unpacking Application24-Projectgt-WS.ear
    Unpacking WebServices.war
    Done unpacking WebServices.war
    Initialize D:\product\10.1.3.1\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications\Application24-Projectgt-WS.ear ends...
    Starting application : Application24-Projectgt-WS
    Initializing ClassLoader(s)
    Initializing EJB container
    Loading connector(s)
    Starting up resource adapters
    Initializing EJB sessions
    Committing ClassLoader(s)
    Initialize WebServices begins...
    Initialize WebServices ends...
    Started application : Application24-Projectgt-WS
    Binding web application(s) to site default-web-site begins...
    Binding WebServices web-module for application Application24-Projectgt-WS to site default-web-site under context root Application24-Projectgt-context-root
    Operation failed with error:
    Error compiling :D:\product\10.1.3.1\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications\Application24-Projectgt-WS\WebServices: Error instantiating compiler: Web service artifact generation failed:java.lang.NoClassDefFoundError: projectgt/types/com/strikeiron/ws/SubscriptionInfo
    Deployment failed
    Elapsed time for deployment: 26 seconds
    #### Deployment incomplete. #### Apr 21, 2006 5:00:32 AM
    I will be grateful for any response on this issue.
    Thankyou,
    Sagar

    As a matter of fact, I receiving a similar error for all other web services. Please let me know the error in my method of deployment

  • Web Service Deployment Exception

    Hi All,
    I have created a Stateless session bean in which i am accessing JPA entities.
    In my session bean I have two methodes and i exposed those methodes as web services. I deployed this ejb project into server and search for my web service in Web Service Navigator. I didn't find my web service. Then I observer server logs. It is throwing a Web Service Deployment exception.
    Code:
    @WebMethod(operationName="readChannel", exclude=false)
         public ReadChannelResMsg readChannel(@WebParam(name="readChannelReqMsg")
         ReadChannelReqMsg readChannelReqMsg) {
              ReadChannelResMsg readChannelResMsg=new ReadChannelResMsg();     
              readChannelResMsg.setChannel(channelDao.findById(readChannelReqMsg.getChannelId()));
              return readChannelResMsg;
    Exception:
    [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 3324150:Exception occured during web services deployment. Unable to generate serialization framework for web service ProgramPlanWS, application hcl.com/longterm_plan_ear.
    -> class com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5:library:jaxb20 [email protected] alive incompatible with class com.sun.xml.bind.v2.model.impl.ClassInfoImpl:library:jaxb20 [email protected] alive
    server ID 3324150:com.sap.engine.services.deploy.container.DeploymentException:
    Why this exception is coming and how can i resolve this issue?
    Thanks
    Sampath G

    Hi,
    the initial exception suggest
    After an upgrade from SAP NetWeaver release 2004 to SAP NetWeaver release 7.0, according to the new SAP security policy, the J2EE Engine administrator user may be prompted to change his or her password. The password is changed in the User Management Engine (UME).
    According to SAP security policy, the J2EE Engine administrator password must be changed every 90 days. The password is changed in the UME.
    However, SDM reads the J2EE Engine administrator password not from the UME, but from the secure storage instead. The J2EE Engine administrator password is not changed in the secure storage. For more information, see SAP Note 870445.
    and the possible Solution could  be
    Change the J2EE Engine administrator password in the secure storage
    Regards
    Manohar

  • Jdeveloper WS proxy error while invoking  web service deployed on weblogic

    Hello experts, can you please help me. I have web service deployed on weblogic server.
    I have not set any credential for this web service. I can test the service from SOAPUI without providing any credentials.
    Then I generated WS proxy client using Jdeveloper. When I try to run the client, I do not know why I get security execption (shown below) eventhough I have not secured the web service deployed on weblogic server.
    java.lang.SecurityException: keyStoreFilename is either null or empty string
         at weblogic.wsee.security.util.CertUtils.getCertificate(CertUtils.java:87)
         at pilot1.ContactWSPortTypePortClient.getBSTCredentialProvider(ContactWSPortTypePortClient.java:104)
         at pilot1.ContactWSPortTypePortClient.setPortCredentialProviderList(ContactWSPortTypePortClient.java:78)
         at pilot1.ContactWSPortTypePortClient.main(ContactWSPortTypePortClient.java:46)
    Process exited with exit code 0.
    Here is my client class :
    public static void main(String[] args) {
    try {
    contactWSService = new ContactWSService();
    ContactWSPortType contactWSPortType = contactWSService.getContactWSPortTypePort();
    Map<String, Object> requestContext = ((BindingProvider) contactWSPortType).getRequestContext();
    setPortCredentialProviderList(requestContext);
    // Add your code to call the desired methods.
    // QueryPageInputSecondPage qpisp= new QueryPageInputSecondPage(); //I have commented it in order to resolve security issue
    System.out.println("Inside the client class");
    } catch (Exception ex) {
    ex.printStackTrace();
    Inside the method setPortCredentialProviderList(), I have not provided any credentials, keystores etc. Because weblogic is not setup with SSL and also I have not set up any authorization or authentication for the web service. I do not know why I am able to test it through SOAPUI and why not using WS proxy.
    Appreciate your quick response.
    thanks a lot
    jyothi

    Hello experts, can you please help me. I have web service deployed on weblogic server.
    I have not set any credential for this web service. I can test the service from SOAPUI without providing any credentials.
    Then I generated WS proxy client using Jdeveloper. When I try to run the client, I do not know why I get security execption (shown below) eventhough I have not secured the web service deployed on weblogic server.
    java.lang.SecurityException: keyStoreFilename is either null or empty string
         at weblogic.wsee.security.util.CertUtils.getCertificate(CertUtils.java:87)
         at pilot1.ContactWSPortTypePortClient.getBSTCredentialProvider(ContactWSPortTypePortClient.java:104)
         at pilot1.ContactWSPortTypePortClient.setPortCredentialProviderList(ContactWSPortTypePortClient.java:78)
         at pilot1.ContactWSPortTypePortClient.main(ContactWSPortTypePortClient.java:46)
    Process exited with exit code 0.
    Here is my client class :
    public static void main(String[] args) {
    try {
    contactWSService = new ContactWSService();
    ContactWSPortType contactWSPortType = contactWSService.getContactWSPortTypePort();
    Map<String, Object> requestContext = ((BindingProvider) contactWSPortType).getRequestContext();
    setPortCredentialProviderList(requestContext);
    // Add your code to call the desired methods.
    // QueryPageInputSecondPage qpisp= new QueryPageInputSecondPage(); //I have commented it in order to resolve security issue
    System.out.println("Inside the client class");
    } catch (Exception ex) {
    ex.printStackTrace();
    Inside the method setPortCredentialProviderList(), I have not provided any credentials, keystores etc. Because weblogic is not setup with SSL and also I have not set up any authorization or authentication for the web service. I do not know why I am able to test it through SOAPUI and why not using WS proxy.
    Appreciate your quick response.
    thanks a lot
    jyothi

  • Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING

    hello colleagues,
    In the phase Connect Diagnostics dont show the Agent available in SLD, but when go to SLD i have the agents,
    Error,
    Connect Diagnostics Agent
    The table does not contain any data
    Agent availables in all SLD
    SOAP:1.007 SRT: Unupported xstream found: ("HTTP Code 401 : Unauthorized")
    Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING
    Thanks

    OK, then pls follow below steps;
    - Go to step 'Create Users' in solman_setup System Preparation scenario and make sure the user SM_INTERN_WS has a green status. Use the 'Test Login' button to make sure the user is not locked and has correct credentials maintained in solman_setup
    - Immediately after checking the user status, navigate to Configure Connectivity->Enable Web Services and execute again the 'Create Logical Ports' automatic activity, in order to propagate the correct credentials to the Logical Port definitions.
    - If the above operation is not successful, repeat the two steps above, providing a different user Id in 'Create Users' step, eg SM_INTERN_W1. This will prevent situations where the user gets locked by Logical Ports using an obsolete password.
    Let me know the results.
    Regards,
    Vivek

  • Question concerning Web Service Deployment

    I have a question on web service deployment as it pertains to multi-client SAP systems.
    I created and deployed a web service in the client that is used for the development of client-independent objects. There are no issues when calling the web service following deployment.
    I am trying to use the same web service on the same SAP system, but on a different client. What is the proper way for accomplishing this? As of right now, the only way I've been able to do this is to open up the desired client and deploy the service again. I tried to take a transport and copy it to the other client using SCC1, but it failed since all the objects referred to client-independent objects.
    Below is the URL of the WSDL that was generated via SOAMANAGER.
    http://svr-sap05-dev.xxx.com:8010/sap/bc/srt/wsdl/bndg_DF2B9EDC2EA40CF1A9B7001CC4459012/wsdl11/allinone/ws_policy/document?sap-client=120
    Client 120 is the client used for development and is where the web service was created and deployed. I would like to use the same web service, but in a different client.
    I tried in changing the logon parameters of the web service using SICF, but the invocation failed. It only works if the client mentioned in the logon data matches the client specified in the URL.
    I am assuming that SAP builds the namespace of the web service using the client specified in the above URL. If this is the case, then I will have no choice but to deploy this service manually in the other client.
    Is something wrong being done or do I have to do the same deployment in the other client?
    Regards,
    Vince Castello

    In Netweaver 7.01 (with SOAMANAGER) you can no longer deploy webservices via STMS.
    You have to login in each client and create endpoints in each one.
    It's a pain, but SAP says it's too risky to implement the solution via STMS or something like that.
    There is a SAP note about this.

  • Rt web services deployment failed

    I have a sbrio 9612 that I setup with an executable and web services.  I can get it to run great.  I then took an image of that one (using RAD) and deployed it to another sbrio 9612.  The web services don't work.  I then tried to deploy webservices the second sbrio with my project, and I came up with the error in the attached picture: Web Services Deployment Failed.  The NI Application Web Server is still loading.  
    All I can find about that is issues when deploying to a laptop with a wifi card, but nothing about that with a RT unit.
    Any thoughts?
    Thanks,
    Eric.
    Attachments:
    error.jpg ‏83 KB

    I have redeployed the firmware several times and it still doesn't work.  It works on the original unit I took the image from, but not on the unit I'm deploying the image to.  Using max is not an option because these are basically in an OEM environment and if I distribute an image to a customer they will not have national instruments installed.
    Besides, that defeats the purpose of taking an image, if it works correctly in one place, you should be able to take an image of that and deploy it on another unit.

  • Web Service deployment on Sun One 7

    Hi,
    I'm using Netbeans 5.5 and have built a web service that targets tomcat 5.5, J2EE 1.4 and source level 1.5.
    The Service runs very well in the IDE.
    Now, the company's Web Server is Sun One 7.0 and I'm trying to deploy to this server unsuccessfully. I moved all the built files from the IDE to the Sun One 7 folders and i get the following exception on startup.
    Can anyone help please?
    Thanks.
    P.S (Do I have to install JWSDP somewhere? I see it mentioned here and there in the forum)
    Error:
    server has been shutdown
    Sun Java System Web Server 7.0-Technology-Preview-3 B09/13/2006 13:07
    info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_08] from [Sun Microsystems Inc.]
    info: WSSERVLET12: JAX-WS context listener initializing
    info: wsdl cannot be found from DD or annotation. Will generate and publish a new WSDL for SEI endpoints.
    failure: WSSERVLET11: failed to parse runtime descriptor: javax.xml.ws.WebServiceException: java.lang.ClassCastException: com.sun.xml.xwss.SystemHandlerDelegateFactory
    javax.xml.ws.WebServiceException: java.lang.ClassCastException: com.sun.xml.xwss.SystemHandlerDelegateFactory
    at com.sun.xml.ws.spi.runtime.SystemHandlerDelegateFactory.getFactory(SystemHandlerDelegateFactory.java:129)
    at com.sun.xml.ws.binding.soap.SOAPBindingImpl.setupSystemHandlerDelegate(SOAPBindingImpl.java:214)
    at com.sun.xml.ws.binding.soap.SOAPBindingImpl.<init>(SOAPBindingImpl.java:66)
    at com.sun.xml.ws.binding.BindingImpl.getBinding(BindingImpl.java:185)
    at com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser.parseEndpoints(RuntimeEndpointInfoParser.java:108)
    at com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser.parse(RuntimeEndpointInfoParser.java:66)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:110)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4171)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4697)
    at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:170)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1089)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:838)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1089)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:514)
    at org.apache.catalina.startup.Embedded.start(Embedded.java:917)
    at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:47)
    at com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:464)
    at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:292)
    Caused by: java.lang.ClassCastException: com.sun.xml.xwss.SystemHandlerDelegateFactory
    at com.sun.xml.ws.spi.runtime.SystemHandlerDelegateFactory.getFactory(SystemHandlerDelegateFactory.java:123)
    ... 17 more
    failure: WebModule[]PWC1275: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
    WSSERVLET11: failed to parse runtime descriptor: javax.xml.ws.WebServiceException: java.lang.ClassCastException: com.sun.xml.xwss.SystemHandlerDelegateFactory
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:128)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4171)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4697)
    at com.sun.webserver.connector.nsapi.WebModule.start(WebModule.java:170)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1089)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:838)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1089)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:514)
    at org.apache.catalina.startup.Embedded.start(Embedded.java:917)
    at com.sun.enterprise.web.PwcWebContainer.onStartup(PwcWebContainer.java:47)
    at com.sun.webserver.connector.nsapi.WebContainer.start(WebContainer.java:464)
    at com.sun.webserver.init.J2EERunner.confPostInit(J2EERunner.java:292)
    Caused by: javax.xml.ws.WebServiceException: java.lang.ClassCastException: com.sun.xml.xwss.SystemHandlerDelegateFactory
    at com.sun.xml.ws.spi.runtime.SystemHandlerDelegateFactory.getFactory(SystemHandlerDelegateFactory.java:129)
    at com.sun.xml.ws.binding.soap.SOAPBindingImpl.setupSystemHandlerDelegate(SOAPBindingImpl.java:214)
    at com.sun.xml.ws.binding.soap.SOAPBindingImpl.<init>(SOAPBindingImpl.java:66)
    at com.sun.xml.ws.binding.BindingImpl.getBinding(BindingImpl.java:185)
    at com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser.parseEndpoints(RuntimeEndpointInfoParser.java:108)
    at com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser.parse(RuntimeEndpointInfoParser.java:66)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:110)
    ... 11 more
    Caused by: java.lang.ClassCastException: com.sun.xml.xwss.SystemHandlerDelegateFactory
    at com.sun.xml.ws.spi.runtime.SystemHandlerDelegateFactory.getFactory(SystemHandlerDelegateFactory.java:123)
    ... 17 more
    failure: PWC1306: Context startup failed due to previous errors
    failure: Null component com.sun.web-1:type=JspMonitor,name=jsp,WebModule=//wws/,J2EEApplication=none,J2EEServer=none
    info: HTTP3072: http-listener-1: http://si-gln:8500 ready to accept requests
    info: CORE3274: successful server startup

    Did you got the solution for the issue you had?

  • Problem with Web Service Deployment

    Ugh...today is not a good day.  Has anyone seen something similar to this error when deploying web services?
    List Folder in Recursive File List.vi->NI Web Service Debug.lvlib:Zip Static Docs.vi->NI Web Service Debug.lvlibtart_WS_RTDebug.vi->NI Web Service Debug.lvlibtart_WS_RTDebug.vi.ProxyCaller<APPEND>
    C:\$Recycle.Bin\S-1-5-18
    This is totally preventing deployment and I can't decipher where to start with fixing this.
    Thanks, Matt

    Thanks, Mike.  What I ended up doing was destroying the existing Web Service and rebuilding the service.  And this worked (obviously).
    But the fact remains that there was no obvious way to recover from this.  I had initially tried to just delete the Public folder from the project and then re-add it, but to no avail.  The message was cryptic (as all deployment error messages tend to be) and exposed some black magic going on in the background (I have no idea where the List Folder Recursive File List.vi or any of those objects in the message come in - they are not called directly by me nor are they in the dependencies).  Without a clear description from NI of what is happening when you deploy a service such as this, I fear that there is no way to address the problem in a timely manner (I don't want to work on something for hours on end that worked and then with one click seemingly didn't work).
    But, this tends to be the way things go with large RT projects....
    Cheers, Matt

Maybe you are looking for