Updated env-entries in web.xml

          We are using WLS 5.1 SP10.
          In a web-application we like to have some parameters (related to the webapp as
          a whole) which can easily be changed (without having to restart the server).
          What is the best way to do that?
          I was thinking of env-entries.
          But when I change them the web.xml is not reloaded and the changes have no affect.
          Is dynamic reload of web.xml possible under WLS5.1 SP10?
          When should env-entries be used, and when init-params?
          Init-params seems to be servlet(JSP) related, while the environment entries affect
          the web-app environment. Are there other elements to take in consideration?
          In the doc I found no real explanation of when to use what...
          Any help would be appreciated,
          Frederic
          Please send answers also to my e-mail: [email protected]

Hi,
these are only configurations and don't cause a harm or use resources. So I suggest to leave them in just in case yu need them later
Frank

Similar Messages

Admin UI for editing environment entries (i.e. env-entry in web.xml)

Hi there,
just wanted to know if Weblogic nowadays features a UI for post-deployment editing of environment entries such as the ones declared via <env-entry> in web.xml ( [http://download.oracle.com/docs/cd/E21764_01/web.1111/e13712/web_xml.htm#autoId30] ). So far, I'm using a deployment plan to re-configure these things at the time of each deployment, which works but which is also probably not the most flexible solution.
Thanks in advance,
Chris

Ah, I was trying to do a lookup from session bean for the env-entry defined in
the web.xml. After reading the J2EE spec, I see this just won't work. env-entries
are only accessible from within the component where they are defined.
Still the error message with "comp.env" instead of the expected "comp/env" is
a bit confusing.
Not much traffic in this newsgroup, is there?
Steve
"Steve Ditlinger" <[email protected]> wrote:
>
>
>
If I create an "env-entry" block for a name (e.g. "MySchemaName") in
my web.xml
file and deploy the web app, I should be able to look up the name from
my webapp
with the line:
<br>
myInitialContext.lookup("java:comp/env/MySchemaName");
<br>
However when I do that I get the error message:
<br>
javax.naming.NameNotFoundException: Unable to resolve 'java:comp.env/MySchemaName'
<br>
Note that the "comp/env" prefix has been changed to "comp.env". This
worked under
WL 6.1. Is this a bug in WL 7's JNDI or a bug in the error message or
both or
something else altogether?
The immediately previous line successfully performs an EJBHome lookup
using the
same Initial Context object. The main difference is that the EJBHome
name is defined
thru the EJB deployment descriptors, not the web.xml.
Thanks,
Steve

Validation error when using env-entry in web.xml

I've added an env-entry element to my web.xml and it falls over at deploy time with a validation error. However, from what I can see, this is valid based on the schema.
And infact, it matches the example in the weblogic doco - http://edocs.bea.com/wls/docs103/webapp/web_xml.html#wp1025195
The error I'm getting is:
<17/12/2008 11:45:56 AM EST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor D:\workspace\source_checkout\investment_control\ic-web\src\main\webapp/WEB-INF/web.xml of module ic-web.war. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4a: Expected elements 'mapped-name@http://java.sun.com/xml/ns/javaee injection-target@http://java.sun.com/xml/ns/javaee' instead of 'env-entry-type@http://java.sun.com/xml/ns/javaee' here in element env-entry@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
My web.xml looks like:
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" 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_2_5.xsd"
     version="2.5">
     <description>IC Web</description>
     <env-entry>
          <env-entry-name>aEntry</env-entry-name>
          <env-entry-value>aValue</env-entry-value>
          <env-entry-type>java.lang.String</env-entry-type>
     </env-entry>
</web-app>
Any suggestions???

Found a resolution to this in the end.
Unless you have the sub-elements in the order below, it will get validation errors.
<env-entry>
<env-entry-name>maxAmount</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>aString</env-entry-value>
</env-entry>
A bit weird and very frustrating....

Env-entry in web.xml and 6.0 sp4

Does anyone know if iws 6.0 sp4 supports env-entry elements in web.xml???
According to servlet specs 2.2 it should support it since it has JSP support.
From 2.3 specs:
"The following addtional elements exist in the web application deployment
descriptor to meet the requirements of web containers that are JSP enabled or part
of a J2EE application server. They are not required to be supported by containers
wishing to support only the servlet specification.:
� taglib
� syntax for looking up JNDI objects (env-entry, ejb-ref, ejb-local-ref, resourceref,
resource-env-ref)
See the DTD comments for further description of these elements."

Additional info...actually the code throws a NamingException.

Move env-entry from web.xml into deployment plan

I have:
<env-entry>
<env-entry-name>USERNAME</env-entry-name>
<env-entry-value>someUser</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
and I'd like to move it from web.xml into my_app_plan.dat. Is it possible? How?
Thank you in advance!

Let me describe my case in few more words...
I have some kind of client-server app. Clients have OC4J installed and they download myApp.ear and myApp_plan.dat files and by using script (Windows CMD batch file) clients install those files with admin_client.jar, OC4J's admin utility. The problem is that I have 2 different types of clients and I have client specific settings set in web.xml file and each time I compile myApp.ear I have to uncomment/comment some lines in web.xml.
So, to make a long story short, I need a way to deploy those settings separated from (outside of) myApp.ear. By following you link, I have read that orion-web.xml should reside inside WEB-INF folder of myApp.ear, which is not good for me.

Env-entry from web.xml not in generated plan.xml

Hello,
Recently I migrated a JDeveloper 10.1.3.4 project to 11.1.1.3 and from there to 11.1.2.4. When I deploy this project to an 10.3.5. weblogic server then the 'env-entry' entires in the web.xml are not available on the application server.
Even when i use weblogic.PlanGenerator with the -all option to create a plan.xml from the WAR-file the env-enties are not found.
The web.xml is like this:
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
id="WebApp_ID" version="2.5">
<listener>
<listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
</listener>
<servlet>
<servlet-name>jaxrpc</servlet-name>
<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>VersionServlet</servlet-name>
<servlet-class>nl.deltalloyd.alfa.keten.version.VersionServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>VersionServlet</servlet-name>
<url-pattern>/version</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>jaxrpc</servlet-name>
<url-pattern>/RelatieSoapHttpPort</url-pattern>
</servlet-mapping>
<jsp-config/>
<security-role>
<role-name>Administrators</role-name>
</security-role>
<resource-ref>
<res-ref-name>jdbc/AlfaDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<env-entry>
<env-entry-name>appl/version</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>2013.06</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/releasedate</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>13-06-2013</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/loglevel</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>INFO</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/omgeving</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>service/case</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>http://test.services.intranet.company.nl/GixoCaseWeb/services/CaseServiceHttp</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>mqueue/rc/host</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>nl001wwavm058.ad.intra</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>mqueue/rc/port</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>1414</env-entry-value>
</env-entry>
</web-app>
Maybe I missed something in the migration path. Can someone please help me.
With kind regard,
Martin

Let me describe my case in few more words...
I have some kind of client-server app. Clients have OC4J installed and they download myApp.ear and myApp_plan.dat files and by using script (Windows CMD batch file) clients install those files with admin_client.jar, OC4J's admin utility. The problem is that I have 2 different types of clients and I have client specific settings set in web.xml file and each time I compile myApp.ear I have to uncomment/comment some lines in web.xml.
So, to make a long story short, I need a way to deploy those settings separated from (outside of) myApp.ear. By following you link, I have read that orion-web.xml should reside inside WEB-INF folder of myApp.ear, which is not good for me.

Calling servlet with out entry in web.xml

Hi
I want to know whether can a servlet be invoked with out having an entry in web.xml.Because to my knowledge when ever an entry is made in teh web.xml the <url-pattern> and the class file will be stored as key value combination it is only then when ever a request is made the server gets the class taht is to be invoked from the <url-pattern> that is passed from the client side.
Is ther any way by whihc we can call the servlet directly with out an entry in web.xml
Thanks in advance
Ajithkumar.S

Interesting that it is possible on Tomcat anyway.
What's the real benefit of not having a Servlet
definied in web.xml?
The only benefit I see is that
you don't need to understand/read/change XML when
adding or removing a servlet. That isn't worth that
imho. What are the other benefits?The only thing I can think of is , to be able to quickly access a Servlet that you've just written, because it takes additional steps to define it in the web.xml.
I think it would be a security concern (of some sort) , if the Servlet's class is known, that's why it is better to access a Servlet with a mapping from web.xml

Adding servlet entry in web.xml of j2ee engine

Hi ,
I want a servlet to be loaded on startup of the j2ee engine SAP WAS which is basically flex based (MessageBrokerServlet).
The init param for the servlet is not accessible or cannot be initialized in init method of the servlet using the servletconfig object.
This is when the servlet is used as a portal component of type servlet.
So as to load the servlet and the servlet being able to access the init param i would be changing the web.xml of the sap j2ee engine (NW CE 7.1). are there any other effects of the same or is it fine if i just add this param in the web.xml
    <servlet>
        <servlet-name>MessageBrokerServlet</servlet-name>
        <display-name>MessageBrokerServlet</display-name>
        <servlet-class>flex.messaging.MessageBrokerServlet</servlet-class>
        <init-param>
            <param-name>services.configuration.file</param-name>
            <param-value>/WEB-INF/flex/services-config.xml</param-value>
       </init-param>
        <load-on-startup>1</load-on-startup>
    </servlet>

Hi ,
Vivek in case my servlet is part of the Portal Application as PortalComponent how do i define init parameters that can be accessed in the servlet.
The config file would be accessed in the init method of the servlet how do i do that when the servlet is added as PortalComponent in PortalApplication. The servlet config file needs to accessed in t he init method.
The load on startup thing would be taken care of by setting parameter startup = true of application properties.
Regards
Srikumar V

Env-entry problem in Pluto portal

I have portlet project. I wrote in web.xml:
<env-entry>
<env-entry-name>time_interval</env-entry-name>
<env-entry-value>5</env-entry-value>
<env-entry-type>java.lang.Long</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>file_path</env-entry-name>
<env-entry-value>d:\tmp</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
I get following error during deploying portlet:
12:21:30,588 INFO [Engine]
StandardContext[pluto]PortletDefinitionRegistryService initializing...
12:21:32,561 ERROR [Engine] StandardContext[pluto]ServiceManager: An
unidentified error occurred
ValidationException: element "env-entry" occurs more than once.
(XMLFieldDesciptor: envEntry AS env-entry)
at
org.exolab.castor.xml.UnmarshalHandler.endElement(UnmarshalHandler.java:
730)
But when I put only one env-entry in web.xml, it works perfectly.
Does any solution exist for adding more than one env-entry?

I have portlet project. I wrote in web.xml:
<env-entry>
<env-entry-name>time_interval</env-entry-name>
<env-entry-value>5</env-entry-value>
<env-entry-type>java.lang.Long</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>file_path</env-entry-name>
<env-entry-value>d:\tmp</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
I get following error during deploying portlet:
12:21:30,588 INFO [Engine]
StandardContext[pluto]PortletDefinitionRegistryService initializing...
12:21:32,561 ERROR [Engine] StandardContext[pluto]ServiceManager: An
unidentified error occurred
ValidationException: element "env-entry" occurs more than once.
(XMLFieldDesciptor: envEntry AS env-entry)
at
org.exolab.castor.xml.UnmarshalHandler.endElement(UnmarshalHandler.java:
730)
But when I put only one env-entry in web.xml, it works perfectly.
Does any solution exist for adding more than one env-entry?

env-entry element in ejb-jar.xml

I just started to create my ejb-jar.xml (deployment descriptor file) manually so
that I won't depend on those generated by proprietary IDEs.
The ejb-jar_2_0.dtd specifies that env-entry is used in
entity, message-driven, and session elements.
My question is - When do we use the element <env-entry>? Under what
circumstances that ejb-jar_2_0.dtd necessitates its provision in the ejb-jar.xml
in relation to entity, message-driven, and session elements?

Hi,
I've same prob here
<env-entry>
<env-entry-name>config.file.location</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>C:/bea/ITReportingConf.xml</env-entry-value>
</env-entry>
Right now config file is out side of my EAR, How can i put it within the EAR I tried with changing the
<env-entry-value>/ITReportingConf.xml</env-entry-value> Value
But i dont know which dir it is refering to and where should i put "ITReportingConf.xml" File
Thanks

Problem in Web.xml.........

Hi to All,
I installed the eval version of Crystal Reporst XI, created an example report with it and now I want to call my report from JSF Page.i followed the crxi_startup_guide_for_j2ee.i got the error in 'web.xml' file.the error is:
"cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry-value'. One of '{"http://java.sun.com/xml/ns/j2ee":env-entry-type}' is expected"
here i shows my entry in web.xml file:
<env-entry>
<env-entry-name>jdbc/mydatabase name</env-entry-name>
<env-entry-value>!com.microsoft.jdbc.sqlserver.SQLServerDriver!jdbc:odbc:mydatabase name</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
im unable to get what was the problem.my environment is Tomcat 5.0.28,SQL2000.
i created that report using ODBC connection.is it correct?suppose if i have to connect using JNDI means how to achive this?
can any one get me out of this please!!
Thanks in Advance,
--RK

This is my web.xml file........
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<env-entry>
<env-entry-name>jdbc/IMDB</env-entry-name>
<env-entry-value>!com.microsoft.jdbc.sqlserver.SQLServerDriver!jdbc:odbc:IMDB</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<context-param>
<param-name>com.sun.faces.verifyObjects</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<param-name>com.sun.faces.validateXml</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
<context-param>
<param-name>crystal_image_uri</param-name>
<param-value>crystalreportviewers11</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>
index.jsp
</welcome-file>
</welcome-file-list>
</web-app>
Thnx,
Rk

Env-entry?

How do you 'configure' a Workshop application?
The normal way to do this in J2EE is to add environment entries in web.xml,
ejb-jar.xml or even application.xml.
In Workshop there is only web.xml. And when deploying as an EAR file, it
gets packaged in a WAR file, not inside the JAR file of the Web Service. So
you can't just look up a web.xml environment entry from your jws file.
=======
Another question: why is web.xml and weblogic.xml available in Workshop in
the first place? What can you do with these files? I don't see how they can
be useful to the developers.
Since all the 'plumbing' of Web Services is hidden inside Workshop anyway, I
think they should remain hidden too. Or if they are useful, then I think we
should be able to see the other deployment descriptors (the WebServices's
(ejb-jar.xml) and the EAR's (application.xml)).
Even better, how about some new categories under the project's properties,
called 'descriptors'. Hide all that XML and show it graphically. Don't allow
modifying what is the guts of the system, it's error-prone.
Thanks,
Emmanuel Proulx

Thanks for the details, Emmanuel. I'm sure that our Product Management team
will be interested in your feedback.
Ian M. Goldstein
Developer Relations Engineer
BEA Systems, Inc.
"Emmanuel Proulx" <[email protected]> wrote in message
news:[email protected]...
Ian, group,
Unfortunately, I'm going to answer your first question with a question
(since we're in Beta, let's think of this as an opportunity for us tolearn
from each other): What kinds of "configuration" do you want to do to
your
Workshop application? What types of environment entries are youinterested
in adding to the deployment descriptors?J2EE defines the environment entries as a way to set up an application
without modifying the code. You just look up the environment entry and you
get a value that you can use in the code. This modifies the behavior ofyour
code without having to change it. It's like an OS environment variable.
Examples:
- Debug Flag
- Currency Symbol
- Location of temp folder
- Location of a resource (although ther are resource references for that,a
special kind of environment entry), like JDBC datasource, JMS conn.factory,
EJB reference (using ejb-refs), etc.
You can change any of those in the XML file and you don't have torecompile.
This is very very useful, in particular when switching an application froma
development to a production box. The debug flag should be turned off, the
temp folder is different, the datasource should point to the production
database, etc.
Currently if you want to configure a Workshop application in this way, you
have to modify the project and recompile. This can introduce problems when
deploying to the production server.
I suggest we add a new category in the project properties (right pane)like
this:
+ target-namespace
+ schema
- configuration
- environment
debugFlag java.lang.Boolean true
currency java.lang.Char $
temp String c:/temp
- resource references
databaseDS javax.sql.DataSource Container DS-JNDI-Name
Shareable
- EJB references
EJB1 Session EJB-JNDI-Name EJBHome EJBRemote EJBName
(ejb-link)
- EJB local references
EJB1 Session Local-EJB-JNDI-Name EJBLocalHome EJBLocal
EJBName (ejb-link)
These should be saved in application.xml at the time of deployment. The
references should be available as a choice in the various controls. E.g.for
the database control, any Datasource reference should appear in thecreation
dialog and properties.
NOTE: The above comes from what I saw in Weblogic Builder. But somethingis
missing from WebLogic Builder: either <resource-ref> or <resource-env-ref>
is not listed.
More 0.02$.
Talk to you soon,
Emmanuel
As for your second question, I agree that exposing the web.xml and
weblogic.xml in the project tree does in fact suggest that developers
may
want to edit them. I'll bring that feedback to our development team.Thanks!
Your suggestion about providing a graphical editor for modifyingdeployment
descriptors is something that the WebLogic Server development team feels
pretty strongly about, too -- check out WebLogic Builder
(http://e-docs.bea.com/wls/docs70/wlbuilder/WebLogicBuilder.html),
included
in the WebLogic Platform 7.0 beta. Of course, you don't need to go thatdeep
into application deployment descriptors to build and deploy your
applications with WebLogic Workshop. (In fact, you don't even need to
know
what a deployment descriptor is to successfully deploy web services you
develop with WebLogic Workshop.)
Cheers!
Ian M. Goldstein
Developer Relations Engineer
BEA Systems, Inc.
"Emmanuel Proulx" <[email protected]> wrote in message
news:[email protected]...
How do you 'configure' a Workshop application?
The normal way to do this in J2EE is to add environment entries inweb.xml,
ejb-jar.xml or even application.xml.
In Workshop there is only web.xml. And when deploying as an EAR file,
it
gets packaged in a WAR file, not inside the JAR file of the WebService.
So
you can't just look up a web.xml environment entry from your jws file.
=======
Another question: why is web.xml and weblogic.xml available in
Workshop
in
the first place? What can you do with these files? I don't see how
they
can
be useful to the developers.
Since all the 'plumbing' of Web Services is hidden inside Workshop
anyway,
I
think they should remain hidden too. Or if they are useful, then I
think
we
should be able to see the other deployment descriptors (the
WebServices's
(ejb-jar.xml) and the EAR's (application.xml)).
Even better, how about some new categories under the project'sproperties,
called 'descriptors'. Hide all that XML and show it graphically. Don'tallow
modifying what is the guts of the system, it's error-prone.
Thanks,
Emmanuel Proulx

Unmarshaller failed for web.xml - weblogic 8.1 to weblogic 9.2

Hi ,
I am also getting the same Unmarshaller Failed Exception as given below.
Unable to load descriptor myapplication\app.ear\app.war/WEB-INF/web.xml of module app.war . The error is weblogic.descriptor.DescriptorException: Unmarshaller failed.....
Please let me know
Thanks in advance
I verified that there is no duplicate entry in web.xml
Binu
I am atatching the error log
<Aug 8, 2006 12:55:47 PM IST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor \app.ear\app.w
ar/WEB-INF/web.xml of module app.war. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:147)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.jav
a:749)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:376)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.j
ava:720)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:729)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134)
at weblogic.application.compiler.WARModule.processLibraries(WARModule.java:286)
at weblogic.application.compiler.WARModule.merge(WARModule.java:303)
at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:41)
at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:94)
at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:47)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
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:130)
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:142)
at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:70)
at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:51)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObj
ectFactoryImpl.java:177)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDeployabl
eObjectFactoryImpl.java:150)
at weblogic.deploy.api.tools.SessionHelper.inspect(SessionHelper.java:629)
at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:450)
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:585)
at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:869)
at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808)
at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477)
at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:305)
at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:335)
at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continu
eChain(ActionInterceptors.java:63)
at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:167)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(
ActionInterceptors.java:49)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continu
eChain(ActionInterceptors.java:57)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java
:86)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114)
at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:
221)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:241)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:130)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1169)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:688)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.j
ava:144)
at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:107)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:99)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:180)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:168)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:222)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:178)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:351)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:128)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:339)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:330)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:162)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:370)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:229)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:183)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:221)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:124)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3212)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: com.bea.xml.XmlException: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descr
iptor.ServletBeanImpl@bb49014(/Servlets[navigationTree])"
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:483)
at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBind
ingType.java:385)
at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingTy
pe.java:145)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:185)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:154)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:136)
... 123 more
Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.ServletBeanImpl@bb49
014(/Servlets[navigationTree])"
at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:207)
at weblogic.j2ee.descriptor.WebAppBeanImpl.setServlets(WebAppBeanImpl.java:1096)
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:585)
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
... 131 more
.>
Thanks
Binu

