Full servlet 2.3 support in WLS 6.1 available?

          Hi,
          I have succeffully ported a servlet 2.3 based web app to WLS 7.0. The same code
          generates compile errors when compiling against WLS 6.1 sp4 jar.
          Here is the list of inconsistencies as documented in 6.1 notes - go to http://edocs.bea.com/wls/docs61/notes/new.html
          and search for "Servlet API Classes" you should see table with the following classes
          that are not fully 2.3 compatible.
          javax.servlet.Filter
          javax.servlet.ServletContext
          javax.servlet.ServletContextAttributesListener
          javax.servlet.http.HttpServletResponse
          javax.servlet.http.HttpSession
          javax.servlet.http.HttpSessionAttributesListener
          For some classes I a rename works fine, however other are more problematic.
          Is there a patch for WLS 6.1 that fully supports servlet 2.3 specification? Or,
          what else would you suggest?
          Thanks,
          Radu
          

          WLS6.1 supports Public Final Draft 1 of Servlet 2.3 specification, not the Servlet
          specification 2.3.
          Refer to
          http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_clfydoc&answerpage=solution&page=wls%2FS-10618.htm
          thanks,
          Deepak
          "Radu" <[email protected]> wrote:
          >
          >Hi,
          >
          >I have succeffully ported a servlet 2.3 based web app to WLS 7.0. The
          >same code
          >generates compile errors when compiling against WLS 6.1 sp4 jar.
          >
          >Here is the list of inconsistencies as documented in 6.1 notes - go to
          >http://edocs.bea.com/wls/docs61/notes/new.html
          >and search for "Servlet API Classes" you should see table with the following
          >classes
          >that are not fully 2.3 compatible.
          >
          >javax.servlet.Filter
          >javax.servlet.ServletContext
          >javax.servlet.ServletContextAttributesListener
          >javax.servlet.http.HttpServletResponse
          >javax.servlet.http.HttpSession
          >javax.servlet.http.HttpSessionAttributesListener
          >
          >For some classes I a rename works fine, however other are more problematic.
          >
          >Is there a patch for WLS 6.1 that fully supports servlet 2.3 specification?
          > Or,
          >what else would you suggest?
          >
          >Thanks,
          >Radu
          >
          >
          >
          

