jsp within the same application (in which web services are defined)?
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
Cheers,
Naren
(OCEEJBD6, SCWCD5, SCDJWS, SCJP1.4 and Oracle SQL 1Z0-051)
Vivek Raut wrote:Web service is expensive as it involves forming a verbose XML (SOAP), marshalling and unmarshalling and serialization and deserialization.
Hikari Shidou wrote:The WS must call some internal operation (considering business logic isn't implemented inside it lol).
So why don't you just call that same operation directly?
Now, if you wanna develop a separated client, then yes WS is a good solution. WS isn't just for people that can't access your software directly, it can be used as a client-server communication.
Hikari Shidou wrote:Ok I got that.
But how is your UI? If it's a separated software, WS is a possible solution. But if it's in the same process as your software, it can call those operations directly.
If your software is accessed by many users, you may be wanting to have a server hosting business logic and many clients to interact with users and communicate with your server using WebService, is that it?
WebService is recommended just when different technologies are talking, like Java with C#, or when you wanna provide services to ther softwares with possibility of a future software with different technology to use it too. It takes too much time to transfer and process XML building and parsing, it's not the first technology you should consider for any server-client communication.
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
Praful Thakare wrote:
It takes too much time to transfer and process XML building and parsing, it's not the first technology you should consider for any server-client communication.
I beg to differ , web service dose not only mean JAX-WS, JAX-RS is much simpler and light weight.
Hikari Shidou wrote:I saw a small benchmark comparing SOAP with CORBA, and CORBA is a bit faster.
What I'm talking to him is that Servlet may be a better solution then some Swing (?) client talking via SOAP, and if he'll stay in Java it may be better use RMI.