<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Spring AMQP...<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://static.springsource.org/spring-amqp/reference/html/">http://static.springsource.org/spring-amqp/reference/html/</a><br>
<br>
...brings, to AMQP, the familiar benefits of Spring (high level
abstractions - eliminating boilerplate code, while providing access
to lower level APIs when necessary, consistent exception hierarchy
across different vendor implementations, etc).<br>
<br>
It also provides a listener container, enabling message-driven
POJOs, thus eliminating all infrastructure dependencies from
application code.<br>
<br>
While clearly aimed at existing Spring users, who are already aware
of these benefits, we feel it is equally applicable to those users
who are not (yet) using Spring.<br>
<br>
Gary<br>
<br>
On 02/27/2012 10:13 PM, preeti sp wrote:
<blockquote
cite="mid:1330398784.33543.YahooMailClassic@web39301.mail.mud.yahoo.com"
type="cite">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="font: inherit;" valign="top">Hi
<div>Do we get any advantages If we use Spring AMQP over
Java Client Library or vice-versa?</div>
<div><br>
</div>
<div>Is it advised to use Spring AMQP If we do not intend
to primarily use Spring as such?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Preeti</div>
</td>
</tr>
</tbody>
</table>
</blockquote>
</body>
</html>