Hi Scott,
I'll take over from Sandro. I assume you're using ULC Version 6.2 or earlier. Because in the latest release ULC'08 we
have put a lot of effort to making deployment easier, by introducing a central configuration file. The next minor
release, that is expected at the end of this month, will even allow to configure the coders, such that you can simple
make an entry in the xml file to register a coder.
Did you register the Coder on the Server side by adding the init parameter to
the web.xml ?
<init-param>
<param-name>server-coder-registry-provider</param-name>
<param-value>sample.MyServerCoderRegistryProvider</param-value>
</init-param>
You find all the details in the ULCExtensionGuide.pdf 4.4 Writing a Custom
Coder.
I hope this helps you
Regards
Marcel
-----------------------------------------
Marcel Rüedi
email: [EMAIL PROTECTED]
url: http://www.canoo.com
Beyond AJAX - Java Rich Internet Applications
*Subject: **RE: [ULC-developer] Proper project structure for development.*
Hey Sandro,
Thanks for your response.
And also thanks for creating such a useful tool.
I think I'm getting very close to making it work for my project.
I wrote and you responded:
>> 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".
I put the ClientCoderRegistryProvider.java in the client-extensions
area as you suggested, but the only way I could get the “ULC Servlet
Export Wizard” to compile was to copy the coder classes into the
client-extensions area, rename them (ex:
GregorianCalendarCoderClient.java), and then change
the ClientCoderRegistryProvider.java to reference these classes instead.
All the coder classes are duplicated. I don’t see a good workaround
for this situation.
So now I'm getting a clean deploy (no errors). The
“client-coder-registry-provider” was not being added by the wizard to
the jnlp file, so I added it manually, and I can successfully launch
the application.
However, as soon as try to invoke one of the extensions, it throws an
exception:
/com.ulcjava.base.shared.internal.IllegalArgumentException: No coder
registered for class java.util.GregorianCalendar/
/ /
The client-extensions.jar file contains
the ClientCoderRegistryProvider and the coder classes as it should, so
I don’t see why it’s failing...
I would be very nice to see a sample ULC project that has all the
basic application components (extensions, coders, icons, resource
files, launchers, splash screen, etc.) Have you ever seen any such thing?
Many thanks,
Scott
-----Original Message-----
From: Sandro Pedrazzini [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2008 7:40 AM
To: Scott Woodson
Cc: ULC Developer List
Subject: Re: [ULC-developer] Proper project structure for development.
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
>
Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.0.134 / Virus Database: 270.4.5/1533 - Release Date:
7/3/2008 7:19 PM
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
