Well, the JavaDTWGeneration stuff is abstracted from the applet
because it's also used by the other D2* technologies. Although the
D2W assistant is an applet, we don't encourage remote development with
it (security issues). The applet should work on the local machine
with WO installed. If not, here's a bug in there somewhere.
On Feb 5, 2008, at 11:54 AM, Don Lindsay wrote:
Hello Daryl;
I was able to turn java debugging on in the browser and saw the
classpath did not include the client side classes that were needed
to be able to render the applet. I would have epxected that these
classes would be provided as part of the applet to allow users to
run the assistant on a machine without the WO jar files installed
(specifically) the JavaDTWGeneration.jar. Am I wrong? Is this
something that should be a feature request?
Don
On Feb 5, 2008, at 2:51 PM, Daryl Lee wrote:
Perhaps there is a classloading issue. Do you have
JavaDTWGeneration.framework as part of your classpath?
On Feb 4, 2008, at 5:19 PM, Don Lindsay wrote:
Hello;
I wanted to play with D2W, I created a simple eomodel with 5
tables in a d2web project. when I run the project and select to
run the administrator firefox and safari just hang. Eventually,
after 4 minutes the d2w applet loads. However, the applet never
finishes initing and there are no errors displayed?
Is there something I am missing when creating a project?
Don
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/dlee%40apple.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
