ERROR: Error parsing 'ejb-jar.xml'

Hello ppls,
i am getting the following error while compiling using ejbc :
ERROR: Error parsing 'ejb-jar.xml' line 25: The content of element
type "entity"
must match "(description?,display-name?,small-icon?,large-icon?,ejb-name,home?,
my ejb-jar.xml looks like this
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://www.java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd'
>
<ejb-jar>
     <enterprise-beans>
          <entity>
               <ejb-name>Account</ejb-name>
               <home>wlEntityBeanexample.AccountHome</home>
               <remote>wlEntityBeanexample.Account</remote>
               <ejb-class>wlEntityBeanexample.HelloBean</ejb-class>
               <persistence-type>Bean</persistence-type>
               <prim-key-class>java.lang.String</prim-key-class>
               <transaction-type>Container</transaction-type>
               <reentrant>False</reentrant>
               <cmp-version>2.x</cmp-version>
               <resource-ref>
                    <res-ref-name>mysql</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
               </resource-ref>
          </entity>
     </enterprise-beans>
     <assembly-descriptor>
          <container-transaction>
               <method>
                    <ejb-name>Account</ejb-name>
                    <method-intf>Remote</method-intf>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
     <ejb-client-jar>AccountClient<ejb-client-jar>
</ejb-jar>
I compared the file with other ejb-jar.xml file coming as an Example
in Weblogic, i didn't find any difference.
Thanks in Advance,
Prashant

Thanks Deepak, i got it running at last.
Prashant
"Deepak Vohra" <[email protected]> wrote in message news:<[email protected]>...
The entity element in ejb-jar.xml should be of the
format:
<!ELEMENT entity (description?, display-name?, small-icon?,
          large-icon?, ejb-name, home?, remote?, local-home?,
          local?, ejb-class, persistence-type, prim-key-class,
          reentrant, cmp-version?, abstract-schema-name?,
          cmp-field*, primkey-field?, env-entry*, ejb-ref*,
          ejb-local-ref*, security-role-ref*, security-identity?,
          resource-ref*, resource-env-ref*, query*)>
transaction-type is not defined for a entity ejb.
<entity> <ejb-name>Account</ejb-name> <home>wlEntityBeanexample.AccountHome</home>
<remote>wlEntityBeanexample.Account</remote> <ejb-class>wlEntityBeanexample.HelloBean</ejb-class>
<persistence-type>Bean</persistence-type> <prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant> <cmp-version>2.x</cmp-version>
<resource-ref> <res-ref-name>mysql</res-ref-name> <res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth> </resource-ref>
</entity>
[email protected] (prashant) wrote:
Hello ppls,
i am getting the following error while compiling using ejbc :
ERROR: Error parsing 'ejb-jar.xml' line 25: The content of element
type "entity"
must match "(description?,display-name?,small-icon?,large-icon?,ejb-name,home?,
my ejb-jar.xml looks like this
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://www.java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd'
>
<ejb-jar>
     <enterprise-beans>
          <entity>
               <ejb-name>Account</ejb-name>
               <home>wlEntityBeanexample.AccountHome</home>
               <remote>wlEntityBeanexample.Account</remote>
               <ejb-class>wlEntityBeanexample.HelloBean</ejb-class>
               <persistence-type>Bean</persistence-type>
               <prim-key-class>java.lang.String</prim-key-class>
               <transaction-type>Container</transaction-type>
               <reentrant>False</reentrant>
               <cmp-version>2.x</cmp-version>
               <resource-ref>
                    <res-ref-name>mysql</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
               </resource-ref>
          </entity>
     </enterprise-beans>
     <assembly-descriptor>
          <container-transaction>
               <method>
                    <ejb-name>Account</ejb-name>
                    <method-intf>Remote</method-intf>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
     <ejb-client-jar>AccountClient<ejb-client-jar>
</ejb-jar>
I compared the file with other ejb-jar.xml file coming as an Example
in Weblogic, i didn't find any difference.
Thanks in Advance,
Prashant

Similar Messages

IOException while parsing'ejb-jar.xml

