env-entry-mapping element is removed during deployment process

I overwrite the variable value defined in ejb-jar.xml by the one defined in orion-ejb-jar.xml using <env-entry-mapping> element. But after my appliocation has deployed I don't find this element in the application orion-ejb-jar.xml. Oracle AS just removes this element from the descriptor!
ejb-jar.xml:
<env-entry>
<env-entry-name>server</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>172.38.48.12</env-entry-value>
</env-entry>
orion-ejb-jar.xml:
<session-deployment name="Inventory" max-instances="-1" location="Inventory">
<env-entry-mapping name="server">dummy</env-entry-mapping>
</session-deployment>
Can anybode help?

Avi!
Of course, I had tried it before I wrote the question. I put the modified xml file into the application area. After that AS restarts OC4J instance. And then I find my xml without any changes I made! I tried to do the same thing from the AS console. The same!
Leonid

Similar Messages

Env-entry-mapping in orion-application-client not available in JNDI lookup

I have an application client module in my EAR file that I've configured to auto-start.
It has a few env-entry defined in it's application-client.xml.
When I deploy the EAR file to OC4J 10.1.3, the application client module gets started and can access these env-entry properties from its JNDIContext.
Now, comes the problem. During the deployment process, I edit the Deployment Plan, and change the env-entry property values, and then deploy the application.
However, the application client module still gets the original values when it does the JNDI lookups of those env-entry names.
I have checked to see that OC4J creates an orion-application-client.xml during deployment and it shows the env-entry-mapping elements with the updated values.
Why is the JNDI lookup returning the values from application-client.xml and not the overriden values set in orion-application-client.xml?
I have tried this on OC4J 10.1.3, as well as 10.1.3.1.0 - got same behavior.
Is this a bug in OC4J? This seems to work fine with ejb modules, but not application client modules.
Thanks,
Kalpak

Avi!
Of course, I had tried it before I wrote the question. I put the modified xml file into the application area. After that AS restarts OC4J instance. And then I find my xml without any changes I made! I tried to do the same thing from the AS console. The same!
Leonid

Trailing spaces in env-entry-type elements

Hi,
We have been porting our EJB application from another app server over to Oracle iAS (9.0.3 Lite) and have encountered a rather frustrating problem.
We have an CMP (2.x) entity bean that has ejbSelect methods. There are corresponding <query> blocks in the ejb-jar.xml file for these methods. In the same ejb-jar.xml file there are <env-entry> blocks that setup a few things that are needed by the bean.
If the <env-entry-type> element is written as "<env-entry-type>java.lang.String </env-entry-type>" (note the trailing space after the type name) the following exception occurs during deployment of the ear file;
java.lang.InstantiationException: Failure to initialize EJBQL descriptors: com.sun.enterprise.deployment.xml.ContentTransformationException: java.lang.String is not an allowed property value type
     at com.evermind.server.ejb.deployment.EJBPackage.initializeEjbqlDescriptors(EJBPackage.java:2075)
     at com.evermind.server.ejb.deployment.EJBPackage.init(EJBPackage.java:2054)
     at com.evermind.server.ServerComponent.init(ServerComponent.java:208)
     at com.evermind.server.ejb.EJBPackageDeployment.getPackage(EJBPackageDeployment.java:672)
     at com.evermind.server.administration.ServerApplicationInstallation.finish(ServerApplicationInstallation.java:547)
     at com.evermind.server.administration.ServerApplicationInstallation.deploy(ServerApplicationInstallation.java:913)
     at com.evermind.server.administration.DefaultApplicationServerAdministrator.deploy(DefaultApplicationServerAdministrator.java:337)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:119)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:479)
