Author: irooskov(a)redhat.com
Date: 2010-02-02 23:45:10 -0500 (Tue, 02 Feb 2010)
New Revision: 20086
Modified:
trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml
Log:
updated release notes with new fixed issues
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-02
22:51:34 UTC (rev 20085)
+++ trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml 2010-02-03
04:45:10 UTC (rev 20086)
@@ -8,11 +8,28 @@
Following is a list of issues fixed in this release:
</para>
<formalpara>
+ <title>Contexts and Dependency Injection (CDI)</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5770">JBIDE-577...;:
The EL code completion icon has been updated to use the <application>JBoss
Weld</application> icon.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
<title>ESB Editor</title>
<para>
<itemizedlist>
<listitem>
<para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5653">JBIDE-565...;:
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5548">JBIDE-554...;:
In the ESB Configuration Editor, when selecting a JBR Listener, JBR Bus or JBR Provider,
new functionality has been added to allow a user to configure the properties:
<property>synchronous</property>,
<property>serviceInvokerTimeout</property> and
<property>asyncResponse</property> through the new child object
<property>Config</property>. These new configurable properties allow a user
increased control over the execution of the JBR components.
</para>
</listitem>
@@ -30,6 +47,16 @@
<itemizedlist>
<listitem>
<para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5643">JBIDE-564...;:
Within the <guilabel>Hibernate</guilabel> tab of the
<filename>persistence.xml</filename> editor, the button beside the
<guilabel>Configuration file</guilabel> line was labeled
<guibutton>Browse</guibutton>. This was misleading as upon clicking the button
the user would be asked setup a configuration file. To provide an improved user
experience, the button has now been altered to be called
<guibutton>Setup</guibutton> and correctly guides the user through
configuration file creation.
+ </para>
+ </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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5499">JBIDE-549...;:
</para>
</listitem>
@@ -37,6 +64,35 @@
</para>
</formalpara>
<formalpara>
+ <title>JavaServer Faces (JSF)</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5670">JBIDE-567...;:
The <filename>faceleted-taglib</filename> tag library was not supported in
<filename>*taglib.xml</filename> with XML Schema Definition (XSD). Support for
this library has been added to this release of the <application>JBoss Developers
Studio</application>, allowing for support of <application>JavaServer Faces
2</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5660">JBIDE-566...;:
When setting the location of an
<property><error-page></property> within
<filename>web.xml</filename>, the location would not be recognized if it
included a query string. For example the location
<filename>views/error/error.xhtml</filename> would be valid, whereas the
location <filename>/views/error/error.xhtml?statusCode=403</filename> would
not be valid. This has been corrected by adding a test for a query string into the
<filename>CheckResource.java</filename> file, allowing for locations to be
specified that include a query string.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>RichFaces</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-574...;:
Content assistance in coding did not show anything for the tag
<property><rich:menuItem ... icon="|" /></property>.
The content assistance has been corrected by adding the
<property>icon</property> attribute to the
<filename>RichFaces.xml</filename> tag library.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
<title>XML Structured Editor</title>
<para>
<itemizedlist>
@@ -48,4 +104,21 @@
</itemizedlist>
</para>
</formalpara>
+ <formalpara>
+ <title>General Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink
url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-574...;:
The Web Servlet Mapping dialog box now contains a drop-down list for the
<guilabel>Servlet-Name</guilabel> field so that servlets that have been
entered into the <filename>web.xml</filename> file can be selected easily.
+ </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>
+ </itemizedlist>
+ </para>
+ </formalpara>
</section>