Hi,
While I am building my project I am getting the below error. Please anybody help suggest me to overcome this problem.
[ejbjar] Unable to load dependency analyzer: org.apache.tools.ant.util.depend.bcel.FullAnalyzer - dependent class not found: org/apache/bcel/classfile/Visitor
[ejbjar] Could not resolve ( publicId: -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN, systemId: http://java.sun.com/dtd/ejb-jar_2_0.dtd) to a local entity
BUILD FAILED
IOException while parsing'ejb-jar.xml'. This probably indicates that the descriptor doesn't exist. Details: Connection timed out: connect
Regards,
Sameer

Do you have the appropriate bcel jar file in your path that includes org/apache/bcel/classfile/Visitor?

SAXException while parsing 'ejb-jar.xml'.

Hi
My machine is behind a proxy. When I try to compile an EJB using ANT 1.3 I am getting the following Exception.
D:\src\tools\ant\build.xml:1267: SAXException while parsing 'ejb-jar.xml'. This probably indicates badly-formed XML. Details: External entity not found: "http://java.sun.com/dtd/ejb-jar_1_1.dtd".
--- Nested Exception ---
java.net.SocketException: no further information (code=10071)
at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
I read inone of the news groups that I need to have weblogic.jar in the classpath.
I am using webligic 6.1 and I have also set weblogic.jar in the classpath.
Please help me
Thanks
Seshadri.

It's http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd. Also, check your doctype -
it publicid is correct (-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN),
local DTD will be used.
Seshadri <[email protected]> wrote:
Hi
My machine is behind a proxy. When I try to compile an EJB using ANT 1.3 I am getting the following Exception.
D:\src\tools\ant\build.xml:1267: SAXException while parsing 'ejb-jar.xml'. This probably indicates badly-formed XML. Details: External entity not found: "http://java.sun.com/dtd/ejb-jar_1_1.dtd".
--- Nested Exception ---
java.net.SocketException: no further information (code=10071)
at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
I read inone of the news groups that I need to have weblogic.jar in the classpath.
I am using webligic 6.1 and I have also set weblogic.jar in the classpath.
Please help me
Thanks
Seshadri.--
Dimitri

Error compiling ejb-jar.xml. Help!!

I do not know why this xml file is giving me the errors displayed below.
Thank you in advance.
Here is my xml file:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://www.java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>ObjectConnectorBean</ejb-name>
<display-name>ObjectConnector</display-name>
<home>com.harris.netboss.shared.posting.ObjectConnectorHome</home>
<remote>com.harris.netboss.shared.posting.ObjectConnector</remote>
<ejb-class>com.harris.netboss.shared.posting.ObjectConnectorBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>com.harris.netboss.shared.posting.ObjectConnectorPK</prim-ke
y-class>
<reentrant>False</reentrant>
</entity>
</enterprise-beans>
</ejb-jar>
Here is the error message:
org.xml.sax.SAXParseException: The content of element type "entity" must
match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Exception.java:42)
at org.xml.sax.SAXException.<init>(SAXException.java:45)
at org.xml.sax.SAXParseException.<init>(SAXParseException.java:56)
at
weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
at
weblogic.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1280)
at
weblogic.apache.xerces.validators.common.XMLValidator.callEndElement(Compile
d Code)
at
weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(Compiled Code)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
Code)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:128)
at
weblogic.ejb20.dd.xml.EjbJarLoader_EJB20.process(EjbJarLoader_EJB20.java:919
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:74)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:47)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:38)
at weblogic.ejbc20.runBody(Compiled Code)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20)
--------------- nested within: ------------------
weblogic.xml.process.XMLParsingException: The content of element type
"entity" must match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
. - with nested exception:
[org.xml.sax.SAXParseException: The content of element type "entity" must
match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
.] Line: 16 Column: 16
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at weblogic.utils.NestedException.<init>(NestedException.java:18)
at
weblogic.xml.process.XMLParsingException.<init>(XMLParsingException.java:17)
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:132)
at
weblogic.ejb20.dd.xml.EjbJarLoader_EJB20.process(EjbJarLoader_EJB20.java:919
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:74)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:47)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:38)
at weblogic.ejbc20.runBody(Compiled Code)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20)
ERROR: weblogic.xml.process.XMLParsingException: The content of element type
"entity" must match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
. - with nested exception:
[org.xml.sax.SAXParseException: The content of element type "entity" must
match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
.] Line: 16 Column: 16

