we have some Stateless EJBs ( EJB 1.1) deployed on WebLogic 5.1.
Now we want to migrate to WebLogic 10.
WebLogic 10 supports EJB 3.0 specification.
So I was expecting few changes while deploying these EJB's on WL 10.
But to my surprise these EJB's developed with EJB 1.1 specification got deployed on WL 10 without any problem.
So does that mean WL 10 supports EJB 1.1 without any alterations.
Any special care that I should take?
The porting of EJB from Weblogic 5 to weblogic 10 is still in progress.
Following are the points I observed till now:
1. In WebLogic 5 there used to be a file called as weblogic.properties.
This file contained the various attributes specific to weblogic.
Now it has been replaced by config.xml.
So in order to port your application one should port weblogic.properties to config.xml
(Note that config.xml should not be modified manually use the weblogic console as far as possible)
2. EJB 1.1 is supported by Weblogic 10, so need dont worry about changing the code.
Note: I am not sure about EJB 1.2.
3. Looks like prior to Weblogic 6 there was no concept of domains, which is present in all the later versions.
4. In WebLogic 5 one can have a documentRoot (in weblogic.properties ) which acts as the Root application.
To port this you must have a web.xml file in your web application and to make it the default application
specify "context-root" as "/" ( present in application.xml)
EJB1.1 migrate to weblogic 10 from 8
lease help me out here..
Failed to parse descriptor at 'META-INF/weblogic-ejb-jar.xml' for module 'PAMaintenanceBean.jar': javax.xml.stream.XMLStreamException: weblogic.xml.process.SAXValidationException: Could not locate bean with ejb-name "PAMaintenance" in ejb-jar.xml
I am also facing the same issue.
Its a bit strange issue.
I need not explain the problem again.
Following are two solutions:
1. Do not create an EAR. Creating an ear gives problem.
Deploy these two EJB's as independent EJB's ,
Those would be successfully deployed.
2. Create only one EJB module.
And in that module in ejb-jar.xml and in weblogic-ejb-jar.xml
mention the entries for both the EJB's.
So the result would be you will have only one ejb module defined
And the entries would be mentioned in the ejb-jar.xml and in weblogic-ejb-jar.xml.
This should solve your problem.
The problem is some how weblogic is not able to deploy more than one EJB's from an EAR.
If you deploy only one EJB it works fine.
But when you deploy the second one it tries to search for the entries in the ejb-jar.xml and in weblogic-ejb-jar.xml
of the first EJB.