Error during deployment: Failure to initialize EJBQL descriptors: com.sun.enterprise.deployment.xml.ContentTransformationException: java.lang.String is not an allowed property value type
Removing the trailing space and the deployment proceeds to completion without exceptions.
I should also add that if the ejbSelect methods are remove d from the application and the trailing space left in place the resulting ear file will deploy sucessfully.
It is trivial to reproduce this problem with the ORMAP demo that ships with 9.0.3.
This was a really subtle problem that is not present on the *3* other appserver implementations that our application runs on. It was very frustrating to locate and perhaps some consideration could be given to how PCDATA is handled when parsing <env-entry-type> blocks.
Cheers,
Mick.

Hi ,
Create two Characteristic InfoObjects in BW With length 60 Char and then in the Transfer Rules of this two InfoObjects write the Formula using Left() and right() function present in the Formula Builder .
That is First infoObject Contains the Left 60 Char and next one Contains the right 60 Char.
Regards,
Vijay.

Env-entry-mapping suppressed

Hi,
Did anyone try <env-entry-mapping> in orion-ejb-jar.xml? It seems that it is suppressed during deployment. The orion-ejb-jar.xml being generated into -deploymentDirectory place (specified or default) simply drops these mappings. The effect is that whatever had been specified in ejb-jar.xml prevails, with obvious, bad consequences.
Besides, I think I read somewhere that Deployer-supplied orion-ejb-jar.xml would only be augmented with missing specifications. This to me implies that nothing should be removed from it. Perhaps, then, THIS IS A BUG.
ORION TEAM: I'm running 9.0.3.0.0/NT. I'd appreciate your help and 'know-how', especially if you could offer something better than manually editing orion-ejb-jar.xml in -deploymentDirectory AFTER EACH SUCH TIME THE APPLICATION IS DEPLOYED!

Avi!
Of course, I had tried it before I wrote the question. I put the modified xml file into the application area. After that AS restarts OC4J instance. And then I find my xml without any changes I made! I tried to do the same thing from the AS console. The same!
Leonid

env-entry-mapping

hi,
i am using oracle application server 10g,
when i am trying to override the values of more than one enviroment enteries in enterprise manager web module enviroment page /enviroment entries
the following error appear:
Commit Failed - Entity et="system";ei="0",et="application";ei="18",et="WebModule";ei="30",et="orion-web-app";ei="31",et="env-entry-mapping";ei="41"
cannot have the same key values with its sibling entity et="system";ei="0",et="application";ei="18",et="WebModule";ei="30",et="orion-web-app";ei="31",et="env-entry-mapping";ei="42".
Resolution: Check key values for the sibling entities.
any ideas?

Avi!
Of course, I had tried it before I wrote the question. I put the modified xml file into the application area. After that AS restarts OC4J instance. And then I find my xml without any changes I made! I tried to do the same thing from the AS console. The same!
Leonid

Photoshop 7 Element keep stopping during output process why?

Photoshop element 7 keep stopping while in output phase, it get up to 70% then it stop. The slideshow about 39min-40 sec, the file size is 4752x 3168 pixels for each pictures, I removed all other software that deals with dvd making and it still stops, What do I do now ?

try to remove all devices connected to a USB port on your computer besides keyboard and mouse.
- try to create a new admin account and work from there.
hope this helps!
-mike cutie

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?

Issue with [env-entry] element in web.xml

I know it's possible to define [env-entry] elements in web.xml for environment
properties of a web application. But how do you access [env-entry] elements from
classes that do not exist within a web application? In other words, this is my
problem:
I have an EAR file, enterprise.ear, which contains the following...
employee.jar
employeeSearchEJB.jar
webApp1.war
META-INF/
application.xml
The employee.jar file is a utility archive that contains common classes, one of
which is a class called LogManager. LogManager needs to read environment properties
in order to initialize itself. Currently, LogManager reads these properties from
a property file, and therefore it needs to know the name of the property file
in order to access it. I dont like this approach because I'm forced to hard-code
the name of the property file in LogManager. I would rather leverage the power
of J2EE deployment descriptors and use the [env-entry] element to define the environment
properties for the LogManager class. Then, I would simply use JNDI to get the
values of the [env-entry] elements without ever having to specify their location
aside from the default JNDI context; java:comp/env, which is standard anyway.
The problem I'm having is that you can define the [env-entry] element in only
2 types of deployment descriptors; namely, web.xml and ejb-jar.xml, neither of
which are available to LogManager because LogManager exists at the EAR root level.
I was hoping application.xml supported the [env-entry] element, but it doesn't.
Any suggestions?
SAF