Thanks Rob for youir response.
I had actually duplicate url pattern entry in web.xml.
Now I am facing an issue with security principal.
I am getting anoynymous principal for the sessionContext.getCallerPrincipal() .
I am using the same security module which used to work with weblogic 8.1 (I have generated respctive jar file with 9.2 jar though and I could configure a new provider)
Any thoughts on this?
Thanks
Binu

Handling 404 error through web.xml

In my application i made the following entry in web.xml:
<error-page>
    <error-code>404</error-code>
    <location>/error.jspx</location>
</error-page>
error.jspx is a jspx file and exist in the public_html folder and has following entry:
<f:view>
    <af:document id="d1">
      <af:form id="f1">
      <af:outputText value="Hello There error occured" id="ot_11" />
      </af:form>
    </af:document>
</f:view>
when a 404 occurs in the application, i am getting following application in the log:
<[ServletContext@3806419[app:j2ee-app module:retailer path:/retailer spec-version:2.5]] error-page location: "/error.jspx" for the error-code: "404" does not exist. Serving the default error page.>
Any suggestion what to do next?

on more thing,
404 errors are handled by web.xml using following:
<error-page>
   <error-code>404</error-code>
   <location>/login/404errorPage404.html</location>
</error-page>
but in case of 500 errors or nullpointers i treid a no of options, but neither one worked:
<error-page>
<error-code>500</error-code>
   <location>/login/500errorPage500.html</location>
