Looking for something that documents the required ULC project structure, mostly to ensure the project is properly deployed.
I'm using the Eclipse IDE, but I suppose this applies universally. 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 I've gotten by for quite some time by putting most of the operational code in the application folder. This includes ULC extensions. "development-launchers" contains the launchers. "resources" contains the images, etc. ".ulcproperties", "build.properties", and "build.xml" are generated. 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. 2) Obviously, client extensions go in that folder. a. Does that include both the server and client sides? Will the deployer know which classes go where? b. What about the custom coders and registration providers? Don't these classes need to be available on both sides? 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? Many thanks for any assistance.