SAF,
I am not sure if this applies to you situation but if you create an initial context
instance and then grab the value using the jndi name within that context then
you should be able to grab that environment variable.
I have a helper class that is used as part of a deployed application. The helper
class doesn't have access to the Servlet context but it is created as part of
the application workflow. When it gets initiated it grabs an env-entry created
in the web.xml deployment descriptor to find the default url for a content path.
After I create an initialContext, I perform a initContext.lookup("jndi.env.entry.here")
where "jndi.env.entry.here" is the name specified in the env-entry tag.
This returns the value of the entry.
This works under both Jrun and Weblogic so my guess is it should work for you.
Again, I am assuming that your class will at least be able to grab a context
object to communicate back to the server.
Hope this helps,
Troy
"SAF" <[email protected]> wrote:
>
I know it's possible to define [env-entry] elements in web.xml for environment
properties of a web application. But how do you access [env-entry] elements
from
classes that do not exist within a web application? In other words, this
is my
problem:
I have an EAR file, enterprise.ear, which contains the following...
employee.jar
employeeSearchEJB.jar
webApp1.war
META-INF/
application.xml
The employee.jar file is a utility archive that contains common classes,
one of
which is a class called LogManager. LogManager needs to read environment
properties
in order to initialize itself. Currently, LogManager reads these properties
from
a property file, and therefore it needs to know the name of the property
file
in order to access it. I dont like this approach because I'm forced to
hard-code
the name of the property file in LogManager. I would rather leverage
the power
of J2EE deployment descriptors and use the [env-entry] element to define
the environment
properties for the LogManager class. Then, I would simply use JNDI to
get the
values of the [env-entry] elements without ever having to specify their
location
aside from the default JNDI context; java:comp/env, which is standard
anyway.
The problem I'm having is that you can define the [env-entry] element
in only
2 types of deployment descriptors; namely, web.xml and ejb-jar.xml, neither
of
which are available to LogManager because LogManager exists at the EAR
root level.
I was hoping application.xml supported the [env-entry] element, but it
doesn't.
Any suggestions?
SAF

Orion-web.xml and resource-env-ref-mapping correct usage

What happened to resource-env-ref-mapping element in orion-web.xml? I have a 9.0.4.1 server running several .EAR files containing web applications using this attribute to configure JMS related items. But when deploying the .EAR to newer versions (9.0.5.2) of the server this attribute doesn't appear to be valid any longer?
Here it is in the 9.0.4 documentation:
http://strogoff.unex.es/oradoc/form_y_report_10g/web.904/b10322/apdx_a.htm
Any help would be appreciated?

