Weblogic 6.0 and Servlet Api

          I read somewhere that Weblogic 6.0 supports Servlet Api 2.3 ( which in turn support
          http Filters etc.).
          I searched the Weblogic docs site for 6.0 and there is no mention of Servlet Api
          2.3 over there. Can someone pls. validate this.
          Thanx,
          Tajdar
          

AFAIK 2.2.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "Tajdar Siddiqui" <[email protected]> wrote in message
          news:3b043919$[email protected]..
          >
          > I read somewhere that Weblogic 6.0 supports Servlet Api 2.3 ( which in
          turn support
          > http Filters etc.).
          >
          > I searched the Weblogic docs site for 6.0 and there is no mention of
          Servlet Api
          > 2.3 over there. Can someone pls. validate this.
          >
          > Thanx,
          > Tajdar
          

Similar Messages

  • Weblogic 6.1 and Servlet API 2.3

    Dears All,
    could you confirm weblogic v6.1 can support J2EE v1.3 and especially Servlet API v2.3 ?
    Our war deployment is fine (v2.3 seems supported) but queries about major/minor versions in Web application Context return v2.2.
    Are some upgrade or deployments specifications required ?
    Thanks,
    Bruno

    AFAIK 2.2.
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com
              +1.617.623.5782
              WebLogic Consulting Available
              "Tajdar Siddiqui" <[email protected]> wrote in message
              news:3b043919$[email protected]..
              >
              > I read somewhere that Weblogic 6.0 supports Servlet Api 2.3 ( which in
              turn support
              > http Filters etc.).
              >
              > I searched the Weblogic docs site for 6.0 and there is no mention of
              Servlet Api
              > 2.3 over there. Can someone pls. validate this.
              >
              > Thanx,
              > Tajdar
              

  • Weblogic 9.2 and servlet 2.3

    I'm trying to run a web application with servlet 2.3 standard in weblogic 9.2.
              I have some Servlet Filters configured in it but none of them seems to be invoked when requesting a page.
              The application works fine in Tomcat 5.0.28.
              I have also tried to update web.xml to servlet 2.4 by adding the <dispatch> tag to <servlet-mapping> but the problem still remain.
              Am i missing something ?
              How can i run web application with servlet 2.3 standard on weblogic 9.2 ?
              I'd like to run the application with servlet 2.3 standard as i have some custom tag translating expression language so i do not want the application server to parse expression language too.
              Thanx
              Ivan

    WLS 9.2 does support servlet2.3 standard applications. It is hard to tell if there is something missing in your web.xml. Would you please attach your simplified web.xml here? Maybe someone can help you out.
              Thanks,
              -Fred

  • Where can I find document for weblogic(process JSP and Servlet)

     

    Hello Maksim,
    The link in your message no longer worked.  I got "page can't be displayed".
    Thank you.

  • I FOUND : servlet-api.jar ...WHERE insert it to can compile SERVLETS

    I FOUND : servlet-api.jar in TOMCAT 6
    WHERE insert it to can compile SERVLETS ?
    where added(directory), some folders follow...?
    C:\Program Files\Java\jdk1.6.0_15\bin
    C:\Sun\AppServer\lib
    C:\Program Files\Java\jdk1.6.0_15\src\javax

    You can use any of the following methods:
    i) SET CLASSPATH variable with absolute path of your servlet-api.jar and then compile your servlet from any folder.
    ii)you can use
    C:\jdk\bin>javac -cp C:\tomcat\lib\servlet-api.jar SampleServlet.javaand after comilation put the compiled java class file to classes folder of you web application.
    [Obviously if you have any package, then you need to maintaing that folder structure inside classes folder]
    Here I assumed your javac is available at C:\jdk\bin folder and servlet-api.jar is available at C:\tomcat\lib folder
    ---Sujoy

  • Servlet API 2.3 in Weblogic 6.1

    I am running WebLogic Server 6.1 SP2 but SnoopServlet says "Servlet Spec Version Implemented 2.2"
              any idea why? shouldn't this be ver. 2.3?
              

    Simon forgot to mention than 6.1 doesn't actually implement final 2.3 spec ;-)
              William Kemp <[email protected]> wrote:
              > Simon is looking over my shoulder and 'Simon says (b)'.
              > Bill
              > Doug Matthews wrote:
              >> Simon,
              >>
              >> I want to make sure I understand what you're saying, because I can interpret it
              >> a couple ways
              >>
              >> is it:
              >>
              >> (a) WL 6.1 only supports servlet api 2.2
              >>
              >> or
              >>
              >> (b) WL 6.1 supports servlet api 2.3 but only reports that it supports 2.2
              >>
              >> thanks, Doug
              >>
              >> Simon Nunn <[email protected]> wrote:
              >> >Doug,
              >> >
              >> > For 6.1, the major and minor versions returned are 2. This is a known
              >> >issue, and CR050846 was filed to address it. You would
              >> >need to open a support case in order to get more details for this CR.
              >> > I checked the code for the 7.0 Beta, and it is returning 2
              >> >for the major and 3 for the minor version.
              >> >
              >> >Thanks,
              >> > Simon
              >> > Developer Relations Engineer
              >> > BEA Support
              >> >
              >> >Doug Matthews wrote:
              >> >
              >> >> Simon,
              >> >>
              >> >> you're right, it's not in the servlet, but it's in the jsp
              >> >> (maybe you can get it added to the servlet?)
              >> >>
              >> >> look at SnoopServlet.jsp, it has the following:
              >> >>
              >> >> <h3>
              >> >> Servlet Spec Version Implemented
              >> >> </h3>
              >> >>
              >> >> <pre>
              >> >> <%= getServletConfig().getServletContext().getMajorVersion() + "."
              >> >+ getServletConfig().getServletContext().getMinorVersion()
              >> >> %>
              >> >> </pre>
              >> >>
              >> >> I modified the servlet (SnoopServlet.java) just to be sure:
              >> >>
              >> >> out.println("<h1>Servlet Spec Version Implemented</h1><pre>" + getServletConfig().getServletContext().getMajorVersion()
              >> >> + "." + getServletConfig().getServletContext().getMinorVersion() +
              >> >"</pre>");
              >> >>
              >> >> same results, it says ver. 2.2
              >> >>
              >> >> Simon Nunn <[email protected]> wrote:
              >> >> >Doug,
              >> >> >
              >> >> > I just ran the SnoopServlet in 6.1 SP2 using the examples server,
              >> >and
              >> >> >I do not see a line that
              >> >> >indicates the "Servlet Spec". Did you modify the SnoopServlet to
              >> >print
              >> >> >out additional information?
              >> >> >
              >> >> >Thanks,
              >> >> > Simon
              >> >> > Developer Relations Engineer
              >> >> > BEA Support
              >> >> >
              >> >> >Doug Matthews wrote:
              >> >> >
              >> >> >> I am running WebLogic Server 6.1 SP2 but SnoopServlet says "Servlet
              >> >> >Spec Version Implemented 2.2"
              >> >> >> any idea why? shouldn't this be ver. 2.3?
              >> >> >
              >> >
              

  • Weblogic 7.0 and 6.1 javax.servlet.filter implementation

              Hi All,
              I was using weblogic 6.1 and as my organization wants to go for 7.0, we
              are in the process of evaluating 7.0 ver.
              WL6.1 javax.servlet.filter interface provides the methods doFilter(), setFilterConfig(),
              getFilterConfig(). We have an implementation for the Filter which also contains
              a private method init(FilterCongig filterConfig).
              In 7.0 javax.servlet.filter interface the methods are doFilter(), init(), destroy().
              Because of the obvious reason i have a private implementation of init(FilterConfig
              )in my code the build does not succeed. When i checked the java specifications
              from Sun site I found 1.3.1 and 1.4(beta) specs provide doFilter(), init() and
              destroy().
              Question is: Is weblogic 6.1, JDK 1.3.1 compliant, if so why there is not init()
              method in the filter interface??. (Otherwise its a bug)
              Because of this the porting has become a serious issue as in some cases we need
              to support both 6.1 and 7.0
              

    6.1 did not implement the final version of the Servlet 2.3 specification, that's
              why you see differences.
              http://edocs.bea.com/wls/docs61/notes/new.html#1064420
              Sanjeev <[email protected]> wrote:
              > Hi All,
              > I was using weblogic 6.1 and as my organization wants to go for 7.0, we
              > are in the process of evaluating 7.0 ver.
              > WL6.1 javax.servlet.filter interface provides the methods doFilter(), setFilterConfig(),
              > getFilterConfig(). We have an implementation for the Filter which also contains
              > a private method init(FilterCongig filterConfig).
              > In 7.0 javax.servlet.filter interface the methods are doFilter(), init(), destroy().
              > Because of the obvious reason i have a private implementation of init(FilterConfig
              > )in my code the build does not succeed. When i checked the java specifications
              > from Sun site I found 1.3.1 and 1.4(beta) specs provide doFilter(), init() and
              > destroy().
              > Question is: Is weblogic 6.1, JDK 1.3.1 compliant, if so why there is not init()
              > method in the filter interface??. (Otherwise its a bug)
              > Because of this the porting has become a serious issue as in some cases we need
              > to support both 6.1 and 7.0
              Dimitri
              

  • IllegalStateException: strict servlet API: cannot call getWriter()

    I am getting an exception in Weblogic when I am trying to display a pdf file in a web page.
    java.lang.IllegalStateException: strict servlet API: cannot call getWriter() after getOutputStream()
    I am using the following code code
    ByteArrayOutputStream baos;
    ServletOutputStream out = response.getOutputStream();
    baos.writeTo(out);
    I have seen this error in so many discussion forum and there is no proper solution for this error.
    I am able to see the pdf page even with this exception. But I want to get rid of this exception also from Weblogic.

    I just did a quick (and dirty!) test with the following to display a jpg image and it worked for me without any trace of an exception:
        @Override
        protected void doGet(HttpServletRequest request, HttpServletResponse response)  throws ServletException, IOException {
            response.setContentType("image/jpg");
            File f = new File("/Users/me/Desktop/IMG_0032.JPG");
            byte[] bits = new byte[(int) f.length()];
            FileInputStream fos = new FileInputStream(f);
            fos.read(bits);
            ByteArrayOutputStream baos = new ByteArrayOutputStream();
            baos.write(bits, 0, bits.length);
            baos.writeTo(response.getOutputStream());
            baos.close();
            fos.close();
        }Note that there is no call anywhere to response.getWriter() in that.
    I'd guess the exception is directing you at what the problem is, at least as the server is seeing it -- somewhere in the execution of the request path there would appear to be call to response.getWriter() occurring after a call to response.getOutputStream() has been called, which is not permitted on WLS according to the error message.
    Do you use filters on this app? If response.getWriter() has been called on the same response object in a post request filter phase, that would be on the same call path with the same response object and would result in the exception.
    -steve-

  • EJB and Servlets

    Hi there,
    A frontend processing of HTTP request that pass thru WebLogic server that make
    API calls thru tuxedo to the application servers that eventually running C, C++
    that retrieve data from a backend database of Oracle.
    Being the services of EJB and Servlets, EJB is more kind of processes inside the
    server but Servlets can handle better in request and respond (talk to the client),
    whats your opinions in this kind of integration? Go for pure EJB or Servlets?
    Or shall mixed matched? and how should the architecture should looks like?
    Thanks
    Neo

    Sorry, wrong question, just ignore it.

  • Third-party jars not visible to EJB's and servlets.

    Hi, This is an unanswered post in an newsgroup which exactly displays our
    current problem,
    Extract Begins -->
    "I've got a WebApp with classloading issues while running WebLogic 5.1.
    According to the JSDK 2.2 API, if I include third-party classes in
    WEB-INF/lib, my EJBs and servlets should be able to load any jar'ed classes
    inside. In practice, however, it seems to make no difference. My EJB always
    comes back with a NoClassDefFound error for xerces.jar that's in WEB-INF/lib
    (and I've even tried adding it to the EJB JAR itself with no change).Of
    course, if I put Xerces in the server's classpath, there are no problems but
    that's a road I don't want to go down.How can I tell my EJB's to load
    third-party classes from the WEB-INF/lib directory of the WAR file? I'd
    appreciate your insight. <-- End
    We are busy migrating one of our apps from 5.1 to 6.1, What we have done
    thus far and fairly successfully is the following,
    We packaged all the jsps, WEB-INF, html, images into a WAR file and then
    packed all EJB's, META-INF and classes to which the ejbs refer, into an EAR
    file.
    EMARKET_APPS/
    +myjsp.jsp
    +myhtml.html
    +images
    +WEB-INF/+
    |
    +classes/+
    |
    +myclass1.class
    +myclass2.class
    |
    +lib/+
    |
    +OReily.jar
    +jts.jar
    +xerces-1_4_1.jar
    +junit.jar
    +jcschart110Kwl.jar
    |
    +web.xml
    +weblogic.xml
    +META-INF/+
    |
    +applications.xml
    +ejbs/+
    |
    +myejb1.jar
    +myejb2.jar
    +lib/+
    |
    +classes.jar
    Please advise.
    Rgs Roly

    Have you tried to include the jars in the Class path entry in the manifest file.
    That should work eventhough I haven't tried it yet (fighting with ear deployement
    and I must say WLS seems to be winning). I'll get back to when I've tried it.
    There is a VERY good article on theserverside.com regarding class loaders and
    EAR/WAR/EJBs at http://www.theserverside.com/resources/articles/J2EE-Deployment/chapter.html
    Good luck
    /erik

  • Strict servlet API: cannot call getOutputStream() after getWriter()

    i have an applet which will communicate with a servet ,  but got following error in the servlet
    java.lang.IllegalStateException: strict servlet API: cannot call getOutputStream() after getWriter()
    at weblogic.servlet.internal.ServletResponseImpl.getOutputStream(ServletResponseImpl.java:280)
    at oracle.osl.lt.web.servlets.AudioServlet._processGetPlayList(AudioServlet.java:235)
    at oracle.osl.lt.web.servlets.AudioServlet.doPost(AudioServlet.java:91)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:276)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101020 MACHINE = p1dvosl02 TXID = CONTEXTID = TIMESTAMP = 1318836952580
    WatchAlarmType: AutomaticReset
    WatchAlarmResetPeriod: 30000
    >
    *below _processGetPlayList() is called by doPost() of the servlet.*
    seems the exception is thrown due to response.getOutputStream()?
    any idea? thanks!!
    private void _processGetPlayList(HttpServletRequest request,
    HttpServletResponse response)
    throws ServletException, IOException {
    try {
    ObjectOutputStream objectOut =
    new ObjectOutputStream(new BufferedOutputStream(response.getOutputStream()));
    try {
    RichDataDTOExt richData = _getRichData(request);
    if (richData == null) {
    Log.web().debug(s7);
    throw new ServletException(s7);
    objectOut.writeObject(richData.getAudioRecordings().getAll(new ContentRefDTO[0]));
    finally {
    objectOut.close();
    catch (IOException e) {
    Log.web().error(e.getMessage());
    throw new ServletException();
    }

    thanks for you reply. but seems we don't call getWriter() at all in our code.
    actually this error only happen in our customer's env, no this issue in our development env.
    besides using getOutputStream() and getWriter() simultaneously for same response, is this maybe related with some web server configuration?

  • Strict servlet API: cannot call getWriter() after getOutputStream()

    Hi,
    Am getting below exception when i click on create report button.
    It was successfully running in development machine, when we deploy the same application into the testing server.
    what could be problem..
    am using JSF 2.0, Primefaces 3.5, Jdeveloper and Weblogic 12 C server..
    java.lang.IllegalStateException: strict servlet API: cannot call getWriter() after getOutputStream()
      at weblogic.servlet.internal.ServletResponseImpl.getWriter(ServletResponseImpl.java:299)
      at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:362)
      at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
      at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
      at javax.faces.webapp.FacesServlet.service(FacesServlet.java:155)

    Issue resolved, because testing machine doesn't have specified font in font directory.
    recompiled the jrxml file with arial font its working both the env machine..

  • IllegalStateException: strict servlet API:

    Hello All,
    I'm trying to do a simple rpc webservice. The wsgen process runs to a successful
    completion and I deploy the result to Weblogic 6.1 sp1, which is also successful.
    When accessing this new service, everything runs fine until the response is generated
    and I get following stack trace:
    <br>
    java.lang.IllegalStateException: strict servlet API: cannot call getWriter() after
    getOutputStream() <br>
    at weblogic.servlet.internal.ServletResponseImpl.getWriter(ServletResponseImpl.java:160)
    <br>
    at weblogic.soap.server.servlet.StatelessBeanAdapter.reportFault(StatelessBeanAdapter.java:238)
    <br>
    etc...
    It would appear that this is being generated in a Weblogic class. There is no
    mention of my EJB in the stack trace.
    Has anyone seen this error? Or, better yet, what causes it and what is the solution?
    Thanks,
    Kris

    Kris,
    I too have run into this problem with Weblogic 6.1. The first time I
    got this exception was when I had java.util.Date attributes within my
    serializable data object that I was returning from my WebService interface.
    When those date attributes were set with values, I would get the exception
    outlined below. Then I set those date values to null, and everything worked
    fine.
    Coincidentally, I'm currently have the same problem with a serializable
    object that has another serializable object defined as an attribute. I'm
    not wondering if Weblogic can't handle Serializable objects within other
    Serializable objects?
    I guess my suggestion would be to look at the values you are returning
    and passing in as parameters to your WebService interface, are there any
    Serializable objects that have other Serializable objects defined as
    attributes ( Strings don't count )? If so, set them to null and try your
    WebService again. ( Does that make sense?? )
    Hope this helps?
    Jeff
    "Kris W. Keener" <[email protected]> wrote in message
    news:3bd71794$[email protected]..
    >
    Hello All,
    I'm trying to do a simple rpc webservice. The wsgen process runs to asuccessful
    completion and I deploy the result to Weblogic 6.1 sp1, which is alsosuccessful.
    When accessing this new service, everything runs fine until the responseis generated
    and I get following stack trace:
    <br>
    java.lang.IllegalStateException: strict servlet API: cannot callgetWriter() after
    getOutputStream() <br>
    atweblogic.servlet.internal.ServletResponseImpl.getWriter(ServletResponseImpl.
    java:160)
    <br>
    atweblogic.soap.server.servlet.StatelessBeanAdapter.reportFault(StatelessBeanA
    dapter.java:238)
    <br>
    etc...
    It would appear that this is being generated in a Weblogic class. There isno
    mention of my EJB in the stack trace.
    Has anyone seen this error? Or, better yet, what causes it and what is thesolution?
    >
    Thanks,
    Kris

  • I need to install servlet-api.jar in the libext folder.

    Hi I am doing a tutorial on struts 2.0.11.
    i need to install servlet-api.jar in the libext folder which I have created inside WEB-INF
    Now I have downloaded servlet.api which is in the zip form.
    When I extract the files. Its giving me two folders
    1. javax
    2. META-INF
    Inside javax there is a folder called servlet. Inside servlet folder there are
    a) bunch of call files
    b) http folder
    c) resources folder
    Inside http folder there are
    a) class files
    b) properties files
    Inside the resources folder there are
    a) dtd files
    b) xsd files
    Inside the META-INF folder there is the manifest.mf file
    I just need servlet-api.jar
    I think that I have extracted the contents of servlet-api.jar by using the extract feature of winzip.
    Do you think that by just changing the extension of the file from servlet-api.zip to servlet-api.jar it will do the trick or do i need to do something else.
    Please guide

    pksingh79 wrote:
    Hi ^^,
    your replies were very helpful. I did try to check the lib folder of the webserver and there was not servlet-api.jar. However I downloaded a dummy project and it did have servlet-api.jar in it, so I am ok for now.
    thanks and regards,
    PrashantYou should not be doing that. Always use the one from the application server which you're going to use. Otherwise you will possibly get in runtime trouble due to version differences.
    The actual location and filename of the servlet API might differ per application server implementation. If it was for example Tomcat 6, it is the servlet-api.jar in the /lib directory. If it was for example Glassfish (the current release), then it is the javaee.jar in the /lib directory.

  • How to set classpath to EJB and Servlets

    Hi all,
    How can I add a classpath to EJB and Servlets in Weblogic 6.1, so that that classpath
    can be achieved by both EJB jar and war file? I have deployed a .ear file having
    the jar and war files. Now the EJBs inside the jar file are not reaching the class
    files of the war file and the class files in the war file are not reaching to
    the EJBs. Please let me know at the earliest.
    Atanu

    Hi.
    You might try looking at the petstore example which combines webapps (war files) with
    ejbs in an ear file to see how to do this. It may be a simple config problem.
    Regards,
    Michael
    Atanu Dey wrote:
    Hi all,
    How can I add a classpath to EJB and Servlets in Weblogic 6.1, so that that classpath
    can be achieved by both EJB jar and war file? I have deployed a .ear file having
    the jar and war files. Now the EJBs inside the jar file are not reaching the class
    files of the war file and the class files in the war file are not reaching to
    the EJBs. Please let me know at the earliest.
    Atanu--
    Michael Young
    Developer Relations Engineer
    BEA Support

Maybe you are looking for