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

List:       jboss-user
Subject:    [jboss-user] [JBoss Tools] - How do we use JBoss Tools with the JBoss AS 7 Fedora package?
From:       Dan Allen <do-not-reply () jboss ! com>
Date:       2012-05-31 8:42:56
Message-ID: 2-738954-3-4200-1338453772971.jivesbs.jivemailuser () https://community ! jboss ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Dan Allen [https://community.jboss.org/people/dan.j.allen] created the discussion

"How do we use JBoss Tools with the JBoss AS 7 Fedora package?"

To view the discussion, visit: https://community.jboss.org/message/738954#738954

--------------------------------------------------------------
As you may have heard,  \
https://plus.google.com/114112334290393746697/posts/9Ri8U4wuCLY JBoss AS 7 is now \
packaged in Fedora 17. It can be installed using the YUM package manager:

yum install jboss-as


This package not only puts JBoss AS 7 on your system, it also makes it a bonafide \
system service. You start the service using the service command:

service jboss-as start


The service runs as the jboss-as user. The main installation directory is \
/usr/share/jboss-as, though the executables are in /usr/bin and the logs in \
/var/log/jboss-as.

*JBoss Tools: Prerequisties*

It's necessary to create a management user in order for JBoss Tools to control the \
server:

/usr/share/jboss-as/bin/add-user.sh


*JBoss Tools: What works*

JBoss Tools detects the installation when the scanner is pointed at \
/usr/share/jboss-as and properly sets up a server runtime. (The server configuration \
needs to be updated to mark the server as externally managed since JBoss Tools is not \
privy to the startup scripts anymore, nor would the user have the proper \
permissions). Navigating the management interface in the Server view works as \
expected.

*JBoss Tools: What doesn't work*

What JBoss Tools is unable to do is deploy an application to the server (for example \
the numberguess quickstart). The problem is that *+JBoss Tools tries to copy files \
into the /usr/share/jboss-as/standalone/deployments directory+*, but doesn't have \
permission to write to this directory.

An obvious quickfix is to add the user to the jboss-as group and change the \
permission of /var/lib/jboss-as/standalone/deployments to 664 w/ the group sticky \
flag set (so that the file is written with the group set to jboss-as).

However, I think the way it should work is that *+JBoss Tools should deploy the \
application using the management interface+*. Currently, this would require deploying \
the application as a packaged war. *+The server runtime can be configured to deploy a \
packaged war, but JBoss Tools still tries to copy the archive to the deployment \
folder+* rather than using the management interface deployment API.

Ideally, JBoss Tools should support incremental deployment over the management \
interface rather than a direct file system copy. Another approach would be to tell \
the management interface to look in a different location for a deployment (maybe \
that's possible already).

Long story short, I don't see a way currently to use JBoss Tools with JBoss AS 7 \
installed from the RPM package because of permission issues. Changing the file \
permissions and elevating the permissions of the user is one workaround. Ideally, \
though, JBoss Tools would support this use case without requiring any special \
customization. It would also be nice if JBoss Tools could add a management user \
(replacing the call to the add-user.sh command). Finally, it would be great if JBoss \
Tools could start and stop the jboss-as service (through the use of sudo).

This is new territory for JBoss Tools and I'm excited to see us get to a seamless out \
                of the box experience.
--------------------------------------------------------------

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

Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2128]



