[jbosstools-commits] JBoss Tools SVN: r39458 - trunk/documentation/whatsnew/as.

jbosstools-commits at lists.jboss.org jbosstools-commits at lists.jboss.org
Tue Mar 13 03:10:46 EDT 2012


Author: rob.stryker at jboss.com
Date: 2012-03-13 03:10:46 -0400 (Tue, 13 Mar 2012)
New Revision: 39458

Added:
   trunk/documentation/whatsnew/as/as-news-3.3.0.Beta1.html
Log:
n&n for astools

Added: trunk/documentation/whatsnew/as/as-news-3.3.0.Beta1.html
===================================================================
--- trunk/documentation/whatsnew/as/as-news-3.3.0.Beta1.html	                        (rev 0)
+++ trunk/documentation/whatsnew/as/as-news-3.3.0.Beta1.html	2012-03-13 07:10:46 UTC (rev 39458)
@@ -0,0 +1,97 @@
+<html>
+
+<head>
+<link rel="stylesheet" href="../whatsnew.css">
+<title>JBoss AS Tools 3.3.0.Beta1 News</title>
+<script type="text/javascript">
+
+  var _gaq = _gaq || [];
+  _gaq.push(['_setAccount', 'UA-17645367-5']);
+  _gaq.push(['_trackPageview']);
+
+  (function() {
+    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+  })();
+
+</script></head>
+
+<body>
+
+<h1>JBoss AS Tools 3.3.0.Beta1 What's New</h1>
+
+  <p align="right"><a href="../index.html">&lt; Main Index</a> <a href="../jst/jst-news-3.3.0.Beta1.html">JST/JSF Tools&gt;</a></p>
+<table border="0" cellpadding="10" cellspacing="0" width="80%">
+
+  <tr>
+    <td colspan="2">
+      <hr/>
+      <h3>Server</h3>
+      <hr/>
+    </td>
+  </tr>
+  <tr>
+    <td valign="top" align="right">
+      <p><b>Bind to All Ports</b></p>
+    </td>
+    <td valign="top" width="90%">
+        <p>Server Tools now supports an option to bind your server to all ports. This usability improvement helps ensure that users don't have to hunt around to allow their application server to accept remote connections. 
+    </p>
+	    <p><img src="https://issues.jboss.org/secure/attachment/12349889/JBIDE-10319.png" alt="bind to all ports image"/></p>
+	    <p><small><a href="https://issues.jboss.org/browse/JBIDE-10319">Related Jira</a></small></p>
+    </td>
+  </tr>  
+  <tr><td colspan="2"><hr /></td></tr>
+  <tr>
+    <td valign="top" align="right">
+      <p><b>Customize application reload behavior</b></p>
+    </td>
+    <td valign="top" width="90%">
+
+      <p>Users can now customize the reload behavior of their application server in a new setting in the server editor. Some users may have aggressive reload strategies during development, while others may prefer more conservative strategies, for example on larger applications that take longer to deploy. Whatever your development workflow strategy is, this new setting can help accomodate you. </p>
+      	    <p><img src="https://issues.jboss.org/secure/attachment/12351312/JBIDE-10464.png" alt="module restart behavior screenshot"/></p>
+      <p><small><a href="https://issues.jboss.org/browse/JBIDE-10464">Related Jira</a></small></p>
+    </td>
+  </tr>  
+  <tr><td colspan="2"><hr /></td></tr>
+  <tr>
+    <td valign="top" align="right">
+      <p><b>Support for Gate-In Server</b></p>
+    </td>
+    <td valign="top" width="90%">
+        <p>The Gate-In server should now start seamlessly without errors. This allows gate-in users to access the same development experience that other JBoss Application Server users have. </p> 
+	    <p><small><a href="https://issues.jboss.org/browse/JBIDE-10680">Related Jira</a></small></p>
+    </td>
+  </tr>  
+  <tr><td colspan="2"><hr /></td></tr>
+  <tr>
+    <td valign="top" align="right">
+      <p><b>Server Editor's Deployment Page has filtering!</b></p>
+    </td>
+    <td valign="top" width="90%">
+        <p>The Deployment page of the server editor allows customizations on a per-module basis for deployment location, and other settings. In the past, some users needed the ability to customize deployment location before a module was added to the server. Unfortunately, this meant all possible modules in the workspace were listed in the table, leading it to be cluttered. </p> 
+         <p>New filter options have been added to fix this situation. Users can now filter this view to showing all possible modules, showing all deployed modules, or filtering based on name. </p>
+	    <p><img src="https://issues.jboss.org/secure/attachment/12351634/JBIDE-10733.png" alt="deployment filter options"/></p>
+	    <p><small><a href="https://issues.jboss.org/browse/JBIDE-10733">Related Jira</a></small></p>
+    </td>
+  </tr>  
+  <tr><td colspan="2"><hr /></td></tr>
+  <tr>
+    <td valign="top" align="right">
+      <p><b>Passwords stored in secure storage</b></p>
+    </td>
+    <td valign="top" width="90%">
+        <p>For enhanced security, passwords are now stored in secured storage. Once every workspace restart, you will be asked to enter your secure storage username and password to access all securely-stored data, but that's a small price to pay for knowing your data is safe with us! </p>
+
+	    <p><small><a href="https://issues.jboss.org/browse/JBIDE-10490">Related Jira</a></small></p>
+    </td>
+  </tr>  
+
+</table>
+
+</body>
+
+</html>
+
+



More information about the jbosstools-commits mailing list