Web Deployment Descriptor

Hi!
1.)How can I stop directory browsing in tomcat.
I am using jboss/tomcat
2.)Where can I find documentation on web.xml
3.)I want the request in the address bar to stay same
//localhost:8080/myapp all the time.
And every time the user does something I want the request to go to my request handler servlet. I used
<servlet-mapping>
<servlet-name>requesthandler</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
this makes all the requests to come to the servlet but how do i redirect the requests for images and other static contents back to the web server
Thanx for the any help in advance.

1) Check the security docs in Tomcat at:
http://localhost:8080/tomcat-docs/security-manager-howto.html when you tomcat server is running.
2) Check out the Servlet 2.3 Spec API at:
http://java.sun.com/products/servlet/download.html
All Web developers should read it even if it is 10 times larger than the 2.2 spec.
3) try: <url-pattern>/*</url-pattern>
as quoted:
SRV.11.2 Specification of Mappings
In the web application deployment descriptor, the following syntax is used to define
mappings:
� A string beginning with a �/� character and ending with a �/*� postfix is used
for path mapping.
� A string beginning with a �*.� prefix is used as an extension mapping.
� A string containing only the �/� character indicates the "default" servlet of the
application. In this case the servlet path is the request URI minus the context
path and the path info is null.
� All other strings are used for exact matches only.
Cheers,
Anthony

Similar Messages

  • Dynamic update of EJB/Web deployment descriptors

    In 8.1SP3, is there any provision to allow for dynamic update of EJB/Web deployment descriptors? I'm specifically looking at env var changes.
    I noticed that there are some mentions of the ability to dynamically update deployment descriptors, but it appears that the general facility has been deprecated, and they've incorporated all of the WebLogic-specific descriptor information directly into the console.
    When I dig through the JMX namespace and some of the MBean classes, I also see mentions of "deployment descriptor editors", but it's not clear how to utilize that.
    I'm aware of the fact that my application would have to be aware of possible dynamic updates to the descriptors, so I'd have to be able to implement some sort of listener for that.

    I have the same question but for a different purpose. I am part of a hosting group and we have app teams that have defined init-params in the web.xml that have to be changed as the app is promoted up through test environments and ultimately to production - only we need to be able to do this WITHOUT "cracking open" the archive.
    I was hoping to be able to script something to do the update after deployment.
    So any help at all would be appreciated. In the meantime will continue to poke around in the WLST and MBean docs.
    Thanks,
    Ed

  • Alternate deployment descriptor for an exploded war (web.xml/weblogic.xml)

    Hi.
    I believe this is a simple question: Am i able to deploy an exploded war directory using an alternate deployment descriptor (web.xml outside the directory structure of my application)? According to the docs, I can do it for an ear, but I'm not sure if it can be done for an war.
    http://download.oracle.com/docs/cd/E13222_01/wls/docs81b/deployment/concepts.html#1001945
    http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/Application.html#AltDescriptorPath
    Thanks in advance.
    Best regards,
    Daniel.

    Or should i use a deployment plan?
    http://download.oracle.com/docs/cd/E13222_01/wls/docs103/deployment/config.html#wp1057141

  • How to edit web.xml deployment descriptor from console in weblogic 8.1?

    In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
    console, but on weblogic 8.1 I can't find a way to do so.
    Is this function taken out? Why is it taken out? Do I have an alternative to edit
    it without unpacking and packing the EAR or WAR?
    Thanks in advance.
    Bill

    In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
    console, but on weblogic 8.1 I can't find a way to do so.
    Is this function taken out? Why is it taken out? Do I have an alternative to edit
    it without unpacking and packing the EAR or WAR?
    Thanks in advance.
    Bill

  • J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"

    Hi ,
    When I try to deploy using admin console i get the following error msg.
    J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"
    The war file has web.xml.
    Can some give me the reason for the above error.
    LOG content:
    weblogic.management.ApplicationException: [J2EE:160043]Missing deployment descriptor
    "WEB-INF/web.xml" at "C:\bea8\user_projects\domains\eConnect\applications\myEconnect.war"
         at weblogic.j2ee.J2EEApplicationContainerFactory.handleError(J2EEApplicationContainerFactory.java:729)
         at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:470)
         at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
         at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
         at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
         at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.runtime.DeployerRuntimeMBean_Stub.activate(DeployerRuntimeMBean_Stub.java:1064)
         at weblogic.management.console.actions.mbean.WebAppComponentDeployAction.prePerform(WebAppComponentDeployAction.java:141)
         at weblogic.management.console.actions.mbean.DoMBeanWizardAction.perform(DoMBeanWizardAction.java:215)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    You'll have to at least show me the out contents of that WAR file.
    -- Rob
    Sowjanya wrote:
    Suppose the directory structure of the appl is c:\myroot\webapp\...
    then we need to go to webapp and then build the war file.
    C:\myroot\webapp>jar -cvf abc.war *
    then copy the war file and paste it in applicaitons folder.
    "sowjanya" <[email protected]> wrote:
    Hi ,
    When I try to deploy using admin console i get the following error msg.
    J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"
    The war file has web.xml.
    Can some give me the reason for the above error.
    LOG content:
    weblogic.management.ApplicationException: [J2EE:160043]Missing deployment
    descriptor
    "WEB-INF/web.xml" at "C:\bea8\user_projects\domains\eConnect\applications\myEconnect.war"
         at weblogic.j2ee.J2EEApplicationContainerFactory.handleError(J2EEApplicationContainerFactory.java:729)
         at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:470)
         at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
         at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
         at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
         at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.runtime.DeployerRuntimeMBean_Stub.activate(DeployerRuntimeMBean_Stub.java:1064)
         at weblogic.management.console.actions.mbean.WebAppComponentDeployAction.prePerform(WebAppComponentDeployAction.java:141)
         at weblogic.management.console.actions.mbean.DoMBeanWizardAction.perform(DoMBeanWizardAction.java:215)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

  • Oracle9i Jdeveloper Web Services Deployment Descriptor

    hii,
    i have created a web service in oracle9i jdeveloper. It is running. But I need to define a handler for this web service to handle multiple attachments. But whenever i give the handler chain in web.xml, the handler is not invoked. Also it does not allow me to change the deployment descriptor file to webservices.xml. please let me know a solution.

    I believe this is a bug in JDev/OC4J 9.0.3 that is being further investigated right now. I have duplicated your problem in a simpler test case and folks are looking into it.
    Mike.

  • Error while deploying an application on weblogic 12c. An error occurred while reading the deployment descriptor. The error was: Error processing annotations

    Anyone please help me solve this error. I am trying to deploy an application on weblogic 12c  i am getting an error but the same application gets successfully deployed on weblogic 11g. The error is
    An error occurred during activation of changes, please see the log for details.
    Exception preparing module: EJBModule(gsCallbackAdapterLGTX-ejb.jar) An error occurred while reading the deployment descriptor. The error was: Error processing annotations: .
    [EJB:015001]Unable to link class com.aep.gridsmart.adapters.lgtx.buslogic.deliver.xform.AdapterTransfomerDeliverSession in Jar /appl/oracle/middleware/WLS/12.1.1.0/user_projects/domains/Gridsmart/servers/ManagedServer1/tmp/_WL_user/gsCallbackAdapterLGTX/34vz4d/gsCallbackAdapterLGTX-ejb.jar : java.lang.NoClassDefFoundError: com/aep/gridsmart/adapter/deliver/CommonAdapterDeliverBean

    Cotton please let me know what is the mistake i am
    doingThe following path does not exist.
    C:\Sun\AppServer7\domains\domain1\server1\
    applications\j2ee-modules\task_1\WEB-INF\web.xml

  • Challenges in deployment descriptors

    We currently have an EJB (called CD) that is contacted "remotely" by a web service
    (called CA) for some processing. The two (CD and CA) are deployed on different
    WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar) whereas
    CA is part of an EAR file and is deployed as an application. We ran into the necessity
    of making CD as part of EAR (much like CA). However, as part of the CA package,
    there is currently an initialization class (we're using a servlet) that saves
    some entries in JNDI for both CA and CD. We want to mimic the functionality of
    that class in CD when we create the ear for it.
    I just ran into some settings that could be made in the weblogic-application.xml
    deployment descriptor as follows:
    <startup-class>startup class name</startup-class>
    We're hoping this can help us mimic CA's init process. However, we need to pass
    that class some parameters upon load (which in the case of CA was done by using
    the <init-param> in its web.xml). We came across the following tag:
    <application-param>
         <param-name>someparam</param-name>
         </param-value>somevalue</param-value>
    </application-param
    However, we have the following questions:
    1. How do we make the startup class fetch those param values at load time? (for
    CA, the servlet was using the appPropLoc = getInitParameter("someparam") in its
    init method
    2. We needed to perform the remote lookup from CA to CD. Would enclosing CD in
    an EAR affect our ability to do so? If so, then how do we go about doing that?
    Thanks much,
    Sami

    Hi sami,
    Enclosing the EJB (CD) in an EAR file is not going to stop you from Remotely accessing
    it.
    As CD and CA are in different application package and moreover in different JVM,
    you have to package the interface classes as client jar with in CA for type casting.
    Joe
    "sami titi" <[email protected]> wrote:
    >
    We have resolved the first part of this problem by using a startup servlet
    much
    like we do in CA. However, we still face the issue of question number
    2 below.
    Please provide some feedback.
    Thanks,
    Samir
    "sami titi" <[email protected]> wrote:
    We currently have an EJB (called CD) that is contacted "remotely" by
    a web service
    (called CA) for some processing. The two (CD and CA) are deployed on
    different
    WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar)
    whereas
    CA is part of an EAR file and is deployed as an application. We raninto
    the necessity
    of making CD as part of EAR (much like CA). However, as part of the
    CA package,
    there is currently an initialization class (we're using a servlet) that
    saves
    some entries in JNDI for both CA and CD. We want to mimic the functionality
    of
    that class in CD when we create the ear for it.
    I just ran into some settings that could be made in the weblogic-application.xml
    deployment descriptor as follows:
    <startup-class>startup class name</startup-class>
    We're hoping this can help us mimic CA's init process. However, weneed
    to pass
    that class some parameters upon load (which in the case of CA was done
    by using
    the <init-param> in its web.xml). We came across the following tag:
    <application-param>
         <param-name>someparam</param-name>
         </param-value>somevalue</param-value>
    </application-param
    However, we have the following questions:
    1. How do we make the startup class fetch those param values at load
    time? (for
    CA, the servlet was using the appPropLoc = getInitParameter("someparam")
    in its
    init method
    2. We needed to perform the remote lookup from CA to CD. Would enclosing
    CD in
    an EAR affect our ability to do so? If so, then how do we go about doing
    that?
    Thanks much,
    Sami

  • Error in Sun XML schema for servlet2.4 deployment descriptor?

    Hi,
    I'm including the new XML schema for version 2.4 of the servlet standard in my web.xml deployment descriptor, using http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
    When I try to save the XML file, XMLSpy reports an error in the schema file itself: "Undefined schema component 'base' encountered - simpleContext can not have a base that is a complexType with complexContent"
    This error is on line 744, and is caused by the snippet:
    <xsd:simpleContent>
    <xsd:extension base="j2ee:nonEmptyStringType"/>
    </xsd:simpleContent>
    Can anyone explain why I'm getting a validation failure on this schema? Surely someone else must have experienced the same thing, but I can't track down any reference to it anywhere. Help!

    XMLSpy is known to be flawed. From my own experience of implementing
    validators and data-binding tools, and from my experience of working in the
    W3C Schema working group, I can tell you that there are countless cases
    where XMLSpy violates the schema specification.
    I checked the corresponding part of the schema, but it looks correct to me.
    So I suspect that this is another bug in XMLSpy.
    Try Xerces. That's probably the best in terms of conformance to the spec.

  • How to specify OAS instance in deployment descriptor

    Hi
    I've got OAS 10.1.3.1.0, where exist home, home1, home2... instances. In JDev I've developed web app. and deployment descriptor for it. How to specify correct instance in depl. descriptor?
    Thank you

    Sorry, it's still not clear. You have a deployment profile. Now:
    Are you right-clicking that profile and saying "deploy to <app server>?" If so, you define the instance when you created the app server connection.
    Otherwise, if you're using some other way of deploying (e.g., AS control), you explicitly navigate to the instance and deploy the app from there.
    John

  • WAR files (Tomcat) and deployment descriptor

    Hello,
    I am currently writing a small utility to package a web application for Jakarta Tomcat as a .war file.
    I have a functional version that imports the deployment descriptor web.xml, but I'd like to make it possible for the user to edit or create from scratch that file. I use the DOM API to make a logical model of my web.xml, but the parser won't accept the external dtd definition :
    <!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
    "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
    Here is my parser :
    private void parse(File in) {
    try {
    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
    factory.setNamespaceAware(true);
    factory.setValidating(true);
    DocumentBuilder builder = factory.newDocumentBuilder();
    document = builder.parse(in); (((*)))
    catch (...)
    }//parse
    ---------------------------------------------It seems I have no further controls on DocumentBuilder and DocumentBuilderFactory.
    The builder.parse call generates this exception :
    java.net.NoRouteToHostException: Operation timed out: no further information
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at org.apache.crimson.parser.Resolver.resolveEntity(Resolver.java:389)The problem seems to be located in DOM's DefaultHandler entity resolver, but I don't ee clearly what to do.
    Thanks for helping.

    Hi,
    I already tried every combination of settings with
    DocumentBuilderFactory.setNamespaceAware
    DocumentBuilderFactory.setValidating
    DocumentBuilderFactory.setCoalescing
    DocumentBuilderFactory.ExpandEntityReferencesI had the same result. Here is the exact dump :
    java.net.NoRouteToHostException: Operation timed out: no further information
            at java.net.PlainSocketImpl.socketConnect(Native Method)
            at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
            at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
            at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
            at java.net.Socket.<init>(Socket.java:273)
            at java.net.Socket.<init>(Socket.java:100)
            at sun.net.NetworkClient.doConnect(NetworkClient.java:50)
            at sun.net.www.http.HttpClient.openServer(HttpClient.java:331)
            at sun.net.www.http.HttpClient.openServer(HttpClient.java:517)
            at sun.net.www.http.HttpClient.<init>(HttpClient.java:267)
            at sun.net.www.http.HttpClient.<init>(HttpClient.java:277)
            at sun.net.www.http.HttpClient.New(HttpClient.java:289)
            at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
    .java:379)
            at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
    nection.java:472)
            at org.apache.crimson.parser.Resolver.resolveEntity(Resolver.java:389)
            at org.apache.crimson.parser.ExternalEntity.getInputSource(ExternalEntit
    y.java:88)
            at org.apache.crimson.parser.Parser2.pushReader(Parser2.java:2986)
            at org.apache.crimson.parser.Parser2.externalParameterEntity(Parser2.jav
    a:2721)
            at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1154)
            at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:488)
            at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
            at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
            at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl
    .java:179)
            at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:161)
            at DOMView.main(DOMView.java:96)This shows that the entity resolver tries to access the distant DTD, so I tried to implement myself the EntityResolver interface, but I didn't well understood
    what to do with that InputStream it has to return.

  • Custom deployment descriptor

    Hi there
    We are in the process of deploying our standard J2EE EAR file to
    WebLogic 9.2 MP2. The EAR file does not contain weblogic custom
    deployment descriptors (e.g.: weblogic.xml) but only standard DDs (e.g.:
    web.xml)
    I have some doubts about resources mapping and I'd like to get some help
    from experienced WL users.
    Basically our EAR file is composed of an EJB module and a WEB module.
    Each module declares some references such as:
    WEB.XML snippet
    <resource-ref>
    <description>DataSource for partition 'default'</description>
    <res-ref-name>jdbc/Datasource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    Now the questions:
    1) Is there a way to map the resources during the deployment, using the
    console? This is the way followed by WebSphere and Oracle AS, for
    example. If this is not possible, should I provide a Deployment Plan for
    that EAR file? I tried to provide the xml Deployment Plan generated by
    weblogic.PlanGenerator utility together with the EAR file while
    deploying the app, but no luck. It seems the Deployment Plan should be
    provided in a jar file. Is that correct?
    2) If the previous options are not possible, how can I create the custom
    deployment descriptor? Is there an "Assembly Tool" that imports the
    standard EAR and then export the custom EAR file with the custom
    deployment descriptors correctly generated?
    Thank you a lot in advance.

    A deployment plan is external to the ear/jar file.
    It is probably easiest to deploy the application with the console, and then
    use the console to change the values you want. It will automatically
    generate a deployment plan for you.
    "Quasar" <[email protected]> wrote in message
    news:[email protected]..
    Hi there
    We are in the process of deploying our standard J2EE EAR file to
    WebLogic 9.2 MP2. The EAR file does not contain weblogic custom
    deployment descriptors (e.g.: weblogic.xml) but only standard DDs (e.g.:
    web.xml)
    I have some doubts about resources mapping and I'd like to get some help
    from experienced WL users.
    Basically our EAR file is composed of an EJB module and a WEB module.
    Each module declares some references such as:
    WEB.XML snippet
    <resource-ref>
    <description>DataSource for partition 'default'</description>
    <res-ref-name>jdbc/Datasource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    Now the questions:
    1) Is there a way to map the resources during the deployment, using the
    console? This is the way followed by WebSphere and Oracle AS, for
    example. If this is not possible, should I provide a Deployment Plan for
    that EAR file? I tried to provide the xml Deployment Plan generated by
    weblogic.PlanGenerator utility together with the EAR file while
    deploying the app, but no luck. It seems the Deployment Plan should be
    provided in a jar file. Is that correct?
    2) If the previous options are not possible, how can I create the custom
    deployment descriptor? Is there an "Assembly Tool" that imports the
    standard EAR and then export the custom EAR file with the custom
    deployment descriptors correctly generated?
    Thank you a lot in advance.

  • Deployment descriptor "weblogic.xml" is malformed. in managed server

    Hi All,
              Appreciate if anyone can help.
              I have set up a cluster containing two nodes - one local and other
              remote machine on weblogic 8.1.4
              then i install my application this cluster setup its working fine.
              for my requirement i upgrade the the weblogic version from 8.1.4 to
              8.1.6 .
              i upgrade through the smart update from the bea site . i upgraded both
              the node.
              i started the admin server.it started with no issue.
              my problem comes when i start the my managed server on the cluster .it
              gives me this exception.
              <HTTP> <BEA-101296> <Unable to load the default compiler class
              "com.sun.tools.javac.Main". Using the default javac compiler to compile
              JSPs.>
              i checked the classpath it has the same jdk that i used for 8.1.4
              (jdk1.4.05 from sun.)
              should i used new jdk that comes with the upgrade package of 8.1.6 like
              (jdk1.4.11)
              my class path having the weblogic jar also.
              this is my class path.:
              E:\bea\weblogic81\server\lib\weblogic.jar and other my application
              jars.
              complete exception it is shown like :
              <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
              <Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
              Module: 'Nexaweb': Public ID references the old version of the Servlet
              DTD. You must change the public ID in web.xml file to "-//Sun
              Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
              <[Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
              Check against the DTD: org.xml.sax.SAXParseException: The content of
              element type "weblogic-web-app" must match
              "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
              (line 26, column 20).>
              Compiler class: 'com.sun.tools.javac.Main', not found
              java.lang.ClassNotFoundException: com.sun.tools.javac.Main
              at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
              at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
              at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:141)
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
              <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
              will have better performance if it is enabled. To enable
              call-by-reference, set the enable-call-by-reference element to True in
              the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
              <Failed to initialize the application Xellerate due to error
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
              <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
              to initialize due to failed deployments.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
              <The deployment framework was unable to resume accepting requests.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
              <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
              deployment framework was unable to resume accepting
              requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
              is unable to initialize due to failed deployments.>
              hope the scope of the questions is not too broad. Kindly let me know
              if you need more information.
              Thanks a lot.

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

  • The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing

    Hello,
    I want to create web service from ejb but everytime I want to do it, I get the following error:
    I'm using NWDS 7.2 and JDK 1.6
    [004]Deployment aborted
    Settings
    SDM host : XXX
    SDM port : 50118
    URL to deploy : file:/C:/DOCUME1/XXXX/LOCALS1/Temp/temp3760382784932063822XXXWSProjectEar.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/XXX/LOCALS1/Temp/temp3760382784932063822XXX/WSProjectEar.ear
    Aborted: development component 'XXXWSProjectEar'/'sap.com'/'localhost'/'2011.01.06.15.48.31'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/XXXWSProjectEar.. Reason: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing. ; nested exception is:      com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Can anyone tell me why am I getting this error.
    Thnx for your help.
    Best regards.

    Hello Decio Junior,
    Actually yes, I resolved my problem.
    I'm developing an EJB 3.0 project. I'm using NWDS 7.2 and JDK 1.6 as I said.
    The problem is that my server was using JDK 1.4 and that was the problem.
    EJB 1.1 and 2.1 need ejb-jar.xml but EJB 3.0 use the annotations instead.
    Check your server JDK Version. It should be JDK 1.5 or higher.
    Something else that you should check, in your project properties :
    In the Build PATH : Use JDK 1.5
    In the Java Compiler : Set the java compiler compliance level to 1.6 and check use default compliance settings
    Hope it would help.
    If you need more explanations, I'm here
    Good luck.

  • Ejb accessing the deployment descriptor

    My ejb needs to be able to access the deployment descriptor to retrieve some user information needed to connect to a web service. What is the best way to do this? I know servletts can do this, and if necessary, I could have my servlet retrieve the info and pass it to the bean, but I was hoping to avoid this.
    Thanks
    Matt

    Well, sure I think that is easy. In your <entity> or <session> deployment descriptor you can have:
    <env-entry>
    <env-entry-name>WebServiceLogins</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>su, dan, bob, steve, richard, suzie, carla</env-entry-value>
    </env-entry>
    <env-entry>
    <env-entry-name>WebServicePasswords</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>drs100, vfdds2, ajk14, pass411, richard23, q4lty, uo738ww1</env-entry-value>
    </env-entry>
    Then in your intial-context in your session or entity ejb.....
    InitialContext ic = new InitialContext();
    String logins = (String) ic.lookup("java:comp/env/WebServiceLogins");
    String passwords = (String) ic.lookup("java:comp/env/WebServicePasswords");

Maybe you are looking for

  • Image with a Link to an URL

    Hi, I have an easy question. I would like to have a little question mark-image on my view. And this image has an link to an url. So I would like to push this image, and a new browser-window opens. I only found the Layout-element "LinkToUrl". But with

  • HOW TO MAKE THE CONTENT OF THE TABLE PRINT IN A TABLE CONTROL SCREEN?

    Can any one tell me how to make the content of the table control print in a table control screen!!? Please help!! I have to make the contents of a table in the table control screen print ? any idea Regards, Vj

  • The Screen Off , The Problem Came When I Restart

    Sometimes , When i Turn On The Laptop Screen Will Not Turn On . But Then Restart Problem Sloved . Where is The Problem And What Can be do to Fix it ?

  • Calculating MTBF

    One of my customer would like information on the MTBF on the Cisco kit we use in their network. They recently had a high profile outage (it was a power issue) that highlighted a single point of failure. This has raised the issue with their senior man

  • Interest splitting method and self withholding tax......

    hi all, please let me know the concept for interest splitting method with examples and also self withholding tax. thanks in advance