Web services: j2ee 1.4 vs weblogic

hi.
i have been an enterprise java developer for some years now but have not
stepped into web services realm until very recently. one of the reasons
for me holding back was due to this piece of news that i stumbled upon
about 4 months ago. it stated that Sun's implementation of web services
will not be fully functional until its ee 1.4 release. it claimed that
due to this lag, many app server vendors (BEA being one of them) are not
waiting for Sun, but instead developing their own versions of web
service imlementation which are specific to their respective enterprise
environments.. as a result, this would lead away from a standardized
implementation of web services within the java world. what is your take
on this?
thanks!!!

Hi Mikhail,
IMHO, Sun absolutely "drug its feet" with the JSRs that eventually resulted in
the "Java Web Services Developer Pack" (JWSDP)! See http://java.sun.com/webservices/downloads/webservicespack.html.
By the time they came up with suitable APIs, all the vendors creating Java-based
implementations of the XML grammars that underly Web services, already had shipping
product ;-) Naturally, they (Sun) would like to see all these vendors move there
product's code-base onto the API in the JWSDP, and I presume some will. The problem
I see with JWSDP is that it doesn't truly address what is still the biggest issue:
interoperability between Microsoft's Web Services tools (.NET, ASP.NET, or whatever)
and the Java-basd Web Services tools. A lot of vendors have already made "substantial
headway" in resolving this problem, and I doubt if they are willing to give this
up ;-)
That said, I think you will find that most J2EE-vendors (can't really speak for
WebLogic, of course) will wait until JWSDP becomes part of a J2EE specification,
before they expend a lot of effort "porting" their Web Service platforms to its
APIs ;-) You should probably pose your question to folks like Graham Glass (from
MindElectric, creators of GLUE) and Anne Thomas Mannes (CTO of Systinet, creators
of WASP). I'm sure they will be forthright and candid with their reply.
Regards,
Mike Wooten
mikhail perelman <[email protected]> wrote:
hi.
i have been an enterprise java developer for some years now but have
not
stepped into web services realm until very recently. one of the reasons
for me holding back was due to this piece of news that i stumbled upon
about 4 months ago. it stated that Sun's implementation of web services
will not be fully functional until its ee 1.4 release. it claimed that
due to this lag, many app server vendors (BEA being one of them) are
not
waiting for Sun, but instead developing their own versions of web
service imlementation which are specific to their respective enterprise
environments.. as a result, this would lead away from a standardized
implementation of web services within the java world. what is your take
on this?
thanks!!!

