More effecient? Session var or web.xml

Hi list,
Like the subject line suggests. Just wondered what is more effecient/better practice.
I would like to use a variable in my Web App, which defines the pagesize, i.e. how many rows are displayed in my Database application.
Does anyone have any comments whether its better to persist this int value in a session, or keep it in the web.xml and just keep reading the parameter from the web.xml.
Would really appreciate any replies,
Ben Bookey

Thanks for the replies..
I guess web.xml is the obvious way, (definitely better than using session) but perhaps its better rather than reading every time I need the value from the web.xml, to store the variable in an server side variable somehow. I come from using MS ASP and i would then create an Appication Variable in the Global.asa, rather than reading (disk IO) from an ini file or something. This variable is then available (public) to all my scripts.
What do you think about using the ServletContextListener event, reading the web.xml once on app startup, and assigning this variable to a Public variable of some AppPropeties object or something...Perhaps this more effecient?
What would you think?
regards
ben bookey

Similar Messages

  • Critical: Adding session-config to web.xml cause application NOT to start

    I added the <session-config> element under <web-app> in web.xml:
    <session-config>
    <session-timeout>30</session-timeout>
    </session-config>
    Now the app won't start!
    The reason: the built-in sun app server removes context-root attribute from <web-module> element in domain.xml when the app tries to start!
    Please fix this ASAP, guys!

    I placed it in the wrong place. After following the instructions contained in the Technical FAQ (below), it worked.
    Add the following element in your web.xml file, placing it after the mapping for the error servlet and before the welcome file list:
    <session-config>
    <!-- Set global default timeout to 60 minutes -->
    <session-timeout> 60 </session-timeout>
    </session-config>

  • In Web.xml  welcome file tag not works

    Hi All ,
    I am developing simple web application using spring framework
    when i am try to add welcome file tag in web.xml with respective welcome page path but it not works.
    but when use jsp page without to having any property it works.
    what the problem with me
    Thanks

    Hi Frank
    Thank you for your reply.
    This is how I registered the session filter in web.xml
    <filter>
    <filter-name>SessionFilter</filter-name>
    <filter-class>com.avery.view.filter.SessionFilter</filter-class>
    </filter>
    <filter-mapping>
    <filter-name>SessionFilter</filter-name>
    <url-pattern>/faces/*.jsf</url-pattern>
    </filter-mapping>
    I'll try to use phaselisenter as you suggested.
    Also, one more thing please, in the session filter, I have something like this.
    public void doFilter(ServletRequest request, ServletResponse response,
    FilterChain chain) throws IOException, ServletException {
    System.out.println("JF--- Calling the Filter");
    if (request instanceof HttpServletRequest) {
    HttpServletRequest httpRequest = (HttpServletRequest)request;
    HttpServletResponse httpResponse = (HttpServletResponse)response;
    HttpSession session = httpRequest.getSession();
    String url = httpRequest.getPathTranslated();
    String path = httpRequest.getContextPath() + httpRequest.getServletPath();
    if (httpRequest.getRequestURI().equals(path+"/Login")) {
    System.out.println(" the request path is" + httpRequest.getRequestURI().toString());
    session.setAttribute("WELCOME", Boolean.TRUE);
    chain.doFilter(request, response);
    else if (session.getAttribute("WELCOME") == null){
    httpResponse.sendRedirect(path+"/Login");
    else {
    chain.doFilter(request, response);
    else {
    chain.doFilter(request, response);
    Do you think it looks right ?
    thanks
    Edited by: Lang on Apr 13, 2012 1:41 AM

  • Processing web.xml -Adding servlet

    Can you please give me an out line how to add servlets/filters/session-configs to web.xml programatically.
    I have writen a program for adding these but In web.xml the order in which elements are placed matters. So right now in the program I specify that I should add this element before another specified element like that .
    How can we make this generic ? I mean how I can maintain the same order as of DTD ?
    please help me.

    Answering your original question. Yes it is possible to have a web.xml without servlet classes, if you are not using servlet classes.
    >
    But I got the following error from Tomcat.
    2007-01-12 18:31:25 ContextConfig[worktigers] Parse
    error in application web.xml
    org.xml.sax.SAXParseException: The processing
    instruction target matching "[xX][mM][lL]" is not
    allowed.
    at
    t
    org.apache.xerces.parsers.AbstractSAXParser.parse(Unkn
    own Source)
    TA
    MalaiIt looks like there may be BOM characters (invisible in regular editors), before the opening angle bracket of the XML prolog: <?xml version="1.0"
    The special characters usually are inserted by some editors such as Notepad.
    You can download a free Hex editor, like Cygnus hex editor and see if you have the 3 special characters (in Hex) appearing before the XML prolog.
    If you see anything before the prolog delete them, save the web.xml file and re-test it.
    Reading from previous answers to your problem from here:
    http://forum.java.sun.com/thread.jspa?threadID=694303&messageID=4033694
    http://mail-archives.apache.org/mod_mbox/xerces-j-users/200201.mbox/%3Cp04330102b8689660dcbc@%5B192.168.254.4%5D%3E

  • I  have some more problem in the  web.xml file and url-pattern in my  syste

    HI ALL!
    How can I create and place the web.xml and URL-parrten.Because I run
    the tomcat in my computer with ME system.
    Hoc

    what is the problem? please be more specific and detailed? check a sample web.xml file and make your own one and place it in your <application-context>\WEB-INF folder..

  • SJSC2u1 JSP accessing web.xml session-config session-timeout

    What is the best way of accessing web.xml session-config session-timeout from JSP page ?
    I wish to have this on the JSP page and also have it count down automatically.
    I did this by creating a propery in the session bean and then used javascript to count it down.
    Is there a better way ? Simpler Way ?
    /Roger

    What is the best way of accessing web.xml session-config session-timeout from JSP page ?
    I wish to have this on the JSP page and also have it count down automatically.
    I did this by creating a propery in the session bean and then used javascript to count it down.
    Is there a better way ? Simpler Way ?
    /Roger

  • Web.xml - adjusting the session configuration

    I recently applied SP07 for NW7.01 to one of our portals, and since doing this I can not find where to make adjustments for the session timeout. It used to be defined in the web.xml, does anyone know where it was moved to?
    I used to go here:
    /usr/sap/<SID>/JC##/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/web.xml and adjust the default of 30 as necessary. Where is this value found now?
    I can also make the adjustment from the visual administrator under web container> properties> Session Timeout and this requries a restart of the web container service.
    From SAP HELP:
    Specifying HTTP Session Timeout 
    You can specify a timeout period for HTTP sessions created in your Web application. If the session is inactive for this timeout period, it is invalidated by the Web container.
    If you do not specify such a timeout explicitly, a default one of 30 minutes is assumed.
    You can configure the HTTP session timeout using the web.xml descriptor.
    Procedure
    On the web.xml screen, proceed as follows:
           1.      Open the General screen.
           2.      To specify the timeout period, enter a value in the Session configuration u2013 Session timeout field.
    The value is specified in minutes. If you enter a negative value in this field, HTTP sessions are never terminated because of a timeout. Instead, only an explicit logout by the user will terminate the corresponding session.

    Hello David.
    The help article is about custom development using NWDS. For adjusting session timeout system wide refer to Re: Portal session time out is 30 minutes.
    Best regards,
    Aliaksandr Zhukau

  • Sun-web.xml memory based sessioning issue

    I recently installed Sun WebServer 7.0 Update 8 on Fedora 20. Everything seems to be working fine with my webserver except for the memory based sessioning.
    My First Configuration - no sun-web.xml file defined
    Expected Behavior - I would assume that memory based sessioning would be used.
    Actual Behavior on my local instance - Every 1-2 minutes my session would abruptly end and a new JSESSIONID would be issued. This does not happen on other machines running the same webapp, so it does seem to be a sun webserver configuration problem.
    My Second Configuration - using the following sun-web.xml file:
    <!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 Servlet 2.5//EN" "http://www.sun.com/software/appserver/dtds/sun-web-app_2_5-0.dtd">
    <sun-web-app>
      <session-config>
         <session-manager persistence-type="memory">
              <manager-properties>
                   <property name="reapIntervalSeconds" value="20000" />
             </manager-properties>
         </session-manager>
        </session-config>
    </sun-web-app>
    Expected Behavior - Memory based sessioning would be used
    Actual Behavior on my local instance - Same as with no sun-web.xml. Every 1-2 minutes my session would abruptly end and a new JSESSIONID would be issued.
    Does anyone see what is wrong with my sun-web.xml file? I'm also not sure if the file permissions/ownerships are correct on all of my sun webserver files. Is there a particular temp file or location that Sun Webserver uses to track active sessions? Or are in-memory sessions completely stored in memory and not on disk? Is there a default sun-web.xml file somewhere that is overriding my settings (and if so, where is it located)?
    Thanks for your help!

    Hi,
    Firstly you should know Fedora is not a support platform. it might work but you could run into a load of issues as your go.
    in any case you don't need a sun-web.xml file at all. For any deployed Web app the default session manager is memory. So remove that 1st. After that check that
    the requests are really sending a JSESSIONID. This kind of issue can occur when you have a Load balancer.
    regards,
    Russell

  • How to set two different welcome-file to different servlets in web.xml

    Hi friends,
    Can some one help with web.xml file
    I have to different servlets in applications.
    I want to set two different welcome files for my two different
    servlets in web.xml
    Please, can some one give me sample code to achieve this.
    Here web.xml code:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE web-app PUBLIC
    "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>     
         <servlet>
              <servlet-name>reports</servlet-name>
              <servlet-class>com.caremark.ivr.servlet.IvrReportsServlet</servlet-class>
         </servlet>
         <servlet-mapping>
              <servlet-name>reports</servlet-name>
              <url-pattern>/reports</url-pattern>
         </servlet-mapping>
         <session-config>
              <session-timeout>30</session-timeout>
         </session-config>
         <welcome-file-list>
              <welcome-file>reportsindex.jsp</welcome-file>
         </welcome-file-list>
         <servlet>
              <servlet-name>calldetails</servlet-name>
              <servlet-class>com.caremark.ivr.servlet.IvrCallDetailsServlet</servlet-class>
         </servlet>
         <servlet-mapping>
              <servlet-name>calldetails</servlet-name>
              <url-pattern>/calldetails</url-pattern>
         </servlet-mapping>
    <welcome-file-list>
              <welcome-file>calldetailsindex.jsp</welcome-file>
         </welcome-file-list>
    </web-app>
    I need this fix immediately. Your help will be really appreciated. Thanks in advance.

    First of all, my understanding is that you need to have a Servlet 2.4 complaint server to do this...Given that, you're supposed to be able to simply specify the Name of the servlet as the welcome-file to get it to work. For example:
    Your servlet section:
    <servlet>
      <servlet-name>Controller</servlet-name>
      <servlet-class>com.company.ControllerServlet</servlet-class>
    </servlet>Now you would add the following to your welcome file list:
    <welcome-file-list>
      <welcome-file>Controller</welcome-file>
    </welcome-file-list>Note that you use the servlet-name value from the servlet definition, NOT the url-mapping from the servlet-mapping section.
    Please note that I cannot verify this as I am running a 2.3 server at home. When I get to work Friday I can test on a 2.4 machine. However this shouldn't take you more than a minute to test.
    Note that I did try this on the 2.3 compliant server and it did NOT work (as I expected)...
    HTH.

  • Welcome File in Web.xml

              I am having problems with my web.xml file.
              I have my welcome page <welcome-file> as my “home_page.jsp” which I want to be
              the default page on start-up. On this page is a link to “log on”. When you click
              on this you are taken to my (FORM) “Login.jsp”. After successful logon I want
              to go to the “Welcome.jsp”, instead I am returned to my “home_page.jsp”. Which
              puts me in a continuous loop. How after successful logon can I be directed to
              a page other than the <welcome-file> “home_page.jsp”
              My web.xml file looks like this;
              <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
              "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              <web-app>
              <welcome-file-list>
              <welcome-file>Welcome.jsp</welcome-file>
              </welcome-file-list>
              <login-config>
              <auth-method>FORM</auth-method>
              <realm-name>default</realm-name>
              <form-login-config>
                   <form-login-page>/Login.jsp</form-login-page>
                   <form-error-page>/LoginFailure.jsp</form-error-page>
              </form-login-config>
              </login-config>
              <security-role>
              <role-name>web-user</role-name>
              </security-role>
              <security-constraint>
              <web-resource-collection>
              <web-resource-name>Logged into NOTiFY</web-resource-name>
              <url-pattern>/Welcome.jsp</url-pattern>
              <http-method>GET</http-method>
              <http-method>POST</http-method>
              </web-resource-collection>
              <auth-constraint>
              <role-name>web-user</role-name>
              </auth-constraint>
              </security-constraint>
              </web-app>
              Thanks.
              

    It doesn't quite work that way. You should just direct the user directly to
              the Welcome.jsp page. If they're not already logged in, they'll be asked to
              log-in via the Login.jsp. The login mechanism knows to redirect them to the
              last page they wanted once they successfully log in. I think this is why you
              are being returned to the home_page.jsp, since there was no target
              restricted page requested.
              I have to admit - this mechanism doesn't lend itself to the portal-style
              login used on the web. It's geared more towards security and authorization
              for access to particular URL resources. You might need to tweak how your GUI
              looks to make this mechanism make sense.
              Alternatively, you could add some code to the home_page.jsp to redirect the
              user to a specific restricted page based on what is in their session. I
              would also suggest that the Welcome.jsp and home_page.jsp be the same page
              that just behaves differently based upon whether a user is logged in or not.
              "Roger Lee" <[email protected]> wrote in message
              news:[email protected]...
              >
              > I am having problems with my web.xml file.
              >
              > I have my welcome page <welcome-file> as my "home_page.jsp" which I want
              to be
              > the default page on start-up. On this page is a link to "log on". When you
              click
              > on this you are taken to my (FORM) "Login.jsp". After successful logon I
              want
              > to go to the "Welcome.jsp", instead I am returned to my "home_page.jsp".
              Which
              > puts me in a continuous loop. How after successful logon can I be directed
              to
              > a page other than the <welcome-file> "home_page.jsp"
              >
              > My web.xml file looks like this;
              >
              > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
              2.2//EN"
              > "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              >
              > <web-app>
              >
              > <welcome-file-list>
              > <welcome-file>Welcome.jsp</welcome-file>
              > </welcome-file-list>
              >
              > <login-config>
              > <auth-method>FORM</auth-method>
              > <realm-name>default</realm-name>
              > <form-login-config>
              > <form-login-page>/Login.jsp</form-login-page>
              > <form-error-page>/LoginFailure.jsp</form-error-page>
              > </form-login-config>
              > </login-config>
              >
              > <security-role>
              > <role-name>web-user</role-name>
              > </security-role>
              >
              > <security-constraint>
              > <web-resource-collection>
              > <web-resource-name>Logged into NOTiFY</web-resource-name>
              > <url-pattern>/Welcome.jsp</url-pattern>
              > <http-method>GET</http-method>
              > <http-method>POST</http-method>
              > </web-resource-collection>
              > <auth-constraint>
              > <role-name>web-user</role-name>
              > </auth-constraint>
              > </security-constraint>
              >
              > </web-app>
              >
              > Thanks.
              >
              

  • Web.xml security-constraint order matters?

    After a long and frustrating debuggin session I've just discovered that the order in which <security-constraint>
    entries are added to the web.xml file matters to OC4J.
    That is if a more laxed rule is matched first the rest
    (even though they might be more precise or even an
    exact match won't be applied.
    Is this normal behaviour?
    EXAMPLE BELOW WORKS - INVERT ENTRIES AND IT WILL FAIL
    <security-constraint>
        <web-resource-collection>
          <web-resource-name>Protected</web-resource-name>
          <url-pattern>/admin*.uix</url-pattern>
        </web-resource-collection>
        <auth-constraint>
          <role-name>DSMSuperUser</role-name>
        </auth-constraint>
      </security-constraint>
      <security-constraint>
        <web-resource-collection>
          <web-resource-name>Secure</web-resource-name>
          <url-pattern>/*</url-pattern>
        </web-resource-collection>
        <auth-constraint>
          <role-name>DSMUser</role-name>
        </auth-constraint>
      </security-constraint>

    Here is an excerpt from the servlet spec stating the proper behavior:
    The container matches URL patterns defined in security constraints
    using the same algorithm described in this specification for matching client
    requests to servlets and static resources as described in SRV.11.1
    SRV.11.1 Use of URL Paths
    Upon receipt of a client request, the web container determines the web application
    to which to forward it. The web application selected must have the the longest
    context path that matches the start of the request URL. The matched part of the URL
    is the context path when mapping to servlets.
    The web container next must locate the servlet to process the request using the
    path mapping procedure described below:
    The path used for mapping to a servlet is the request URL from the request
    object minus the context path. The URL path mapping rules below are used in
    order. The first successful match is used with no further matches attempted:
    1. The container will try to find an exact match of the path of the request to the
    path of the servlet. A successful match selects the servlet.
    2. The container will recursively try to match the longest path-prefix: This is done
    by stepping down the path tree a directory at a time, using the ’/’ character as
    a path separator. The longest match determines the servlet selected.
    3. If the last segment in the URL path contains an extension (e.g. .jsp), the servlet
    container will try to match a servlet that handles requests for the extension.
    An extension is defined as the part of the last segment after the last ’.’ character.
    4. If neither of the previous three rules result in a servlet match, the container will
    attempt to serve content appropriate for the resource requested. If a "default"
    servlet is defined for the application, it will be used.
    The container must use case-sensitive string comparisons for matching.
    So this is STILL an issue w/ 10.1.2.0.2...
    EXAMPLE BELOW WORKS - INVERT ENTRIES AND IT WILL FAIL
    <security-constraint>
    <web-resource-collection>
    <web-resource-name>oemAdmin</web-resource-name>
    <url-pattern>/admin/*</url-pattern>
    </web-resource-collection>
    <auth-constraint>
    <role-name>OEM_ADMIN</role-name>
    </auth-constraint>
    <user-data-constraint>
    <transport-guarantee>NONE</transport-guarantee>
    </user-data-constraint>
    </security-constraint>
    <security-constraint>
    <web-resource-collection>
    <web-resource-name>allOem</web-resource-name>
    <url-pattern>/*</url-pattern>
    </web-resource-collection>
    <auth-constraint>
    <role-name>OEM_USER</role-name>
    </auth-constraint>
    <user-data-constraint>
    <transport-guarantee>NONE</transport-guarantee>
    </user-data-constraint>
    </security-constraint>
    If I don't find a SR for this issue I'll open one b/c this is not acceptable.

  • Overide web.xml sessiontimeout info via Console

    I have various modules in the project with each web.xml. I have session timeout specified in each of them
    <session-config>
    <session-timeout>15</session-timeout>
    </session-config>
    I am using WebLogic Server 9.2 MP3
    I would like to override this information via weblogic console without bringing down the server or changing the code manually and redeploy.
    Thanks for any information on this.
    -jb

    Hi Pete,
    A description of the construction of the web service home page url can
    be found here [1]
    I believe I've seen a CR on that warning message from the lack of a
    web.xml (BEA-101313); this can be safely ignored, an empty webapp
    descriptor file gets created by default.
    Thanks,
    Bruce
    [1]
    http://edocs.bea.com/wls/docs81/webserv/assemble.html#1076491
    Pete wrote:
    >
    When I deploy my Webservices as a WAR at the application folder level e.g. :-
    \applications
    mywebservices.war
    The Weblogic Console seems to be aware that the war contains web services, so
    if I go to the
    console Tree -
    Deployments
    - Web Application Modules
    - mywebservices
    Then choose the 'Testing' tab, I can see a page that allows testing of the Web
    Service e.g.
    "This page allows you to test the Web Service to make sure it is deployed and
    working as expected."...
    But when I deploy the WAR as part of an Exploded EAR, then the Web Apps becomes
    listed under :-
    Deployments
    - Applications
    - myEAR
    - mywebservices
    but the Testing tab thinks the Web App is more standard ? e.g.
    "This page allows you to test the deployment of the Web application to make sure
    it was a successful one. "
    and consequently there are no links to the URLs for testing the Web Service. But
    it still works but is hidden to administators.
    Any ideas ?
    Also, I did notice that the web app in both cases doesn't have the standard web.xml
    present. The web app was built using a build.xml from http://manojc.com 's sample43
    , and that when it is deployed weblogic gives a warning to say web-xml is missing.
    Everything still works though.

  • Ias-web.xml

    a) What is the significance of 'impl' and 'dsync-type' elements in the
    ias-web.xml. I have an application running
    on a single instance of iAS 6.0 SP3 with two kjs processes.What should
    be the typical values of the above
    mentioned elements.
    b) Also what is recomended number of kjs processes per CPU ?
    Thanks in advance
    MP

    Hi,
    Answer inline.
    MP wrote:
    a) What is the significance of 'impl' and 'dsync-type' elements in the
    ias-web.xml. I have an application running
    on a single instance of iAS 6.0 SP3 with two kjs processes. What should
    be the typical values of the above
    mentioned elements.
    These fields are used to specifies session information.
    A session can be either a distributed, fault-tolerant session, or a
    lightweight local-only session. this is specifies by 'impl' field, its Legal
    values:{'distributed' | 'lite'}
    If the impl is ?distributed?, then the session could be of two further types,
    and this specifies by 'dsync-type' field. Its Legal values: {'dsync-local'
    |'dysnc-distributed')
    and value of 'impl' is up to you If you want your application to be
    distributed then
    use 'distributed ' otherwise 'lite'.
    for more information you can see java programmer guide and iAS admin guide
    available at
    http://docs.iplanet.com/docs/manuals/ias.html#sp3
    http://docs.iplanet.com/docs/manuals/ias/60/sp2/JavaProgGuide/contents.htm
    http://docs.iplanet.com/docs/manuals/ias/60/sp3/admin/contents.htm
    b) Also what is recommended number of kjs processes per CPU ?
    Its depend on your requirement and type of hardware.
    how fast your processor is?
    what type of application you are going to deploy?
    how many customer can simultaneously hit your program?
    and so on...
    so If you will send me your all requirements and configuration than only I can
    tell
    you.
    Please get back if this has solved your problem or if you have any issues.
    Deepak
    dev_support

  • Unable to load descriptor .../web.xml - DescriptorException - Java EE6 war

    Deploying a simple Java EE 6 war into WebLogic 10.3.3 fails with <Unable to load descriptor /root/Oracle/Middleware/user_projects/domains/palis1/servers/AdminServer/upload/SimpleEE6App.war/WEB-INF/web.xml of module SimpleEE6App.war. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-enumeration-valid: string value '3.0' is not a valid enumeration value for web-app-versionType in namespace http://java.sun.com/xml/ns/javaee:<null>
    The web app consists of one JSF 2 web dialog, one managed bean, one stateless session bean and one entity bean. In GlassFish v3 the app works fine. Then I installed the actual version of WebLogic server in order to check whether I can run EE6 apps there to. But deploying the war using WebLogic admin console fails with
    ... <AdminServer> <main> <<WLS Kernel>> <> <> <1273649525966> <BEA-000360> <Server started in RUNNING mode>
    ... <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <admin> <> <> <1273649790693> <BEA-160197> <Unable to load descriptor /root/Oracle/Middleware/user_projects/domains/palis1/servers/AdminServer/upload/SimpleEE6App.war/WEB-INF/web.xml of module SimpleEE6App.war. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-enumeration-valid: string value '3.0' is not a valid enumeration value for web-app-versionType in namespace http://java.sun.com/xml/ns/javaee:<null>
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:155)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
    at weblogic.servlet.utils.WarUtils.getWebAppBean(WarUtils.java:124)
    at weblogic.application.compiler.WARModule.processLibraries(WARModule.java:413)
    at weblogic.application.compiler.WARModule.merge(WARModule.java:455)
    at weblogic.application.compiler.flow.SingleModuleMergeFlow.proecessModule(SingleModuleMergeFlow.java:16)
    at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
    at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
    at weblogic.application.compiler.ReadOnlyWarMerger.merge(ReadOnlyWarMerger.java:27)
    at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:88)
    at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:41)
    at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
    at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.application.compiler.AppMerge.merge(AppMerge.java:169)
    at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:88)
    at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:63)
    at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:181)
    at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDeployableObjectFactoryImpl.java:156)
    at weblogic.deploy.api.tools.SessionHelper.inspect(SessionHelper.java:661)
    at com.bea.console.actions.app.install.Flow$2.execute(Flow.java:469)
    at com.bea.console.utils.DeploymentUtils.runDeploymentAction(DeploymentUtils.java:5000)
    at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:467)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
    at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
    at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
    at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
    at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
    The web.xml is
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
    <context-param>
    <param-name>javax.faces.PROJECT_STAGE</param-name>
    <param-value>Development</param-value>
    </context-param>
    <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    <session-config>
    <session-timeout>
    30
    </session-timeout>
    </session-config>
    <welcome-file-list>
    <welcome-file>faces/index.xhtml</welcome-file>
    </welcome-file-list>
    </web-app>
    After changing the version number I got the same error message with the differing number. I also tryed to deploy the web-app_3_0.xsd into the server. This also did not solve the problem.
    Any ideas?
    Thanks in advance
    Axel Burghof

    The web app consists of one JSF 2 web dialog, one managed bean, one stateless session bean and one entity bean. In GlassFish v3 the app works fine. Then I installed the actual version of WebLogic server in order to check whether I can run EE6 apps there to. But deploying the war using WebLogic admin console fails with ...
    Hey Axel -
    WLS 10.3.x does not implement Java EE 6 -- it's a Java EE 5 based server.
    While we have added support for a few independent Java EE 6 specifications where we can -- such as JSF 2.0 in WLS 10.3.3 and JPA 2.0/JAX-RS 1.1 with WLS 10.3.4 that is coming in the next patchset -- we don't support all of the Java EE 6 model and thus you can't use any of the EJB 3.1, Servlet 3.0 changes and you can't deploy EJBs (and JPA entities) inside of a WAR file. Our next major release will be a Java EE 6 implementation, where this will be possible.
    -steve-

  • Web service and servlets in the same project...web.xml?

    Hello, I have a problem with my web service.
    I have a server, which displays a web service. I programmed this service with JAXRPC.
    I have a client, in another directory. I succeded in compiling, deploying and running the web service.
    The problem is that after I tried to integrate this service in an existing project. This project contains servlets. In these servlets, I'm using sessions.
    These servlets are on the same side as the server of the web service. Because of the implementation of my code, I'd like to use in the class that represents the server of the service, the same session as the one I'm using in the servlets.
    But of course, it's not working by itself. I know there's something to do with the web.xml files.
    The thing is that I created a web.xml file for the service, and another for the servlets.
    I was thinking of joining both of them in one xml file, but everything crashes then...
    Could someone tell me how to create a project with a web service and servlets, and mostly how to configure the xml file??
    Thanks for any help
    Philippe

    Hello, I have a problem with my web service.
    I have a server, which displays a web service. I programmed this service with JAXRPC.
    I have a client, in another directory. I succeded in compiling, deploying and running the web service.
    The problem is that after I tried to integrate this service in an existing project. This project contains servlets. In these servlets, I'm using sessions.
    These servlets are on the same side as the server of the web service. Because of the implementation of my code, I'd like to use in the class that represents the server of the service, the same session as the one I'm using in the servlets.
    But of course, it's not working by itself. I know there's something to do with the web.xml files.
    The thing is that I created a web.xml file for the service, and another for the servlets.
    I was thinking of joining both of them in one xml file, but everything crashes then...
    Could someone tell me how to create a project with a web service and servlets, and mostly how to configure the xml file??
    Thanks for any help
    Philippe

Maybe you are looking for

  • Reception / Battery problems with iPhone 3GS after upgrading to iOS 4.2.1

    There are major reception and battery problems with iPhone 3GS after upgrading to iOS 4.2.1. I can not believe that Apple did not test this for major bugs like this one is. I am a business user and can not effort to have bad reception. Apple wants to

  • Oracle 11g R2 RAC installation on AIX

    hi, I wana setup Oracle 11g R2 RAC on Ibm with AIX. Is there any good document or cookbook explaining step by step procedure for the installation...I'll be thankful thanx

  • Building WSDL client for OIM SPML webservice

    Has any one created WSDL client for OIM SPML webservice, Any help is appreciated. Thanks, Pandu old thread --> add udfs to spml prov. request to oim ========================== Hi, I am provisioning users in OIM from by sending spml requests I used th

  • Microsoft Office Product Key

    Hi I am planning on getting a new hard drive for my macbook pro and I can't find my Microsoft Office 2011 product key (or installation disk) If i want to have office on the new hard drive, do I simply have to copy the Applications (and related files)

  • Operating Lease

    Dear Experts, Our company would like to introduce Operating Lease. I have read about customizing this operating lease but at the moment, it is still not working. FYI - I have activated cost accounting depreciation area 20 (post to GL inactive). I als