Using DTO Factory causes error in deploy

Question

I am trying to deploy a test application on Oracle9iAS 9.0.3 utilizing the Session Facade design pattern. I have been trying to implement the DTO Factory as a plain Java class in my EJB JAR file and think this might be causing the problem.
First, when I read from "EJB Design Patterns", Floyd Marinescu, pg. 28 it says:
"When used behind a session bean facade, the DTO factory can be implemented as a plain Java class that simply stores creation/consumption logic for different data transfer objects in its methods."
As I am using the session bean facade, I was going to implement the DTO factory as the plain Java class as it states. Also, of course, the DTO classes themselves are plain Java classes.
When I try to deploy the application I get the following error:
Deployment failed: Nested exception Root Cause: Syntax error in source. Syntax error in source
Now, my question is three-fold:
1) Is it due to using plain Java classes in my EJB JAR that I am receiving this error?
2) Can these plain Java classes located in my EJB JAR truly call the local interfaces for my entity beans?
3) Does 9.0.3 not support any of the above?
As I can't deploy my application, I am a touch confused by what is causing this error. I have seen it before in conjunction with 9.0.2 when my heap size was too small, but have adjusted this so this cannot be the cause. Besides, I am not trying to run anything else on this instance of the app server other than the example.
I will tag this on...about every 4 of 5 times I try to restart the OC4J instance (using the EM website) I get this error:
An error occurred while restarting. The opmn request has failed. From opmn: HTTP/1.1 204 No Content Content-Length: 0 Content-Type: text/html Response: 0 of 1 processes restarted. Check opmn log files such as ipm.log and ons.log for detailed.
Any help would be truly appreciated. Thanks!

Answer 1

Hi Alex,
Now, my question is three-fold:
1) Is it due to using plain Java classes in my EJB
JAR that I am receiving this error?No, unless there is a problem in your POJOs (Plain Old Java Class)
2) Can these plain Java classes located in my EJB JAR
truly call the local interfaces for my entity beans?No. But the EJBs can call the POJOs
3) Does 9.0.3 not support any of the above?No, 9.0.3 does support the above.
It appears that there is a problem in your code somewhere. It may be due to a java compatibility mismatch. By default, OC4J supports java version 1.3.1. Perhaps your POJOs rely on java version 1.4.x?
When you deploy, OC4J builds and compiles classes that implement the EJB interfaces. I think the error you describe is due to the fact that this part of the deploy process is failing (i.e. the compilation part). This implies that there may be a problem in one of your EJB interfaces.
Perhaps if you posted the entire error message and stack trace you are getting, I may be able to offer more.
Good Luck,
Avi.