Downgrading from JDK 1.5.x to JDK 1.4.x

Question

Hi there,
I hope someone helps me with an issue:
I developed a web app using JDev 10.1.3.3 using the JDK 1.5 included with JDev.
As we are now faced with the fact that this app has to run on an OAS 10.1.2, which to my knowledge uses JDK 1.4.x I have to downgrade from JDK1.5.x->1.4.x.
The technologies that I used are Toplink, EJB 3.0 Session Bean and ADF Faces for the UI layer.
I already downloaded and installed JDK 1.4.2_15 from Sun and changed the default JDK from 1.5.x in JDeveloper to use 1.4.2_15. When I recompiled my Model Project, as excected, I got the following compilation errors on my Bean Class java source file:
Error(29,1): errorIllegalCharacter
Error(29,2): 'class', 'interface', or 'enum' expected
on the same line where I had the EJB 3.0 annotation as follows:
@Stateless(name = "NordPublicFacade")
and also on my Local Interface source:
Error(22,1): errorIllegalCharacter
Error(22,2): 'class', 'interface', or 'enum' expected
for the line:
@Local
OK, I know that these annotations/injections(or whatever they're called) are new features of EJB 3.0 and can only be used with JDK 1.5.
I also have red underlines in some facade methods where generics are used for Toplink Named Queries (please remember this is generated code) so for example:
List<CompanyStructure> findAllCompanyStructure();
On my ViewController project (the UI project) I get the following errors:
refresh = false;
Error(37,17): operator = not applicable to class java.lang.Boolean and boolean
JSFUtils.setManagedBeanValue(ctx,"userState.refresh",true);
Error(92,7): method setManagedBeanValue(javax.faces.context.FacesContext, java.lang.String, boolean) not found in class NordMaintApp.view.util.JSFUtils
My questions
1) What's the best way to go about downgrading?
a) Should I create a new EJB 2.x Session Bean or should I use the Java Service Facade (which I hope creates a POJO and therefore is EJB version independant or not?)
b) Is it necessary to do anything special to the Toplink classes?
2) What are the errors that I get in my ViewController project ?
Thanks In Advance
G.P.

Answer 1

Hi again Shay and THANK YOU!
We simply downloaded OC4J 10.1.3 & installed it (all we had to do is simply unzip it) in a separate directory on its own, on the SAME Server as OAS (10.1.2.02 EE, which includes Discoverer and Portal) AND IT WORKED !
We're now back on using JD 10.1.3 with all its new features etc etc. We even downloaded JDK1.5 and got OC4J working with this JDK WITHOUT, of course, affecting our OAS 10.1.2 installation which works with JDK1.4.2. That woudn't have been possible without your feedback.
It's just that looking at that reference you gave me, I thought that I would have to create a separate instance on the OAS 10.1.2 installation and install 10.1.3 on that one. But eventually it was so much simpler than that. And the memory overhead of OC4J is not that much.
I could create a simple ADF JSF page which just displays data from a table and it's OK!
I could deploy it just fine, though I found out that I have to deploy the ADF Runtimes first; OC4J doesn't come with them. Other than that, it was just fine!
As I said, I'm now using ADF JSF pages for my front-end and ADF BC for my back end; it's so much easier than using Toplink directly.
Only one problem left though (sorry to bother you like that):
In one of the previous emails you mentioned it might be better to use Webcenter for ADF Faces. Unfortunately we cannot go with this option I'm afraid, because we already have an existing portal running on the Oracle Portal that's already included with our OAS 10.1.2.02. I assume that the Oracle Portal's version is also 10.1.2.02. Can I deploy ADF JSF faces as a portlet on this one ? I realise that JDev 10.1.3 comes with some wizards to do this and it seems that I have 2 options: Oracle PDK-Java Portlets or JSR-168 based portlets. I just want whichever one will allow me to have my ADF JSF pages deployed as Portlets on OP 10.1.2.02, so that it can be integrated into any one of the exisiting Portal pages that a colleague of mine already developed (and are waiting for my pages to finish, which currently, when called from a link inside a Portal page displays it in a new page and the user can get back to the Portal page by clicking on the browser's back button). I realise that If I have the JSF page as a portlet, it will then be possible to be integrated into an existing page, that is, have my page to occupy it's own region in a Portal's page.
Once again, Thanks for your help and Thanks In Advance.
R,
G.P.