[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="https://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;">  How do we use JBoss Tools with the JBoss AS 7 Fedora \
package? </h3>
<span style="margin-bottom: 10px;">
    created by <a href="https://community.jboss.org/people/dan.j.allen">Dan Allen</a> \
in <i>JBoss Tools</i> - <a \
href="https://community.jboss.org/message/738954#738954">View the full discussion</a> \
</span> <hr style="margin: 20px 0; border: none; background-color: #dadada; height: \
1px;">

<div class="jive-rendered-content"><p>As you may have heard, <a \
class="jive-link-external-small" \
href="https://plus.google.com/114112334290393746697/posts/9Ri8U4wuCLY">JBoss AS 7 is \
now packaged in Fedora 17</a>. It can be installed using the YUM package \
manager:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;">&#160;</p><pre \
class="jive-pre"><code class="jive-code">yum install jboss-as </code></pre><p \
style="min-height: 8pt; height: 8pt; padding: 0px;">&#160;</p><p>This package not \
only puts JBoss AS 7 on your system, it also makes it a bonafide system service. You \
start the service using the service command:</p><p style="min-height: 8pt; height: \
8pt; padding: 0px;">&#160;</p><pre class="jive-pre"><code class="jive-code">service \
jboss-as start </code></pre><p style="min-height: 8pt; height: 8pt; padding: \
0px;">&#160;</p><p>The service runs as the jboss-as user. The main installation \
directory is /usr/share/jboss-as, though the executables are in /usr/bin and the logs \
in /var/log/jboss-as.</p><p style="min-height: 8pt; height: 8pt; padding: \
0px;">&#160;</p><p><strong>JBoss Tools: Prerequisties</strong></p><p \
style="min-height: 8pt; height: 8pt; padding: 0px;">&#160;</p><p>It's necessary to \
create a management user in order for JBoss Tools to control the server:</p><p \
style="min-height: 8pt; height: 8pt; padding: 0px;">&#160;</p><pre \
class="jive-pre"><code class="jive-code">/usr/share/jboss-as/bin/add-user.sh \
</code></pre><p style="min-height: 8pt; height: 8pt; padding: \
0px;">&#160;</p><p><strong>JBoss Tools: What works</strong></p><p style="min-height: \
8pt; height: 8pt; padding: 0px;">&#160;</p><p>JBoss Tools detects the installation \
when the scanner is pointed at /usr/share/jboss-as and properly sets up a server \
runtime. (The server configuration needs to be updated to mark the server as \
externally managed since JBoss Tools is not privy to the startup scripts anymore, nor \
would the user have the proper permissions). Navigating the management interface in \
the Server view works as expected.</p><p style="min-height: 8pt; height: 8pt; \
padding: 0px;">&#160;</p><p><strong>JBoss Tools: What doesn't work</strong></p><p \
style="min-height: 8pt; height: 8pt; padding: 0px;">&#160;</p><p>What JBoss Tools is \
unable to do is deploy an application to the server (for example the numberguess \
quickstart). The problem is that <strong><em>JBoss Tools tries to copy files into the \
/usr/share/jboss-as/standalone/deployments directory</em></strong>, but doesn't have \
permission to write to this directory.</p><p style="min-height: 8pt; height: 8pt; \
padding: 0px;">&#160;</p><p>An obvious quickfix is to add the user to the jboss-as \
group and change the permission of /var/lib/jboss-as/standalone/deployments to 664 w/ \
the group sticky flag set (so that the file is written with the group set to \
jboss-as).</p><p style="min-height: 8pt; height: 8pt; padding: \
0px;">&#160;</p><p>However, I think the way it should work is that <strong><em>JBoss \
Tools should deploy the application using the management interface</em></strong>. \
Currently, this would require deploying the application as a packaged war. \
<strong><em>The server runtime can be configured to deploy a packaged war, but JBoss \
Tools still tries to copy the archive to the deployment folder</em></strong> rather \
than using the management interface deployment API.</p><p style="min-height: 8pt; \
height: 8pt; padding: 0px;">&#160;</p><p>Ideally, JBoss Tools should support \
incremental deployment over the management interface rather than a direct file system \
copy. Another approach would be to tell the management interface to look in a \
different location for a deployment (maybe that's possible already).</p><p \
style="min-height: 8pt; height: 8pt; padding: 0px;">&#160;</p><p>Long story short, I \
don't see a way currently to use JBoss Tools with JBoss AS 7 installed from the RPM \
package because of permission issues. Changing the file permissions and elevating the \
permissions of the user is one workaround. Ideally, though, JBoss Tools would support \
this use case without requiring any special customization. It would also be nice if \
JBoss Tools could add a management user (replacing the call to the add-user.sh \
command). Finally, it would be great if JBoss Tools could start and stop the jboss-as \
service (through the use of sudo).</p><p style="min-height: 8pt; height: 8pt; \
padding: 0px;">&#160;</p><p>This is new territory for JBoss Tools and I'm excited to \
see us get to a seamless out of the box experience.</p></div>

<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
    <p style="margin: 0;">Reply to this message by <a \
href="https://community.jboss.org/message/738954#738954">going to Community</a></p>  \
<p style="margin: 0;">Start a new discussion in JBoss Tools at <a \
href="https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2128">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] 

Configure | About | News | Add a list | Sponsored by KoreLogic