I should have been more clear about the issue. The error only occurs when running inside the embedded OC4J container of JDeveloper 10.1.2 build 1913. The error does NOT occur in JDeveloper 9.0.3. The application also runs fine when deployed to a 10.1.2 Enterprise application server. The error only occurs in JDeveloper.
The following error occurs when validating my orion-web.xml file. The entry is:
orion-web.xml:
<orion-web-app>
<resource-ref-mapping name="jms/mQueueConnectionFactory" location="jms/matchingQueueConnectionFactory"/>
<resource-env-ref-mapping name="jms/mQueue" location="jms/matchingQueue"/>
</orion-web-app>
web.xml
<resource-env-ref>
<resource-env-ref-name>jms/mQueue</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
java.lang.IllegalArgumentException: Unrecognized parent-elem combination: interface oracle.jdeveloper.xml.oc4j.war.OrionWebApp - resource-env-ref-mapping
     at oracle.javatools.xml.bind.XMLBinding.throwUnrecognizedElem(XMLBinding.java:127)
     at oracle.jdeveloper.xml.j2ee.war.WebAppBinding.elem2intImpl(WebAppBinding.java:637)
     at oracle.javatools.xml.bind.XMLBinding.elem2int(XMLBinding.java:104)
     at oracle.javatools.xml.bind.XMLBinding.insertBetween(XMLBinding.java:88)
     at oracle.javatools.xml.bind.BindingContext.insertNewElement(BindingContext.java:121)
     at oracle.javatools.xml.bind.BindingContext.insertElem(BindingContext.java:95)
     at oracle.javatools.xml.bind.BindingContext.setElement(BindingContext.java:71)
     at oracle.javatools.xml.bind.SetImpl.callSetterForUniqueElem(SetImpl.java:66)
     at oracle.javatools.xml.bind.SetImpl.callSetter(SetImpl.java:57)
     at oracle.javatools.xml.bind.SetImpl.invoke(SetImpl.java:26)
     at oracle.javatools.xml.bind.ElementProxy.invoke(ElementProxy.java:35)
     at $Proxy10.setWebApp(Unknown Source)
     at oracle.jdevimpl.runner.oc4j.Oc4jWorkspaceConfig.ensureLocalPageReposRootIsSet(Oc4jWorkspaceConfig.java:633)
     at oracle.jdevimpl.runner.oc4j.Oc4jWorkspaceConfig.transmogrifyConfigFiles(Oc4jWorkspaceConfig.java:269)
     at oracle.jdevimpl.runner.oc4j.Oc4jWorkspaceConfig.configureAll(Oc4jWorkspaceConfig.java:114)
     at oracle.jdevimpl.runner.oc4j.Oc4jStarter.preStart(Oc4jStarter.java:618)
     at oracle.jdevimpl.runner.oc4j.Oc4jStarter.start(Oc4jStarter.java:268)
     at oracle.ide.runner.RunProcess.startTarget(RunProcess.java:756)
     at oracle.jdeveloper.runner.JRunProcess.startTarget(JRunProcess.java:461)
     at oracle.ide.runner.RunProcess$2.run(RunProcess.java:699)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

Can't access env-entry s in init()

          Hi all,
          How can I access the <env-entry>'s I have in my deployment descriptor in my servlet's
          "init()" method? I'm not getting the values from there.
          Should I pass parameters to my "new InitialContext(...)" call? What params do
          I pass?
          Thanks,
          Boogie


Then it is probably a WebLogic bug.
          boogie <[email protected]> wrote:
          > yes, that's how my code looks like.
          > except when it's in "init()", i don't get any values back.
          > so now i have to put it in another method which gets called the first time my
          > servlet processes a response. as you might imagine, it isn't very elegant (it's
          > a hack, actually) and it sorta defeats the purpose of having an "init()" method.
          > Dimitri Rakitine <[email protected]> wrote:
          >>boogie <[email protected]> wrote:
          >>
          >>> Hi all,
          >>
          >>> How can I access the <env-entry>'s I have in my deployment descriptor
          >>in my servlet's
          >>> "init()" method? I'm not getting the values from there.
          >>> Should I pass parameters to my "new InitialContext(...)" call? What
          >>params do
          >>> I pass?
          >>
          >>None - everything is set up by the container. env-entries are in java:comp/env
          >>subcontext,
          >>for example, if you define env-entry named Foo, you can access is like
          >>this:
          >>
          >>Context ctx = new InitialContext();
          >>ctx.lookup("java:comp/env/Foo");
          >>
          >>> Thanks,
          >>> Boogie
          >>
          >>--
          >>Dimitri
          Dimitri

Changing env-entry after deployment

Hi,
I was wondering how I can change the value of an env-entry after deployment? Do I have to change the value in the ejb-jar.xml, redeploy the application, or is there a utility I can use?
thanks
Steve