Similar Messages

  • Java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

    We have some web services that run under OC4J 10.1.3.4. We have various JEE 'client' apps (JSF, servlets etc.) that use these web services. These JEE apps also run under OC4J.
    We started a migration project from oc4j to weblogic 10.3.2. In phase 1 we want to move these JEE 'client' apps to weblogic. In phase 2 we want to move the web services themselves to weblogic with adjustments to the JEE 'client' apps as needed.
    However we ran into an issue during this phase 1. Deploying these JEE 'client' apps to weblogic results in an error like this:
    java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions.
    We are including Oracle web services client libraries (http://download.oracle.com/otn/java/oc4j/1013/wsclient_extended.zip) in these JEE 'client' apps's war files because weblogic does not have them.
    What part of Web Service Migration Guide is the above error message talking about? Do we have to re-generate the client side proxies for all these web services using weblogic's clientgen task in 'JAXRPC' mode? Many of these web services are doc/literal jax-rpc web services. Or does the migration guide recommend we migrate the web services first to weblogic? Any other specific information on working around this error message would be greatly appreciated.

    Hi,
    I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
    Regards,
    Sylvain

  • Is role base security supported by WLS 5.1?

    To what extent is role based security supported by servlets under WLS 5.1?
              Declarative role based security does not seem to be supported?
              Are any of the following methods supported?
              HttpServletRequest.isUserInRole()
              HttpServletRequest.getUserPrincipal()
              If so, where are the roles declared? Where is the role/principal mapping
              done? Does getUserPrinicipal() return the principal using the WLS security
              realm?
              Thank you.
              Marko.
              

    Cool. Bonus mystery feature. I will call support.
              Thanks Winston.
              Marko.
              Winston Koh <[email protected]> wrote in message
              news:[email protected]...
              > no, i am not referring to ACL. to my knowledge, the servlet security
              > features docs do not make it into the WLS 5.1. I understand its a bit hard
              > to use the features properly without proper documentation. contact support
              > for more info
              >
              > thanx
              >
              > Winston
              > Marko Milicevic <[email protected]> wrote in message
              > news:[email protected]...
              > > The only servlet authorization mechanism I can see documented is ACL's.
              > Is
              > > this what you are referring to Winston? If so, I believe ACL are
              > different
              > > than declarative role based security. An ACL grants access to a servlet
              > for
              > > a set of principals (users and/or groups). But a role is not a
              > prinicipal.
              > > A role name is mapped to a set of principals.
              > >
              > > If you are referring to roles, can you give a URL to the documentation
              > which
              > > discusses this?
              > >
              > > Thanks Winston.
              > >
              > > Marko.
              > > .
              > >
              > > Winston Koh <[email protected]> wrote in message
              > > news:[email protected]...
              > > > both declarative and programmtic based security roles are supported by
              > WLS
              > > > 5.1.
              > > >
              > > > if you don't specify any specific security realm in the
              > > weblogic.properties
              > > > file, a default WebLogic Security realm is assumed. you could specify
              > the
              > > > group and its associated users and passwords there in the properties
              > file.
              > > > in the web.xml file associated with each web app, you could speciify
              the
              > > > security constraints for each servlet
              > > >
              > > > I would imagine when accessing a secured servlet within a web app, a
              > > client
              > > > would supply her credentials thru some sort of authentication, and
              based
              > > on
              > > > the credentials, we find out the role name from the
              weblogic.properties
              > > file
              > > > which in turn mapped to the web.xml which specify the security role
              that
              > > > could access the particular servlet. if the role matches, access to
              the
              > > > servlet is granted
              > > >
              > > > refer to WL Docs for more specific details
              > > >
              > > > thanx
              > > >
              > > > Winston
              > > > Marko Milicevic <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > To what extent is role based security supported by servlets under
              WLS
              > > 5.1?
              > > > >
              > > > > Declarative role based security does not seem to be supported?
              > > > >
              > > > > Are any of the following methods supported?
              > > > >
              > > > > HttpServletRequest.isUserInRole()
              > > > > HttpServletRequest.getUserPrincipal()
              > > > >
              > > > > If so, where are the roles declared? Where is the role/principal
              > > mapping
              > > > > done? Does getUserPrinicipal() return the principal using the WLS
              > > > security
              > > > > realm?
              > > > >
              > > > > Thank you.
              > > > >
              > > > > Marko.
              > > > > .
              > > > >
              > > > >
              > > > >
              > > >
              > > >
              > >
              > >
              >
              >
              

  • Is servlet chaining (filtering) supported?

    For a given virtual name I would like to set up a chain of servlets
              (ProducerServlet, ConsumerServlet) so that the ServletInputStream of the
              ConsumerServlet contains the results of the ServletOutputStream of the
              ProducerServlet. The ConsumerServlet is in effect 'filtering' the results
              of ProducerServlet.
              eg. BrowserRequest --> ProducerServlet --> ConsumerServlet -->
              BrowserResponse
              Can this be done with WLS 5.1?
              The RequestDispatcher interface does not seem to satisfy these requirements?
              If I understand this interface correctly, it allows requests to be either
              'forwarded' (where the output of the forwarder is not used) or 'included'
              (where the included servlet inserts output in the stream). But it does not
              allow servlets to be connected in a producer-consumer chain.
              Am I missing something?
              Thank you.
              Marko.
              

    Is there any way to achieve the same effect within the current spec?
              Marko.
              Winston Koh <[email protected]> wrote in message
              news:[email protected]...
              > Hey Marko, servlet chaining is not supported in WLS since its a
              proprietary
              > mechanism not specified in the current servlet/jsp specs
              >
              > thanx
              >
              > Winston
              > Marko Milicevic <[email protected]> wrote in message
              > news:[email protected]...
              > > For a given virtual name I would like to set up a chain of servlets
              > > (ProducerServlet, ConsumerServlet) so that the ServletInputStream of the
              > > ConsumerServlet contains the results of the ServletOutputStream of the
              > > ProducerServlet. The ConsumerServlet is in effect 'filtering' the
              results
              > > of ProducerServlet.
              > >
              > > eg. BrowserRequest --> ProducerServlet --> ConsumerServlet -->
              > > BrowserResponse
              > >
              > > Can this be done with WLS 5.1?
              > >
              > > The RequestDispatcher interface does not seem to satisfy these
              > requirements?
              > > If I understand this interface correctly, it allows requests to be
              either
              > > 'forwarded' (where the output of the forwarder is not used) or
              'included'
              > > (where the included servlet inserts output in the stream). But it does
              > not
              > > allow servlets to be connected in a producer-consumer chain.
              > >
              > > Am I missing something?
              > >
              > > Thank you.
              > >
              > > Marko.
              > > .
              > >
              > >
              > >
              >
              >
              

  • Jdeveloper 11g - JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

    Hi,
    I am using Jdeveloper 11g and migrating a web Service Proxy created using jdeveloper 10g.
    I imported all the proxy classes and when I try to run web service client In Jdeveloper 11g I get the following error
    "JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions."
    Please advise on how to solve this?
    which is the offending jar/library file in Jdeveloper 11g which is causing the above error?.
    Is the above problem there in the WebLogic Server Runtime also?
    Please let me know.
    2) I cannot generate web server proxies also with jdev11g because the wsdl has overloaded methods omitting the name property within the input and output message, ie, they have a null name. therefore Jdeveloper 11g is using the library which
    when called with an overloaded operation that contains null input/output message names, a duplicate error occurs because it sees other operations with the same name. so it is effectively not allowing to create the web service proxies.
    Thanks,
    Appreciate your quick response to the above

    Have you checked the 'Web Service Migration Guide' mentioned in the error message?
    Timo

  • Will JDK 1.2.2_08 be supported with WLS 5.1?

    Hiya,
    Will JDK 1.2.2_08 be supported with WLS 5.1?
    If not, why?
    If so, when?
    Much thanks,
    Richard Fanta
    Systems Architect
    Morgan Stanley Online

    Oh yeah, like - that wasn't there when he asked the question - THREE MONTHS AGO.
    Slow day at Loud Cloud?
    Mike
    David Peng <[email protected]> wrote:
    http://e-docs.bea.com/wls/platforms/index.html#solaris
    Mike Reiche wrote:
    It seems to work fine here.
    Is there some reason you're not running 1.3 ?
    As I recall you guys are on Solaris (I was there in December).
    Mike Reiche
    "Richard Fanta" <[email protected]> wrote:
    Hiya,
    Will JDK 1.2.2_08 be supported with WLS 5.1?
    If not, why?
    If so, when?
    Much thanks,
    Richard Fanta
    Systems Architect
    Morgan Stanley Online

  • Weblogic Events - are they supported in WLS 8.1?

    Weblogic Events - are they supported in WLS 8.1?
    From the documents posted at:
         http://e-docs.bea.com/wls/docs81/upgrade/upgrade51to81.html
    which states:
         The following APIs and features are deprecated in anticipation of future removal
    from the product.
    WebLogic Events are deprecated and should be replaced by JMS messages with NO_ACKNOWLEDGE
    or MULTICAST_NO_ACKNOWLEDGE delivery modes. See Non-transacted session <../jms/fund.html>
    in Programming WebLogic JMS for more information.
    and
         http://e-docs.bea.com/wls/docs81/cluster/overview.html
         Which states Weblogic Events cannot be clustered.
    Packages:
    weblogic.event.actions <../javadocs/weblogic/event/actions/package-summary.html>Package
    weblogic.event.common <../javadocs/weblogic/event/common/package-summary.html>Package
    weblogic.event.evaluators <../javadocs/weblogic/event/evaluators/package-summary.html>
    However - I cannot find these in the package paths of WLS 8.1.
    Does anybody know for sure whether or not they are supported?
    Is anybody using Weblogic events with WLS 8.1?
    Thanks.

    I believe it's 6.1.
    -- Rob
    John Slaman wrote:
    Thanks Rob.
    Does anybody know the actual last version of WLS where the Weblogic Events were
    supported?
    Rob Woollen <[email protected]> wrote:
    No, WebLogic Events are not included in the 8.1 product. The docs
    should be cleaned up to reflect that.
    -- Rob
    John Slaman wrote:
    Weblogic Events - are they supported in WLS 8.1?
    From the documents posted at:
         http://e-docs.bea.com/wls/docs81/upgrade/upgrade51to81.html
    which states:
         The following APIs and features are deprecated in anticipation offuture removal
    from the product.
    WebLogic Events are deprecated and should be replaced by JMS messageswith NO_ACKNOWLEDGE
    or MULTICAST_NO_ACKNOWLEDGE delivery modes. See Non-transacted session<../jms/fund.html>
    in Programming WebLogic JMS for more information.
    and
         http://e-docs.bea.com/wls/docs81/cluster/overview.html
         Which states Weblogic Events cannot be clustered.
    Packages:
    weblogic.event.actions <../javadocs/weblogic/event/actions/package-summary.html>Package
    weblogic.event.common <../javadocs/weblogic/event/common/package-summary.html>Package
    weblogic.event.evaluators <../javadocs/weblogic/event/evaluators/package-summary.html>
    However - I cannot find these in the package paths of WLS 8.1.
    Does anybody know for sure whether or not they are supported?
    Is anybody using Weblogic events with WLS 8.1?
    Thanks.

  • Servlet 2.3 implementation in WLS 6.1 SP2

              Hi,
              What exactly is the implementation of the Servlet 2.3 specification in WLS 6.1
              SP2? The Final one or some of the earlier Drafts? I am particularly interested
              in the Filter interface.
              Regards,
              Plamen
              

    Servlets and Web Applications
              The following new features and changes apply to servlets and Web Applications:
              Web Application Events (Servlet 2.3 only)
              Web Application Events provide notifications of a change in state of
              the servlet context (each
              Web Application uses its own servlet context) or of an HTTP session
              object. You can write event
              listener classes that respond to these changes in state.
              Filters (Servlet 2.3 only)
              A filter is a Java class that is invoked in response to a request
              for a resource in a Web Application.
              These resources can include Java Servlets, JavaServer Pages (JSPs),
              or static resources such as
              HTML pages or images. A filter intercepts the request and can
              examine and modify the response
              and request objects or execute other tasks. For more information,
              see Using Filters.
              Single sign-on between Web Applications. This means the server tracks
              users at the Web Server level
              and not the Web Application level, as mandated by the Servlet 2.2
              specification.
              Plamen Petrov wrote:
              > Hi,
              >
              > What exactly is the implementation of the Servlet 2.3 specification in WLS 6.1
              > SP2? The Final one or some of the earlier Drafts? I am particularly interested
              > in the Filter interface.
              >
              > Regards,
              > Plamen
              

  • BIweb service proxy JAX-RPC 1.1 method is not supported in WLS 8.1 clients

    Hello
    I have an application in oracle Application server and I'm migrating to weblogic 11g .
    I have used web service proxy for BIPublisher 10.1.3.4 , careated by jdeveloper web service proxy wizard , when I want using it in weblogic , In corresponding form that uses BI Publisher web service proxy , I encounter following error :
    "JAX-RPC 1.1 method is not supported in WLS 8.1 clients , if you attempting to run oc4j 10.1.3 JAX-RPC client in WLS,please see Web service Migration Guide for Instructions"
    What should I do?
    Regards
    Mehdi

    Spoke to dev and there was a bug logged, it seems to be down to Weblogic's implementation.
    +This is pure WLS issue. The root cause of this problem is that Weblogic's
    SAAJ implementation. No codechange on BIP server side
    WLS 10 ships with two SAAJ implementations. By default the buggy 9.x
    implementation is used (which lives in the package
    weblogic.webservice.core.soap), but there is a new implementation, which
    supports SAAJ 1.3 (which lives in the package weblogic.xml.saaj). I also
    checked in a debugging jsp page, which could help looking at the DEBUG
    logging to see which SAAJ implementation is used.
    JSP testpage xmlponline/wwwroot/wsclient/soapclient-wls-8270711.jsp
    To use this new version, you have to make sure setting the
    -Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl
    in startWebLogic script. +
    Please give the solution a try and let me know if it works.
    Regards
    tim

  • My iphone is full of photos - how do I copy to get available space?

    My iphone is full of photos - how do I copy to get available space?

    Import them to your computer, then delete them from camera roll as explained here: http://support.apple.com/kb/HT4083.  (Syncing them to iCloud using Photo Stream will not remove them from your phone.  Also, only photos taken after Photo Stream is turned on will upload to Photo Stream, not earlier photos.)

  • HT201071 When will RAW support for Pentax K3 be available for OSX and Aperture 3, finally? Really very much waiting for it!!!

    When will RAW support for Pentax K3 be available for OSX and Aperture 3, finally? Really very much waiting for it!!!

    We're all other users here, so can't answer that question. You can request it by submitting feedback here:
    http://www.apple.com/feedback/

  • Servlets implementing custom protocol in WLS 6.1

              Hi.
              Does WLS 6.1 support other than HTTP/S protocols with servlets? If it does, how
              requests are dispatched to a servlet implementing a custom procotol.
              b r
              juha
              

    No, I don't think it does. You'll have to implement it yourself.
              "Juha Räsänen" <[email protected]> wrote in message
              news:[email protected]..
              >
              > Hi.
              > Does WLS 6.1 support other than HTTP/S protocols with servlets? If it
              does, how
              > requests are dispatched to a servlet implementing a custom procotol.
              >
              > b r
              > juha
              Dimitri
              

  • Java 1.5, Servlet 2.4 support in Sun Java System Web Server?

    Hi All,
    Does anyone know when the next version of Sun Java System Web Server will be released? 6.1 has been around a while and it doesn't support the latest Java releases, which is odd for a Java product from the company that owns Java. My Sun rep didn't have an answer for me and suggested posting here.
    I have seen references to people trying to use 1.5 with their server in another forum, but they were reporting problems and their questions weren't answered.
    Thanks!
    Dennis

    Hi,
    Try the new
    SAP NetWeaver Application Server, Java EE 5 Edition
    thus you will have the chance to use the latest Servlet 2.5. The download package includes also the new SAP NetWeaver Developer Studio.
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/da699d27-0b01-0010-99b0-f11458f31ef2">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/da699d27-0b01-0010-99b0-f11458f31ef2</a>
    Regards,
    Violeta

  • Servlet reloading not working with WLS 5.1 sp8

              I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
              problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
              work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
              the servler reloading works fine.
              Does anybody experience similar problem or have I forgot to do something?
              WLS properties/env vars setting:
              - weblogic.httpd.servlet.reloadCheckSecs=0
              - WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
              - JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
              Thanks in advance for any help.
              

              I've experienced the same problem with both sp6 and sp8. In both cases I performed several test, including
              - varied the value of weblogic.httpd.servlet.reloadCheckSecs
              - changes to the package depth the servlet belonged to
              - changes to the string length of the package names the servlet belonged to
              At best, the servlet would reload sometimes. I've moved back to sp5 and the problem has subsided.
              Note: I did not try registering the servlet to see how that would effect the dynamic reloading.
              Hope this helps
              - Dave
              "Michel Dinh" <[email protected]> wrote:
              >
              >I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
              >problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
              >work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
              >the servler reloading works fine.
              >
              >
              >Does anybody experience similar problem or have I forgot to do something?
              >
              >WLS properties/env vars setting:
              >
              >- weblogic.httpd.servlet.reloadCheckSecs=0
              >- WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
              >- JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
              >
              >Thanks in advance for any help.
              

  • Servlets in Jar files  in WLS 6.1 ?

    Trying to port a WLS 5.1 servlet into 6.1 (an entirely different
              animal it appears)
              I have added an application to my config.xml file as below as well as
              trying to start it
              PasswordPolicy="wl_default_password_policy"
              Realm="wl_default_realm"/>
              <Application Deployed="true" Name="DefaultWebApp_cb2java"
              Path=".\config\PM\applications">
              <WebAppComponent Name="DefaultWebApp_cb2java"
              Targets="PCPNEARN"
              URI="DefaultWebApp_cb2java" WebServers="PCPNEARN"/>
              </Application>
              <StartupClass Arguments="servlet=ProMan"
              ClassName="weblogic.servlet.utils.ServletStartup"
              FailureIsFatal="true" Name="StartPMServlet1"
              Targets="PCPNEARN"/>
              Now my servlet is packaged in a JAR file under the lib directory of so
              when I assume that WLS will automatically pick this up from
              C:\Weblogic6.1\wlserver6.1\config\PM\applications\DefaultWebApp_cb2java\WEB-INF\lib
              directory ? ( as the lib directory is where the doc says it picks up
              jar files from )
              Now when I start WLS it cant find the servlet? Is that because I cant
              package it in a JAR as of WLS 6.1 and have to move the class files to
              the Classes directory instead ?
              Furthermore the Servlet itself references JavaBeans deployed in a
              totally different application. Can I also assume that if I have my
              Classpath correct these will get picked up ?
              

    I would look here
    http://e-docs.bea.com/wls/docs61/webapp/security.html#100365 for methods on
    protecting web app resources.
    "zhen Ni" <[email protected]> wrote in message
    news:3c86d70c$[email protected]..
    Hello:
    I have some derectories and files on my web site,and only appointed usersstored in my database can access their special directories.how can i do?
    thank u!

Maybe you are looking for

  • How to create tablespaces in Windows

    using Oracle 10g XE on Windows how do I create tablespaces on Windows?

  • Standard queries installation

    Hi,             My requirement is only standard queries installation.            can i install particular infoarea ,infocubes and all????in my se09 having only query requests and infoarea shows "NODEISNOTCONNECTED" Can you suggest me. what is the pro

  • Re: External HD Problem

    I've been meaning to ask this question for a while and this topic seems to be a good opportunity. I have a PC that is being used as a media server. All drive formated as NTFS. I can write to these drives from my IMAC and open those files both from my

  • SD Overwrite condition type value of subitem with value of mainitem

    Hi, Suppose we have a sales order with a material and a submaterial. On the head material a condition record for according a reduction is found. On the submaterial also but it's different. Our requirement is that if there is a submaterial, the reduct

  • My iPhone 4 lock button doesn't work

    My lock button on  my iPhone 4 doesn't and my Facebook app kickes me off all the time and so does wifi. I got the apple iCare plan and i was wondering if i could either get it fixed or trade it in 4 the new white one it looks so much better.