'[jboss-user] [JNDI and Naming] - Re: Using JNDI to connect to'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: jboss-user
Subject: [jboss-user] [JNDI and Naming] - Re: Using JNDI to connect to
From: Stuart Clayton <do-not-reply () jboss ! com>
Date: 2011-09-30 1:24:27
Message-ID: 2-619269-3-68410-1312411260606-2-629454-3-89549-1317345864856.jivesbs.jivemailuser () http://community ! jboss ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Stuart Clayton [http://community.jboss.org/people/stuartclayton22] created the \
discussion

"Re: Using JNDI to connect to Websphere MQ, without hardcoded info"

To view the discussion, visit: http://community.jboss.org/message/629454#629454

--------------------------------------------------------------
zecas, you write: "So since I was going for an MDB in EJB3, I was not thinking about \
the need for an ejb-jar.xml on the project". Of course you weren't ! What we are \
doing here is fighting EJB3 tooth and nail, in order to get back to EJB2

Of course EJB2 was a terrible mess, but it did get one thing exactly right: a clean \
separation of "deployment" and "development" mechanisms. One aspect of deployment was \
the ability to configure without having to change code.   

EJB3 has now melted deployment and development together to get one inflexible \
mechanism: "annotations". I'll tell you why I think this was done: so that \
inexperienced programmers who don't have a clue about what's involved can quickly \
write code that "runs" in a fixed environment. EJB3 creates an illusion of \
productivity improvement. The price you pay for this illusion is administrative \
                nightmares.
--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/629454#629454]

Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2083]

[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; \
margin: 0; padding: 20px;">

<div>
	<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: \
1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; \
-webkit-border-radius: 6px;">  <tbody>
			<tr>

				<td>

					<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" \
style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: \
6px; -webkit-border-radius: 6px;">  <tbody>
							<tr>
								<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px \
solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; \
-moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; \
                -webkit-border-top-left-radius: 5px;">
									<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; \
                margin: 0; display: block !important;">
									<!-- To have a header image/logo replace the name below with your img tag \
                -->
									<!-- Email clients will render the images when the message is read so any \
                image -->
									<!-- must be made available on a public server, so that all recipients can \
                load the image. -->
									<a href="http://community.jboss.org/index.jspa" style="text-decoration: \
none; color: #E1E1E1">JBoss Community</a></h1>  </td>

							</tr>
							<tr>
								<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; \
color:#333333; padding: 20px;  -moz-border-radius-bottomleft: 4px; \
-moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; \
-webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: \
17px; font-weight: normal;">  Re: Using JNDI to connect to Websphere MQ, without \
hardcoded info </h3>
<span style="margin-bottom: 10px;">
    created by <a href="http://community.jboss.org/people/stuartclayton22">Stuart \
Clayton</a> in <i>JNDI and Naming</i> - <a \
href="http://community.jboss.org/message/629454#629454">View the full discussion</a> \
</span> <hr style="margin: 20px 0; border: none; background-color: #dadada; height: \
1px;">

<div class="jive-rendered-content">zecas, you write: "So since I was going for an \
MDB in EJB3, I was not thinking about the need for an ejb-jar.xml on the project". Of \
course you weren't ! What we are doing here is fighting EJB3 tooth and nail, in order \
to get back to EJB2&#160;Of course EJB2 was a terrible mess, but it did get one thing \
exactly right: a clean separation of "deployment" and "development" mechanisms. One \
aspect of deployment was the ability to configure without having to change \
code.&#160; &#160;EJB3 has now melted deployment and development together to get one \
inflexible mechanism: "annotations". I'll tell you why I think this was done: so that \
inexperienced programmers who don't have a clue about what's involved can quickly \
write code that "runs" in a fixed environment. EJB3 creates an illusion of \
productivity improvement. The price you pay for this illusion is administrative \
nightmares. </div>

<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
    <p style="margin: 0;">Reply to this message by <a \
href="http://community.jboss.org/message/629454#629454">going to Community</a></p>  \
<p style="margin: 0;">Start a new discussion in JNDI and Naming at <a \
href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2083">Community</a></p>
 </div></td>
                        </tr>
                    </tbody>
                </table>

                </td>
            </tr>
        </tbody>
    </table>

</div>

</body>
</html>

_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[prev in list] [next in list] [prev in thread] [next in thread] 