When I faced such key-not-found problems, that was because I had
"old" versions of components with the same name on some frameworks.
They were not picked up in development but showed up in deployment.
Could this be the case?
Did you check that your components are properly built in the wars?
I just got my D2W prototype application working. I just had to make sure to set all the necessary target setting to make Xcode use Java 1.4 to compile the source code. It's interesting that the application run when compiled under Java 1.5, but the bindings won't work when compiled that way.Anyway
Bernard,I agree, however, we also do some development in JDeveloper which requires Java EE 5.x. That's the reason I upgraded to 5.0. I am in the process of attempting to configure Xcode to compile the test application with the Java 1.4 compiler. I've gotten that to work before by changing some s
Robert,
I don't know if it is within your control to revert to Java 1.4. I
believe there is some way to configure OS X to revert back to that
version temporarily. That might be the easiest next step in trying
to find the cause.
I have never gone beyond that AFAIK 1.5+ are not officially
Bernard,
Thanks for you feedback. I just tried your suggestion: I created a
D2W application with two entities
Department <>> Person
The database is in MySQL. Application runs normally in development
mode.
Target Setting for Servlets:
SERVLET_COPY_JARS
I've had WO apps working on Tomcat 4.x running on OS X, Windows, and
even OS/2. So, mostly it does just work. One thing is that I've
always used SSDD.
Can you try producing a D2W app and deploying that as a Tomcat app?
That should tell you if it is something intrinsically wrong with
di
