Hi Scott,
My current structure, created by the “New ULC Project” wizard, has
the well known folders.
project root
application
build-extensions
client-extensions
development-launchers
resources
.ulcproperties
build.properties
build.xml
build-extensions are not part of the wizard structure. You can add
whatever directory to the structure, but this will be not considered
by the "Export as servlet" wizard.
You then need to adapt the generated build.xml file
I’ve gotten by for quite some time by putting most of the
operational code in the application folder.
This includes ULC extensions.
Yes, server side extensions.
“development-launchers” contains the launchers.
Only the launchers used during development time. You will not need
them in your deployed version.
“resources” contains the images, etc.
“.ulcproperties”, “build.properties”, and “build.xml” are generated.
Yes, build.xml is generated by the "Export as servlet" wizard. You can
edit and adapt it in case you need some special generations not
considered in the usual wizard-based case.
This configuration runs just fine in “development” mode, and I can
also deploy this,
as long as I provide all the server side jars to the client side.
But now I’m ready to productize…
1) “build-extensions” is a complete mystery – haven’t seen a
reference to this anywhere.
In fact this is not generated at all by the new project wizard. I do
not know where it comes from.
In any case it should not contain anything, because nothing there will
be part of the deployment bundle.
2) Obviously, client extensions go in that folder.
Right
a. Does that include both the server and client sides? Will
the deployer know which classes go where?
No, as you stated before, the server side of an extension goes into
the application folder. It is part of the application, which will be
deployed server side.
b. What about the custom coders and registration providers?
Don’t these classes need to be available on both sides?
Client part on "client-extensions", server parts on "application".
3) There are some resource files that need to be deployed
external to the jar file (the JNLP icon, config files, etc.). Can
those be handled in some way?
4) Where does a custom JNLP launcher go?
Everything that needs to be deployed client side should go into the
client-extension folder.
Have a look at here:
http://ulc-community.canoo.com/ulceclipseintegrationdoc/faq.html
All images within the "resources" folder are considered application
resources, i.e. they are deployed to the server. If you need a
resource on the client (resources needed by the launcher, like a
splash screen image, must be deployed on the client), just put it into
the "client-extensions" folder. It will be automatically deployed on
the client.
Best regards
Sandro
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
