Author: irooskov(a)redhat.com
Date: 2010-02-22 23:44:36 -0500 (Mon, 22 Feb 2010)
New Revision: 20428
Modified:
trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml
Log:
updated with new JIRA
Modified: trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml 2010-02-23
03:20:26 UTC (rev 20427)
+++ trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml 2010-02-23
04:44:36 UTC (rev 20428)
@@ -300,6 +300,36 @@
<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 delared in the included pages. The information
collected is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Namespaces that are declared
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tag labraries 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>
@@ -368,7 +398,7 @@
</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>
@@ -378,6 +408,11 @@
</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 arifact 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>
@@ -396,6 +431,11 @@
<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>
@@ -618,6 +658,11 @@
<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 enhibited the
<guibutton>Previous</guibutton> and <guibutton>Next</guibutton>
buttons for detected occurances 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 occurances 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>
@@ -666,6 +711,11 @@
</listitem>
<listitem>
<para>
+ <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 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.
</para>
</listitem>