JBoss Tools SVN: r20654 - branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US.
7:12 a.m.
Author: ochikvina
Date: 2010-03-04 08:12:09 -0500 (Thu, 04 Mar 2010)
New Revision: 20654
Modified:
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Article_Info.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Release_Notes.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/master.xml
Log:
<html><head><meta name="qrichtext" content="1"
/></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1107 -Updated docs source files here with
the ones for JBDS 3.0.0 GA release. </p>
<p></p>
</body></html>
Modified:
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Article_Info.xml
===================================================================
---
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Article_Info.xml 2010-03-04
13:08:09 UTC (rev 20653)
+++
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Article_Info.xml 2010-03-04
13:12:09 UTC (rev 20654)
@@ -1,3 +1,3 @@
<?xml version='1.0' encoding='utf-8' ?>
-<articleinfo><title>Release Notes</title><subtitle>Information
about the changes made to this JBoss Developer Studio
release.</subtitle><productname>JBoss Developer
Studio</productname><productnumber>3.0</productnumber><edition>0</edition><pubsnumber>0</pubsnumber><abstract><para>These
release notes contain important information related to the JBoss Developer Studio. New
features, known problems, resources, and other current issues are addressed
here.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata
fileref="Common_Content/images/title_logo.svg"
format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include
href="Common_Content/Legal_Notice.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g...
href="Author_Group.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g...
+<articleinfo><title>Release Notes</title><subtitle>Information
about the changes made for this release of the JBoss Developer
Studio.</subtitle><productname>JBoss Developer
Studio</productname><productnumber>3.0</productnumber><edition>0</edition><pubsnumber>0</pubsnumber><abstract><para>These
release notes contain important information related to the JBoss Developer Studio. New
features,<!-- known problems,--> resources, and other current issues are addressed
here.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata
fileref="Common_Content/images/title_logo.svg"
format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include
href="Common_Content/Legal_Notice.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g...
href="Author_Group.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g...
Modified:
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
---
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml 2010-03-04
13:08:09 UTC (rev 20653)
+++
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml 2010-03-04
13:12:09 UTC (rev 20654)
@@ -18,7 +18,7 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5355">JBIDE-535...;:
A Contexts and Dependency Injection Project Facet has been added to
<application>JBoss Developer Studio</application>.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5355">JBIDE-535...;:
A Contexts and Dependency Injection Project Facet has been added to
<application>JBoss Developer Studio</application>. This makes it possible to
enable CDI support for a faceted project via the <guilabel>New Dynamic Web
Project</guilabel> wizard or the <guilabel>Project Facets</guilabel>
setting page available at
<menuchoice><guimenuitem>Project</guimenuitem><guimenuitem>Properties</guimenuitem><guimenuitem>Project
Facets</guimenuitem></menuchoice>.
</para>
</listitem>
<listitem>
@@ -35,13 +35,13 @@
<itemizedlist>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5653">JBIDE-565...;:
The <guilabel>ESB Content Based Router </guilabel> dialog box has been
modified so that the <guilabel>CBR Alias</guilabel> field is now mondatory,
allowing the value of it to determine what other fields are available. The
<guilabel>Rule Set</guilabel> field is now not required when a
<guilabel>CBR Alias</guilabel> of Regex or XPath is provided, since with these
alias the rules can be specified inline and the <guilabel>Rule
Language</guilabel> field is now set to apply only when the <guilabel>CBR
Alias</guilabel> is Drools. The <guilabel>Rules Reload</guilabel> field
will only apply when a <guilabel>Rule Set</guilabel> has been specified.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5653">JBIDE-565...;:
The <guilabel>ESB Content Based Router </guilabel> dialog box has been
modified so that the <guilabel>CBR Alias</guilabel> field is now mandatory,
allowing the value of it to determine what other fields are available. The
<guilabel>Rule Set</guilabel> field is now not required when a
<guilabel>CBR Alias</guilabel> of Regex or XPath is provided, since with these
alias the rules can be specified in-line and the <guilabel>Rule
Language</guilabel> field is now set to apply only when the <guilabel>CBR
Alias</guilabel> is Drools. The <guilabel>Rules Reload</guilabel> field
will only apply when a <guilabel>Rule Set</guilabel> has been specified.
</para>
<para>
The table <guilabel>Route List</guilabel> found in the
<guilabel>JBoss ESB Editor</guilabel> now lists the
<emphasis>expression</emphasis> since this is a common undertaking by users.
</para>
<para>
- In the <guilabel> Add Route To</guilabel> dialog box, the
<guilabel>Service Category</guilabel> field has been made mandatory. Other
changes to this dialog box include the <guilabel>Desitination name</guilabel>
only being required if the previous CBR action contained a <guilabel>Rule
Set</guilabel> and if the CBR action did not contain a <guilabel>Rule
Set</guilabel>, an <guilabel>Expression</guilabel> field is included.
+ In the <guilabel> Add Route To</guilabel> dialog box, the
<guilabel>Service Category</guilabel> field has been made mandatory. Other
changes to this dialog box include the <guilabel>Destination name</guilabel>
only being required if the previous CBR action contained a <guilabel>Rule
Set</guilabel> and if the CBR action did not contain a <guilabel>Rule
Set</guilabel>, an <guilabel>Expression</guilabel> field is included.
</para>
</listitem>
<listitem>
@@ -71,12 +71,12 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5427">JBIDE-542...;:
In the ESB Editor, the items that displayed when right clicking and going to
<menuchoice><guimenuitem>Provider</guimenuitem><guimenuitem>New</guimenuitem></menuchoice>
were presented in a different order to those of the
<menuchoice><guimenuitem>Listner</guimenuitem><guimenuitem>New</guimenuitem></menuchoice>
list. To ensure consistency the <guimenuitem>Provider</guimenuitem> list of
items has been reordered to match the <guimenuitem>Listner</guimenuitem>
menu.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5427">JBIDE-542...;:
In the ESB Editor, the items that displayed when right clicking and going to
<menuchoice><guimenuitem>Provider</guimenuitem><guimenuitem>New</guimenuitem></menuchoice>
were presented in a different order to those of the
<menuchoice><guimenuitem>Listener</guimenuitem><guimenuitem>New</guimenuitem></menuchoice>
list. To ensure consistency the <guimenuitem>Provider</guimenuitem> list of
items has been reordered to match the <guimenuitem>Listener</guimenuitem>
menu.
</para>
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5229">JBIDE-522...;:
ESB 4.7 that is contained within <application>JBoss SOA Platform
5.0</application> is now offically supported in this version of the
<application>JBoss Developer Studio</application>.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5229">JBIDE-522...;:
ESB 4.7 that is contained within <application>JBoss SOA Platform
5.0</application> is now officially supported in this version of the
<application>JBoss Developer Studio</application>.
</para>
</listitem>
<listitem>
@@ -86,9 +86,34 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5108">JBIDE-510...;:
The JBoss Runtime Manager was setup to search for ESB Runtime files from a specified
location reguardless of how it was installed. This caused issue when the ESB Runtime was
installed as a user defined runtime. The issue has been rectified by adding a
<guilabel>Configuration</guilabel> field to the
<guilabel>Preference</guilabel> page. If the user sets the
<guilabel>Configuration</guilabel> field to the home location of the
<application>JBoss Enterprise Application Platform</application> or
<application>JBoss SOA Platform</application>, there configuration combination
will list all available configurations. If the user selects a standalone ESB Runtime
location, the configuration combination will be empty and the user should ignore the
field. The ESB runtime classpath container now gathers configuration information from the
selected server runtime and then selects JARs accordingly or the s!
tandalone ESB Runtime.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5108">JBIDE-510...;:
The JBoss Runtime Manager was setup to search for ESB Runtime files from a specified
location regardless of how it was installed. This caused issue when the ESB Runtime was
installed as a user defined runtime. The issue has been rectified by adding a
<guilabel>Configuration</guilabel> field to the
<guilabel>Preference</guilabel> page. If the user sets the
<guilabel>Configuration</guilabel> field to the home location of the
<application>JBoss Enterprise Application Platform</application> or
<application>JBoss SOA Platform</application>, there configuration combination
will list all available configurations. If the user selects a standalone ESB Runtime
location, the configuration combination will be empty and the user should ignore the
field. The ESB runtime classpath container now gathers configuration information from the
selected server runtime and then selects JARs accordingly or the st!
andalone ESB Runtime.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4730">JBIDE-473...;:
The ESB project creation wizard receives a new logo following this update. Instead of
using the generic <application>JBoss Developer Studio</application> logo
within the ESB project wizard, a new ESB wizard logo is displayed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4320">JBIDE-432...;:
ESB projects are now Web Tools Platform (WTP) modules. This ensures that it is possible to
use an ESB module inside a WAR or EAR archive within WTP. ESB project deployment has not
been limited though and they can still be deployed as an individual module.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4168">JBIDE-416...;:
The ability to select a directory using a browser window has been added for the FS Message
Filter and the FTP Message filter attributes of
<property>directory</property>,
<property>post-directory</property> and
<property>error-directory</property>. This added feature ensures that a user
does not need to manually type the entire path to a directory but instead they just select
the path from a browser.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2024">JBIDE-202...;:
The <guilabel>Process</guilabel> field f the
<guilabel>Action</guilabel> tab in the ESB now includes a
<guibutton>Browse</guibutton> button that allows a user to select which method
of the <classname>Action</classname> class should be used for the process. The
list in the dialog will show all public methods that has a
<property>Message</property> parameter. Multiple methods can be selected if
necessary.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2023">JBIDE-202...;:
The <guilabel>Class</guilabel> field of the
<guilabel>Action</guilabel> tab now includes a
<guibutton>Browse</guibutton> button that displays the possible classes that
extend from the <classname>AbstractActionLifecycle</classname> class.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -108,7 +133,7 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5641">JBIDE-564...;:
When specifying the persistence property: <property><property
name="hibernate.ejb.cfgfile"
value="hibernate.cfg.xml"/></property>, an error could display
saying that the <filename>hibernate.cfg.xml</filename> file could not be
found. This occured because the validator only considered full paths and not relative path
naming. This has since been corrected through the modification of the
<classname>HibernatePersistenceUnit</classname> class.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5641">JBIDE-564...;:
When specifying the persistence property: <property><property
name="hibernate.ejb.cfgfile"
value="hibernate.cfg.xml"/></property>, an error could display
saying that the <filename>hibernate.cfg.xml</filename> file could not be
found. This occurred because the validator only considered full paths and not relative
path naming. This has since been corrected through the modification of the
<classname>HibernatePersistenceUnit</classname> class.
</para>
</listitem>
<listitem>
@@ -145,7 +170,7 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5222">JBIDE-522...;:
A new feature as been added that allows for support of <guilabel>filter
configurations in closed porjects</guilabel> for console configuration. This option
is available through
<menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>Run/Debug</guimenuitem><guimenuitem>Launching</guimenuitem><guimenuitem>Launch
Configurations</guimenuitem></menuchoice>.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5222">JBIDE-522...;:
A new feature as been added that allows for support of <guilabel>filter
configurations in closed projects</guilabel> for console configuration. This option
is available through
<menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>Run/Debug</guimenuitem><guimenuitem>Launching</guimenuitem><guimenuitem>Launch
Configurations</guimenuitem></menuchoice>.
</para>
</listitem>
<listitem>
@@ -173,6 +198,41 @@
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4899">JBIDE-489...;:
The <guilabel>Hibernate Configurations</guilabel> view was not updated after a
hibernate console enabled project with console configuration was deleted from the
workspace. This meant that the console configuration was not removed along with the
project. This bug is rectified with this update.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4780">JBIDE-478...;:
The <guilabel>Options</guilabel> tab now allows you to browse and set the
<property>NamingStrategy</property> and
<property>EntityResolver</property>. The console configuration option has also
been updated to react when one of the packages of a referenced class changes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4733">JBIDE-473...;:
A new feature has been added that allows a user to select wheather JPA-Generate DDL should
be executed in the database. Before this update this feature was automatic, always
executing JPA-Generate in the database.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4715">JBIDE-471...;:
A toggle button has been added to the Hibernate Mapping diagram to allow the outline view
to be ordered either alphabetically or by the structure outlined in the file. The toggle
button interface ensures the experience remains consistent across all tools included
within the <application>JBoss Developer Studio</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4666">JBIDE-466...;:
Annotations support has been added to Hibernate Tools. The addition of annotations support
allows for interaction with the Eclipse Dali Java Persistence Tools Project plug-in.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4451">JBIDE-445...;:
The option is now given to the user to enable the <guilabel>HQL
Editor</guilabel> and <guilabel>Hibernate Criteria Editor</guilabel> to
be dynamically updated when opening a new query instead of opening an instance of each
editor for each query. This can be achieved by clicking the button of a tack to the right
of the <guilabel>Max results:</guilabel> drop-won box in the editor.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4450">JBIDE-445...;:
The <guilabel>Properties</guilabel> view has been updated with a new property
called <property>Tab name</property>. The addition of this property allows for
a user to individually name each query tab, allowing for improved tab management.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4227">JBIDE-422...;:
The <guimenuitem>Open Mapping File</guimenuitem> option now supports all
possible configuration files. In the past only files called
<filename>orm.xml</filename> have been supported and this update now provides
increased user functionality.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -240,6 +300,46 @@
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4978">JBIDE-497...;:
<application>KBbuilder</application> now loads composite components from the
JSF resource folders and adds them to the KB module. This allows for the components to be
available for code assistance.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4771">JBIDE-477...;:
The <property>Find Usages</property> function has been improved to provide
information about methods when inside an EL expression.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2806">JBIDE-280...;:
The Eclipse OpenOn feature that allows a user to click any reference to a template as if
it was a hyperlink did not work if the template path was set using an EL variable. This
limitation has now been corrected so that OpenOn works with all paths, including those set
using the EL variable. This is a great advantage to users as the Expression Language
variable is a frequently used feature.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-816">JBIDE-816&...;: A
bug existed within the JSF component of the <application>JBoss Developer
Studio</application> where if a resource bundle is defined in a template page code
completion for the bundle would not be available within the file that includes the
template with the loadbundles. The workaround for this was to also define the resource
bundle in this template client file, however that meant the same component was defined
twice in the component tree.
+ </para>
+ <para>
+ The bug has since been fixed by adding a schema for included page contexts. This
schema enables the creation of contexts for all the pages included in the source and for
the gathering of information on bundles declared in the included pages. The information
collected is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Namespaces that are declared
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tag libraries that are used
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Resource bundles that are declared
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-512">JBIDE-512&...;:
The drop-down box for context variable code completion has been upgraded for enhanced
usability. The source of the variable is now outlined during code completion and the code
is highlighted in a different colour for improved reading and overall understanding of
each file.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -271,7 +371,7 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5221">JBIDE-522...;:
The <guilabel>JBoss Server View</guilabel> has now been replaced with the
<guilabel>Server View</guilabel> in the Seam perspective. This has occured out
of the <guilabel>JBoss Server View</guilabel> being depricated.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5221">JBIDE-522...;:
The <guilabel>JBoss Server View</guilabel> has now been replaced with the
<guilabel>Server View</guilabel> in the Seam perspective. This has occurred
out of the <guilabel>JBoss Server View</guilabel> being deprecated.
</para>
</listitem>
<listitem>
@@ -308,14 +408,49 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4987">JBIDE-498...;:
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4987">JBIDE-498...;:
Seam and JPA Connection Profiles have been synchronized for this release. The
<filename>jpa-connection</filename> profile is used in the launch
configuration instead of <filename>hibernate.properties</filename> if the JPA
facet is installed.
</para>
</listitem>
<listitem>
<para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4985">JBIDE-498...;:
Seam projects now create a Hibernate configuration that uses the selected connection
profile directly (without copying its settings into the
<filename>hibernate.properties</filename> file).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4944">JBIDE-494...;:
The Seam wizards <guilabel>Action</guilabel>,
<guilabel>Entity</guilabel> and <guilabel>Conversation</guilabel>
had the ability to overwrite resources when they generated code. The wizards would warn
the user that some resources already existed and yet overwrite them. This has been
corrected through the modification of the
<filename>SeamBaseOperation.java</filename> file.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4856">JBIDE-485...;:
Seam component methods and properties used in the Expression Language (EL) have been
refactored. This has caused the internal structure of the components to be modified so
that the <classname>Query Participant</classname> works with the JDT Java
Search to find usages and append them to search results. The <classname>Rename
Participant</classname> has also been modified to work with the JDT Java Refactor to
rename usages and apply changes to the Java Refactor, allowing for a user to rename a
<emphasis>setter</emphasis> or <emphasis>getter</emphasis> method
and have the <classname>Rename Participant</classname> warn the user of the
consequences of renaming a paired method.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4136">JBIDE-413...;:
Classloading issues were being faced by users of Seam Tools because the
<application>JBoss Developer Studio</application> used the
<filename>MANIFEST.MF</filename> file for creating an artifact classpath
instead of using the EAR <filename>lib/</filename> directory that is
recommended by Seam. Until now the <application>JBoss Developer
Studio</application> has not been able to use the EAR
<filename>lib/</filename> directory because this functionality has not been
supported by Eclipse. With the introduction of Eclipse 3.5 in this release the use of the
EAR <filename>lib/</filename> directory is now supported and the process of
creating an artifact classpath has been updated.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2807">JBIDE-280...;:
An option is now provided when creating a <guilabel>New Seam
Project</guilabel>, to not create a test project. This has become an option since
the Seam model does not require the test project to exist and so allows the user to decide
if it is of importance. Selecting to create or not create a test project is achieved
through the ticking of a <guilabel>Create Test Project</guilabel> check box
within the <guilabel>New Seam Project</guilabel> wizard.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-1452">JBIDE-145...;:
Support has been added for the Seam PDF Facelet tag library. This Facelet library allows
for PDF creation from within Seam.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-1451">JBIDE-145...;:
Support has been added for the Seam Mail Facelet tag library. This Facelet library allows
for email forms to be created from within Seam. All components of the Facelet have been
included except <property>mail:message</property> and
<property>mail:body</property> as these components are rendered as divisions
(using the <div> tag).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-1176">JBIDE-117...;:
The Seam Web Project now supports the JPA facet. Addition of the Java Persistence API
allows for the management of relational data within applications.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -421,7 +556,7 @@
</listitem>
<listitem>
<para>
- The <methodname>createPartControl()</methodname> method in the
<classname>MozillaEditor</classname> and
<classname>MozillaPreview</classname> classes create
<classname>XullRunnerEditor</classname> as an inner class. The issue was that
the <classname>XullRunnerEditor</classname> class retained a reference to
<classname>MozillaEditor(MozillaPreview)</classname> that caused it not to be
released and instead retain references to WST and EMF classes. This has now been corrected
so that <classname>MozillaEditor(MozillaPreview)</classname> is now released
after use and referecnes are not retained.
+ The <methodname>createPartControl()</methodname> method in the
<classname>MozillaEditor</classname> and
<classname>MozillaPreview</classname> classes create
<classname>XullRunnerEditor</classname> as an inner class. The issue was that
the <classname>XullRunnerEditor</classname> class retained a reference to
<classname>MozillaEditor(MozillaPreview)</classname> that caused it not to be
released and instead retain references to WST and EMF classes. This has now been corrected
so that <classname>MozillaEditor(MozillaPreview)</classname> is now released
after use and references are not retained.
</para>
</listitem>
</itemizedlist>
@@ -448,7 +583,7 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4934">JBIDE-493...;:
Facelets tag librarys support has been added to the
<guilabel>Palette</guilabel> for the Visual Page Editor.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4934">JBIDE-493...;:
Facelets tag library support has been added to the
<guilabel>Palette</guilabel> for the Visual Page Editor.
</para>
</listitem>
<listitem>
@@ -456,6 +591,98 @@
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4914">JBIDE-491...;:
The Visual Page Editor has been redesigned so that all drop-down menu items are placed in
the toolbar as buttons.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4323">JBIDE-432...;:
Zoom actions have been added to the visual context menu so that a user can now resize the
content of the Visual Page Editor to make it easier to read and manage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2820">JBIDE-282...;:
Support for new JSF 2.0 elements has been added to the Visual Page Editor. The tags that
are newly supported are:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ h:head
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:body
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:outputscript
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:outputstyle
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:button
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:link
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:ajax
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:event
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:validateBean
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:validateRequired
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:viewParam
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:metadata
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2571">JBIDE-257...;:
Selection of the <property><h:selectOneMenu></property> did not
function correctly. Instead of being selected with one mouse click, two clicks were
necessary. A bug was also present that made the nested components
<property><f:selectItem></property> and
<property><f:selectItems></property> unable to be selected from
within the Visual Page Editor. Correction of the two clicks necessary to select the
<property><h:selectOneMenu></property> component has been
completed by removing the check within <filename>VpeController.java</filename>
that ensures the node is of type text. The issue that did not allow for the selection of
the <property><f:selectItem></property> and
<property><f:selectItems></property> components was found to be
a bug in XULRunner. To correct this the XULRunner component has been updated to version
1.9, which corrects this error and provides!
numerous other small bug fixes (<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2248">JBIDE-224...;.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2248">JBIDE-224...;:
The XULRunner component has been upgraded to version 1.9. This new version of XULRunner
adds support for the newest HTML and CSS features to the Visual Page Editor. Included in
this is support for CSS3.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-1592">JBIDE-159...;:
A new feature has been added that allows for Facelets tag libraries from
<filename>file.jar/META-INF/*.tablib.xml</filename> or those that are
registered within <filename>web.xml</filename> by the
<filename>facelets.LIBRARIES</filename> context parameter to now be used
within content assist for source editing in the Visual Page Editor.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-527">JBIDE-527&...;: A
bug existed within the Visual Page Editor that inhibited the
<guibutton>Previous</guibutton> and <guibutton>Next</guibutton>
buttons for detected occurrences of searched annotations to not function correctly. The
action of these buttons has now been corrected so that a user can navigate their way
through all found occurrences of a searched annotation. This functionality works in the
Visual Page Editor as it would work in a text editor.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -499,16 +726,26 @@
</listitem>
<listitem>
<para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5734">JBIDE-573...;:
The shortcut keys for full publishing a project to the server and building a full archive
have been combined under then shortcut key menu accessed with
<keycombo><keycap>Alt</keycap><keycap>Shift</keycap><keycap>Y</keycap></keycombo>.
From this menu press <keycap>F</keycap> to full publish the project or
<keycap>B</keycap> to build the full archive.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5690">JBIDE-569...;:
The <guibutton>Full-Publish</guibutton> hotkey would only accept the first
module and re-deploy it to the first server the module is deployed on. For the user this
meant that if the module was already deployed on several servers, using
<guibutton>Full-Publish</guibutton> would only re-deploy it to the first
server returned in the list. To solve this issue a user interface has been added for the
<guibutton>Full-Publish</guibutton> hotkey that allows for the selection of
the server to re-deploy to. During the implementation of this fix, the package has been
renamed to XPL.
</para>
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-526...;:
The <application>JBoss Enterprise Application Platform</application> server
would start correctly, however the <application>JBoss Developer
Studio</application> would not acknowledge that it had started. To counteract this
the <filename>JMXPoller.java</filename> timeout behaviour has been modified to
always return that the server succeeded in starting instead of ignoring the timeout. This
fix ensures that a user is not informed that the server did not start correctly when it
did.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2541">JBIDE-538...;:
Expression Language Code Assistance has been added for the
<property>@Name</property> beans. This allows for users to begin typing code
and for suggestions of automatic completion to be suggested, improving user efficiency.
</para>
</listitem>
<listitem>
<para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-526...;:
The <application>JBoss Enterprise Application Platform</application> server
would start correctly, however the <application>JBoss Developer
Studio</application> would not acknowledge that it had started. To counteract this
the <filename>JMXPoller.java</filename> timeout behavior has been modified to
always return that the server succeeded in starting instead of ignoring the timeout. This
fix ensures that a user is not informed that the server did not start correctly when it
did.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5153">JBIDE-515...;:
A <guilabel>JavaMain</guilabel> tab has been added to the tab group to allow
for customization of the main class of the server. The changes to the main class are
verified to persist by server startup checks.
</para>
</listitem>
@@ -551,7 +788,7 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5005">JBIDE-500...;:
A new export wizard has been added to the <application>JBoss Developer
Studio</application>. The new wizard allows the export operation to utilize IModule
objects. This added feature reduces redundancy and inconsistancy for the export
operation.
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5005">JBIDE-500...;:
A new export wizard has been added to the <application>JBoss Developer
Studio</application>. The new wizard allows the export operation to utilize IModule
objects. This added feature reduces redundancy and inconsistency for the export
operation.
</para>
</listitem>
<listitem>
@@ -559,7 +796,7 @@
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4976">JBIDE-497...;:
The <guilabel>JBoss Tools Palette</guilabel> has been intergrated into the
standard Eclipse GEF <guilabel>Palette</guilabel> view. The standard
<guilabel>Palette</guilabel> view, accessible at
<menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show
View</guimenuitem><guimenuitem>Others</guimenuitem><guimenuitem>General</guimenuitem><guimenuitem>Palette</guimenuitem></menuchoice>
is now shown in the right top part of the <guilabel>Web Development</guilabel>
and <guilabel>Seam</guilabel> perspectives. The <guilabel>JBoss Tools
Palette</guilabel> remains at
<menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show
View</guimenuitem><guimenuitem>Others</guimenuitem><guimenuitem>JBoss
Tools Web</guimenuitem><guimenuitem>JBoss Tools
Palette</guimenuitem></menuchoice>.
</para>
<para>
- The differences in behaviour between the paletts are:
+ The differences in behavior between the palettes are:
</para>
<itemizedlist>
<listitem>
@@ -574,7 +811,7 @@
</listitem>
</itemizedlist>
<para>
- Though the behaviour of the new palette is standard for Eclipse, for customers
used to the globally set state of tabs and perfer to customize the palette before opening
the <guilabel>Visual Page Editor</guilabel>, the old palette will remain
accessible.
+ Though the behavior of the new palette is standard for Eclipse, for customers
used to the globally set state of tabs and perfer to customize the palette before opening
the <guilabel>Visual Page Editor</guilabel>, the old palette will remain
accessible.
</para>
</listitem>
<listitem>
@@ -589,7 +826,7 @@
</listitem>
<listitem>
<para>
- <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4888">JBIDE-488...;:
The porlet facets configuration utility has been added for m2eclipse. This configuration
utility allows for the following:
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4888">JBIDE-488...;:
The portlet facets configuration utility has been added for m2eclipse. This configuration
utility allows for the following:
</para>
<itemizedlist>
<listitem>
@@ -614,6 +851,124 @@
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4877">JBIDE-487...;:
Tag completion has been upgraded so that partial matches are displayed and selectable
following direct tag matches.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4850">JBIDE-485...;:
A new feature has been added to the CSS Views with this release that allows a user to edit
styles inside HTML and xhtm.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4690">JBIDE-469...;:
The Maven Portlet library provider has been added to the <application>JBoss
Developer Studio</application> with this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-4689">JBIDE-468...;:
The portlet libraries engine has been updated to use the WTP 3.1 Library Framework. This
framework is implemented in the Portlet Core and JSF Portlet installation page. The
following library providers are now available to the user:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Library provider:
+ </para>
+ <itemizedlist>
+ <listitem>
+
+ <para>
+ User Library
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Library provided by Target Runtime
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Disable Library Configuration
+ </para> </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ Portlet Core Facet library providers:
+ </para>
+ <itemizedlist>
+ <listitem>
+
+ <para>
+ Portlet Target Runtime Provider
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Maven Portlet 1.0 and 2.0 Libraries
+ </para> </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ JSF Portlet Facet library providers:
+ <itemizedlist>
+ <listitem>
+
+ <para>
+ JSF Portletbridge Runtime provider
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ JSF Portlet Target Runtime Provider
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Maven Portletbridge 2.0.0 ALPHA Libraries
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Maven Portletbridge 2.0.0 ALPHA Libraries with dependencies
+ </para> </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-3563">JBIDE-356...;:
Code assist has been added for classes that are defined in linked CSS. The schema for
included page contexts has been added. This has occurred as it is needed to create the
contexts for all the pages included in the source. It allows for the gathering of
information on bundles declared in included pages.
+ </para>
+ <para>
+ The included page contexts are created and the following information is collected
within the included contexts:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Namespaces are declared within the included pages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tag libraries are used in the included pages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Resource bundles are declared within the included pages
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-3125">JBIDE-312...;:
Exadel OpenOn support has been added to the code editors. This new functionality allows
for a user to open a file that is being referenced within the code, in a new editor
window. Related CDI Beans will also appear from a search of references to an object within
the code, allowing for a user to quickly see where else an object is referenced.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-2541">JBIDE-254...;:
A new feature has been added to this release that allows for the JavaDoc documentation to
be available for the EL proposals as it is for Java methods. The JavaDoc comments are also
available if they originated from a projects source folders.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
Modified:
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Release_Notes.xml
===================================================================
---
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Release_Notes.xml 2010-03-04
13:08:09 UTC (rev 20653)
+++
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/Release_Notes.xml 2010-03-04
13:12:09 UTC (rev 20654)
@@ -3,9 +3,9 @@
<article>
<xi:include href="Article_Info.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="Overview.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="New_Features.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<!-- <xi:include href="New_Features.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> -->
<xi:include href="Component_Versions.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="Fixed_Issues.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="Known_Issues.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<!-- <xi:include href="Known_Issues.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> -->
<xi:include href="Revision_History.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
</article>
Modified:
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/master.xml
===================================================================
---
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/master.xml 2010-03-04
13:08:09 UTC (rev 20653)
+++
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US/master.xml 2010-03-04
13:12:09 UTC (rev 20654)
@@ -34,7 +34,7 @@
<holder>JBoss by Red Hat</holder>
</copyright>
<releaseinfo>
- Version: 1.0
+ Version: 3.0.0.GA
</releaseinfo>
<!--<abstract>
<title/>
5424
days inactive
5424
days old
jbosstools-commits@lists.jboss.org
0 comments
1 participants
participants (1)
-
jbosstools-commits＠lists.jboss.org