Hi Dany
When I said other ULC 2008 improvements, I meant easy deployment
improvements. ULC API improvements like sortable tables are useful.
However when trying to replace our own sorting implementation by
implementation based on community code snippets for Filtered Table
Model, I
found one problem.
Setting sorting by second column in descending order seems to be
ignored and
table is not sorted. I assume ULC implementation is not based on Java
6 Swing implementation, what would explain why there's no support for
sorting based on multiple columns, a.k.a.
tableRowSorter.setSortKeys(sortKeys). Please see attached code both
for ULC
and Swing solutions.
Regarding rest of the questions, I use version based download
protocol to
avoid unnecessary jar downloads. As part of our build process, we
sign client jars which changes its timestamp which is important for
base
JNLP download. As a result, each of the libraries is downloaded
every time client application starts. One solution to this problem
would be
to limit number of signed jars as per your ULCDeploymentGuide, but
this
would not solve a problem completely. I would also say that
unnecessary
downloads is not a major issue for us, it's just a low priority
problem.
Regarding OSGi compliance for ULC jars, what we do at the moment is
that we
patch released ULC jars and add those MANIFEST.MF entries ourselves.
Obviously, the difficulty is that we will have to do that for every
release
of ULC. It's definitelly something we would like to avoid rather
than a
show-stopper for us. I think other ULC users may benefit from it too.
Also, it would be very useful if you could publish XML schema for
ULCApplicationConfiguration.xml file to be available via http in web
browser. Thus, XML validation in Eclipse would automatically work
without a
requirement to have XML schema in the same folder as
ULCApplicationConfiguration.xml.
What I mean is something like this:
<ULCApplicationConfiguration
xmlns="http://www.canoo.com/ulc";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://www.canoo.com/ulc
http://www.canoo.com/ulc/schema/
ULCApplicationConfiguration.xsd">
...
</ULCApplicationConfiguration>
Please notice xsi:schemaLocation attribute in form of "namespaceUri
schemaUrl". If you use just ULCApplicationConfiguration.xsd as
schemaUrl, Eclipse tries to find that schema is the same folder,
whereas if you use full http url, Eclipse tries to resolve it and use
it.
I hope my explanation makes sense.
Regards Vlado
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Daniel Grob
Sent: Wednesday, August 13, 2008 10:12 AM
To: [email protected]; Vyvojava
Subject: Re: [ULC-developer] ULC 2008 easy deployment
Hi Vlado,
I have come accross to a possible bug when loading client
configuration properties in JNLP environment. I have followed steps
in
ULCApplicationDevelopmentGuide and I have set LaF in
ULCApplicationConfiguration.xml. I have deployed skeleton server
project from Eclipse into JBoss. When I run launch.jnlp
(http://localhost:8080/app/launch.jnlp), my LaF settings seem to be
ignored.
However, LaF is set correctly when running the application in
develomnet environment. I think there is a bug in ulc-jnlp-client.jar
lib, as there is no request asking for /clientconfig.properties at
the
startup of the application.
I can confirm this bug. I have created a corresponding bug in our
issue
database:
=> http://www.canoo.com/jira/browse/UBA-7521: JNLP environment
ignores
application configuration
We will fix this issue for the next maintenance release.
I cannot use any other ULC 2008 improvements for following reasons:
* com.ulcjava.container.servlet.server.servlets.JNLPDownloader
generates JNLP in runtime, bun only with basic tags,
* com.ulcjava.container.servlet.server.servlets.ClientJarDownloader
does not support version based downloading, pack200
When you say "I cannot use any other ULC 2008 improvements" do you
mean
other easy deployment improvements or any other improvements, e.g.
form
component, sortable tables, application framework? The two issues
you point
out are related to the Easy Servlet Deployment feature which is quite
independent from the other UltraLightClient '08 features, i.e. you
should be
able to use other improvements.
The two improvments you mention are already known and we will fix
them for
the next maintenance release:
* http://www.canoo.com/jira/browse/UBA-7505: Application configuration
should enable deployment descriptor configuration
* http://www.canoo.com/jira/browse/UBA-7496: Provide a Servlet that
delivers
pack200 compressed Jar files on the fly
does not support version based downloading
Do you mean the version-based download protocol of the JNLP
specification?
We want to better understand your requirement. Can you please give
us some
more information why you need the version-based download protocol?
What
features of the version-based download protocol are important to you?
Also, it would be really good if you could make all ULC jars OSGi
friendly (adding relevant MANIFEST.MF entries) so I can use them as
OSGi bundles.
I have created the following feature request in our issue database:
=> http://www.canoo.com/jira/browse/UBA-7522: Make all ULC jars OSGi
friendly
How important is this feature for you?
Regards Dany
On 12.08.2008, at 07:08, Vyvojava wrote:
Hi
I am evaluating ULC 2008 and its new features focusing on making
application deployment easier.
I have come accross to a possible bug when loading client
configuration properties in JNLP environment. I have followed steps
in
ULCApplicationDevelopmentGuide and I have set LaF in
ULCApplicationConfiguration.xml. I have deployed skeleton server
project from Eclipse into JBoss. When I run launch.jnlp
(http://localhost:8080/app/launch.jnlp), my LaF settings seem to be
ignored.
However, LaF is set correctly when running the application in
develomnet environment. I think there is a bug in ulc-jnlp-client.jar
lib, as there is no request asking for /clientconfig.properties at
the
startup of the application.
I cannot use any other ULC 2008 improvements for following reasons:
* com.ulcjava.container.servlet.server.servlets.JNLPDownloader
generates JNLP in runtime, bun only with basic tags,
* com.ulcjava.container.servlet.server.servlets.ClientJarDownloader
does not support version based downloading, pack200
Also, it would be really good if you could make all ULC jars OSGi
friendly (adding relevant MANIFEST.MF entries) so I can use them as
OSGi bundles. I am trying to integrate ULC with Spring OSGi and run
it
in SpringSource Application Platform.
I would like to thank your team for putting great effort into
improving ULC and I hope my suggestions will help you make the
product
better.
Best Regards
Vlado
----------------------------------------------------------------------
---- Tato sprava a vsetky pripojene subory su doverne a urcene
vyhradne osobam alebo organizaciam, ktorym boli adresovane. Ak ste
dostali tento e- mail omylom, prosim, upovedomte Chemosvit, a.s.
([EMAIL PROTECTED]).
This email and any files transmitted are confidential and intended
solely for the use of the individual or entity to which they are
addressed. If you have received this email in error, please notify
Chemosvit, a.s. ([EMAIL PROTECTED]).
----------------------------------------------------------------------
-----
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
--------------------------------------------------------------------------
Tato sprava a vsetky pripojene subory su doverne a urcene vyhradne
osobam
alebo organizaciam, ktorym boli adresovane. Ak ste dostali tento e-
mail
omylom, prosim, upovedomte Chemosvit, a.s. ([EMAIL PROTECTED]).
This email and any files transmitted are confidential and intended
solely for the use of the individual or entity to which they are
addressed. If you have received this email in error, please notify
Chemosvit, a.s. ([EMAIL PROTECTED]).
--------------------------------------------------------------------------- <
src.zip>
