Swing Client

have not worked on Swing much, so would appreciate if somebody can help with some links where i can find some design tutorial/notes/tips etc for Swing.

Thanks
Bhupesh

Originally posted by Bhupesh Arya:
have not worked on Swing much, so would appreciate if somebody can help with some links where i can find some design tutorial/notes/tips etc for Swing.

Thanks
Bhupesh

i dont think we have to enter so much in details, with swing client app : dont you think ? I mean, once you said the travel agent will connect thru a swing app, i think the next step is to say how : protocols, differents subystems ...

what s your opinion ?

tery

Yes. I agree with Tery. I think we only need to specify how the swing client communicate, and then call the various services deployed.

I think we only need to specify how the swing client communicate, and then call the various services deployed.

Plus the architect needs to justify why a swing client was prefered over a thin client.

I think that we should specify also what type of java container swing application uses: generic or J2EE client container

Regards
Marcel

Originally posted by Mahesh Kumaraguru:


Plus the architect needs to justify why a swing client was prefered over a thin client.

I don't think we have to do that since it is a clear customer requirement. Why should you justify the customers decision? It would make sense if you would break that requirement - but that's a no go!

D.

Originally posted by David Follow:

I don't think we have to do that since it is a clear customer requirement. Why should you justify the customers decision? It would make sense if you would break that requirement - but that's a no go!
D.

I think the customer requirement is best performance, the client has not specified that a thick swing client is needed. The choice of thick-vs-thin client is made by architect.

This is being discussed in multiple threads in this forum :-

Topic : Why Swing client at all?

Topic : "Fast lane reader" on the Swing client

and each thread is looking at one side of this thick-vs-thin client ( Swing-vs-browser client ).

David

The only customer requirement for the user interface is that it should be graphical. We have to justify why we preferred a standalone swing application. There are other web based choices: applet, java webstart. java server faces (you can build reach visual components).

Regards

Marcel

thanks guys,

i decided to show that there are some swing widgets that coordinate with other classes to connect to the required EJB services.

bhupesh