Well I already use your soultion.
I have same jar file I use on web server and on that client application.
Client application is in frames. Left frame is java applet that
represents search engine. In right frame I show search results and a lot
of html data that user search for (some legal stuff)
So this is combination of java applet +javascript neded for interframe
communication + ...
It seems to me a little dirty so I like to clean that little bit.
I have total separation of applicaion logic and presentation. (3 layers)
Well I start to transfer all of that into full page applet application
but this is tricky because of poor supoort for html +css data and all of
our data is in that format
plus Presentation is often change to reflect some new stuff and it is
annoying to change and test on two different places.
Embeeded tomcat seems intersting solution.
I will make an applet that load tomcat and then redirect to start page
and let tomcat hadle from that point.
But Im not sure how that will work?!
And more important in that way tomcat have to listen on some port and
that can be huge problem for me with all the coroprate firewalls and
unprivileged users.
If i can use tomcat embedded to parse url and generate html without
acting as server that would be ideal, but can I achieve something like
that, or as close as I can.
Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Danilo,
Danilo Cubrovic wrote:
I have web application (java jsf+xml) that works fine on tomcat.
Can I pack somehow web application and tomcat and install it on user client
pc.
This is possible, but probably non-ideal. If your Java applet is pretty
good-looking, consider deploying it as a client-side app (that is,
unwrap the applet into a full-fledged application).
You could take your existing web application and split it up into
components: back-end versus presentation. That shouldn't be all that
hard assuming that you already have a pretty good separation between
your business logic and data access layers versus your presentation layer.
Then, for a web deployment, you simply use your business logic + data
access layers as the foundation (JAR files?) for your web app. The same
can be done for the local deployment.
Perhaps this is not the solution you're looking for, but it's definitely
one option.
Good luck,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFp8Qd9CaO5/Lv0PARAu78AKC59rC3TD4v4ISJZKzEq9h4O36I7wCeO7w1
bMWvdUh5DiH6BFRLWsvZHyI=
=Q/Lf
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