</error-page>
<error-page>
   <exception-type>javax.el.ELException</exception-type>
   <location>/login/500errorPage500.html</location>
</error-page>
<error-page>
   <exception-type>java.lang.Exception</exception-type>
   <location>/login/500errorPage500.html</location>
</error-page>
<error-page>
   <exception-type>java.lang.Throwable</exception-type>
   <location>/login/500errorPage500.html</location>
</error-page>
Any advise?

Taglib tag doesn't work with web.xml 2.4 ?

That is, I switched to the 2.4 version of web.xml and now none of the taglib elements I have in there work.
I get the following excpetion
org.apache.jasper.JasperException: File "/tags/struts-html" not found
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.jav a:105)
I've been surfing a good portion of the day looking for some documentation on this but to no avail. I did find that I should wrap the taglib elements in a jsp-info. I'm runing tomcat 5.0.19.
In any event here is my web.xml:
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee web-app_2_4.xsd"
version="2.4">
<display-name>Struts Examples Application</display-name>

<servlet>
<servlet-name>InitServlet</servlet-name>
<servlet-class>com.jacent.admin.servlet.init.InitServlet</servlet-clas s>
<init-param>
<param-name>log4j</param-name>
<param-value>/WEB-INF/log4j.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class&g t;
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>

<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>