Similar Messages

  • Error in deploying a web service from jdeveloper 10 to weblogic 10

    hi , I succeed to create connexiion to weblogic 10 from jdeveloper 10 but in deploying my service i have this Exception:
    ---- Deployment started. ---- 1 mai 2009 09:21:45
    Target platform is WebLogic Server 9.x (webAppli).
    Checking weblogic.xml for completeness...
    Wrote WAR file to D:\jdevstudio10134\jdev\mywork\Soustraction\SoustarctionWS\deploy\WebServices.war
    Wrote EAR file to D:\jdevstudio10134\jdev\mywork\Soustraction\SoustarctionWS\deploy\Soustraction-SoustarctionWS-WS.ear
    D:\jdevstudio10134\jdk\jre\bin\javaw.exe -classpath C:\bea\wlserver_10.3\server\lib\wlclient.jar weblogic.Deployer -adminurl http://aymen:7001 -user weblogic -password **** -debug -verbose -deploy -upload -source D:\jdevstudio10134\jdev\mywork\Soustraction\SoustarctionWS\deploy\Soustraction-SoustarctionWS-WS.ear -name Soustraction-SoustarctionWS-WS
    weblogic.Deployer invoked with options: -adminurl http://aymen:7001 -user weblogic -debug -verbose -deploy -upload -source D:\jdevstudio10134\jdev\mywork\Soustraction\SoustarctionWS\deploy\Soustraction-SoustarctionWS-WS.ear -name Soustraction-SoustarctionWS-WS
    WebLogicDeploymentManagerImpl.<init>():103 : Constructing DeploymentManager for J2EE version V1_4 deployments
    WebLogicDeploymentManagerImpl.getNewConnection():146 : Connecting to admin server at aymen:7001, as user weblogic
    ServerConnectionImpl.getEnvironment():282 : setting environment
    ServerConnectionImpl.getEnvironment():285 : getting context using http://aymen:7001
    ServerConnectionImpl.close():328 : Closing DM connection
    ServerConnectionImpl.close():348 : Unregistered all listeners
    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://aymen:7001': Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'aymen' and port: '7001' a WebLogic Server?; No available router to destination. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:306)
    at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:143)
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:93)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.Deployer.run(Deployer.java:70)
    at weblogic.Deployer.main(Deployer.java:54)
    Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:425)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:287)
    ... 6 more
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:142)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
    ... 9 more
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: http://aymen:7001: Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'aymen' and port: '7001' a WebLogic Server?; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:48)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:739)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:343)
    at weblogic.jndi.Environment.getContext(Environment.java:263)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:167)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:324)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:296)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:140)
    ... 11 more
    Caused by: java.net.ConnectException: http://aymen:7001: Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'aymen' and port: '7001' a WebLogic Server?; No available router to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:137)
    at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:324)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:319)
    ... 16 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'aymen' and port: '7001' a WebLogic Server?; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:465)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:255)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:199)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:220)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:187)
    ... 21 more
    **** weblogic.deploy returned with non-zero exit status: 1
    **** weblogic.deploy returned with non-zero exit status: 1
    Elapsed time for deployment: 2 seconds
    #### Deployment incomplete. #### 1 mai 2009 09:21:47
    please someone help me.
    thank you
    aymen

    Hi Wenhao,
    I did face something similar ....but when i tried it again...it worked..
    In case it does not then before u try to start the procedure to dwnld the Enterprise service wsdl....
    uncheck the wsdl validator check box in NWDS...
    I suggest u first try to consume the wsdl by importing it locally...
    just follow this blog by Boris step by step..
    /people/boris.mohr/blog/2007/01/23/how-to-guide-for-consuming-a-web-service-with-a-standalone-client-using-sap-netweaver-application-server-javatm-ee-5-edition
    Once u r able to do this..then u can try to consume it from service registry
    Edited by: Mohd Tauseef Ibrahim on Jun 26, 2008 2:28 PM
    Edited by: Mohd Tauseef Ibrahim on Jun 26, 2008 2:30 PM

  • Invoking a web service from dynamic client in weblogic 7

    Is it possible to invoke a webservice from dynamic client in weblogic 7. Because i tried and it doesn't work. But it works with WL 8.1
    I don't see any samples on the net for weblogic 7.

    Hello rss,
    If you want to invoke a web service from a JCD you will have to build the SOAP message using JAX-RPC or AXIS and then programmatically creat an HTTP connection.
    Or you can leverage the HTTP(S) eWay and then you only have to build the SOAP message.
    Or use eInsight. You can import a WSDL into eInsight and eInsight will offer you a business process Activity to invoke the web service operations defined in the WSDL.

  • PL/SQL  Web Service fails when deployed to WebLogic server

    I have a web service generated via JDeveloper from a PL/SQL package. It runs fine both when tested in JDeveloper and when the WAR file is manually deployed to the Integrated WebLogic Server. However, when the WAR file is deployed to our actual WebLogic server, it fails. Other existing web services that were not generated with the JDeveloper wizard work correctly. I am having trouble finding any references to this type of issue to solve it. Are there any ideas what might be causing the WSDL to fail?
    References:
    * JDeveloper 11.1.1.6.
    * No proxies are involved.
    * The PLSQL package is a basic function that returns varchar2 input fed in by one parameter:
    create or replace package body pkg_ws_test as
    function test_me (p_anything_in varchar2)
    return varchar2 is
    begin
    return p_anything_in;
    end test_me;
    end pkg_ws_test;
    * Top of error stack is as follows:
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://svr:8892/wsTest2-getSame-context-root/TestMePort?wsdl: HTTP connection error code is 500 at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:325) at
    ...

    Hi,
    The below error trace you've provided doesn't confirm that Weblogic server has thrown the error.
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://svr:8892/wsTest2-getSame-context-root/TestMePort?wsdl: HTTP connection error code is 500 at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:325) at
    Please paste complete stacktrace of the error to check and also include the caused by section in the error.
    Thanks,
    Vijaya

  • Problem with Deployments of web service Project as EAR in weblogic console

    Hi All :-)
    I was facing the problem with the Deployments of web service(java class) as EAR.I created the one web project associated with EAR project. After my development i exported this project as EAR and deployed the same on the weblogic console.....But time it will work fine and sometime it Deployments status will not become active (its running status) and failed after activate the changes.
    Can any body tell me the real problem with weblogic console for Deployments?
    Please tell me the solution...it?s urgent for me...If you know the answer please mail me on [email protected] or reply here on forum
    Thank you very much for your time.
    Rgds
    Ranjit

    I received the same message and resolved it by adding the following jars to the classpath. All these jars came from the weblogic92 directory:
    server/lib/ant/ant.jar
    common/lib/apache_xbean.jar
    server/lib/jsafe.jar
    server/lib/weblogic.jar
    server/lib/webservices.jar
    server/lib/webserviceclient.jar
    server/lib/webserviceclient+ssl.jar
    server/lib/schema/weblogic-container-binding.jar
    server/lib/xbean.jar
    hth,
    John

  • Why JDEVADF11.1.1.3 can not test web service in IE for  Integrated WebLogic

    Hi,
    Testing a web service deployed to Integrated WebLogic Server.
    1.When you deploy the web service to Integrated WebLogic Server, examine the contents of the log window. Find http://IP_address:port/Project1-context-root/MyWebService1
    2.Copy the URL and paste it into browser. The browser shows a simple page which lists the operations available on the service.
    3.Enter a parameter, and click Enter. The result from the web service is displayed.
    My question:
    Why only display Web Services Endpoint and Information . Can not have Enter a parameter and operations available on the service.
    HttP analyzer test web service is OK.
    Thanks

    Hi,
    That is because you are looking at the endpoint information.
    If you want to test the service in a browser, then you can use the Weblogic Test Client.
    When your Integrated WLS is running, point the browser to the following url: http://localhost:7101/wls_utc/
    Thanks,
    Vishal

  • Web Services with Apache Axis plugin Weblogic

    Hi,
    I am a newbie to Web Services & Apache Axis. I have plugged in Apache Axis with
    Weblogic 6.1. I wanted to know whether an architecture of the following is possible.
    Web Services published on Apache Axis wrapped on SessionBeans on Weblogic 6.1.
    Also can I get some docs, samples that can help me.
    Any help is appreciated.
    Meghna

    Hi Meghna,
    hmmm...if you are going to start off with webservices, why not go with
    the very best available: WLS 8.1 has:
    - much better schema coverage,
    - rpc, doc-literal and doc-literal-wrapped style
    - async client
    - jms transport
    - security and RM
    - many new ant tasks
    See the full list: http://edocs.bea.com/wls/docs81/webservices.html
    All the features...plus outstanding performance and our award winning
    support.
    Bruce
    Meghna Sinha wrote:
    >
    Hi,
    I am a newbie to Web Services & Apache Axis. I have plugged in Apache Axis with
    Weblogic 6.1. I wanted to know whether an architecture of the following is possible.
    Web Services published on Apache Axis wrapped on SessionBeans on Weblogic 6.1.
    Also can I get some docs, samples that can help me.
    Any help is appreciated.
    Meghna

  • Problem with a  web service with Jbuilder 2005 and Weblogic 8.1

    Hi,
    i�m trying to create a web-service using Jbuilder 2005 Enterprise and Weblogic 8.1. It is a very simple web-service, come kinda "Hello World".
    In the last step, after deploying my "ApplicatioModule1", i get this error:
    "Unable to connect to server t3://localhost:7001 as user weblogic.
    Reason: javax.naming.CommunicationException. Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:291)
         at weblogic.jndi.Environment.getContext(Environment.java:164)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:143)
         at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(MBeanHomeTool.java:157)
         at weblogic.Deployer.runBody(Deployer.java:555)
         at weblogic.utils.compiler.Tool.run(Tool.java:146)
         at weblogic.utils.compiler.Tool.run(Tool.java:103)
         at weblogic.Deployer.main(Deployer.java:399)
    Check option -adminurl, -username and -password. "
    I dont know why i get this error. I think the weblogic server is properly configured and running.
    Anybody can help me?? Thx.

    i have found the solution to the problem myself. I only had to execute this command file startWebLogic.cmd which is placed in this default installation directory C:\bea\user_projects\domains\mydomain in order to put the server listening to ports.
    i hope anybody with the same problem could fix it by reading this post.

  • BW Web Service J2EE Engine

    Hello,
    Please can anyone tell me,
    1. if the J2EE Engine must be installed to send XML data to BW using the HTTP port provided under the WAS soap service?
    I am new working with XML data for BW and we do not have the engine installed. I have followed the 'How to send XML data to BW' but it is not clear on my question.  We are using BW 3.5.
    Thank you for any advise

    Hello Teresa,
    it is not necessary to run an J2EE engine to send XML data to BW.
    Then you craete an DataSource based on a WebService Source System we generate a WebService / WSDL in background. You can find this WebService in Transaction WSADMIN. This WebService can be used in any other development tools which can handle WSDL or can send data to the http protocoll to the WebApplications Server (ABAP).
    Best,
    Michael
    ps. The Howto paper is very old and not released for NetWeaver 2004s.

  • Example web service will not deploy in WebLogic Server 9.2

    This example:
    http://e-docs.bea.com/wls/docs92/webserv/use_cases.html#wp210789
    fails to deploy the war with the following exception:
    BUILD FAILED
    D:\dev\user_projects\webServiceDomain\myExamples\hello_world\build.xml:52: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.de
    ployer.DeployerException: Task 0 failed: [Deployer:149026]deploy application helloWorldEar on AdminServer.
    Target state: deploy failed on Server AdminServer
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee
    Does anyone know of a workaround?

    This works with WLS 10.0. Make sure you use the same version of the domain wizard as your 'setenv' command $WLS_HOME env var references (eg, wls 10.0)

  • Unable to pass xmlbeans object in weblogic web services using OEPE

    Migrating Weblogic web services from Weblogic Workshop 10.3 to Oracle Enterprise for Eclipse...Passing xmlbean generated types in arguments of webservice call
    How to work around the following errors? I do not have this error when in workshop 10.3 only in OEPE eclipse
    "oracle.eclipse.tools.webservices.compiler.CompilationException: Errors: JAX-WS web services must not have xmlBean parameter or return type"
    PLease note that I want DocType to be xmlbeans generated or inherited from org.apache.xmlbeans.XmlObject....
    @WebMethod
         public void upload(String filename, DocType doc) {
    Hi, I have legacy codes from Weblogic workshop 10.1 and 10.3.....
    I am able to compile and run in Weblogic workshop 10.3 by passing the xmlbean generated DocType as arguments in the web services call.... but why am I not able to do this in Oracle Enterprise for Eclipse OEPE......
    If I were to generate the web service from teh wsdl...it will generate it's own DocType.class in the jar files and not use the xmlbean generated class one....
    How to get iOEPE to generate the classes in build\jws\ for
    testWSService-annotation.xml
    weblogic-webservices.xml etc like in workshop
    How can I resolve this??? Am I stuck with Workshop on this?? How to work around??
    Any help or clarifications would be much appreciated.
    Inside testWS.java,
    package ws;
    import java.io.File;
    import javax.jws.*;
    import org.example.doc.DocType;
    @WebService
    public class testWS {
         @WebMethod
         public void upload(String filename, DocType doc) {
              try {
                   doc.save(new File(filename));
              catch(Exception e) {
                   System.out.println(e);
    Inside xmlbeans generated DocType.java.....and DocTypeDocuments.java
    * XML Type: DocType
    * Namespace: http://www.example.org/doc
    * Java type: org.example.doc.DocType
    * Automatically generated - do not modify.
    package org.example.doc;
    * An XML DocType(@http://www.example.org/doc).
    * This is a complex type.
    public interface DocType extends org.apache.xmlbeans.XmlObject
    public static final org.apache.xmlbeans.SchemaType type = (org.apache.xmlbeans.SchemaType)
    org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(DocType.class.getClassLoader(), "schemaorg_apache_xmlbeans.system.testWSTypeSystem").resolveHandle("doctypec217type");
    * Gets the "element1" element
    java.lang.String getElement1();
    * Gets (as xml) the "element1" element
    org.apache.xmlbeans.XmlString xgetElement1();
    * Sets the "element1" element
    void setElement1(java.lang.String element1);
    * Sets (as xml) the "element1" element
    void xsetElement1(org.apache.xmlbeans.XmlString element1);
    * Gets the "element2" element
    java.lang.String getElement2();
    * Gets (as xml) the "element2" element
    org.apache.xmlbeans.XmlString xgetElement2();
    * Sets the "element2" element
    void setElement2(java.lang.String element2);
    * Sets (as xml) the "element2" element
    void xsetElement2(org.apache.xmlbeans.XmlString element2);
    * A factory class with static methods for creating instances
    * of this type.
    public static final class Factory
    public static org.example.doc.DocType newInstance() {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance( type, null ); }
    public static org.example.doc.DocType newInstance(org.apache.xmlbeans.XmlOptions options) {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance( type, options ); }
    /** @param xmlAsString the string value to parse */
    public static org.example.doc.DocType parse(java.lang.String xmlAsString) throws org.apache.xmlbeans.XmlException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xmlAsString, type, null ); }
    public static org.example.doc.DocType parse(java.lang.String xmlAsString, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xmlAsString, type, options ); }
    /** @param file the file from which to load an xml document */
    public static org.example.doc.DocType parse(java.io.File file) throws org.apache.xmlbeans.XmlException, java.io.IOException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( file, type, null ); }
    public static org.example.doc.DocType parse(java.io.File file, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( file, type, options ); }
    public static org.example.doc.DocType parse(java.net.URL u) throws org.apache.xmlbeans.XmlException, java.io.IOException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( u, type, null ); }
    public static org.example.doc.DocType parse(java.net.URL u, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( u, type, options ); }
    public static org.example.doc.DocType parse(java.io.InputStream is) throws org.apache.xmlbeans.XmlException, java.io.IOException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( is, type, null ); }
    public static org.example.doc.DocType parse(java.io.InputStream is, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( is, type, options ); }
    public static org.example.doc.DocType parse(java.io.Reader r) throws org.apache.xmlbeans.XmlException, java.io.IOException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( r, type, null ); }
    public static org.example.doc.DocType parse(java.io.Reader r, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( r, type, options ); }
    public static org.example.doc.DocType parse(javax.xml.stream.XMLStreamReader sr) throws org.apache.xmlbeans.XmlException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( sr, type, null ); }
    public static org.example.doc.DocType parse(javax.xml.stream.XMLStreamReader sr, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( sr, type, options ); }
    public static org.example.doc.DocType parse(org.w3c.dom.Node node) throws org.apache.xmlbeans.XmlException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( node, type, null ); }
    public static org.example.doc.DocType parse(org.w3c.dom.Node node, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( node, type, options ); }
    /** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
    public static org.example.doc.DocType parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xis, type, null ); }
    /** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
    public static org.example.doc.DocType parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
    return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xis, type, options ); }
    /** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
    public static org.apache.xmlbeans.xml.stream.XMLInputStream newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
    return org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newValidatingXMLInputStream( xis, type, null ); }
    /** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
    public static org.apache.xmlbeans.xml.stream.XMLInputStream newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream xis, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
    return org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newValidatingXMLInputStream( xis, type, options ); }
    private Factory() { } // No instance of this class allowed
    Edited by: user11079482 on Jan 1, 2010 2:09 AM

    Ok just as I expected. So I guess I am left with the following two options
    1) either I switched to using JAXB in my apps instaed of xmlbeans....
    2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
    Programming Web Services for WebLogic Server (ant tasks)
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
    Getting Started With WebLogic Web Services Using JAX-RPC
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
    Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

  • Calling a WebLogic web service from a WebLogic web application

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

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

  • Error calling BEA Weblogic Web Service

    Hi all!
    We are working with SAP PI 7.0 and we have a problem when we importing the WSDL specification of a Web service. This Web service is generated automatically with WebLogic 8.1 (servicegen).
    The error is:
    +Cause: Unable to recognize the loaded document as valid WSDL 
    The value ":arrayType" is not permitted for the attribute "name" of the "QName" type in the "/schema/complexType("List")/complexContent/restriction/attribute("http://prueba.encoding.miEsquema:arrayType")" element+
    We can make some changes in the WSDL to avoid this error but SAP PI can't parse the response of the Web service...
    Anyone has worked before with Weblogic services?
    Thanks in advance.
    Best Regards,
    Roberto

    Hi all!
    We are working with SAP PI 7.0 and we have a problem when we importing the WSDL specification of a Web service. This Web service is generated automatically with WebLogic 8.1 (servicegen).
    The error is:
    +Cause: Unable to recognize the loaded document as valid WSDL 
    The value ":arrayType" is not permitted for the attribute "name" of the "QName" type in the "/schema/complexType("List")/complexContent/restriction/attribute("http://prueba.encoding.miEsquema:arrayType")" element+
    We can make some changes in the WSDL to avoid this error but SAP PI can't parse the response of the Web service...
    Anyone has worked before with Weblogic services?
    Thanks in advance.
    Best Regards,
    Roberto

  • Stateful WebLogic Web Services using cookie

    Hi all,
    How do I configure WebLogic Web Services to return cookie in the HTTP header?
    In my weblogic.xml I included the following attributes but no cookie is returned in the HTTP header.
    <session-descriptor>
    <cookie-http-only>false</cookie-http-only>
         <tracking-enabled>true</tracking-enabled>
         <cookies-enabled>true</cookies-enabled>
         <cookie-name>JSESSION_ID</cookie-name >
    </session-descriptor>
    Thanks
    SMT

    Ok just as I expected. So I guess I am left with the following two options
    1) either I switched to using JAXB in my apps instaed of xmlbeans....
    2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
    Programming Web Services for WebLogic Server (ant tasks)
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
    Getting Started With WebLogic Web Services Using JAX-RPC
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
    Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

  • Propagating user credentials to Web Services in WebLogic 6.1

    Hi All,
    Does anybody provide me some information about propagating client
    credentials to the Web Service. Agree with documentation I have tried as in
    code below, but it doesn't work. On a server i still have a guest user.
    Thanks in advance for any help.
    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.soap.http.SoapInitialContextFactory");
    h.put("weblogic.soap.wsdl.interface",
    RaServices.class.getName() );
    h.put(Context.SECURITY_AUTHENTICATION,"simple");
    h.put(Context.SECURITY_PRINCIPAL,"user");
    h.put(Context.SECURITY_CREDENTIALS,"password");
    Context context = new InitialContext(h);

    Hi Jerzy,
    Were you actually able to achieve what you wanted? I'm not exactly sure, because
    you said "it began to work", but you also said I "wasted much of your time". If
    you still are not satisfied, I'm sure the folks in our tech support area can help
    you.
    Regards,
    Mike Wooten
    "Jerzy Nawrot" <[email protected]> wrote:
    Hi Mike,
    Thank you for comprehensive explanation how to resolve my problem. I
    have
    done all work exactly
    as you wrote and then it began to work, both for static and dynamic
    client.
    As is written in WebLogic documentation
    I only restricted access to the stateless session bean that implements
    my
    Web Service, not the SOAP servlet.
    It seams that in this case user credentials are not propagated from servlet
    to ejb.
    Thanks once again you wasted much time for me.
    Regards ,
    Jerzy Nawrot
    "Michael Wooten" <[email protected]> wrote in message
    news:[email protected]...
    Hi Jerzy,
    This does indeed work, because I just verified it. Let's go througheverything
    to make sure you have all the pieces.
    1. You need client code that looks something like
    proxy.setUserName(userName);
    proxy.setPassword(password);
    where "userName" has been assigned the value of the user and "password"is
    a clear-text
    representation of their password.
    2. You need to use the Admin console to add the user to the system.I add
    mlwooten
    as a user, and employees as a group. Then I put mlwooten in the employeesgroup.
    3. The web.xml file for your web service should contain lines similarto
    this:
    <security-constraint>
    <web-resource-collection>
    <web-resource-name>PhoneBookService</web-resource-name>
    <url-pattern>/examples/webservices/security/PhoneBookService</url-pattern>
    </web-resource-collection>
    <auth-constraint>
    <role-name>AuthorizedUsers</role-name>
    </auth-constraint>
    <user-data-constraint>
    <transport-guarantee>NONE</transport-guarantee>
    </user-data-constraint>
    </security-constraint>
    <login-config>
    <auth-method>BASIC</auth-method>
    </login-config>
    <security-role>
    <role-name>AuthorizedUsers</role-name>
    </security-role>
    4. The weblogic.xml for your web service should look something like:
    <weblogic-web-app>
    <security-role-assignment>
    <role-name>AuthorizedUsers</role-name>
    <principal-name>employees</principal-name>
    </security-role-assignment>
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>examples.webservices.security.PhoneBookService</ejb-ref-name>
    <jndi-name>examples.webservices.security.PhoneBookService</jndi-name>
    </ejb-reference-description>
    </reference-descriptor>
    </weblogic-web-app>
    6. That's all I did to get it to work.
    NOTE: wsgen does not add the stuff in 4 and 5, above. You must addit
    manually.
    Regards,
    Mike Wooten
    "Jerzy Nawrot" <[email protected]> wrote:
    Hi Michael,
    Thanks for your advice.
    The way you have proposed I've tested earlier and unfortunately this
    method
    does'nt work properly too.
    It seams that session bean used as a Web Service knows nothing about
    user
    credentials passed from a client aplication.
    Maybe, there is a bug in servlet
    weblogic.soap.server.servlet.StatelessBeanAdapter wchich does'nt
    propagate
    credentials to a session bean implementing a Web Service, or some
    configuration tasks are required on the WebLogic Web Server Components
    Jerzy Nawrot
    "Michael Wooten" <[email protected]> wrote in message
    news:[email protected]...
    Hi Jerzy,
    You must do this through the WebServiceProxy object. The methods
    you
    want
    are:
    setUserName(String userName);
    setPassword(String password);
    The internals of WebServiceProxy will Base64 encode the password
    before
    it
    invokes
    the target web service.
    Regards,
    Mike Wooten
    "Jerzy Nawrot" <[email protected]> wrote:
    Hi All,
    Does anybody provide me some information about propagating client
    credentials to the Web Service. Agree with documentation I have
    tried
    as in
    code below, but it doesn't work. On a server i still have a guestuser.
    Thanks in advance for any help.
    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.soap.http.SoapInitialContextFactory");
    h.put("weblogic.soap.wsdl.interface",
    RaServices.class.getName() );
    h.put(Context.SECURITY_AUTHENTICATION,"simple");
    h.put(Context.SECURITY_PRINCIPAL,"user");
    h.put(Context.SECURITY_CREDENTIALS,"password");
    Context context = new InitialContext(h);

Maybe you are looking for