Rgarding deployment descriptor

Hi,
When I convert a DD named weblogic-cmp-rdbms-member-jar.xml using DDcoverter from weblogic 9.1 to 10.0, then the converted file namespace looks like
xmlns="http://www.bea.com/ns/weblogic/60"
Why it is showing 60 in namespace?
Thanks,
Amar

The datasource name tells the CMP container how to look up the DBMS connection that you will need (using a JDBC driver).
The container needs to be told how to map the CMP fields to the database table and columns. Please see the cmp examples that ship with the server to get an idea about how that's done, you may also refer to the EJB CMP documentation to get the basic ideas.
The datasource name must match the name of a datasource that you will have bound into JNDI by the server. If you do not have a datasource the available, you will not be able to connect to your database.
hope this helps
-thorick

Similar Messages

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

Deployment descriptor error for an EJB 3.0 entity bean module

Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto

Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto

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

How to edit deployment descriptor in weblogic 9.0?

Hi ,
I need to edit the values of certain environment variables mentioned in the deployment descriptor of a ejb module.
In weblogic 7,its a straight forward method in which we have the option to edit the deployment descriptor in weblogic console.
But I'm not sure how the same can be done in weblogic 9.0.
Please guide me..!!! its urgent...
Thanks,
Smita

If you want to edit the actual deployment descriptor (ie as a developer) than using any text editor or using an IDE like WebLogic Workshop/Eclipse etc would be the way to go.
If you're trying to change values in an already deployed application, then configuration and tunables can be changed in the admin console. These write the changes to a separate file called a deployment plan. It allows you to change performance and environment settings without disturbing the original EAR file.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

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.

How to reference sapjco from EAR deployment descriptors

Hello techies,
I´ve set up an EJB to use the JCo RFC Provider Service of the J2EE engine. Connection from R3 to EJB works but as soon as the EJB gets invoked, I get the error 'incompatible bean type - no processFunction found' from the RFCDefaultRequestHandler.invokeBean(..., JCO.Function) method.
The reason is clear to me - the JCO.Function class is loaded by different class loaders and thus the method parameters don´t match.
I´ve read in earlier postings that it is neccessary to reference the JCO in the module project and the ear deployment descriptor. That´s where my question begins.
How do I reference the JCO in the module project (what´s that?)? I think it has to do with the EJB jar, doesn´t it?
In the DeployTool I found a way how to set a reference to a library in the menu deploy-->libraries. But I am not sure what to specify here. I entered 'sapjco', since I saw an entry in the managers/library.txt file. Is that correct?
Any hints are welcome!
Regards,
Jan

Jan,
you can set the reference to the EAR project using the reference.txt file that exists in the /managers folder.
In the library.txt file set a path which is reference to sapjco.jar files..like
library JCO sapjco.jar
in the refernce.txt add the JCO referece to the EAR project...like
reference Project library:JCO
where Project here is the name of your EAR file..
Ravi

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");

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 do JAAS and J2EE Deployment Descriptor ACL in WLS

The examples on this website and shipped with WLS stink. Does there exist a GOOD
example of how to
Log in with a form
authenticate (I guess using j_security_check to hook into the web.xml security)
then pull a user from a database and use the roles defined there for authorization
in the rest of the system?
The weblogic examples are from java clients to RMI (ya, thats handy). They also
sit alone. They dont say how to hook them into weblogic. They say to use JAAS
but they have just JAAS examples! No hooking of it into an EJB, servlet, etc!
They also dont show how to hook that code into WLS to use it as your security
module!
Help, I'm at a loss.
They recommend using JAAS but their documentation and examples of doing so suck
or are non existant. We have a complex real world product and need examples of
the same. Stupid, stand alone examples that teach nothing do no help.
frustrated at BEA for their poor documentation and support,
Mike

Also, I use struts....
In struts you have to extend the Action class which then calls the perform()
method on your servlet.
So to call an EJB I have to have my servlet implement PrivilegedAction?
If so, then this wants a run() method. Struts calls perform so that means
I'm going to have to make another class to call from my servlet with a run
method()? Or I'm going to have my servlet implement PrivledgedAction and
call Security.runAs()?
What if I just want to call the EJB from my servlet and put my security
credentials in the JNDI lookup? I want the container to use the roles of the
user in the JNDI lookup to authorize methods based on the deployment
descriptors.
thanks,
Mike
"Vimala Ranganathan" <[email protected]> wrote in message
news:[email protected]...
Hi Micheal,
Attached is an exmaple of JAAS login and invoking an EJB.
Let me know if this turns out to be useful.
Regarding the form based authentication, Could you be more clear on whatissue you are
facing?
Just as note, when you use form based login, WLS would authenticate theuser against
the realm
WLS is setup for, which could be a file Realm, or a RDBMS realm (in whichcase users
and groups are from database)
Roles cannot be defined at the database level. This needs to be atapplication level
which you can define in web.xml or
console(in 7.0)
If you need any specific help or more information please let me know.
Vimala
Michael Lee wrote:
The examples on this website and shipped with WLS stink. Does there
exist a GOOD
example of how to
Log in with a form
authenticate (I guess using j_security_check to hook into the web.xmlsecurity)
then pull a user from a database and use the roles defined there forauthorization
in the rest of the system?
The weblogic examples are from java clients to RMI (ya, thats handy).They also
sit alone. They dont say how to hook them into weblogic. They say to useJAAS
but they have just JAAS examples! No hooking of it into an EJB, servlet,etc!
They also dont show how to hook that code into WLS to use it as yoursecurity
module!
Help, I'm at a loss.
They recommend using JAAS but their documentation and examples of doingso suck
or are non existant. We have a complex real world product and needexamples of
the same. Stupid, stand alone examples that teach nothing do no help.
frustrated at BEA for their poor documentation and support,
Mike

Rgarding deployment descriptor

Similar Messages

Maybe you are looking for