By the way... if i wanted to make it J2EE compliant, how should it
be ?. Anybody knows a good tutorial ?.
My guess is, please correct me if i'm wrong, Swing in the front end
(presentation tier), and Tomcat running logic tier (implemented by me)
and business tier (hibernate).
The big question is... how do you 'glue' Swing and the logic'n
business tiers?
Thanks!!!
On 12 mayo, 12:21, mcorle...@gmail.com wrote:
> Swing then, it won't be J2EE, and i'll use just one '?' in the future.
>
[quoted text clipped - 30 lines]
>
> - Mostrar texto de la cita -
>By the way... if i wanted to make it J2EE compliant, ...
Please refrain from top-posting, I find it most confusing.
<http://www.physci.org/codes/javafaq.html#toppost>
J2EE is Sun's name for stuff that generally occurs on the
server. A web site generated by Java would use J2EE.
J2SE is Sun's name for 'core and desktop' API's, the
GUI parts include AWT (uses native components) and
Swing (has richer toolset). SWT is another GUI toolkit
(obviously).
A J2EE powered server might put output to a browser,
as HTML, or HTML improved with Javascript, or to an
(AWT) Applet, or a (Swing) JApplet, or an AWT or
Swing based application, or the web started versions
of the same. I am not sure about SWT (shrugs).
A J2SE based GUI to would usually be refered to as a
rich client, and the HTML equivalent, a 'thin client' (as
opposed to a 'poor client' ;).
J2EE is important to understand, but before you attempt
it, you should have a good understanding of (at least) the
non-GUI parts of the J2SE, because in J2EE programming,
you often find yourself importing J2SE classes!
>..how should it be ?
>... Anybody knows a good tutorial ?.
For the J2SE, I recommend Sun's own 'Java Tutorial'.
It be downloaded or browsed on-line.
<http://java.sun.com/docs/books/tutorial/>
>My guess is, please correct me if i'm wrong, Swing in the front end
>(presentation tier), and Tomcat running logic tier (implemented by me)
>and business tier (hibernate).
>
>The big question is... how do you 'glue' Swing and the logic'n
>business tiers?
..hmm. Just checking, but you do realise that you
can do all of 'purely desktop' applications *without*
a server at all, right? What is the application?
If you need a server, what do you actually need it for?
What information for the application changes?
Does the app. offer the viewing/editing of information
held in a central location?

Signature
Andrew Thompson
http://www.athompson.info/andrew/
Lew - 12 May 2007 18:43 GMT
mcorleone@gmail.com wrote:
>> My guess is, please correct me if i'm wrong, Swing in the front end
>> (presentation tier), and Tomcat running logic tier (implemented by me)
>> and business tier (hibernate).
No. Swing is not for JEE apps, generally. (Nor is SWT; they serve the same
architectural niche.)
As Andrew said, you might invoke an applet that uses Swing, but that has
nothing to do with JEE either.
Swing (SWT) => desktop or applet.
Not JEE.
JEE uses servlets, HTML and JSP for the front end. (Use JSP, not "raw"
servlets.) There can be client-side scripting there, too.
Not Swing.

Signature
Lew
mcorleone@gmail.com - 12 May 2007 21:06 GMT
> Please refrain from top-posting, I find it most confusing.
> <http://www.physci.org/codes/javafaq.html#toppost>
Thanks for the tip Andrew
> .hmm. Just checking, but you do realise that you
> can do all of 'purely desktop' applications *without*
> a server at all, right? What is the application?
Now i get it, i hadn't understood clearly the difference between J2EE
and J2SE. The application has to generate invoices, and control stock.
> If you need a server, what do you actually need it for?
> What information for the application changes?
> Does the app. offer the viewing/editing of information
> held in a central location?
Yes, it allows viewing / editing, and right now, only in a central
location. But i was just trying to find a better way of designing the
whole thing. Suppose that i get a request (in six months) to allow
more than one instance, in different machines. A central server,
working with SOAP, providing persistance functions, and a client
written in swing, sounds nice.
I've got experience working with Webwork (similar to Struts) and
Hibernate -which is, as far as i understand now, J2EE-. But i got
requested to make this development standalone, non-web, and that's the
reason behind Swing.
Also, it also seems easy to implement the invoice-printing code. I
have no idea how to work around that in a web development. Exporting a
report as PDF and printing it from acrobat looks awful.
Thank you again,
Regards!!
Lew - 13 May 2007 17:20 GMT
> Also, it also seems easy to implement the invoice-printing code. I
> have no idea how to work around that in a web development. Exporting a
> report as PDF and printing it from acrobat [sic] looks awful.
Actually, it's a very clean and easy solution, although Acrobat is not
required. It works for both desktop and web apps.

Signature
Lew