looks like your xml file(ejb-jar.xml) is missing some required tag element or
the elements are out of
order. the format is specified in a dtd, you should take a look at the dtd for
ejb-jar.xml. for wl5.1, try looking under c:\weblogic for ejb-jar.dtd
Richard Ong wrote:
I do not know why this xml file is giving me the errors displayed below.
Thank you in advance.
Here is my xml file:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://www.java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>ObjectConnectorBean</ejb-name>
<display-name>ObjectConnector</display-name>
<home>com.harris.netboss.shared.posting.ObjectConnectorHome</home>
<remote>com.harris.netboss.shared.posting.ObjectConnector</remote>
<ejb-class>com.harris.netboss.shared.posting.ObjectConnectorBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>com.harris.netboss.shared.posting.ObjectConnectorPK</prim-ke
y-class>
<reentrant>False</reentrant>
</entity>
</enterprise-beans>
</ejb-jar>
Here is the error message:
org.xml.sax.SAXParseException: The content of element type "entity" must
match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Exception.java:42)
at org.xml.sax.SAXException.<init>(SAXException.java:45)
at org.xml.sax.SAXParseException.<init>(SAXParseException.java:56)
at
weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
at
weblogic.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1280)
at
weblogic.apache.xerces.validators.common.XMLValidator.callEndElement(Compile
d Code)
at
weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(Compiled Code)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
Code)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:128)
at
weblogic.ejb20.dd.xml.EjbJarLoader_EJB20.process(EjbJarLoader_EJB20.java:919
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:74)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:47)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:38)
at weblogic.ejbc20.runBody(Compiled Code)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20)
--------------- nested within: ------------------
weblogic.xml.process.XMLParsingException: The content of element type
"entity" must match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
. - with nested exception:
[org.xml.sax.SAXParseException: The content of element type "entity" must
match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
.] Line: 16 Column: 16
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at weblogic.utils.NestedException.<init>(NestedException.java:18)
at
weblogic.xml.process.XMLParsingException.<init>(XMLParsingException.java:17)
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:132)
at
weblogic.ejb20.dd.xml.EjbJarLoader_EJB20.process(EjbJarLoader_EJB20.java:919
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:74)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:47)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:38)
at weblogic.ejbc20.runBody(Compiled Code)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20)
ERROR: weblogic.xml.process.XMLParsingException: The content of element type
"entity" must match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
. - with nested exception:
[org.xml.sax.SAXParseException: The content of element type "entity" must
match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home,remote,ej
b-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-sche
ma-name?,cmp-field*,primkey-field?,transaction-scope?,env-entry*,ejb-ref*,se
curity-role-ref*,security-identity?,resource-ref*,resource-env-ref*,query*)"
.] Line: 16 Column: 16

Parsing ejb-jar.xml using jaxb

hi all,
how to parse the ejb-jar.xml using jaxb? can anybody send the information about the API which we have to use to parse the ejb-jar.xml? (ejb2.0)
i need the details about all ejbs in an application, (like jndi name, Home and Remote name). so, how can i parse the ejb descriptors?
regards,
panneer

