rookie - Book for Spring - JMS and 3rd Party

[dr_pompeii]

hello guys

for this section of forum

i want to learn JMS with Spring, if is there a good book to learn from the scratch this?,
or special documentation with examples etc etc
pls let me know , i appreciate

a huge doubt i have related with JMS/Spring???
what is better Hessian/Burlap, RMI, and JAX-RPC,
why?
and
when should i choice one of them???

i hope you knowledge

thanks for advanced

p.d: yes, totally rookie in this

[TOPPER_HARLEY]

Hi,
You could try the spring user manual

Seriously though, it does have good examples of getting JMS and Spring up and running for MDPs etc. Thats where I started anyway.

/Tom

[dr_pompeii]

hi harley

You could try the spring user manual

well, is a liitle specific and not very detail it like for beginners,
i need something like a book

it does have good examples of getting JMS and Spring up and running for MDPs etc.

you meant this link
http://static.springframework.org/sp.../remoting.html ??
or other?

the spring distribution has examples of this?

regards

[TOPPER_HARLEY]

Hi,
"Pro Spring" by Rob Harrop is pretty good, though i'm not sure if the new version is out for Spring2.x.

User manual has a chapter for JMS
http://www.springframework.org/docs/reference/jms.html

/Tom

[dr_pompeii]

hi man

Hi,
"Pro Spring" by Rob Harrop is pretty good, though i'm not sure if the new version is out for Spring2.x.

yes, i have the book ,
this only has 1/2 chapter about JMS, and has enough information of course,
what i want to learn this form the scratch, more deeply

User manual has a chapter for JMS
http://www.springframework.org/docs/reference/jms.html

again, the link is not deep or is specific
(i am not saying tha is bad, but i hope you see my point)

including Hessian/Burlap, RMI, and JAX-RPC,

what is better? and why?, better support

regards

[Lyserg]

Hi,

i think there are every time two (nearly indepentend things to learn).
One thing to learn is on how spring remoting works, i think the best source
is the reference manual (and perhaps the demo applications).
The other thing is to learn about the middleware/protocolls that you are using with spring remoting. So for example if you are doing jms, IMHO it is important to have a good knowledge of the jms api and the custom messaging middleware that you are using (activemq, websphere etc..)

regards
agim

[gregturn]

hello guys
what is better Hessian/Burlap, RMI, and JAX-RPC,
why?
and
when should i choice one of them???

Hessian, Burlap, and Spring HTTP require a web container. If you don't want to use any type of container, but run as pure stand alone apps, they won't support you. If web container is an option, then they are up for grabs.

If you want to talk Java-to-nonJava app, Hessian/Burlap are two options to consider. Spring HTTP and RMI and Java-to-Java utilizing java serialization.

JAX-RPC is oriented towards SOAP (I think). According to Pro Java Development with Spring, JAX-RPC takes the most steps to set-up, is probably the most expensive in parsing, but may the most interoperable with other SOAP-based services. I think it needs a web or J2EE container also. (Can't remember).

RMI is the one Java-to-Java solution that requires no container, but may require you to open an extra port in a firewall.

These are some of the pros and cons you must sift through before picking a solution. But thanks to Spring, you should be able to shift easily should and not be bound to rewriting your code due to technology choices.

Personally, my solution is only inside a single intranet, so firewalls are no problem. I like minimal container constraints, so I first picked the RMI option. But my requirements may be totally different on the next project I work, as can be the case for you.

[dr_pompeii]

dear guys

sorry for the delay in my reply and thanks so much by your replies
by order

Jörg

You need a transaction manager - and they work differently. (Have a look at this poll for all the different transaction managers Spring provides as wrapper around the actual transaction API.) You have to choose the correct one carefully.

thanks for the link, just wondered why TransactionProxyFactoryBean not appear in the list

Nothing forces you to use Hessian/Burlap, you just have the option. A protocol based on Http is just better when communicating via the internet. It's also said that Hessian/Burlap are quite efficient protocols.

ok, and better for a intranet i guess

gregturn

Hessian, Burlap, and Spring HTTP require a web container. If you don't want to use any type of container, but run as pure stand alone apps, they won't support you. If web container is an option, then they are up for grabs.

you advice, thanks

If you want to talk Java-to-nonJava app, Hessian/Burlap are two options to consider. Spring HTTP and RMI and Java-to-Java utilizing java serialization.

for the bold part, i am confuse,
nonJava- is another application but not in Java right?
so web services is not here the solution?

RMI is the one Java-to-Java solution that requires no container, but may require you to open an extra port in a firewall.

is old but is appreciate, but little cumbersome i think

But thanks to Spring, you should be able to shift easily should and not be bound to rewriting your code due to technology choices.

yeah, that's right

Personally, my solution is only inside a single intranet, so firewalls are no problem.

i am agree.

I like minimal container constraints, so I first picked the RMI option

is this old in these days?


thanks both for advanced

[gregturn]

dear guys
nonJava- is another application but not in Java right?
so web services is not here the solution?

nonJava = not Java = not-written-in-Java, e.g. Java-to-Python, Java-to-C++, Java-to-PERL, etc. This has nothing to do with web services. I have hand-written web services, in other languages. It all comes down to how you marshal the data before transmitting it on the wire. If you, by hand, build an XML message in pure text, transmit it over a socket possibly using HTTP, and parse it at the other end, thats a web service. Java doesn't hold the monopoly on web services (albeit they may have led the way in the market). Hessian/Burlap are also web services which is why they run in a web container.

However, all of these combinations I just listed don't have Java serialization, which rules them out of being able to use RMI or Spring HTTP. You have to pick either Hessian/Burlap or JAX-RPC (SOAP-y) in this situation.

I'm not sure why you keep referring to RMI as "old". It works. CORBA is old and also works. I'm interested in whether or not something works, not whether or not it is young or old.

In fact, CORBA is about to become my lifesaver in porting an old app into Java. I can only move a piece at a time, and the only way it can communicate with Java is through CORBA. Parts that migrate into Java can refer to the Spring beans directly, while the legacy parts willl talk to the CORBA-exposed proxy. For my convenience, I'm going to use a JEE app server, because it has a CORBA ORB built right into it.

[Jörg Heinicke]

thanks for the link, just wondered why TransactionProxyFactoryBean not appear in the list

Because it is no TransactionManager, but only creates transactional proxies. For getting them to work you need a TransactionManager - and that's what you inject into TransactionProxyFactoryBean.

Jörg