Author: irooskov(a)redhat.com Date: 2011-09-12 19:43:06 -0400 (Mon, 12 Sep 2011) New Revision: 34657 Modified: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml Log: updated with new fixed issues for JBDS 4.1.1 Modified: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-09-12 23:14:30 UTC (rev 34656) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-09-12 23:43:06 UTC (rev 34657) @@ -264,6 +264,11 @@ <itemizedlist> <listitem> <para> + <ulink url="http://jira.jboss.com/jira/browse/JBDS-1710">JBDS-1710&...;: When using a WSDL (Web Service Definition Language) file to create a new web service, the wizard would not work correctly if the WSDL file contained similar wording to an error that can be generated by the component. By modifying the code within the <classname>AbstractGenerateCodeCommand</classname> class that checks for non-compilation errors from searching for errors based on <property>error:</property> instead of only <property>error</property>, it allows for the word <emphasis>error</emphasis> to now appear in a WSDL without causing issue. Using a WSDL file to create a new web service now works as expected. + </para> + </listitem> + <listitem> + <para> <ulink url="http://jira.jboss.com/jira/browse/JBIDE-9516">JBIDE-951...;: When creating a Sample RESTful Web Service, the wizard referenced a JAR file that did not exist and an error would occur. The issue has been fixed by ensuring that the wizard looks for a file that has a name starting with <filename>jaxrs-api</filename> and ends with <filename>.jar</filename>. This also allows for the JBoss Developer Studio to automatically use newer versions of the the file in the future. </para> </listitem>