Hi Scott,
The servlet export wizard compiles your code separately, clients code
with client side libraries and server code with server side
libraries. This way you are able to discover strange mixes that run
on development mode (because you have everything on it), but would
never run on deployment mode.
In order to distinguish, what should go client side and what server
side, you need to put your client side code (UI part of your
extensions) within the "client-extensions" source folder.
I hope this helps
Best regards
Sandro
On Jan 10, 2008, at 1:24 AM, Scott Woodson wrote:
I’ve been running using the development launcher for the last
couple of months.
Before buying, I initially did a servlet deploy to verify this
functionality.
Since then, I’ve created a complete application, including ULC
extensions.
The Servlet Export Wizard now fails with compile errors, all of the
type:
[javac] Compiling 163 source files to C:\GCAS-Workspace\2013 APT
\build
[javac] C:/GCAS-Workspace/2013 APT/application/com/gcas/apt/ulc/
extensions/ULCClientCoderRegistryProvider.java:14: package
com.ulcjava.base.client.streamcoder does not exist
[javac] import
com.ulcjava.base.client.streamcoder.DefaultClientCoderRegistryProvider
;
Apparently, the Wizard is not accounting for the extension jar files.
Upgrading to the latest Eclipse plugin did not help.
Is there some way to fix this situation?
A manual workaround perhaps?
I have to do a big demo in a couple of days.
Am I screwed?
Scott!
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
