Life BEA web service

Hi,
Can someone help me to find some examples of live/open web services create
on BEA that i can test my new solution with?
thanks

Hello,
Check out this site: http://webservice.bea.com:7001
Hope this helps,
Bruce
Omri Reuter wrote:
Hi,
Can someone help me to find some examples of live/open web services create
on BEA that i can test my new solution with?
thanks

Similar Messages

  • Future direction of BEA Web Services? - binary / attachments

    Hello,
    I'm looking at needing to transfer binary data through a web service,
    but can't handle the 4/3+ size increase that occurs when embedding the
    data with base64 encoding.
    I know that WL 8.1sp3 support SwA, but that standard is being deprecated
    in favor of newer technologies like Fast Web Services (based on ASN.1
    encoding rules), MTOM/XOP, Basic Attachments Profile.
    We'd prefer to be able to rely on the support of the application server.
    What is BEA's future direction in terms of this technology? Will they be
    supporting one or all of these binary standards? When is the estimated
    date for this technology to be implemented?
    If these technologies won't be implemented for a while, is it possible
    to plug in 3rd party web services solutions into BEA WL8.1 (e.g. Sun's
    JWSDP, Axis, etc)? I believe it is, but am just asking for the sake of a
    full answer.
    Thanks

    Steve,
    Due to BEA's award winning support they offer, I had to figure this out on my own. After weeks of dealing with a support case they provided me with absolutely nothing. Just as they have done in this thread. I will share what I have done for the mean time to get around their limitations using attachments.
    I used the Axis libraries to create a DIME attachment and call a BEA web service. Since BEA doesn't support Dime, a servlet filter had to be implemented and parse the DIME message prior to the web service received it. I'm sending 2GB files with transfer rates of 6MB/S.
    This is a response from BEA's award winning support:
    "We do not have good specification standard as yet as to how to best solve the issue. It appears like a pretty larger issue to solve because of the lack os standards and specification. Engineering is still researching on the issue and we don't know which version will have the fix."

  • BEA Web Service Session Example (Reformatted)

    Hi,<br>
    <p>
    Has anyone been able to get access to the HTTP Session functionality from a web
    service under WebLogic 8.1sp1 (Service Pack 1)?
    I tried the example as shown at http://e-docs.bea.com/wls/docs81/webserv/api.html#1067906.
    The relevant code section is as
    follows:
    <pre>
    import weblogic.webservice.context.WebServiceContext;
    import weblogic.webservice.context.ContextNotFoundException;
    import weblogic.webservice.context.WebServiceSession;
    * Shows how to use HTTP Session to maintain session state between
    * invokes
    public int maintainSessionState(){
    try{
    WebServiceContext wsContext = WebServiceContext.currentContext();
    WebServiceSession session = (WebServiceSession)wsContext.getSession();
    Integer count = (Integer)session.getAttribute( "count" );
    count = (count==null) ?
    new Integer( 0 ) : new Integer( count.intValue() + 1 );
    session.setAttribute( "count", count );
    return count.intValue();
    }catch( ContextNotFoundException e ){
    e.printStackTrace();
    return -1;
    </pre>
    </p>
    <p>
    The ContextNotFoundException exception is thrown (the web service returns a –1
    as it’s result). I have tried everything I
    could think of to track this problem down, but I’ve had no luck. Here is my setup.<br>
    Environment:<br>
    WebLogic 8.1 (Service Pack 1)<br>
    JDK 1.4.1.03<br>
    Windows 2000<br>
    </p>
    <p>
    I created a new clean Basic WebLogic Workshop Domain using the Configuration Wizard
    that ships with WebLogic 8.1sp1. No JDBC,
    JMS, or anything extra. I then created a new clean Empty Application under WebLogic
    Workshop that ships with WebLogic 8.1sp1.
    I associated the Application with the domain through Workshop’s Tools/Application
    Properties menu. I added one Web Service
    project to the application, then added one Web Service to the project, and then
    added one method to the Web Service. I renamed
    the method to the same method as in the example listed above. I copied all the
    imports and method implementation into the web
    service. Then ran the web service inside workshop. It failed. The method returned
    a –1 (the ContextNotFoundException was
    thrown). The return value from the WebServiceContext.currentContext() called
    is null.
    </p>
    <p>
    When I start a debug session (Debug\Start in Workshop), the following warning
    is emitted:<br>
    <br>
    <Warning> <WLW> <000000> <Unable to load class ProcessControl><br>
    <br>
    Not sure if this is part of the problem. Other than not being able to get the
    context through WebServiceContext, everything
    else with the web services seems to be running fine.
    </p>
    <p>
    When I run the example above I get the following stack trace in the logs:
    <br>
    <pre>
    weblogic.webservice.context.ContextNotFoundException: unable to find context for
    current thread
         at weblogic.webservice.context.WebServiceContext.currentContext(WebServiceContext.java:36)
    at WebServiceSessionTest.maintainSessionState(WebServiceSessionTest.jws:15)
    at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:353)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:245)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:185)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:99)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:59)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:159)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:134)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:46)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.exploreExec(HttpServerHelper.java:253)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executeGetRequest(HttpServerHelper.java:570)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doGet(HttpServer.java:81)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    </pre>
    </p>
    Thanks in advance,
    <br>
    Brad Babb
    P.S. Is there a preview pain somewhere on the posting page?

    Hi,<br>
    <p>
    Has anyone been able to get access to the HTTP Session functionality from a web
    service under WebLogic 8.1sp1 (Service Pack 1)?
    I tried the example as shown at http://e-docs.bea.com/wls/docs81/webserv/api.html#1067906.
    The relevant code section is as
    follows:
    <pre>
    import weblogic.webservice.context.WebServiceContext;
    import weblogic.webservice.context.ContextNotFoundException;
    import weblogic.webservice.context.WebServiceSession;
    * Shows how to use HTTP Session to maintain session state between
    * invokes
    public int maintainSessionState(){
    try{
    WebServiceContext wsContext = WebServiceContext.currentContext();
    WebServiceSession session = (WebServiceSession)wsContext.getSession();
    Integer count = (Integer)session.getAttribute( "count" );
    count = (count==null) ?
    new Integer( 0 ) : new Integer( count.intValue() + 1 );
    session.setAttribute( "count", count );
    return count.intValue();
    }catch( ContextNotFoundException e ){
    e.printStackTrace();
    return -1;
    </pre>
    </p>
    <p>
    The ContextNotFoundException exception is thrown (the web service returns a –1
    as it’s result). I have tried everything I
    could think of to track this problem down, but I’ve had no luck. Here is my setup.<br>
    Environment:<br>
    WebLogic 8.1 (Service Pack 1)<br>
    JDK 1.4.1.03<br>
    Windows 2000<br>
    </p>
    <p>
    I created a new clean Basic WebLogic Workshop Domain using the Configuration Wizard
    that ships with WebLogic 8.1sp1. No JDBC,
    JMS, or anything extra. I then created a new clean Empty Application under WebLogic
    Workshop that ships with WebLogic 8.1sp1.
    I associated the Application with the domain through Workshop’s Tools/Application
    Properties menu. I added one Web Service
    project to the application, then added one Web Service to the project, and then
    added one method to the Web Service. I renamed
    the method to the same method as in the example listed above. I copied all the
    imports and method implementation into the web
    service. Then ran the web service inside workshop. It failed. The method returned
    a –1 (the ContextNotFoundException was
    thrown). The return value from the WebServiceContext.currentContext() called
    is null.
    </p>
    <p>
    When I start a debug session (Debug\Start in Workshop), the following warning
    is emitted:<br>
    <br>
    <Warning> <WLW> <000000> <Unable to load class ProcessControl><br>
    <br>
    Not sure if this is part of the problem. Other than not being able to get the
    context through WebServiceContext, everything
    else with the web services seems to be running fine.
    </p>
    <p>
    When I run the example above I get the following stack trace in the logs:
    <br>
    <pre>
    weblogic.webservice.context.ContextNotFoundException: unable to find context for
    current thread
         at weblogic.webservice.context.WebServiceContext.currentContext(WebServiceContext.java:36)
    at WebServiceSessionTest.maintainSessionState(WebServiceSessionTest.jws:15)
    at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:353)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:245)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:185)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:99)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:59)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:159)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:134)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:46)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.exploreExec(HttpServerHelper.java:253)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executeGetRequest(HttpServerHelper.java:570)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doGet(HttpServer.java:81)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    </pre>
    </p>
    Thanks in advance,
    <br>
    Brad Babb
    P.S. Is there a preview pain somewhere on the posting page?

  • BEA Web Service Session Example

    Hi,
    Has anyone been able to get access to the HTTP Session functionality from a web
    service under WebLogic 8.1sp1 (Service Pack 1)? I tried the example as shown at
    http://e-docs.bea.com/wls/docs81/webserv/api.html#1067906. The relevant code
    section is as follows:
    import weblogic.webservice.context.WebServiceContext;
    import weblogic.webservice.context.ContextNotFoundException;
    import weblogic.webservice.context.WebServiceSession;
    * Shows how to use HTTP Session to maintain session state between
    * invokes
    public int maintainSessionState(){
    try{
    WebServiceContext wsContext = WebServiceContext.currentContext();
    WebServiceSession session = (WebServiceSession)wsContext.getSession();
    Integer count = (Integer)session.getAttribute( "count" );
    count = (count==null) ?
    new Integer( 0 ) : new Integer( count.intValue() + 1 );
    session.setAttribute( "count", count );
    return count.intValue();
    }catch( ContextNotFoundException e ){
    e.printStackTrace();
    return -1;
    The ContextNotFoundException exception is thrown (the web service returns a –1
    as it’s result). I have tried everything I could think of to track this problem
    down, but I’ve had no luck. Here is my setup.
    Environment:
    WebLogic 8.1 (Service Pack 1)
    JDK 1.4.1.03
    Windows 2000
    I created a new clean Basic WebLogic Workshop Domain using the Configuration Wizard
    that ships with WebLogic 8.1sp1. No JDBC, JMS, or anything extra. I then created
    a new clean Empty Application under WebLogic Workshop that ships with WebLogic
    8.1sp1. I associated the Application with the domain through Workshop’s Tools/Application
    Properties menu. I added one Web Service project to the application, then added
    one Web Service to the project, and then added one method to the Web Service.
    I renamed the method to the same method as in the example listed above. I copied
    all the imports and method implementation into the web service. Then ran the
    web service inside workshop. It failed. The method returned a –1 (the ContextNotFoundException
    was thrown). The return value from the WebServiceContext.currentContext() called
    is null.
    When I start a debug session (Debug\Start in Workshop), the following warning
    is emitted:
    <Warning> <WLW> <000000> <Unable to load class ProcessControl>
    Not sure if this is part of the problem. Other than not being able to get the
    context through WebServiceContext, everything else with the web services seems
    to be running fine.
    When I run the example above I get the following stack trace in the logs:
    weblogic.webservice.context.ContextNotFoundException: unable to find context for
    current thread
         at weblogic.webservice.context.WebServiceContext.currentContext(WebServiceContext.java:36)
    at WebServiceSessionTest.maintainSessionState(WebServiceSessionTest.jws:15)
    at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:353)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:245)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:185)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:99)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:59)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:159)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:134)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:46)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.exploreExec(HttpServerHelper.java:253)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executeGetRequest(HttpServerHelper.java:570)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doGet(HttpServer.java:81)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Thanks in advance,
    Brad Babb

    The maintain session example works only with the
    web service stack that comes with WLS. You
    need to use servicegen, source2wsdd, etc ant
    tasks to assemble this web service.
    Here is the full session example:
    http://www.manojc.com/?sample30
    Webservice generated by Workshop use a diffrent
    soap stack and this functionality is not supported in it.
    Regards,
    -manoj
    http://manojc.com
    "Brad Babb" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi,
    Has anyone been able to get access to the HTTP Session functionality froma web
    service under WebLogic 8.1sp1 (Service Pack 1)? I tried the example asshown at
    http://e-docs.bea.com/wls/docs81/webserv/api.html#1067906. The relevant
    code
    section is as follows:
    import weblogic.webservice.context.WebServiceContext;
    import weblogic.webservice.context.ContextNotFoundException;
    import weblogic.webservice.context.WebServiceSession;
    * Shows how to use HTTP Session to maintain session state between
    * invokes
    public int maintainSessionState(){
    try{
    WebServiceContext wsContext = WebServiceContext.currentContext();
    WebServiceSession session =(WebServiceSession)wsContext.getSession();
    Integer count = (Integer)session.getAttribute( "count" );
    count = (count==null) ?
    new Integer( 0 ) : new Integer( count.intValue() + 1 );
    session.setAttribute( "count", count );
    return count.intValue();
    }catch( ContextNotFoundException e ){
    e.printStackTrace();
    return -1;
    The ContextNotFoundException exception is thrown (the web service returnsa -1
    as it's result). I have tried everything I could think of to track thisproblem
    down, but I've had no luck. Here is my setup.
    Environment:
    WebLogic 8.1 (Service Pack 1)
    JDK 1.4.1.03
    Windows 2000
    I created a new clean Basic WebLogic Workshop Domain using theConfiguration Wizard
    that ships with WebLogic 8.1sp1. No JDBC, JMS, or anything extra. I thencreated
    a new clean Empty Application under WebLogic Workshop that ships withWebLogic
    8.1sp1. I associated the Application with the domain through Workshop'sTools/Application
    Properties menu. I added one Web Service project to the application, thenadded
    one Web Service to the project, and then added one method to the WebService.
    I renamed the method to the same method as in the example listed above.I copied
    all the imports and method implementation into the web service. Then ranthe
    web service inside workshop. It failed. The method returned a -1 (theContextNotFoundException
    was thrown). The return value from the WebServiceContext.currentContext()called
    is null.
    When I start a debug session (Debug\Start in Workshop), the followingwarning
    is emitted:
    <Warning> <WLW> <000000> <Unable to load class ProcessControl>
    Not sure if this is part of the problem. Other than not being able to getthe
    context through WebServiceContext, everything else with the web servicesseems
    to be running fine.
    When I run the example above I get the following stack trace in the logs:
    weblogic.webservice.context.ContextNotFoundException: unable to findcontext for
    current thread
    atweblogic.webservice.context.WebServiceContext.currentContext(WebServiceConte
    xt.java:36)
    atWebServiceSessionTest.maintainSessionState(WebServiceSessionTest.jws:15)
    at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source)
    atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
    .java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    atcom.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:353)
    atcom.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420)
    atcom.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393)
    atcom.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:245)
    atcom.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean
    .java:185)
    atcom.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.jav
    a:103)
    atcom.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_l
    y05hg_ELOImpl.java:99)
    atcom.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLS
    BContAdpt.java:59)
    atcom.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherB
    ean.java:160)
    atcom.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.j
    ava:54)
    atcom.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.j
    ava:159)
    atcom.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispat
    cher_k1mrl8_EOImpl.java:100)
    atcom.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.jav
    a:134)
    atcom.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:46)
    atcom.bea.wlw.runtime.core.dispatcher.HttpServerHelper.exploreExec(HttpServerH
    elper.java:253)
    atcom.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executeGetRequest(HttpS
    erverHelper.java:570)
    atcom.bea.wlw.runtime.core.dispatcher.HttpServer.doGet(HttpServer.java:81)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    atweblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
    tStubImpl.java:1053)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :387)
    atweblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    atweblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    atweblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
    ebAppServletContext.java:6316)
    atweblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
    t.java:317)
    atweblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:3622)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Thanks in advance,
    Brad Babb

  • Expecting response in XML format after invoking bea web service

    What should I do in order to receive the response from the web service in XML document
    (i.e. a well-formed XML document) after invoking the web service via my client
    application
    (a servlet in my case)? I would like to validate the XML document against a schema
    in my
    servlet. I deployed my web service sucessfully and followed the WSDL web page
    recommendation about creating a client. That is I used the generated stub (client
    jar file
    generated using clientgen) in my servlet. The result I received was a java object
    and not in
    XML document form.

    If you do clientgen on a WSDL, it will generate
    java types by default. You can trun this off by
    setting autotype="false" in the clientgen ant task.
    I have not tried it out, but i think this will use
    javax.xml.soap.SOAPElement instead of
    generated java types. Then you can create a
    DOM object from soap element.
    Another option is to use DII with generic
    typemapping. An example here:
    http://www.manojc.com/?sample27
    Regards,
    -manoj
    http://manojc.com
    "Michael Wong" <[email protected]> wrote in message
    news:3f1edd7c$[email protected]..
    >
    What should I do in order to receive the response from the web service inXML document
    (i.e. a well-formed XML document) after invoking the web service via myclient
    application
    (a servlet in my case)? I would like to validate the XML document againsta schema
    in my
    servlet. I deployed my web service sucessfully and followed the WSDL webpage
    recommendation about creating a client. That is I used the generated stub(client
    jar file
    generated using clientgen) in my servlet. The result I received was ajava object
    and not in
    XML document form.

  • Why cannot build BEA web service examples?

    My weblogic is 7.0 and the webservices.jar has been installed. When I built an
    example, the console alert me that the javax.xml.namespace.Qname cannot be found.
    Later I found out that the Qname class is included in JDK1.4 and I installed it.
    But the console alert me that the weblogic/management/descriptors/webservice/FaultMBean
    cannot be found when I build the example again.
    What can I do?

    [att1.html]

  • Web services Development

    A general question for the group (sorry if this is off-topic, if there's a better
    forum for this type of Q let me know).
    I'm a web services and web app developer who is new to BEA. In the past I've used
    toolkits like Axis for web services and I've always preferred this approach. It
    seems to me that using BEA I can develop Web Services in one of two ways. The
    'low-level' way where I could use the command line tools (or ant) to create, deploy
    and manage the code, or I could use WLW and the nice attribute driven approach.
    It strikes me (on first blush) that these techniques are not compatible, so if
    I choose one I have to stick with that, and I shouldn't (can't) mix and match
    the two.
    As a relative newcomer to this community which one should I choose?
    Which are people out there using?
    Can the approaches me mixed?
    What implications does using one or the other have in terms of deployment and
    the type of WLS I have installed?
    Again sorry if this is off topic, or an RTFM. If either of these is the case pointers
    to the FM would be appreciated.
    Thanks,
    Kevin Jones

    I think if you are looking for training in "BEA web services" then do
    it the WLW way.
    However, if you think your web service may be deployed to a non-BEA
    app server, then pick up the standards.
    This is true for regular web apps using struts vs. WLW's 'netui'
    and JSR 162 vs. WLW Portals as well.
    Kevin Jones wrote:
    Thanks Michael,
    anybody else have any comments?
    For example if you were looking for training in BEA web services would you expect
    it to be WLW or 'command line' based?
    Kevin
    "Michael Wooten" <[email protected]> wrote:
    Hi Kevin,
    The two web services development approaches are for two different audiences,
    so
    it's up to you to select which is more to your liking :-)
    Developers who are familiar with the Apache Axis Web Services Platform,
    will find
    lots of similarities in the Ant-scrpt based approach that the WLS 8.1
    Web Services
    Platform uses. This would also be the environment for those that really
    like to
    see that their code uses classes from a standard, like JAX-RPC or SAAJ.
    Workshop is really targeted at developers who are less interested in
    the mechanics
    of Web service construction, and more interested in what they want the
    web service
    to do. It offers developers with this mindset, almost complete isolation
    from
    the technologies associated with web service development (i.e. SOAP,
    WSDL, XML,
    etc.), while still producing a deployable web service that can interoperate
    with
    web services created by other Web Service stacks.
    Again, both of these approaches have healthy developer audiences, so
    I see no
    real reason to promote one over the other. Personally, I think it makes
    sense
    to become adept at both.
    All in all, I'd have to say that Workshop makes better use of the developer's
    time :-)
    Regards,
    Mike Wooten
    "Kevin Jones" <[email protected]> wrote:
    A general question for the group (sorry if this is off-topic, if there's
    a better
    forum for this type of Q let me know).
    I'm a web services and web app developer who is new to BEA. In the past
    I've used
    toolkits like Axis for web services and I've always preferred this approach.
    It
    seems to me that using BEA I can develop Web Services in one of twoways.
    The
    'low-level' way where I could use the command line tools (or ant) to
    create, deploy
    and manage the code, or I could use WLW and the nice attribute driven
    approach.
    It strikes me (on first blush) that these techniques are not compatible,
    so if
    I choose one I have to stick with that, and I shouldn't (can't) mixand
    match
    the two.
    As a relative newcomer to this community which one should I choose?
    Which are people out there using?
    Can the approaches me mixed?
    What implications does using one or the other have in terms of deployment
    and
    the type of WLS I have installed?
    Again sorry if this is off topic, or an RTFM. If either of these isthe
    case pointers
    to the FM would be appreciated.
    Thanks,
    Kevin Jones

  • Web Services After Deployment...???

    This may be a dumb question since I am new and evaluating BEA WebLogic products.
    I follow the tutorials (Web Services, to be specific) all the way to build EAR
    file and deploy it.
    Now, WHAT DO I DO ???
    Suppose my server is TestServer, my BEA Web Services is TestWebServices,
    What URL should I navigate to verify the deployment is success ?
    Here the the contents of my WebLogic Console Deployments:
    Configurations:
    Name: TestWebServices
    Path: E:\Bea\TestWebServices
    Deployment Protocol: Two-Phase
    Staging Mode: nostage
    Targets:
    Independent Servers: TestServer
    Deploys:
    Module:TestWebServicesWeb Status:Active Target:testServer Type:Server LastAction:Success
    Can I have a specific url example to try ?
    Thanks.

    I'd suggest you start with the tutorials on this site:
    http://dev2dev.bea.com/index.jsp
    -- Rob
    Tom Nagel wrote:
    This may be a dumb question since I am new and evaluating BEA WebLogic products.
    I follow the tutorials (Web Services, to be specific) all the way to build EAR
    file and deploy it.
    Now, WHAT DO I DO ???
    Suppose my server is TestServer, my BEA Web Services is TestWebServices,
    What URL should I navigate to verify the deployment is success ?
    Here the the contents of my WebLogic Console Deployments:
    Configurations:
    Name: TestWebServices
    Path: E:\Bea\TestWebServices
    Deployment Protocol: Two-Phase
    Staging Mode: nostage
    Targets:
    Independent Servers: TestServer
    Deploys:
    Module:TestWebServicesWeb Status:Active Target:testServer Type:Server LastAction:Success
    Can I have a specific url example to try ?
    Thanks.

  • Problem in calling a web service hosted on tomcat from BEA WebLogic portal

    Hi,
    I have a wsdl file for my web service which is hosted on apache tomcat 5.5(running on port : 8080). The contents of the wsdl file are-
    *<?xml version="1.0" encoding="UTF-8"?>*
    *<wsdl:definitions targetNamespace="http://soa.tutorials.serg.edu" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://soa.tutorials.serg.edu" xmlns:intf="http://soa.tutorials.serg.edu" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">*
    *<!--WSDL created by Apache Axis version: 1.4*
    Built on Apr 22, 2006 (06:55:48 PDT)-->
    *<wsdl:types>*
    *<schema elementFormDefault="qualified" targetNamespace="http://soa.tutorials.serg.edu" xmlns="http://www.w3.org/2001/XMLSchema">*
    *<element name="getNums">*
    *<complexType>*
    *<sequence>*
    *<element name="n" type="xsd:int"/>*
    *<element name="m" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNumsResponse">*
    *<complexType>*
    *<sequence>*
    *<element maxOccurs="unbounded" name="getNumsReturn" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNums2">*
    *<complexType>*
    *<sequence>*
    *<element name="n" type="xsd:int"/>*
    *<element name="m" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNums2Response">*
    *<complexType>*
    *<sequence>*
    *<element maxOccurs="unbounded" name="getNums2Return" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *</schema>*
    *</wsdl:types>*
    *<wsdl:message name="getNums2Request">*
    *<wsdl:part element="impl:getNums2" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNumsRequest">*
    *<wsdl:part element="impl:getNums" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNums2Response">*
    *<wsdl:part element="impl:getNums2Response" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNumsResponse">*
    *<wsdl:part element="impl:getNumsResponse" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:portType name="Echo">*
    *<wsdl:operation name="getNums">*
    *<wsdl:input message="impl:getNumsRequest" name="getNumsRequest"/>*
    *<wsdl:output message="impl:getNumsResponse" name="getNumsResponse"/>*
    *</wsdl:operation>*
    *<wsdl:operation name="getNums2">*
    *<wsdl:input message="impl:getNums2Request" name="getNums2Request"/>*
    *<wsdl:output message="impl:getNums2Response" name="getNums2Response"/>*
    *</wsdl:operation>*
    *</wsdl:portType>*
    *<wsdl:binding name="EchoSoapBinding" type="impl:Echo">*
    *<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>*
    *<wsdl:operation name="getNums">*
    *<wsdlsoap:operation soapAction=""/>*
    *<wsdl:input name="getNumsRequest">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:input>*
    *<wsdl:output name="getNumsResponse">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:output>*
    *</wsdl:operation>*
    *<wsdl:operation name="getNums2">*
    *<wsdlsoap:operation soapAction=""/>*
    *<wsdl:input name="getNums2Request">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:input>*
    *<wsdl:output name="getNums2Response">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:output>*
    *</wsdl:operation>*
    *</wsdl:binding>*
    *<wsdl:service name="EchoService">*
    *<wsdl:port binding="impl:EchoSoapBinding" name="Echo">*
    *<wsdlsoap:address location="http://localhost:8080/SOATest/services/Echo"/>*
    *</wsdl:port>*
    *</wsdl:service>*
    *</wsdl:definitions>*
    I created a client from the above wsdl file using ClientGen wizard in WebLogic. This client contains the follwoing classes-
    Echo.java
    EchoService.java
    EchoService_Impl.java
    Echo_Stub.java
    I created a JSP portlet and the jsp content of it is-
    String url = "http://localhost:8080/SOATest/services/Echo";
    Echo echo = new EchoService_Impl(url).getEcho();
    getNumsResponse = echo.getNums(getNums);
    I tried to call that web service from BEA weblogic portal through a JSP potlet. I got an error saying -
    *<An exception [javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element] was thrown while rendering the content at [TestEcho.jsp].*
    *javax.servlet.ServletException: javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.servlet.jsp.PageContextImpl.handlePageException(PageContextImpl.java:420)*
    *     at jsp_servlet.__testecho._jspService(__testecho.java:112)*
    *     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)*
    *     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)*
    *     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)*
    *     Truncated. see log file for complete stacktrace*
    *javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:174)*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:485)*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)*
    *     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
    *     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
    *     Truncated. see log file for complete stacktrace*
    *weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:391)*
    *     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)*
    *     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)*
    *     Truncated. see log file for complete stacktrace*
    *java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:38)*
    *     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:122)*
    *     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)*
    *     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
    *     Truncated. see log file for complete stacktrace*
    *javax.xml.stream.XMLStreamException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:206)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:73)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:35)*
    *     Truncated. see log file for complete stacktrace*
    *Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.babel.baseparser.BaseParser.parseProlog(BaseParser.java:417)*
    *     at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:328)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:195)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
    *     Truncated. see log file for complete stacktrace*
    My web service is using soap binding. I have tested it with eclipse and other tools also. It is working well and good. But when I tried to call a web service which is created and hosted on WebLogic server(running on port : 7001), I got the correct output.
    Can anyone help me out in calling a web service hosted on different server from WebLogic server.
    Thanks in advance,
    Tiijnar
    Edited by: user8715057 on Aug 13, 2009 1:11 AM

    Hi
    1. The way you are invoking the WebService deployed on Tomcat server is looks suspicious. It may be valid by adding extra ?wsdl etc into the url, but still I have not seen this way to invoke the webservice.
    2. So you used Weblogic ant task to generate client JARs by giving this WSDL. So looks like it generated the 4 classes (.java) and in addition any other classes for Request/Response xml objects.
    3. Look at the source code of EchoService.java. It should have one default empty constructor. Internally it uses the default wsdl defined in this class. You will see another constructor that takes WSDL URL as one of the parameters (QName) etc. Echo.java is the class corresponding to the Port. In the same EchoService you should see an instance method like getEcho() something like that. This Echo.java class will have methods for all the Operations defined on this Port. So the standard code snippet we use most of the times will be like this:
    EchoService myEchoService = new EchoService(); // Default it uses WSDL deployed on Tomcat at localhost:8080
    Echo myEchoPort = myEchoService.getEchoPort(); // Something along these lines.
    myEchoPort.xxxYYY(); // NOW this is the operation name that takes the input parameters and returns outputs defined as per the WSDL defintions. If the Input and Outputs are complex xml types, it will have corresponing .JAVA files with setters and getters.
    Now if this WebService is deployed on same Tomcat but on different machine or different port, you just give the full WSDL URL with that host and port in the constructor for new EchoService(...). You may need to instantiate QName object. But look at the methods generated in EchoService.java class.
    The way you are using with Impl and Stubs class may also work. I am not much famiiar with this APIs apporach. Still look at the methods generated in these classes.
    Also if you latest Sun JDK 1.6, it also has one command like wsimport. Infact if you install WLS 10.3 with Sun JDK, it should have C:\beawlp103\jdk160_05\bin\wsimport command. This will also generate client jar given a WSDL URL.
    Thanks
    Ravi Jegga

  • Error invoking Web Service from Web application in BEA

    I have a web service wich run fine at bea weblogic.
    If i invoke it from webapp in sunappserver no problem , from plain client no problem , from oc4j no problem, but if a invoke from same webapp from weblogic i get this error:
    <b>java.rmi.RemoteException: Failed to invoke; nested exception is:
    javax.xml.rpc.JAXRPCException: web service invoke failed: javax.xml.soap.SOAPException: failed to ser
    ialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup
    failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://ejb.ds
    ic.pucv.cl/types/']:getMatriculaElement}
    at jrockit.reflect.NativeConstructorInvoker.newInstance([Ljava.lang.Object;)Ljava.lang.Object;(Unknown
    Source)
    at java.lang.reflect.Constructor.newInstance([Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
            at weblogic.webservice.core.rpc.StubImpl.throwRemoteException(StubImpl.java:269)
            at weblogic.webservice.core.rpc.StubImpl.invoke(StubImpl.java:254)
            at $Proxy46.getMatricula(Ljava.lang.String;)Ljava.lang.String;(Unknown Source)
            at cl.pucv.dsic.ws.cliente.ClienteWebService.getMatricula(ClienteWebService.java:100)
            at cl.pucv.dsic.consulta.queryBtn_action(consulta.java:667)
            at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.
    Object;(Unknown Source)
            at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown S
    ource)
            at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
            at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72)
            at com.sun.rave.web.ui.appbase.faces.ActionListenerImpl.processAction(ActionListenerImpl.java:57)
            at javax.faces.component.UICommand.broadcast(UICommand.java:312)
            at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:267)
            at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:381)
            at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:75)
            at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
            at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
            at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
            at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
            at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
    Caused by: javax.xml.rpc.JAXRPCException: web service invoke failed: javax.xml.soap.SOAPException:  failed to
    serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping look
    up failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://ejb
    .dsic.pucv.cl/types/']:getMatriculaElement}
    at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:334)
    at weblogic.webservice.core.rpc.StubImpl.invoke(StubImpl.java:250)
    at $Proxy46.getMatricula(Ljava.lang.String;)Ljava.lang.String;(Unknown Source)
    at cl.pucv.dsic.ws.cliente.ClienteWebService.getMatricula(ClienteWebService.java:100)
    at cl.pucv.dsic.consulta.queryBtn_action(consulta.java:667)
    at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.
    Object;(Unknown Source)
    at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown S
    ource)
            at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
            at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72)
            at com.sun.rave.web.ui.appbase.faces.ActionListenerImpl.processAction(ActionListenerImpl.java:57)
            at javax.faces.component.UICommand.broadcast(UICommand.java:312)
            at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:267)
            at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:381)
            at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:75)
            at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
            at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
            at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
            at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
            at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
            at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
            at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
            at com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.jav
    a:3212)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
            at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
            at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)</b>
    the WSDL for this ws is:
    <b> <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions name="WSMatricula" targetNamespace="http://ejb.dsic.pucv.cl/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="http://ejb.dsic.pucv.cl/types/" xmlns:s1="http://ejb.dsic.pucv.cl/" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
    - <types>
    - <xsd:schema elementFormDefault="qualified" targetNamespace="http://ejb.dsic.pucv.cl/types/" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ns1="http://ejb.dsic.pucv.cl/types/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://ejb.dsic.pucv.cl/types/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <xsd:element name="getMatriculaElement" nillable="true" type="string" />
      <xsd:element name="getMatriculaResponseElement" nillable="true" type="string" />
      </xsd:schema>
      </types>
    - <message name="EJBConsultaWebService_getMatricula">
      <part element="s0:getMatriculaElement" name="parameters" />
      </message>
    - <message name="EJBConsultaWebService_getMatriculaResponse">
      <part element="s0:getMatriculaResponseElement" name="result" />
      </message>
    - <portType name="WSMatricula">
    - <operation name="getMatricula">
      <input message="s1:EJBConsultaWebService_getMatricula" />
      <output message="s1:EJBConsultaWebService_getMatriculaResponse" />
      </operation>
      </portType>
    - <binding name="WSMatriculaSoapHttp" type="s1:WSMatricula">
      <s2:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="getMatricula">
      <s2:operation soapAction="http://ejb.dsic.pucv.cl//getMatricula" />
    - <input>
      <s2:body parts="parameters" use="literal" />
      </input>
    - <output>
      <s2:body parts="result" use="literal" />
      </output>
      </operation>
      </binding>
    - <service name="WSMatricula">
    - <port binding="s1:WSMatriculaSoapHttp" name="WSMatriculaSoapHttpPort">
      <s2:address location="http://ip:port/EJB-WebServicesDSIC/WSMatriculaSoapHttpPort" />
      </port>
      </service>
      </definitions></b>
    and the client is
    <b>
    package cl.pucv.dsic.ws.cliente;
    import com.ac.util.MyDOMParser;
    import java.util.Hashtable;
    import java.util.ArrayList;
    import com.ac.util.Config;
    import java.net.URL;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.JAXRPCException;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.ServiceFactory;
    import org.w3c.dom.Document;
    import org.w3c.dom.NodeList;
    import java.io.*;
    public class ClienteWebService implements Serializable  {
    private String UrlString    = "";
    private String nameSpaceUri = "";
    private String serviceName  = "";
    private String portName     = "";
        public ClienteWebService() {
    public String getMatricula(String servicename, String param) throws Exception
    try
    Hashtable ht = (Hashtable)Config.getInstance().getHashtable("WS","Nombre",servicename);
    setUrlString((String)ht.get("EndPoint"));
    setNameSpaceUri((String)ht.get("URI"));
    setServiceName((String)ht.get("ServiceName"));
    setPortName((String)ht.get("PortName"));
    URL wsdlUrl = new URL(getUrlString() + "?WSDL");
    ServiceFactory serviceFactory = ServiceFactory.newInstance();
    Service helloService =
    serviceFactory.createService(wsdlUrl,
    new QName(getNameSpaceUri(), getServiceName()));
    WebServiceDSICIF myProxy =
    (WebServiceDSICIF) helloService.getPort(new QName(getNameSpaceUri(),
    getPortName()),
    WebServiceDSICIF.class);
    return myProxy.getMatricula(param);
    catch (Exception ex)
    ex.printStackTrace();
    return "<ERROR>"+ ex.getMessage()+"</ERROR>";
    public static void main(String[] args) {
    try {
    ClienteWebService clws = new ClienteWebService();
    ArrayList l = new ArrayList();
    String xml = "";
    if (args.length>0)
    xml = clws.getMatricula("WsSQL",args[0]);
    System.out.println("Rut : " + args[0] + " = " + xml);
    else
    DataInputStream input = new DataInputStream( System.in );
    String bufferIn;
    while((bufferIn = input.readLine()) != null){
    xml = clws.getMatricula("WsSQL",bufferIn);
    System.out.print("Rut : " + bufferIn + " = " + xml);
    } catch (Exception ex) {
    ex.printStackTrace();
    public String getUrlString() {
    return UrlString;
    public void setUrlString(String _UrlString) {
    this.UrlString = _UrlString;
    public String getNameSpaceUri() {
    return nameSpaceUri;
    public void setNameSpaceUri(String _nameSpaceUri) {
    this.nameSpaceUri = _nameSpaceUri;
    public String getServiceName() {
    return serviceName;
    public void setServiceName(String _serviceName) {
    this.serviceName = _serviceName;
    public String getPortName() {
    return portName;
    public void setPortName(String _portName) {
    this.portName = _portName;
    }</b>
    and the external config for this service is:
    <b><Webservices>
    <WS>
         <Nombre>WsSQL</Nombre>     
         <EndPoint>http://ip:port/EJB-WebServicesDSIC/WSMatriculaSoapHttpPort</EndPoint>
         <URI>http://ejb.dsic.pucv.cl/</URI>
         <ServiceName>WSMatricula</ServiceName>
              <PortName>WSMatriculaSoapHttpPort</PortName>
    </WS>
    </Webservices></b>
    please helpme, four days in that :S

    Hi,
    Can you provide the pl/sql function or the web service wsdl generated from it, so that we can try to reproduce it.
    Also, in an earlier post, I saw a workaround of changing it so the function returned defined type as :
    type ListCursor is ref cursor return ListRecord
    You can also see if this works out if possible.
    Regards,
    Sunil..

  • Web Service over SSL failing in BEA Workshop

    I have deployed a web service on weblogic 9.2
    I have enabled one-way ssl on it. got a trial ssl certificate from verisign. installed them on the keystore/truststore on the server as well as the jre (cacerts and jssecacerts truststores) being used by the client. the client is on different machine than the server.
    i have developed the service through 'bea weblogic workshop 9.2' now when i try to test the service through the 'web services explorer' within bea weblogic workshop i receive the following error:
    IWAB0135E An unexpected error has occurred.
    IOException
    sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    on server:
    <Jul 13, 2009 6:45:44 PM EDT> <Warning> <Security> <BEA-090485> <CERTIFICATE_UNKNOWN alert was received from yunus.l1id.local - 10.10.2.72. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.>
    if i try to access the web service (over ssl) through the browser (ie/firefox), it works fine. i have generated a proxy class to access this web service through the same bea workshop and that works fine too. certificates are identified and all. i also created a small .net (c#) application that calls this secure web service over ssl from another machine and it works fine too!
    of course non-secure url for the web service is working fine in every case.
    what can be the reason for this failing only in 'web services explorer' in bea workshop?
    cross posted at: http://www.coderanch.com/t/453879/Web-Services/java/Web-Service-over-SSL-failing
    thanks.

    Hello,
    I used this example, when I made my experiments with SSL and Glassfish (GF):
    http://java.sun.com/developer/EJTechTips/2006/tt0527.html#1
    If you have problems with GF I suggest to post a message here:
    http://forums.java.net/jive/forum.jspa?forumID=56
    e.g. here is one thread:
    http://forums.java.net/jive/thread.jspa?threadID=59993&tstart=0
    Miro.

  • Best practice for loading config params for web services in BEA

    Hello all.
    I have deployed a web service using a java class as back end.
    I want to read in config values (like init-params for servlets in web.xml). What
    is the best practice for doing this in BEA framework? I am not sure how to use
    the web.xml file in WAR file since I do not know how the name of the underlying
    servlet.
    Any useful pointers will be very much appreciated.
    Thank you.

    It doesnt matter whether the service is invoked as part of your larger process or not, if it is performing any business critical operation then it should be secured.
    The idea of SOA / designing services is to have the services available so that it can be orchestrated as part of any other business process.
    Today you may have secured your parent services and tomorrow you could come up with a new service which may use one of the existing lower level services.
    If all the services are in one Application server you can make the configuration/development environment lot easier by securing them using the Gateway.
    Typical probelm with any gateway architecture is that the service is available without any security enforcement when accessed directly.
    You can enforce rules at your network layer to allow access to the App server only from Gateway.
    When you have the liberty to use OWSM or any other WS-Security products, i would stay away from any extensions. Two things to consider
    The next BPEL developer in your project may not be aware of Security extensions
    Centralizing Security enforcement will make your development and security operations as loosely coupled and addresses scalability.
    Thanks
    Ram

  • Asynchronous Web Services in BEA

    I need to build an asynchronous web services SOAP message reciever and an asynchronous
    web services SOAP message sender. Over HTTPS.
    I know how I would do it with JAXM and the Sun RI, but can not seem to find any
    implementation or equivelent in WebLogic (though many of the interfaces and abstract
    classes are in the BEA jar files). We are on WebLogic 7.

    I don't understand what you mean in step 5 that the client does not change. I
    want the client to send a SOAP message instead of call a remote process.
    Steve
    "manoj cheenath" <[email protected]> wrote:
    7.0 supports one-way and it is same as in 8.1.
    You got the steps to write a one-way service right.
    Here is it again:
    1. write the backend component. The method
    that you want to make one-way should return void.
    2. Either run servicegen or autotype+source2wsdd
    to generate the XML codecs and web-services.xml
    DD file.
    3. edit the DD file to change invocation-style as
    shown below.
    <operation name="helloOnewayWorld"
    invocation-style="one-way"...
    4. package and deploy.
    5. There is no change required on the client side. Client
    will knows that an operation is one-way by looking at
    the WSDL.
    -manoj.
    "Steve Watson" <[email protected]> wrote in message
    news:[email protected]...
    Can you send me the WL 8.1 example? How has support for one way messagingchanged
    in 8.1? Would there be any advantage for us to move to 8.1?
    Thanks everyones help so far. I am trying to assemble the rules oncreating one
    way messages - from this thread and bits and peices in the documentationI
    have
    found:
    "a document-oriented Weblogic Web Service operation can have only oneparameter,
    of any supported data type"
    "The backend component that implements the operation must explicitlyreturn void."
    "You specify this type of behavior with the invocation-style attributeof
    the
    <operation> element in web-services.xml"
    Have I missed anything?
    Steve Watson
    "manoj cheenath" <[email protected]> wrote:
    You need to set invocation-style="one-way" in the
    operation element of the web-services.xml dd file [1]
    You can use source2wsdd ant task to generate this DD [2].
    I dont have an example that runs on 7.0. But here is an
    example that works with 8.1.
    -manoj
    [1] http://edocs.bea.com/wls/docs70/webserv/wsp.html#1001373
    [2] http://edocs.bea.com/wls/docs70/webserv/anttasks.html#1080421
    "Steve Watson" <[email protected]> wrote in message
    news:[email protected]...
    I can find very little in the documentation on how to do this -
    is
    there a
    cook
    book?
    Steve Watson
    "manoj cheenath" <[email protected]> wrote:
    WLS only supports JAX-RPC. One can do one-way invokes
    using JAX-RPC. So, you can implement your receiver as a
    web service that accept one way invokes.
    Will this fit your use case?
    -manoj
    "Steve Watson" <[email protected]> wrote in message
    news:[email protected]...
    I need to build an asynchronous web services SOAP message recieverand an
    asynchronous
    web services SOAP message sender. Over HTTPS.
    I know how I would do it with JAXM and the Sun RI, but can not
    seem
    to
    find any
    implementation or equivelent in WebLogic (though many of the
    interfaces
    and abstract
    classes are in the BEA jar files). We are on WebLogic 7.
    begin 666 sample3.zip
    M4$L#!!0`" `(`/>!@BX````````````````)``0`345402U)3D8O_LH```,`
    M4$L'" `````"`````````%!+`P04``@`" #W@8(N````````````````% ``
    M`$U%5$$M24Y&+TU!3DE&15-4+DU&\TW,RTQ++2[1#4LM*L[,S[-2,-0SX.5R
    M+DI-+$E-T76J! F8Z!G&&QCIIB8J: 27YBGX9B87Y1=7%I>DYA8K>.8EZVGR
    M<O%R`0!02P<(V@!HADH```!*````4$L#!!0`" `(`$!U@BX`````````````
    M```.````<')O<&5R=&EE<RYT>'2%4$UKPS ,O0?R'P3==5-W&@1Z&AD4!BL[
    M]1;<1&T]',O(RMHR]M]G)RNL'6PZV4_O0]+L]L\JBQF,%80#B5J*"?I/DRA*
    M?8#."K7*<@)EX$'#H+ C3V*4.MA:E]TRLTG,!6H?<!2;$)QMC5KV,9L`;T'W
    M!)'DG>3NDC%JNPHW9'!(C":-^I9B(^J0LJUQ^-.O+*ZU8^[!'2*V[+=VA_VI
    MX]Y8?Z5+L1L3"09QOP::'DUJ+?:JH4)TW!JWYZC5PWQ^/^V5L6QVEF^$#TD)
    M=*2R^/XL'BM<">_$]/"4+X1+KR2>%.IC<"PDN*S7J^>7U_JN7M?9>#KMN,S-
    MQ_F>GSC!9=$Z2UZ;UID8*5Y0+EME\0502P<(3D:RZ!$!```/`@``4$L#! H`
    M`````.R!@BX````````````````(````<V%M<&QE,R]02P,$% `(``@`VX&"
    M+@```````````````!<```!S86UP;&4S+V)U:6QD+7=E8G-S+GAM;*U6VV[;
    M, Q]+]!_((R]Q@;V[ SH+@4R8$6P"_:L2'2B5K8,24X6#/GW49;MV$F<2]<W
    M2SJ'I,@CTFEI]#-R!P7+<1IM<&%M! (S5BDWC1:55"+Z<']W?P>0.F:6.(#&
    M`0`-@C"L<)PI!0';PO@*^4L$LEBAD>Y!J6GD3(41)#UFY;3;E@AA#?#,UNR3
    MSDM=8.'L-'KW-QBS:-:28UPR_L*6N(L/#WR NZ@U(]"ZS]+L^;IR9>5B(<TN
    M^?WEXV3V])APQ:Q%NGK+:HP_U7<=\^PS$^!I;:!D;M5MT:9?H\*<X@>E.7-2
    M%U?&D?R?'2479VSX;\_W&8YKE['?VO4I:7)XI31I2]06+;6Z,AS?;ZP0;>8H
    MW=S(,H3(#3*'0'%"D[ON7!M@A0"B*LB,SB'8@DPJ;&OGX_M1;Q_7(,!W7<6$
    M>"3F^:S0R:3AV_A/KEH__DYV5F3ZJN(D-;S/;VS^^CX[CK,R:A^DO^UXF"=U
    M''M._<)&A?9&.GL#F=VJLB.1I4E/4IW,N))D<(G%.9&Q@<P")2B+0JHSWY8K
    MG'UE(SWA9!DF@10_,Q/UBGES(1ONR?;2N.BZ2T^=\QOPE<6Y-LYC'^PW="LM
    M`F_0<M,DM.AF=:*W-TV[JP*-BA*-VPY :(PV$:R9JF@/"NW ELAE)E'$\',E
    M+72\O+(.%N@WUE*@H.],&ZH5#0Q9+E.A8!T@R/&.8*F44PN):X@2TIHSZN
    MAT[=*.+>!$DS)A54A4)KV^@.&G;W#G/"T'H$!FV"Z\O5>B7.%6Y\8B[Y\)A7
    M.Z!F<LD^05YM/KR]2QZ:1GVKD_T#&7.P1]QL?/@4QAP,46><#!Y'FC0_2;3Z
    M!U!+!PB&<5T7? (``# )``!02P,$% `(``@`VX&"+@```````````````!$`
    M``!S86UP;&4S+V)U:6QD+GAM;)U62V_;, R^%^A_X(2>BL0^[)ITP- 5&[#M
    MTD./A2(SJ5K%-B2Y25#DOX]Z.;;SZF+ 04SQ\9'Z2&E2Z^H5A862+W'*#%_6
    M"K\R*'#.&V6G;-9(5;"[ZZOK*X#)E_$81+5<5B6088W:2C0P'M_YU2C:P%PJ
    M<I9E^4XILVO+(.\ZZG@P-0HYEP)L!?9%D@#UNQ2X[SKB#,L,WKEJZ/LG*E4]
    M55H5CVDE/V7X7'/QQA<[![:QE99<96T%3MNON&YM>R;'C% _"\6-0=/:W7Q4
    MC:T;^UQ(O<V??GP?__K[D+=:.V_<OH LIDPHB:7-O$;FI,QCC"JH<$G+X/X[
    MYT$[1=VFC(YH=Z'<?,0TM^,8\M6E>]+^E;_S#K(VW"1WGSX5_VFY7F"B6R 7
    MD:W&LC"N4+:I1T2PF@B4A;*-5CB+<#*O/PHH3CWD4%6;UE%(HE/1'@BAD)<.
    MA!%:UE96Y905E)Y%6&")FELLP-AF/F>0*A#7J5J#VG6JU-<YLAN3/& YB,R7
    M8X!,:"1 $$(ZY]2\Q%Q'F!1X^4;B%+?/O2Z^GMHE\/K[Q"#X[:,-*A#]0HE8
    M4#5I?!"#(!B"D04U(L08%,5Q28#1PH/+&,A2J(8<3]EMYA89X#I)`O+\EK6T
    M(+$]EGU*/O<QSN<X)!\[E&38$E)MQU9:K_0(5J90?B*.>BJ)E+NT.;43O6%X
    M^FAC%]YDZZ5B$& %1":"2>GLCYR@E: [66?LI.[>D>&<@^&X;'VD0?H?OAJM
    M6C_Y)6!,U6AQ*)_(C7-^0N]D1)'#H_B\AS@5SU>E-WH"\6B'/]]:R3S!^8_F
    M"J:QN3[56ZF38AD[;;0W'7;U\3)_0FF<'SZD.LE_LNO"_-Z;R4[8]L]L0S>1
    M>B/+!=!A["X.Y\\%__"Z5E)PY[2=GYM^B330^^#[\.:CHS\X'MTM8)OYJT ;
    M>\8-WA\]%DYF/=/5RN @ZR $2YM!9^T"85[IWA6IBQS7*,#]-);/`OI@KWM[
    M1D%!R1([$Y*:<IC8P=Z<Y,[]^5QT,SQ227)@YCE"! ('NZ,ME/WALKR4>)?D
    M_.WI\?[WD+O[B4_R>(.FKW]02P<(81.%XR@#``!-"P``4$L#! H``````-N!
    M@BX````````````````/````<V%M<&QE,R]C;&EE;G0O4$L#!!0`" `(`-N!
    M@BX````````````````8````<V%M<&QE,R]C;&EE;G0O36%I;BYJ879AM9-=
    MJ]- $(;O"_T/0ZY2A$7QSE!$1&G!XQ'+P8O#0::;:;*ZR8;=2=,H_>]N-FD^
    M_+@T!!)F7IYY9V:W0OD=,P*NV5B%6C@L*DTOA=2*2D[6J_5*%96Q#-_PC$(9
    ML;]_=Y%4L3)ELDA>Q*70PE92',B>E:2Y;KVJZJ-6$J1&Y^ .5?FSBP(,<<?(
    M_G,V*H7"9V,XL%5E]O@$:#,'FT$.H$YQ" E-9<8Y;+?P(J0A/"4U`=^+'I\_
    MP2;I<U?2CD8=Y]8T0;W7FC+4;VQ6%[[IT78,T</G#V!.7DO@^J:@- RN(JE.
    MBM)H@G>?ZZ*ENUD;T+A4/U@]&F7;CE9VI+7Y8JQ.A\F-Q;;!X!_YKWN_I7AB
    M)O\D?>JV$U:TO4%%1OS6XH\VZ.)-<ALL0(A 3IB2[?][`Y.RU\T4PA%_Q(+\
    ML&0'A::+]G-98H\F;6_0SI'(.[.["14O*L\!A]8Q%<+4+"H_3=9^KA-NKIS
    M]]XX#CU"M/.[1DO0FOKUW-Q5(LL\AMFI!IJ=IK]5CMZCTI0"&Y"6D D:.HXK
    MZV_.JPB>=:!D6>;WF_%?:@TGT;^_`%!+!PA5MM$EK@$``-\#``!02P,$% `(
    M``@`VX&"+@```````````````!X```!S86UP;&4S+TAE;&QO5V]R;&1397)V
    M:6-E+FIA=F%]4LMJPS 0O!O\#XM/3DJ<0V\)@4(IY-#'P8?VNK&71%26A"3'
    M<4/_O=:C=@)M0""8G9G=64EA]8E[`MM:J1GRPF"C.-VOTR1-EO-YFL <'CK>
    MF55'.T/ZR"H");5]Q88VV:/&K_Y=:EYGCKI,$]7N.*N@XF@,;(ESZ<MED)Z=
    M+T!PAM%;H;9P(*Q)>S9P6:%E4FRR@&:!OG17[!"(!]=A.RGS$9_,9K$KQ-I.
    MUF%FV("@+J#Y;!TX8[4PY%/FEV;%/H(S^!5HLJT6D\[#WW\'E8JT#P9,'&/&
    MA;$]'W8I!2TZ[/^(>I0L)GT;YL4^)BVM9F(/#1GCWM#%=/.4O;'4%+*UA1H(
    MEHL<L@LA&.S-"C*XFZ2W9J93Q=N:_AFKEL(^G90TPTK.-US\$Y\:7KJP;H,@
    M_ \:H+" >N& F^D_7IZOHU_YC>V'\P-02P<(4'P0;$H!``#8`@``4$L#!!0`
    M" `(`-N!@BX````````````````2````<V%M<&QE,R]7;W)L9"YJ879A=9 ]
    M#X(P$(9W$O[#A4D7!B"!A#BY&F/BX%RAP<;2-OU $^-_MQ1$JI)TZMW[W',G
    M4'5%#09M-)<$T5BA5E"<EF$0!L*<*:F@HD@I.'%)ZT<8``A).J0Q'+4DK &&
    M6ES._RFWOX(+0Y$FG#F4K0XPAUFM'0A<%C80;7D_]0ZWOAJ50_&#L"U)FN5)
    MD>5%DA8[U_#TN*-,@_7>,J<!$FLC&>@+4?$DZB<[3FI08VZ^%+PA4]IZ+$#<
    MSG;X87+^J^!=94EDQOB^I:_D'>@7;=\+4$L'"(@-B!+/````WP$``%!+`0(4
    M`!0`" `(`/>!@BX``````@`````````)``0```````````````````!-151!
    M+4E.1B_^R@``4$L!`A0`% `(``@`]X&"+MH`:(9*````2@```!0`````````
    M````````/0```$U%5$$M24Y&+TU!3DE&15-4+DU&4$L!`A0`% `(``@`0'6"
    M+DY&LN@1`0``#P(```X`````````````````R0```'!R;W!E<G1I97,N='AT
    M4$L!`@H`"@``````[(&"+@````````````````@`````````````````%@(`
    M`'-A;7!L93,O4$L!`A0`% `(``@`VX&"+H9Q71=\`@``, D``!<`````````
    M````````/ (``'-A;7!L93,O8G5I;&0M=V5B<W,N>&UL4$L!`A0`% `(``@`
    MVX&"+F$3A>,H`P``30L``!$`````````````````_00``'-A;7!L93,O8G5I
    M;&0N>&UL4$L!`@H`"@``````VX&"+@````````````````\`````````````
    M````9 @``'-A;7!L93,O8VQI96YT+U!+`0(4`!0`" `(`-N!@BY5MM$EK@$`
    M`-\#```8`````````````````)$(``!S86UP;&4S+V-L:65N="]-86EN+FIA
    M=F%02P$"% `4``@`" #;@8(N4'P0;$H!``#8`@``'@````````````````"%
    M"@``<V%M<&QE,R](96QL;U=O<FQD4V5R=FEC92YJ879A4$L!`A0`% `(``@`
    MVX&"+H@-B!+/````WP$``!(`````````````````&PP``'-A;7!L93,O5V]R
    =;&0N:F%V85!+!08`````"@`*`(("```J#0``````
    `
    end

  • Web Services and BEA

    Web Services has all the makings of a home run. As a powerful integration
    platfor, it moves the procedural-heavy complexities of builiding distributed
    app into the realm of simple declarative transactions, while supporting
    location transparency. It is a powerful technology that removes the barrier
    erected by the discontinuity of geographic distance and cross-platform
    technical mismatches that have until now constrained the plumbing between
    heterogeneous networked applications.
    Developers who feel lost in the labyrinth of hype can turn to a new site
    site., Web Services FAQ http://www.webservicesfaq.com devoted to UDDI,
    WSDL, SOAP, ebXML, Best Practices, Intergration issues and so on...
    Here they'll learn how, while Web Services complements J2EE and compliant
    servers superbly, it is also an excellent integration platform for BEA
    technologies, and in fact for the transparent interoperability between the
    two, and between any other architectures that support the new Web Services
    standards.
    Best Regards
    Ramene Anthony

    You should be able to get the username from the context?
    private SessionContext sessionCtx = null;
    public void setSessionContext(SessionContext sctx) {
    this.sessionCtx = sctx;
    public void someMethod() {
    String username = sessionCtx.getCallerPrincipal().getName();
    -Jesus

  • BEA and Web Services problem

    Hi
    I'm new to java and trying to educate myself in this field and therefor I have this question.
    I'm trying to develope a web service to bea. I successfully managed to deploy bea's web service example called Trader(EJB version). Available at webservices.zip that I downloaded from this site(src\examples\webservices\complex\statelessSession).
    But now I'm facing a problem that I can't figure out how to read data from HttpRequest- is this possible at all with EJB? For example I would like to get username from header? Or usually X509 certificate is added to request and how can i deal with it?
    Currently I'm able to read only data specified in the procedure defined in the interface. For example:
    public String doIt(String val,String val2)
    Any help would be appreciated :)
    Thanks in advance :)
    Edited by justcraizy at 04/03/2007 7:34 AM

    You should be able to get the username from the context?
    private SessionContext sessionCtx = null;
    public void setSessionContext(SessionContext sctx) {
    this.sessionCtx = sctx;
    public void someMethod() {
    String username = sessionCtx.getCallerPrincipal().getName();
    -Jesus

Maybe you are looking for

  • New Document' requires a Microsoft SharePoint Foundation-compatible application and web browser

    Hi Guys, I am getting the above message when I try to create a new Excel document from a content type. The background is that I am configuring Content Types for a document library in SharePoint 2013. The first content type I added was a business case

  • ALE AND EDI

    hello,now,i want to send one PO from one cilent to another cilent and in another cilent creat one SALE ODER, A foundation upon which the PO. how can i use ALE and EDI. thank you!

  • Schema level and table level supplemental logging

    Hello, I'm setting up bi- directional DML replication between two oracle databases. I have enabled supplemental logging database level by running this command- SQL>alter database add supplemental log data (primary key) columns; Database altered. SQL>

  • Career transition from ABAP to SD (Certification)

    Hi all, I am posting this question again in the right forum .. I need some guidance regarding SAP SD certification ... I have 3 years of SAP ABAP implementation and support experience with some of the top notch Consulting companies , now I would like

  • Calling JNI from a java sp.

    I read in 8.1.5 docs that JNI is not enabled in the Oracle JVM (for customers) Still the case in in 8.1.7? Has anyone (Brian?) had success when making RMI calls from the Oracle JVM? Thanks, Matt [email protected]