Okay gentlemen, I dug around and couldn't find anything on this concept of defining an env-entry after deployment using Sun Java System Application Server 8.1 - so I just came up with my own hack. Thought I'd share it in case others have the same question and can't find the answer.
Just to restate the problem: In SJAS you can't seem to define an environment entry that you can just look up via JNDI (you can do this in Tomcat pretty easy though using the context.xml file and an env-entry like syntax) - the benefit of this being of course that you can easily define deployment-time variables which a system administrator can set based on his setup. There seems to be no way to do this is SJAS 8.1
As a workaround, you can create your own custom JNDI resource which will expose the properties that you set in the Admin Console as a simple java.util.Map that you can use from your app.
Here's the blow by blow:
2. Create a JNDIProperties object that implements java.util.Map but does NOT implement java.io.Serializable:
package helpers.jndi;
import java.util.Collection;
import java.util.Map;
import java.util.Set;
public final class JNDIProperties implements Map {
    private Map map;
    public JNDIProperties(Map aMap) { map = aMap; }
    public boolean containsKey(Object key) { return map.containsKey(key); }
    public void clear() { map.clear(); }
    public Object get(Object key) { return map.get(key); }
    public boolean containsValue(Object value) { return map.containsValue(value); }
    public Set entrySet() { return map.entrySet(); }
    public boolean isEmpty() { return map.isEmpty(); }
    public Set keySet() { return map.keySet(); }
    public Object put(Object key, Object value) { return map.put(key, value); }
    public void putAll(Map t) { map.putAll(t); }
    public Object remove(Object key) { return map.remove(key); }
    public int size() { return map.size(); }
    public Collection values() { return map.values(); }
}2. Create an object that implements javax.naming.spi.ObjectFactory and returns an instance of JNDIProperties containing the properties defined in the container:
package helpers.jndi;
import java.util.Enumeration;
import java.util.Hashtable;
import java.util.Map;
import javax.naming.Context;
import javax.naming.Name;
import javax.naming.RefAddr;
import javax.naming.Reference;
import javax.naming.spi.ObjectFactory;
public class PropertyFactory implements ObjectFactory {
    public Object getObjectInstance(Object obj, Name name, Context nameCtx, Hashtable environment) throws Exception {
        Map myMap = new Hashtable();
        Reference myReference = (Reference)obj;
        Enumeration myEnumeration = myReference.getAll();
        while (myEnumeration.hasMoreElements()) {
            RefAddr myRefAddr = (RefAddr)myEnumeration.nextElement();
            myMap.put(myRefAddr.getType(), myRefAddr.getContent());
        JNDIProperties myJNDIProperties = new JNDIProperties(myMap);
        return myJNDIProperties;
}3. Build this and copy the jar to $SJAS_HOME/domains/domain1/lib/ext/ (or other appropriate folder for your setup), then restart the app server to get to load the jar.
4. Go to the admin console and go to Resources -> JNDI -> Custom Resources -> New. Give it a sensible JNDI name (I'll use "testproperties" in this example), enter java.util.Map as the resource type and the name of your factory class for the "factory class" field, e.g. "helpers.jndi.PropertyFactory". Below that under "Additional Properties", add in each of the properties that you want to expose, for example enter a property named "testproperty1" with the value of "my test".
5. You can now get a java.util.Map that contains the properties that you set for your custom JNDI resource by doing something like the following (example in JSP):
<%
Context myContext = new InitialContext();
Context myEnvContext = (Context)myContext.lookup("java:comp/env");
Map myMap = (Map)myEnvContext.lookup("testproperties");
%>
<%=myMap.get("testproperty1")%>Output is:
my testNOTE: If this sounds convoluted - I agree, it is. If anyone's got a better idea, please post it; as I could not find another solution to this seemingly simple problem.

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

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.

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.

env-entry-mapping element is removed during deployment process

Similar Messages

Maybe you are looking for