<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>

<jsp-config>
<taglib>
<taglib-uri>/tags/struts-bean</taglib-uri>
<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-html</taglib-uri>
<taglib-location>/WEB-INF/struts-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-logic</taglib-uri>
<taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-nested</taglib-uri>
<taglib-location>/WEB-INF/struts-nested.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-tiles</taglib-uri>
<taglib-location>/WEB-INF/struts-tiles.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/datetime</taglib-uri>
<taglib-location>/WEB-INF/datetime.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/tabs-taglib</taglib-uri>
<taglib-location>/WEB-INF/tabs-taglib.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/admin-widgets</taglib-uri>
<taglib-location>/WEB-INF/admin-widgets.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>http://java.sun.com/jsp/jstl/core</taglib-uri>
<taglib-location>http://java.sun.com/jsp/jstl/core</taglib-location> ;
</taglib>
</jsp-config>
</web-app>
In addition Eclipse is complaining about web-app element not able to be found.
Thanks for anyone's help!
John

#1 programmers excuse: It works for me. You must be doing something wrong.
Finding out what is the trick.
I have Tomcat 5.0.28, but I don't think it would make THAT much difference.
What version of Java are you running?
You shouldn't need the entry for the JSTL library c. That works without an entry in web.xml, provided you use the correct URI.
First step: make a test page that only uses that one taglib - eg an html:base tag.
Confirm that it breaks with the current setup.
Backup web.xml, and start it from scratch with an absolute minimal one - only import the struts-html library.
Does that work?
Slowly copy and paste in the different bits of web.xml until you find what breaks it.
Hope this helps,
evnafets

Updated env-entries in web.xml

Similar Messages

Maybe you are looking for