Hi Panneer,
Well, parsing the EJB descriptors is, in principle, a task for the EJB container where they are deployed. From what you wrote I assume that you need to gather that kind of info to visualize in some (monitoring?) tool. Is that correct?
If so, the question would be whether you have access to the EJB jar on the file system (before it's deployed) or you can only connect to the server with the already deployed EJBs. In the latter case, this information is shown in the [NWA plugins|http://help.sap.com/saphelp_nwce10/helpdata/en/0b/5b5a42ea221153e10000000a155106/frameset.htm]. There are also some [telnet commands|http://help.sap.com/saphelp_nw04/helpdata/en/79/3cf82ade038d45a21fbfdaee349b22/frameset.htm] in NW 04 and 7.0 (04s).
If you have access to the EJB jar file, you can parse the descriptors using DOM or SAX, but I'm not aware of any pre-defined JAXB API for this purpose. Probably you can also generate the mapped classes yourself and use them, however I'm not sure how that works with DTD (because of EJB 2.0).
HTH!
\-- Vladimir

Parsing error in ejb-jar.xml

I am trying to build the war file using apache Ant1.5. But I am getting following error -
[ejbjar] Could not resolve ( publicId: -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN, systemId: http://java.sun.com/dtd/ejb-jar_2_0.dtd) to a local entity
Please help me to resolve the error.
Amit.

Amit,
Did you find a solution to this problem? I am having the same situation and I can not find how to solve it. Although it does not seem to hurt I would like to have my process clean.
Thanks in advance.
Ziweth
I am trying to build the war file using apache Ant1.5.
But I am getting following error -
[ejbjar] Could not resolve ( publicId: -//Sun
Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN,
systemId: http://java.sun.com/dtd/ejb-jar_2_0.dtd) to
a local entity
Please help me to resolve the error.
Amit.

WL ejbc error on a healthy ejb-jar.xml

Hi,
I have an EJB with one-to-one mapping to a few other EJBs.
I had this completely functional in WL 6.0 with sp1.
However when I try to deploy the same EJB in WL 6.1, it says
ERROR: Error parsing 'ejb-jar;xml' line 62: Element type
"ejb-entity-ref" must be declared.
Wired part is that the ejb-jar.xml on line 62 has the
ejb-entity-ref tag defined.
So, who is nuts here ??
thanks
Sanjeev Hegde

WLS 6.1 implements EJB 2.0PFD2 (including some of the latest changes in
the EJB 2.0 spec).
You will need to upgrade your EJBs to support the latest EJB 2.0
changes.
If you have further questions about our EJB 2.0 support, I would suggest
that you post them in the EJB beta newsgroup.
-- Rob
Sanjeev Hegde wrote:
Hi,
I have an EJB with one-to-one mapping to a few other EJBs.
I had this completely functional in WL 6.0 with sp1.
However when I try to deploy the same EJB in WL 6.1, it says
ERROR: Error parsing 'ejb-jar;xml' line 62: Element type
"ejb-entity-ref" must be declared.
Wired part is that the ejb-jar.xml on line 62 has the
ejb-entity-ref tag defined.
So, who is nuts here ??
thanks
Sanjeev Hegde

ejb-local-ref where to put this tag in ejb-jar.xml ??

I have an ejb-jar.xml that looks like this. I have had no problem with remote interfaces. Now I want the bean to have a local interface too.
Just let me know where the tag I have mentioned for the <ejb-local-ref> has to be put into.
When I compile this file it throws me an error which i have shown below the output of the ejb-jar.xml file
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>IDMaster</ejb-name>
<home>maxateev.mondial.brg.idmaster.IDMasterHome</home>
<remote>maxateev.mondial.brg.idmaster.IDMaster</remote>
<local-home>maxateev.mondial.brg.idmaster.IDMasterLocalHome</local-home>
<local>maxateev.mondial.brg.idmaster.IDMasterLocal</local>
<ejb-class>maxateev.mondial.brg.idmaster.IDMasterEJB</ejb-class>
<persistence-type>Container</persistence-type>
<ejb-local-ref>
<ejb-ref-name>ejb/IDMasterLocalHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>maxateev.mondial.brg.idmaster.IDMasterLocalHome</local-home>
<local>maxateev.mondial.brg.idmaster.IDMasterLocal</local>
</ejb-local-ref>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>IDMaster</abstract-schema-name>
<cmp-field>
<field-name>idPrefix</field-name>
</cmp-field>
<cmp-field>
<field-name>idValue</field-name>
</cmp-field>
<primkey-field>idPrefix</primkey-field>
<query>
     <query-method>
          <method-name>findAllIDMasters</method-name>
          <method-params/>
     </query-method>
     <ejb-ql><![CDATA[SELECT OBJECT (f) FROM IDMaster as f]]></ejb-ql>
</query>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>IDMaster</ejb-name>
     <method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
I have also added the following tag in the weblogic-jar.xml
<local-jndi-name>IDMasterEJB.IDMasterLocalHome</local-jndi-name>
Just let me know whether I am correct
On compilation (using ant utility) the error thrown is like this :
ejbc:
[java] ERROR: Error parsing 'ejb-jar.xml' line 47: The content of element type "entity" must ma
tch "(description?,display-name?,small-icon?,large-icon?,ejb-name,home?,remote?,local-home?,local?,e
jb-class,persistence-type,prim-key-class,reentrant,cmp-version?,abstract-schema-name?,cmp-field*,pri
mkey-field?,env-entry*,ejb-ref*,ejb-local-ref*,security-role-ref*,security-identity?,resource-ref*,r
esource-env-ref*,query*)".
[java] ERROR: ejbc found errors
[java] Java Result: 1
Kindly Help !!!
Thanks n regards
Sajiv

This should take care of it
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>IDMaster</ejb-name>
<home>maxateev.mondial.brg.idmaster.IDMasterHome</home>
<remote>maxateev.mondial.brg.idmaster.IDMaster</remote>
<local-home>maxateev.mondial.brg.idmaster.IDMasterLocalHome</local-home>
<local>maxateev.mondial.brg.idmaster.IDMasterLocal</local>
<ejb-class>maxateev.mondial.brg.idmaster.IDMasterEJB</ejb-class>
<persistence-type>Container</persistence-type>
<ejb-local-ref>
<ejb-ref-name>ejb/IDMasterLocalHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>maxateev.mondial.brg.idmaster.IDMasterLocalHome</local-home>
<local>maxateev.mondial.brg.idmaster.IDMasterLocal</local>
</ejb-local-ref>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>IDMaster</abstract-schema-name>
<cmp-field>
<field-name>idPrefix</field-name>
</cmp-field>
<cmp-field>
<field-name>idValue</field-name>
</cmp-field>
<primkey-field>idPrefix</primkey-field>
<ejb-local-ref>
<ejb-ref-name>ejb/IDMasterLocalHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>maxateev.mondial.brg.idmaster.IDMasterLocalHome</local-home>
<local>maxateev.mondial.brg.idmaster.IDMasterLocal</local>
</ejb-local-ref>
<query>
<query-method>
<method-name>findAllIDMasters</method-name>
<method-params/>
</query-method>
<ejb-ql><![CDATA[SELECT OBJECT (f) FROM IDMaster as f]]></ejb-ql>
</query>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>IDMaster</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Ejb-jar.xml for a file adapter in 710

Hi,
we moved our file adapter from 700 to 710. Now there is a problem in ejb-jar.xml. There are entries like this:
<session>
<description></description>
<display-name></display-name>
<icon/>
<ejb-name>FileActConversionToSWIFTModuleBean</ejb-name>
<home>com.sap.aii.af.lib.mp.module.ModuleHome</home>
<remote>com.sap.aii.af.lib.mp.module.ModuleRemote</remote>
<local-home>com.sap.aii.af.lib.mp.module.ModuleLocalHome</local-home>
<local>com.sap.aii.af.lib.mp.module.ModuleLocal</local>
<ejb-class>com.sapcons.xi.swift.FileActConversionToSWIFTModuleBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
The error messages are like this:
Bean Interfaces: stateless bean "FileActConversionToSWIFTModuleBean" should have at least one of the following interface pairs: "local" and "local-home", "home" and "remote" or service endpoint interface
Bean Interfaces: The home interface "com.sap.aii.af.lib.mp.module.ModuleHome" cannot be found in the search path.
What is wrong? The interfaces ModuleHome etc. seem not to be here any more. Which interfaces should be entered in ejb-jar.xml for release 710?
Thanks and regards, Marina

Hi,
yes, there is a module for file adapter. Some modifications were implemented, too. I can imagine that something was forgotten. It is possible to do the build, to deploy and to test the adapter, even if there are errors in ejb-jar.xml .
Is there a list which things that changed between 700 and 710?
I have these 2 links with useful information:
[Developing Adapters and Modules|http://help.sap.com/saphelp_nwpi71/helpdata/en/8b/895e407aa4c44ce10000000a1550b0/content.htm ]
[Javadoc PI 7.1 (Adapter, Module and Mapping Development)|http://help.sap.com/javadocs/pi/SP3/xpi/index.html]
Is there further information for this topic?
Thanks and regards, Marina

ERROR: Error parsing 'META-INF/weblogic-ejb-jar.xml'

I have this error while compiling session bean (Stateful). my weblogic-ejb-jar.xml
file looks like this. Could anyone tell me what I'm doing wrong.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>TransactionAgent</ejb-name>
<stateless-session-descriptor>
<pool>10</pool>
<stateless-clustering>false</stateless-clustering>
</stateless-session-descriptor>
<ejb-ref-name>ejb/Transaction</ejb-ref-name>
<jndi-name>Transaction</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>

<pool> should not have any value. Instead it shud have the child nodes
<max-beans-in-free-pool> and/or <initial-beans-in-free-pool>
it will look like
<pool>
<max-beans-in-free-pool> 500 </max-beans-in-free-pool>
<initial-beans-in-free-pool>100 </initial-beans-in-free-pool>
</pool>
Also, <ejb-ref-name> and <jndi-name> goes under <ejb-reference-descriptor>
which is under <reference-descriptor>
So it would look like
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name> .. </ejb-ref-name>
<jndi-name> .. </jndi-name>
<ejb-reference-description>
</reference-descriptor>
The jndi name should also be defined for the bean. Also note that ejb-refs
are defined under a bean which is referring other beans. Like Transaction
should not refer to itself. Rather if it is referring to Customer, then
ejb-ref will be defined for CustomerBean.
Hope it helps.
Rupesh.
Owen <[email protected]> wrote in message
news:3c614fb0$[email protected]..
>
I have this error while compiling session bean (Stateful). myweblogic-ejb-jar.xml
file looks like this. Could anyone tell me what I'm doing wrong.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>TransactionAgent</ejb-name>
<stateless-session-descriptor>
<pool>10</pool>
<stateless-clustering>false</stateless-clustering>
</stateless-session-descriptor>
<ejb-ref-name>ejb/Transaction</ejb-ref-name>
<jndi-name>Transaction</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>

Error defining transaction-isolation at weblogic-ejb-jar.xml

Hi,
.. from WebLogic 5.1 reference:
(...) the top level elements in weblogic-ejb-jar.xml are as follows:
. description
. weblogic-version
. weblogic-enterprise-bean
. ejb-name
. caching-descriptor
. presistence-descriptor
. clustering-descriptor
. transaction-descriptor
. reference-descriptor
. enable-call-by-reference
. jndi-name
. TRANSACTION-ISOLATION
. security-role-assignment
this way i've appended a transaction isolation section immediatly after the jndi-name section
from my weblogic-ejb-jar.xml file to specify that all methods of my container-managed ejb
should use read-committed accesses to the database. But i've gotten the error message:
org.xml.sax.SAXParseException: Element "weblogic-enterprise-bean" allows no further input; "transaction-isolation" is not allowed.
during compilation time at parsing. Nowhere else in the weblogic-ejb-jar.xml i can put the
isolation transaction section without receiving some related parsing error. The same happens
trying to include such transaction section at ejb-jar.xml. I'm attaching both xml files. Should
anybody help me saying where that section should be described? And if it should be placed in
another file, why the documentation states for describing it at the weblogic-ejb-jar.xml?
[weblogic-ejb-jar.xml]

That means that you do not have the SP6 in the service pack and it is using
the old DTD.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Ana Benites" <[email protected]> wrote in message
news:[email protected]...
>
Cameron,
hello.
When you say "<enterprise-bean>" block, you mean"<weblogic-enterprise-bean>"block, isn't it?
>
Because you recommend in your response exactly what i was doing in myweblogic-ejb-jar.xml,
>
that i had attached to my message when openning this discussion. I copyit again here:
>
My weblogic-ejb-jar.xml:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic5.1.0 EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
>
>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>cluster.ejb.TellerHome</ejb-name>
<caching-descriptor>
</caching-descriptor>
<enable-call-by-reference>False</enable-call-by-reference>
<jndi-name>cluster.ejb.TellerHome</jndi-name>
<transaction-isolation>
<isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
>
<method>
<ejb-name>cluster.ejb.TellerHome</ejb-name>
<method-name>*</method-name>
</method>
</transaction-isolation>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
...and this is resulting in the following parsing error during compiletime:
>
>
org.xml.sax.SAXParseException: Element "weblogic-enterprise-bean" allowsno further input; "transaction-isolation" is not allowed.
at com.sun.xml.parser.Parser.error(Parser.java:2775)
atcom.sun.xml.parser.ValidatingParser$ChildrenValidator.consume(ValidatingPars
er.java:306)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1280)
at com.sun.xml.parser.Parser.content(Parser.java:1498)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1399)
at com.sun.xml.parser.Parser.content(Parser.java:1498)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1399)
at com.sun.xml.parser.Parser.parseInternal(Parser.java:491)
at com.sun.xml.parser.Parser.parse(Parser.java:283)
at weblogic.xml.dom.SunDOMParser.getDocument(SunDOMParser.java:69)
at weblogic.xml.dom.DOMParser.getDocument(DOMParser.java:102)
atweblogic.ejb.deployment.dd.DescriptorLoader.<init>(DescriptorLoader.java:157
at weblogic.ejbc.runBody(ejbc.java, Compiled Code)
at weblogic.utils.compiler.Tool.run(Tool.java:80)
at weblogic.ejbc.main(ejbc.java:353)
Am i forgetting anything?
Thanks for your help
Ana.
"Cameron Purdy" <[email protected]> wrote:
Hi Ana,
Add to weblogic-ejb-jar.xml:
Inside each <enterprise-bean> block, add the following immediately before
the block closes:
<transaction-isolation>
<isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
<method>
<ejb-name></ejb-name>
<method-name>*</method-name>
</method>
</transaction-isolation>
The <ejb-name> value of the <method> block of the <transaction-isolation>
block must match the <ejb-name> value of the <enterprise-bean> block.
Please note the case sensitive nature of the values.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Ana Benites" <[email protected]> wrote in message
news:[email protected]...
Thanks for your attention Cameron,
from my WebLogic Console one can read
"WebLogic Build 5.1.0 Service Pack 6 09/20/2000 21:03:19#84511"
...because i was suspecting the problem was due to a lack of
applying
the service pack 6. But even
after that upgrade the parsing errors remain.
regards
Ana
"Cameron Purdy" <[email protected]> wrote:
Ana,
The 5.1 release did NOT support transaction isolation in the
weblogic-ejb-jar.xml file.
That feature was introduced in a service pack. What SP are you using?
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Ana Benites" <[email protected]> wrote in message
news:[email protected]...
Hi,
.. from WebLogic 5.1 reference:
(...) the top level elements in weblogic-ejb-jar.xml are as follows:
description
weblogic-version
weblogic-enterprise-bean
. ejb-name
. caching-descriptor
. presistence-descriptor
. clustering-descriptor
. transaction-descriptor
. reference-descriptor
. enable-call-by-reference
. jndi-name
. TRANSACTION-ISOLATION
security-role-assignment
this way i've appended a transaction isolation section immediatly
after
the jndi-name section
from my weblogic-ejb-jar.xml file to specify that all methods of mycontainer-managed ejb
should use read-committed accesses to the database. But i've gotten
the
error message:
org.xml.sax.SAXParseException: Element "weblogic-enterprise-bean"
allows
no further input; "transaction-isolation" is not allowed.
during compilation time at parsing. Nowhere else in theweblogic-ejb-jar.xml i can put the
isolation transaction section without receiving some related parsingerror. The same happens
trying to include such transaction section at ejb-jar.xml. I'm
attaching
both xml files. Should
anybody help me saying where that section should be described? And
if
it
should be placed in
another file, why the documentation states for describing it at theweblogic-ejb-jar.xml?

Error while migrating orion-ejb-jar.xml from OC4J 9.0.4.1

I am trying to use Toplink migration tool to take our existing orion-ejb-jar.xml file and toplink-ejb-jar.xml file to new 10.1.3 deployment. While running the migration tool I get the following error
WARNING: Oc4j native CMP setting optimistic-locking on
entity(TransactionTypeEntityBean) is not migrated and supported.
java.lang.IllegalArgumentException: MWDatabaseField[9BE2B5]
(TAX_RULE.TAX_RULE_ID)
at
oracle.toplink.workbench.mappingsmodel.desc.relational.MWRelationalPrima
ryKeyPolicy.addPrimaryKey(MWRelationalPrimaryKeyPolicy.java:99)
at
oracle.toplink.tools.migration.RuntimeCMPProjectToMWProjectConverter.con
vertDescriptor(RuntimeCMPProjectToMWProjectConverter.java:297)
at
oracle.toplink.tools.migration.RuntimeCMPProjectToMWProjectConverter.con
vertDescriptors(RuntimeCMPProjectToMWProjectConverter.java:265)
at
oracle.toplink.tools.migration.RuntimeCMPProjectToMWProjectConverter.con
vertProject(RuntimeCMPProjectToMWProjectConverter.java:144)
at
oracle.toplink.tools.migration.MigrationManagerBase.convertAndWriteoutMW
Project(MigrationManagerBase.java:369)
at
oracle.toplink.tools.migration.MigrationManagerBase.migrate(MigrationMan
agerBase.java:358)
at
oracle.toplink.tools.migration.io.MigrationIOManager.buildMigratedJarFil
e(MigrationIOManager.java:243)
at
oracle.toplink.tools.migration.io.MigrationIOManager.operateEarEntry(Mig
rationIOManager.java:181)
at
oracle.toplink.tools.migration.io.MigrationIOManager.operateEar(Migratio
nIOManager.java:145)
at
oracle.toplink.tools.migration.io.MigrationIOManager.operateIO(Migration
IOManager.java:88)
at
oracle.toplink.tools.migration.MigrationManagerBase.startMigration(Migra
tionManagerBase.java:280)
at
oracle.toplink.tools.migration.MigrationManagerBase.run(MigrationManager
Base.java:121)
at
oracle.toplink.tools.migration.MigrationManagerBase.run(MigrationManager
Base.java:97)
at
oracle.toplink.tools.migration.TopLinkCMPMigrator.main(TopLinkCMPMigrato
r.java:59)

Hello,
The warning message looks to be unrelated to the java.lang.IllegalArgumentException error. The warning states that optimistic locking cannot be migrated to the toplink-ejb-jar.xml file; this is stated in chapter 7 of the TopLink developer's guide at
http://download-west.oracle.com/otn_hosted_doc/toplink/1013/MAIN/_pdf/b13593_v1_01.pdf
The exception though seems to indicate that your orion-ejb-jar.xml contains EJBs mapped to the same table that are not related through EJB inheritance. I do it all the time with POJOs so this will work in TopLink, but you will need a support case to help get your project migrated if this is the case.
Best Regards,
Chris Delahunt

Weblogic 10.3.0 Deployment error when using ejb-jar.xml

Hi,
I am getting the following error while deploying my EJB3 application on Weblogic 10.3.0. This is happening only if I include ejb-jar.xml.
As per the EJB3 descriptor spec, Remote Home or Local home are not exists.
Is this a issue in Weblogic 10.3.0 or am I missing any special setup ?
Please help.
weblogic.application.ModuleException: Exception preparing module: EJBModule(egm-poc.jar)
Unable to deploy EJB: C:\appsrv\domains\WeblogicRS1.1-domain\servers\admin\tmp\_WL_user\_appsdir_egmear_ear\ot2591\egm-poc.
jar from egm-poc.jar:
In EJB JPATestBean, both the remote home and remote component interface must be specified. Currently, only one of them is spec
ified.
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
My ejb-jar.xml is
- <ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<description>JPA Test Application</description>
<display-name>JPATest</display-name>
- <enterprise-beans>
- <session>
<ejb-name>JPATestBean</ejb-name>
<remote>egm.poc.jpa.JPATestBeanRemote</remote>
<local>egm.poc.jpa.JPATestBeanLocal</local>
<ejb-class>egm.poc.jpa.JPATestBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
- <session>
<ejb-name>AuditInfoDAOH</ejb-name>
<local>egm.poc.jpa.Audit</local>
<ejb-class>egm.poc.jpa.AuditInfoDAOH</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
- <assembly-descriptor>
- <container-transaction>
- <method>
<ejb-name>JPATestBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
- <container-transaction>
- <method>
<ejb-name>AuditInfoDAOH</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Regards
Saji

Hi,
Seems the issue is not common. Can anyone throw some light on this ?
Regards
Saji

Ejb-jar.xml DTD validation error?

I am attempting to deploy a JAR on App Server 8 PE. The application does not contain any EJBs but I understand that the ejb-jar.xml descriptor is still needed. I am running the app server on Windows XP.
My issue is as follows:
I understand that the root element for the ejb-jar.xml file (<ejb-jar>) is required. Since I have no EJBs, I should be able to leave this root element blank (as I have in previoius successful deployments to earlier versions of Sun App Server). When I attempt to deploy, I receive the following DTD Validation error via the admin console:
The content of element type "ejb-jar" is incomplete, it must match "(description?,display-name?,small-icon?,large-icon?,enterprise-beans,relationships?,assembly-descriptor?,ejb-client-jar?)".
Am I missing something?
My ejb-jar.xml file looks like:
<!DOCTYPE ejb-jar PUBLIC
     "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
     "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
</ejb-jar>
Many thanks in advance to any assistance...

I am attempting to deploy a JAR on App Server 8 PE.
The application does not contain any EJBs but I
I understand that the ejb-jar.xml descriptor is still
needed. I am running the app server on Windows XP.
My issue is as follows:
I understand that the root element for the
ejb-jar.xml file (<ejb-jar>) is required. Since I
have no EJBs, I should be able to leave this root
element blank (as I have in previoius successful
deployments to earlier versions of Sun App Server).
When I attempt to deploy, I receive the following
g DTD Validation error via the admin console:
The content of element type "ejb-jar" is incomplete,
it must match
"(description?,display-name?,small-icon?,large-icon?,e
nterprise-beans,relationships?,assembly-descriptor?,ej
b-client-jar?)".
Am I missing something?
My ejb-jar.xml file looks like:
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
s 2.0//EN"
     "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
</ejb-jar>
Many thanks in advance to any assistance...I hav tried this and it is working
<?xml version="1.0" encoding="UTF-8" ?>
<ejb-jar
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
version="2.1">

Oc4j generated finders in orion-ejb-jar.xml file causing errors

Any information or assistance would be greatly appreciated.
I have encountered a problem with the generated orion-ejb-jar.xml file.
It looks like the additional finder methods that are generated when the application
is deployed are incorrect from the 9.0.3 version to the new 10.1.2.0.2 version.
The original content of orion-ejb-jar.xml before additional finder syntax is added:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM   NO_SYS_USER_OBJECT_HISTORY H1,
         (SELECT AUTOID
          FROM   NO_SYS_USER_OBJECT_HISTORY
          WHERE USER_ID=UPPER($1)
          ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= $2
    AND H1.AUTOID = H2.AUTOID)">
<method>
<ejb-name>NoUserHistoryEntry</ejb-name>
<method-name>findOldest</method-name>
<method-params>
   <method-param>java.lang.String</method-param>
   <method-param>java.lang.Integer</method-param>
</method-params>
</method>
</finder-method>
After deploying in 9.0.3 the following information is added to the orion-ejb-jar.xml file:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM   NO_SYS_USER_OBJECT_HISTORY H1,
         (SELECT AUTOID
          FROM   NO_SYS_USER_OBJECT_HISTORY
          WHERE USER_ID=$1
          ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= $2
    AND H1.AUTOID = H2.AUTOID)">

<method>
<ejb-name>NoUserHistoryEntry</ejb-name>
<method-name>findOldest</method-name>
<method-params>
   <method-param>java.lang.String</method-param>
   <method-param>java.lang.Integer</method-param>
</method-params>
</method>
</finder-method>
After deploying in 10.1.2.0.2 the following information is added to the
orion-ejb-jar.xml file:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM   NO_SYS_USER_OBJECT_HISTORY H1,
         (SELECT AUTOID
          FROM   NO_SYS_USER_OBJECT_HISTORY
          WHERE USER_ID=UPPER($1)
          ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= $2
    AND H1.AUTOID = H2.AUTOID)">


<method>
<ejb-name>NoUserHistoryEntry</ejb-name>
<method-name>findOldest</method-name>
<method-params>
   <method-param>java.lang.String</method-param>
   <method-param>java.lang.Integer</method-param>
</method-params>
</method>
</finder-method>
The problem with the 10.1.2.0.2 generated finders is that it is prepending H1 when
it should be NO_SYS_USER_OBJECT_HISTORY which results in the following error:
Exception in thread "main" com.cdtelecom.vygroe.configuration.ConfigurationException:
com.evermind.server.rmi.OrionRemoteException:
Transaction was rolled back: Database error: java.sql.SQLException:
ORA-00904: "H1"."SITE_DESCRIPTION": invalid identifier
; nested exception is:
        java.sql.SQLException: ORA-00904: "H1"."SITE_DESCRIPTION": invalid identifier
        at com.cdtelecom.vygroe.configuration.ConfigurationSession.internalRecordAction(ConfigurationSession.java:869)
        at com.cdtelecom.vygroe.configuration.ConfigurationSession.recordAction(ConfigurationSession.java:401)
        at com.cdtelecom.vygroe.configuration.Configuration.recordActionSaveOrder(Configuration.java:886)
        at com.cdtelecom.vygroe.configuration.Configuration.getOrder(Configuration.java:239)
        at test10g.main(test10g.java:47)
I tried to manually edit the file but when I shutdown and restart oc4j it regenerates the file again.

Jingzhi -- If you define the correct EJB-QL you should get the correct SQL generated for the finder. If that's not happening can you verify it against the OC4J v903 production release and see if it is still happening. I don't know if this helps with the JDeveloper problem specifically but if you don't need to create your own finders then that I hope should help.
Thanks -- Jeff

ERROR: Error parsing 'ejb-jar.xml'

Similar Messages

Maybe you are looking for