From jbosstools-commits at lists.jboss.org Tue Apr 27 23:20:54 2010 Content-Type: multipart/mixed; boundary="===============8617703335724754150==" MIME-Version: 1.0 From: jbosstools-commits at lists.jboss.org To: jbosstools-commits at lists.jboss.org Subject: [jbosstools-commits] JBoss Tools SVN: r21772 - trunk/documentation/guides/JBDS_Release_Notes/en-US. Date: Tue, 27 Apr 2010 23:20:53 -0400 Message-ID: <201004280320.o3S3Krm8017664@svn01.web.mwc.hst.phx2.redhat.com> --===============8617703335724754150== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: irooskov(a)redhat.com Date: 2010-04-27 23:20:53 -0400 (Tue, 27 Apr 2010) New Revision: 21772 Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml trunk/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml trunk/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.x= ml trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml trunk/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml trunk/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml trunk/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml trunk/documentation/guides/JBDS_Release_Notes/en-US/master.xml Log: updated for JBDS 3.0.1 Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.= xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml 20= 10-04-27 23:14:11 UTC (rev 21771) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml 20= 10-04-28 03:20:53 UTC (rev 21772) @@ -1,3 +1,25 @@ = -Release NotesInformation about the c= hanges made for this release of the JBoss Developer Studio.JBoss Developer Studio3.000These rele= ase notes contain important information related to the JBoss Developer Stud= io. New features, resources, and other current issue= s are addressed here. + + Release Notes + Information about the changes made for this release of the JBos= s Developer Studio. + JBoss Developer Studio + 3.0.1 + 0 + 0 + + + These release notes contain important information related to the JBoss = Developer Studio. New features, resources, and other= current issues are addressed here. + + + + + + + + + + + + + Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.= xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml 20= 10-04-27 23:14:11 UTC (rev 21771) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml 20= 10-04-28 03:20:53 UTC (rev 21772) @@ -1,4 +1,10 @@ -IsaacRooskovirooskov(a)redhat.com + + + Isaac + Rooskov + irooskov(a)redhat.com + + Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Component_Ver= sions.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.= xml 2010-04-27 23:14:11 UTC (rev 21771) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.= xml 2010-04-28 03:20:53 UTC (rev 21772) @@ -12,7 +12,7 @@ - JBoss Tools 3.1.0 + JBoss Tools 3.1.1 Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.= xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 20= 10-04-27 23:14:11 UTC (rev 21771) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 20= 10-04-28 03:20:53 UTC (rev 21772) @@ -13,19 +13,9 @@ - JBIDE-57= 70: The EL code completion icon has been updated to use the JBoss Weld icon. + - - - JBIDE-53= 55: A Contexts and Dependency Injection Project Facet has been adde= d to JBoss Developer Studio. This makes it possi= ble to enable CDI support for a faceted project via the New Dynam= ic Web Project wizard or the Project Facets= setting page available at ProjectPropertiesProject Facets. - - - - - JBIDE-52= 76: The Add CDI Support and Remove CDI Support items have been added to the Project menu= . = - - @@ -35,85 +25,9 @@ - JBIDE-56= 53: The ESB Content Based Router dialog box h= as been modified so that the CBR Alias field is now ma= ndatory, allowing the value of it to determine what other fields are availa= ble. The Rule Set field is now not required when a CBR Alias of Regex or XPath is provided, since with these= alias the rules can be specified in-line and the Rule Language field is now set to apply only when the CBR Alias is Drools. The Rules Reload field will only appl= y when a Rule Set has been specified. + - - The table Route List found in the JBo= ss ESB Editor now lists the expression sinc= e this is a common undertaking by users. - - - In the Add Route To dialog box, the = Service Category field has been made mandatory. Other changes to= this dialog box include the Destination name only bei= ng required if the previous CBR action contained a Rule Set and if the CBR action did not contain a Rule Set= , an Expression field is included. - - - - JBIDE-56= 27: For this release of the JBoss Developer Studio variations of the Content Based Router menu= have been added to the ESB editor for Drools, Drools XPath, Generic, XPath= and Regex. - - - - - JBIDE-55= 48: 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: synchronous, se= rviceInvokerTimeout and asyncResponse throu= gh the new child object Config. These new configurable= properties allow a user increased control over the execution of the JBR co= mponents. - - - - - JBIDE-55= 47: In the ESB Configuration Editor, when selecting a FTP Listener = in read-only mode new functionality has been added to allow a user to confi= gure the properties: maxNodes, timeToLiveSec= onds and maxAgeSeconds through the new chil= d object Cache. In addition the following properties h= ave been added to allow a user to select their own values for the: Class, Config File and Cache Li= stener available through the new child object Remote F= ilesystem Strategy. These new configurable properties allow a us= er increased control over the execution of the FTP Listener. - - - - - JBIDE-54= 89: For the BPMProcessor within the ESB Editor= , the Command property has been modified to include po= ssible values of NewProcessInstanceCommand, = StartProcessCommand and CancelProcessInstanceCommand in a drop-down box. - - - - - JBIDE-54= 86: When a user would try to open an editor for a property that did= n't exist nothing would occur. With this update, a New File wizard opens to guide the user through the creation of the property t= hey were attempting to open. Once this is completed, the ESB Editor fields = are then populated with the new file name and path for the property. - - - - - JBIDE-54= 27: In the ESB Editor, the items that displayed when right clicking= and going to ProviderN= ew were presented in a different order to those = of the ListenerNew list. To ensure consistency the Provide= r list of items has been reordered to match the = Listener menu. - - - - - JBIDE-52= 29: ESB 4.7 that is contained within JBoss SOA Platfor= m 5.0 is now officially supported in this version of the JBoss Developer Studio. - - - - - JBIDE-51= 91: The Smooks, Drools, jPDL, XSLT and Groovy editors have been lin= ked to the ESB Editor, providing an improved user experience. Br= owse buttons that allow for file association and use have been = added to the Smooks Transformer, GroovyActio= nProcessor, Rule Set and Rule Lan= guage properties. - - - - - JBIDE-51= 08: The JBoss Runtime Manager was setup to search for ESB Runtime f= iles from a specified location regardless of how it was installed. This cau= sed issue when the ESB Runtime was installed as a user defined runtime. The= issue has been rectified by adding a Configuration fi= eld to the Preference page. If the user sets the Configuration field to the home location of the JBoss Enterprise Application Platform or JBos= s SOA Platform, there configuration combination will list all= available configurations. If the user selects a standalone ESB Runtime loc= ation, the configuration combination will be empty and the user should igno= re the field. The ESB runtime classpath container now gathers configuration= information from the selected server runtime and then selects JARs accordi= ngly or the sta! ndalone ESB Runtime. - - - - - JBIDE-47= 30: The ESB project creation wizard receives a new logo following t= his update. Instead of using the generic JBoss Developer Studi= o logo within the ESB project wizard, a new ESB wizard logo i= s displayed. - - - - - JBIDE-43= 20: ESB projects are now Web Tools Platform (WTP) modules. This ens= ures that it is possible to use an ESB module inside a WAR or EAR archive w= ithin WTP. ESB project deployment has not been limited though and they can = still be deployed as an individual module. - - - - - JBIDE-41= 68: The ability to select a directory using a browser window has be= en added for the FS Message Filter and the FTP Message filter attributes of= directory, post-directory and error-directory. This added feature ensures that a user = does not need to manually type the entire path to a directory but instead t= hey just select the path from a browser. - - - - - JBIDE-20= 24: The Process field f the Action tab in the ESB now includes a Browse butto= n that allows a user to select which method of the Action class should be used for the process. The list in the dialog will sho= w all public methods that has a Message parameter. Mul= tiple methods can be selected if necessary. - - - - - JBIDE-20= 23: The Class field of the Action tab now includes a Browse button that displ= ays the possible classes that extend from the AbstractActionLife= cycle class. - - @@ -123,19 +37,7 @@ - JBIDE-57= 19: - Now users can create a new jBPM action by right clicking the source = directory = - in Package Explorer and selecting New ->Other -> JBoss jBP= M-> jBPM 3 Action Handler - . - - - JBIDE-49= 04: - The runtime preference pages of jBPM 3 and jBPM 4 started to be unif= ied. = - - - JBIDE-56= 22: - Resolved the bug connected with the problem that Generate - Task View did not remember the state of some edited field= s. = + @@ -147,128 +49,9 @@ - JBIDE-58= 24: The reveng.xml editor provided an option t= o Exclude column from reverse engineering. Selecting t= his option did not change any functioning of the column and the specified o= ption should not have been part of the interface. This update removes the u= nnecessary option as to not confuse users. + In the H= ibernate reverse engineering editor it was impossible to add a parameter as= the button to do so was missing. This update corrects the user interface t= o include the Add parameter button under the Id Generator details Class section. - - - JBIDE-56= 43: Within the Hibernate tab of the = persistence.xml editor, the button beside the Configur= ation file line was labeled Browse. 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 Setup and correctly gu= ides the user through configuration file creation. - - - - - JBIDE-56= 41: When specifying the persistence property: <propert= y name=3D"hibernate.ejb.cfgfile" value=3D"hibernate.cfg.xml"/>, an error could display saying that the hibernate.cfg.xml file could not be found. This occurred because the validator only con= sidered full paths and not relative path naming. This has since been correc= ted through the modification of the HibernatePersistenceUnit class. = - - - - - JBIDE-54= 99: Refactoring support has been added to Hibernate Code = Generation Configurations. = - - - - - JBIDE-54= 11: The New Hibernate XML Mapping file wizard = used to show all available packages. This update ensures that only packages= containing java classes are shown. - - - - - JBIDE-54= 08: Three issues are fixed: - - - - The new Hibernate XML Mapping file (hbm.xml)= would rewrite all hbm.xml files without warning. To c= orrect this the entire result is written into the systems' temporary direct= ory and then the merge of results is conducted. - - - - - After the merge of results is conducted, clicking the = Finish without Preview button should change the page, however t= his did not work. The Finish without Preview now wor= ks as expected. - - - - - After the merge, following the button clicks GoTo, Next, Back and then = Finish would not work correctly. This method of step= s now functions as users would expect. - - - - - - - - JBIDE-52= 22: A new feature as been added that allows for support of filter configurations in closed projects for console configura= tion. This option is available through Preferences= Run/DebugLaunchingLaunch Configurations. - - - - - - JBIDE-5124: In the Hibernate Diagram Viewer new = - functionality has been added that allows a user to choose between = - two different connection routers: Manhattan connection router for = - small diagrams and Fan connection router for larger diagrams - (View -> Show connections as routed, Show Connections as streight lines). - - - - - JBIDE-50= 31: - To close a database connection a user would have to close the - JBoss Developer Studio and then restart t= he application = - to continue work without the connection. - The database connection can now be closed from within the = - JBoss Developer Studio by choosing the - Close Configuration menu item = - in Hibernate Console context menu located in Hi= bernate Configurations View. - - - - - JBIDE-49= 56: A feature has been added to the Mapping Diagram viewer so that it now displays relationships between database tables. - - - - - JBIDE-49= 16: An editor for the hibernate.properties fil= e has been added to the JBoss Developer Studio. = The editor supports content assist authoring. - - - - - JBIDE-48= 99: The Hibernate Configurations view was not = updated after a hibernate console enabled project with console configuratio= n was deleted from the workspace. This meant that the console configuration= was not removed along with the project. This bug is rectified with this up= date. - - - - - JBIDE-47= 80: The Options tab now allows you to browse a= nd set the NamingStrategy and EntityResolver= . The console configuration option has also been updated to reac= t when one of the packages of a referenced class changes. - - - - - JBIDE-47= 33: A new feature has been added that allows a user to select wheat= her JPA-Generate DDL should be executed in the database. Before this update= this feature was automatic, always executing JPA-Generate in the database. - - - - - JBIDE-47= 15: A toggle button has been added to the Hibernate Mapping diagram= to allow the outline view to be ordered either alphabetically or by the st= ructure outlined in the file. The toggle button interface ensures the exper= ience remains consistent across all tools included within the = JBoss Developer Studio. - - - - - JBIDE-46= 62: Annotations support has been added to Hibernate Tools. The addi= tion of annotations support allows for interaction with the Eclipse Dali Ja= va Persistence Tools Project plug-in. - - - - - JBIDE-44= 51: The option is now given to the user to enable the HQL= Editor and Hibernate Criteria Editor to be= dynamically updated when opening a new query instead of opening an instanc= e of each editor for each query. This can be achieved by clicking the butto= n of a tack to the right of the Max results: drop-won= box in the editor. - - - - - JBIDE-44= 50: The Properties view has been updated with = a new property called Tab name. The addition of this p= roperty allows for a user to individually name each query tab, allowing for= improved tab management. - - - - - JBIDE-42= 27: The Open Mapping File option now sup= ports all possible configuration files. In the past only files called orm.xml have been supported and this update now provides in= creased user functionality. - - @@ -278,104 +61,9 @@ - JBIDE-56= 70: The faceleted-taglib tag library was not s= upported in *taglib.xml with XML Schema Definition (XS= D). Support for this library has been added to this release of the JBoss Developers Studio, allowing for support of JavaServer Faces 2. + - - - JBIDE-56= 60: When setting the location of an <error-page> within web.xml, the location would not be rec= ognized if it included a query string. For example the location v= iews/error/error.xhtml would be valid, whereas the location /views/error/error.xhtml?statusCode=3D403 would not be val= id. This has been corrected by adding a test for a query string into the CheckResource.java file, allowing for locations to be sp= ecified that include a query string. - - - - - JBIDE-54= 71: web-facesconfig_2_0.xsd support has been a= dded to the JavaServer Faces Configuration editor. Thi= s file provides the XML Schema for the JavaServer Faces Application Configu= ration File Version 2.0. - - - - - JBIDE-53= 81: Content Assist has been added for use with the elements defined= using the default namespace. - - - - - JBIDE-52= 77: The options to Add and Remove JSF support have been added to th= e project menu. - - - - - JBIDE-52= 37: CSS Class Hyperlink for the class attribut= e of HTML tags would not search through CSS loaded using JSF tags (for exam= ple: <a:loadStyle />). This has now been fixed so that the searching = of CSS classes returns the correct user expected results. - - - - - JBIDE-50= 99: OpenOn support has been added for custom JSF 2.0 components. - - - - - JBIDE-50= 97: Content Assist did not support multiple namespaces with the sam= e Uniform Resource Identifier (URI).This issue has been fixed by modifying = XmlContextImpl class within the XmlContext= Impl.java file from: nameSpaces.get(region).put(nameSpace.= getURI(), nameSpace); to nameSpaces.get(region).put(nameSpace.= getPrefix(), nameSpace);. - - - - - JBIDE-50= 89: JSF Expression Language (EL) validation has been added for mess= age bundles. This improves the performance of the PageContextFac= tory. - - - - - JBIDE-50= 15: Support for JSF 2.0 composition components has been added in th= is update. = - - - - - JBIDE-49= 78: JSF has been upgraded with the addition of Seam Expression Lang= uage (EL) support. This now allows for JSF EL validation to use all availab= le EL resolvers, providing increased validation over past releases. - - - - - JBIDE-49= 70: KBbuilder now loads composite compon= ents from the JSF resource folders and adds them to the KB module. This all= ows for the components to be available for code assistance. - - - - - JBIDE-47= 71: The Find Usages function has been improved= to provide information about methods when inside an EL expression. = - - - - - JBIDE-28= 06: The Eclipse OpenOn feature that allows a user to click any refe= rence to a template as if it was a hyperlink did not work if the template p= ath 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 variabl= e. This is a great advantage to users as the Expression Language variable i= s a frequently used feature. - - - - - JBIDE-816= : A bug existed within the JSF component of the JBoss= Developer Studio 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 fo= r 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 t= ree. = - - - The bug has since been fixed by adding a schema for included page co= ntexts. This schema enables the creation of contexts for all the pages incl= uded in the source and for the gathering of information on bundles declared= in the included pages. The information collected is as follows: - - - - - Namespaces that are declared - - - - - Tag libraries that are used - - - - - Resource bundles that are declared - - - - - - - JBIDE-512= : The drop-down box for context variable code completion has been u= pgraded for enhanced usability. The source of the variable is now outlined = during code completion and the code is highlighted in a different colour fo= r improved reading and overall understanding of each file. - - @@ -385,14 +73,9 @@ - JBIDE-57= 43: Content assistance in coding did not show anything for the tag = <rich:menuItem ... icon=3D"|" />. The content as= sistance has been corrected by adding the icon attribu= te to the RichFaces.xml tag library. + - - - JBIDE-50= 25: The RichFaces libraries have been updated to version 3.3.2.SR1. - - @@ -402,91 +85,9 @@ - JBIDE-52= 75: The Add Seam Support and Remove Seam Support items have been added to the Project me= nu. = + - - - JBIDE-52= 21: The JBoss Server View has now been replace= d with the Server View in the Seam perspective. This h= as occurred out of the JBoss Server View being depreca= ted. - - - - - JBIDE-51= 92: The name of the editor when using the Diagram Viewer<= /guilabel> was a concatenation of the names of the diagram entities, leadin= g to a long name in some cases. This issue has been corrected by modifying = the OrmDiagram.java and DiagramViewer.java files to display a name from the following three options (based o= n the number of entities): - - - - Console name: Entity name = - - - - - Console name: First Entity name and Second Entity name = - - - - - Console name: First Entity name and <number of other entities&= gt; others - - - - - - - - JBIDE-51= 70: When changing, adding or removing a Seam runtime from within WindowPreferencesJBoss ToolsWeb<= guimenuitem>Seam, Seam projects would not be bui= lt or validated. The behavior has been changed to build and validate Seam p= rojects upon changes in the Preferences section = to ensure correct functioning of the project. The SeamRuntimeMana= ger.java file was updated to correct this. - - - - - JBIDE-50= 12: The Booking and DVDStore Seam examples have been updated for Se= am 2.2 within the JBoss Enterprise Application Platform. = - - - - - JBIDE-49= 87: Seam and JPA Connection Profiles have been synchronized for thi= s release. The jpa-connection profile is used in the = launch configuration instead of hibernate.properties i= f the JPA facet is installed. - - - - - JBIDE-49= 85: Seam projects now create a Hibernate configuration that uses th= e selected connection profile directly (without copying its settings into t= he hibernate.properties file). - - - - - JBIDE-49= 44: The Seam wizards Action, Entity<= /guilabel> and Conversation had the ability to overwri= te resources when they generated code. The wizards would warn the user that= some resources already existed and yet overwrite them. This has been corre= cted through the modification of the SeamBaseOperation.java file. - - - - - JBIDE-48= 56: Seam component methods and properties used in the Expression La= nguage (EL) have been refactored. This has caused the internal structure of= the components to be modified so that the Query Participant works with the JDT Java Search to find usages and append them to s= earch results. The Rename Participant has also been = modified to work with the JDT Java Refactor to rename usages and apply chan= ges to the Java Refactor, allowing for a user to rename a setter<= /emphasis> or getter method and have the Re= name Participant warn the user of the consequences of renaming = a paired method. - - - - - JBIDE-41= 36: Classloading issues were being faced by users of Seam Tools bec= ause the JBoss Developer Studio used the MANIFEST.MF file for creating an artifact classpath instead o= f using the EAR lib/ directory that is recommended by = Seam. Until now the JBoss Developer Studio has n= ot been able to use the EAR lib/ directory because thi= s functionality has not been supported by Eclipse. With the introduction of= Eclipse 3.5 in this release the use of the EAR lib/ d= irectory is now supported and the process of creating an artifact classpath= has been updated. - - - - - JBIDE-28= 07: An option is now provided when creating a New Seam Pr= oject, to not create a test project. This has become an option s= ince the Seam model does not require the test project to exist and so allow= s the user to decide if it is of importance. Selecting to create or not cre= ate a test project is achieved through the ticking of a Create Te= st Project check box within the New Seam Project wizard. - - - - - JBIDE-14= 52: Support has been added for the Seam PDF Facelet tag library. Th= is Facelet library allows for PDF creation from within Seam. - - - - - JBIDE-14= 51: Support has been added for the Seam Mail Facelet tag library. T= his Facelet library allows for email forms to be created from within Seam. = All components of the Facelet have been included except mail:mess= age and mail:body as these components are r= endered as divisions (using the <div> tag). - - - - - JBIDE-11= 76: The Seam Web Project now supports the JPA facet. Addition of th= e Java Persistence API allows for the management of relational data within = applications. - - @@ -496,41 +97,9 @@ - JBIDE-52= 59: The Smooks configuration has received a test facility through t= he modification of the Run button to output a java r= esult to the Console. This allows a user to test Smook= s projects in a simplified way. + - - - JBIDE-50= 88: When opening an existing Smooks configuration file it wouldn't = contain any process information. To correct this an input task is automatic= ally created and the Smooks configuration file is analyzed to add any missi= ng task types if necessary. During the course of this update a NullPointerException was also fixed. - - - - - JBIDE-50= 86: A default layout is added in the Java-Mapping viewer. This allo= ws for the layout of the information in the Smooks editor to be rearranged = into a predefined default layout. - - - - - JBIDE-48= 78: The Smooks Reader page has been replaced w= ith a new Input page. While the Input page inherits many functions from the Reader page= there are some differences as follows: - - - - - The Reader page allowed for multiple Readers = to be created. Input page only allows for one Reader. = - - - - - The Reader page supported the addition of mul= tiple input data , where each was usable. The Input pa= ge only allows for one piece of input data to be used, while still allowing= for multiple pieces of input data. - - - - - The Reader page could view the transformation= results of the Reader. The new Input page utilizes an= input model view to check the transform result. = - - - - @@ -540,7 +109,7 @@ - JBIDE-52= 78: The options to Add and Remove Struts support have been added to= the project menu. + @@ -552,173 +121,9 @@ - JBIDE-51= 84: A memory leak existed in the Visual Page Editor. To fix this le= ak, the following plug-ins have been modified: + - - - - org.jboss.tools.vpe - - - - - org.jboss.tools.vpe.xulrunner - - - - - org.jboss.tools.jst.jsp - - - - - The issues that caused the memory leak were: - - - - - JSPMultiPageEditorSite: The constructor creat= ed the serviceLocator that wasn't disposed of after = use. = - - - - - The XulRunnerBrowser.dispose() method wou= ld remove the progressListener, however this would o= nly be done after all SWT objects and controls were already disposed. This = meant the method had no effect. The dispose method is now called before the= SWT objects and controls are disposed. - - - - - The MozillaEditor.getEditor() madethe Moz= illa window editable using nsIEditingSession.setupEditorOnWindo= w(). To counteract this the objects created are now removed by= using nsIEditingSession.tearDownEditorOnWindow(). = - - - - - The createPartControl() method in the MozillaEditor and MozillaPreview= classes create XullRunnerEditor as an inner class. = The issue was that the XullRunnerEditor class retain= ed a reference to MozillaEditor(MozillaPreview) that= caused it not to be released and instead retain references to WST and EMF = classes. This has now been corrected so that MozillaEditor(Mozil= laPreview) is now released after use and references are not ret= ained. - - - - - - JBIDE-51= 00: Support for JSF 2.0 attributes have been added to the Visual Pa= ge Editor. - - - - - JBIDE-50= 91: Support for JSF 2.0 Composition components that come packaged i= nto the Web Application Root has been added to the Visual Page Editor. - - - - - JBIDE-50= 65: The icons in the Visual Page Editor have been redesigned for im= proved aesthetic appearance. - - - - - JBIDE-49= 45: A new feature has been added to the Visual Page Editor that all= ows a user to select both the element before and the element after a centra= l element. This has been achieved through the modification of the SelectionBar.java file. = - - - - - JBIDE-49= 34: Facelets tag library support has been added to the Pa= lette for the Visual Page Editor. - - - - - JBIDE-49= 14: The Visual Page Editor has been redesigned so that all drop-dow= n menu items are placed in the toolbar as buttons. - - - - - JBIDE-43= 23: 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 eas= ier to read and manage. - - - - - JBIDE-28= 20: Support for new JSF 2.0 elements has been added to the Visual P= age Editor. The tags that are newly supported are: - - - - - h:head - - - - - h:body - - - - - h:outputscript - - - - - h:outputstyle - - - - - h:button = - - - - - h:link = - - - - - f:ajax = - - - - - f:event = - - - - - f:validateBean - - - - - f:validateRequired = - - - - - f:viewParam = - - - - - f:metadata = - - - - - - - JBIDE-25= 71: Selection of the <h:selectOneMenu> d= id not function correctly. Instead of being selected with one mouse click, = two clicks were necessary. A bug was also present that made the nested comp= onents <f:selectItem> and <f:select= Items> unable to be selected from within the Visual Page Edit= or. Correction of the two clicks necessary to select the <h:se= lectOneMenu> component has been completed by removing the che= ck within VpeController.java that ensures the node is = of type text. The issue that did not allow for the selection of the <f:selectItem> and <f:selectItems> components was found to be a bug in XULRunner. To correct this the X= ULRunner component has been updated to version 1.9, which corrects this err= or and provides ! numerous other small bug fixes (JBIDE-2248. - - - - - JBIDE-22= 48: 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. - - - - - JBIDE-15= 92: A new feature has been added that allows for Facelets tag libra= ries from file.jar/META-INF/*.tablib.xml or those that= are registered within web.xml by the facele= ts.LIBRARIES context parameter to now be used within content ass= ist for source editing in the Visual Page Editor. - - - - - JBIDE-527= : A bug existed within the Visual Page Editor that inhibited the Previous and Next buttons for d= etected 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 func= tionality works in the Visual Page Editor as it would work in a text editor. - - @@ -728,7 +133,7 @@ - JBIDE-49= 46: Tool tips for tags and attributes in the XHTML Editor have been= added. + @@ -740,14 +145,9 @@ - JBIDE-55= 21: The Web Servlet Mapping dialog box now contains a drop-down lis= t for the Servlet-Name field so that servlets that hav= e been entered into the web.xml file can be selected e= asily. + - - - JBIDE-54= 26: The Servlet Mapping Editor Servlet-Name fi= eld has been improved with a drop-down menu to fill it in. - - @@ -757,260 +157,9 @@ - JBIDE-57= 43: The Web Servlet Mapping dialog box now contains a drop-down lis= t for the Servlet-Name field so that servlets that hav= e been entered into the web.xml file can be selected e= asily. + - - - JBIDE-57= 34: The shortcut keys for full publishing a project to the server a= nd building a full archive have been combined under then shortcut key menu = accessed with AltShiftY= . From this menu press F to full publi= sh the project or B to build the full archive. - - - - - JBIDE-56= 90: The Full-Publish hotkey would only accep= t the first module and re-deploy it to the first server the module is deplo= yed on. For the user this meant that if the module was already deployed on = several servers, using Full-Publish would only re-de= ploy it to the first server returned in the list. To solve this issue a use= r interface has been added for the Full-Publish hotk= ey 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. - - - - - JBIDE-53= 83: Expression Language Code Assistance has been added for the @Name beans. This allows for users to begin typing code an= d for suggestions of automatic completion to be suggested, improving user e= fficiency. - - - - - JBIDE-52= 67: The JBoss Enterprise Application Platform server would start correctly, however the JBoss Develope= r Studio would not acknowledge that it had started. To counte= ract this the JMXPoller.java 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 th= e server did not start correctly when it did. - - - - - JBIDE-51= 53: A JavaMain tab has been added to the tab g= roup to allow for customization of the main class of the server. The change= s to the main class are verified to persist by server startup checks. - - - - - JBIDE-51= 22: JBoss Servers View has been removed with t= his release. All the functionality provided by this view can be found in th= e Servers View. - - - - - JBIDE-50= 48: SSH deployment has been added to the JBoss Develop= er Studio with this update. Specifically the following improv= ements have been made: - - - - - A server type has been created that accepts SSH deployment for Ecl= ipse Web Tools Platform (WTP) archives - - - - - WTP, single-file and project archives can now be published - - - - - Java Secure Channel (JSch) errors are now verified - - - - - All situations return IStatus objects and their associated user in= terface (an IStatus object represents the outcome of an operation) - - - - - - - JBIDE-50= 41: The menu key on the keyboard would not work in= the Web Projects view, Seam Components view or JBoss Tools XML Editor. The functioning of this key has now = been corrected so it behaves as a user would expect. - - - - - JBIDE-50= 05: A new export wizard has been added to the JBoss De= veloper Studio. The new wizard allows the export operation to= utilize IModule objects. This added feature reduces redundancy and inconsi= stency for the export operation. - - - - - JBIDE-49= 76: The JBoss Tools Palette has been intergrat= ed into the standard Eclipse GEF Palette view. The sta= ndard Palette view, accessible at WindowShow ViewO= thersGeneralPalette is now shown in the right top part of the Web Development and Seam perspectives. T= he JBoss Tools Palette remains at WindowShow ViewO= thersJBoss Tools WebJ= Boss Tools Palette. - - - The differences in behavior between the palettes are: - - - - - The new Palette is filled only when the Visual Page Editor is open and activated. The old palette r= emains static. - - - - - The expanded and collapsed state of tabs in the new palette is ass= ociated with the opened instance of the Visual Page Editor and not globally set as they were in the old palette. This allows for = the state of tabs to be different for individual files. Each new file opene= d in the Visual Page Editor will have the default Palette state with all tabs collapsed. = - - - - - 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 th= e palette before opening the Visual Page Editor, the o= ld palette will remain accessible. - - - - - JBIDE-49= 55: BPEL and ESB projects can now be excluded from deployment throu= gh the addition of new fileset capability. When the fileset is referenced t= he includes, excludes and root folder layout is implemented just as it is f= or archives. - - - - - - JBIDE-48= 88: The portlet facets configuration utility has been added for m2e= clipse. This configuration utility allows for the following: - - - - - If the pom.xml file contains a port= let-api dependency, the JBoss Core Portlet facet is added. = - - - - - If the pom.xml file contains portletbridge de= pendencies, the JBoss JSF Portlet facet is added. = - - - - - If the project contains Seam, JBoss Core Portlet and JBoss JSF Por= tlet facet, the JBoss Seam Portlet facet is added. - - - - - - - JBIDE-48= 77: Tag completion has been upgraded so that partial matches are di= splayed and selectable following direct tag matches. - - - - - JBIDE-48= 50: A new feature has been added to the CSS Views with this release= that allows a user to edit styles inside HTML and xhtm. - - - - - - - JBIDE-35= 63: Code assist has been added for classes that are defined in link= ed CSS. The schema for included page contexts has been added. This has occu= rred as it is needed to create the contexts for all the pages included in t= he source. It allows for the gathering of information on bundles declared i= n included pages. - - - The included page contexts are created and the following information= is collected within the included contexts: - - - - - Namespaces are declared within the included pages - - - - - Tag libraries are used in the included pages - - - - - Resource bundles are declared within the included pages = - - - - - - - JBIDE-31= 25: OpenOn support has been added to the code editors. This new fun= ctionality 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. - - - - - JBIDE-25= 41: A new feature has been added to this release that allows for th= e JavaDoc documentation to be available for the EL proposals as it is for J= ava methods. The JavaDoc comments are also available if they originated fro= m a projects source folders. - - Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.= xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml 20= 10-04-27 23:14:11 UTC (rev 21771) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml 20= 10-04-28 03:20:53 UTC (rev 21772) @@ -12,24 +12,9 @@ - JBDS-11= 55: EAR projects that use classpath variable references to JAR file= s get packaged in /lib/lib instead of /lib. This is due to a bug in Eclipse WTP, for which a bug fix will be= released shortly. Until the bug fix is made available, it is possible to a= void this issue by editing the .settings/org.eclipse.wst.common.c= omponent file and removing the archiveName = attributes. + - - - JBIDE-3= 623: If you use the community Seam versions 2.1.0.SP1 or 2.1.1 Test= NG for WAR projects they will fail with the error Two components= with the same name and precedence. There is no known workaroun= d, however all other Seam releases work correctly and all Seam 2.1 EAR proj= ects are successful. - - - - - JBIDE-77= 9: Currently Facelet pages contain false warnings.This has occured = due to Eclipse WTP's HTML Syntax Validation not allowing for Facelet specif= ic attributes. These warnings can be stopped by disabling validation. To di= sable validation follow WindowsPreferencesValidationHTML Syntax Validation . = - - - - Disabling validation has the potential to remove useful warning in= formation. - - - Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml 2010-0= 4-27 23:14:11 UTC (rev 21771) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml 2010-0= 4-28 03:20:53 UTC (rev 21772) @@ -42,7 +42,7 @@ - JBoss Developer Studio includes both certified visual tooling and a run= time platform that Red Hat supports for 5 years, ensuring developers of a s= table, upgradable, deployable and supportable platform. + JBoss Developer Studio includes both certified visual tooling and a run= time platform (that Red Hat supports for 3 years (Limited) and 5 years resp= ectively), ensuring developers of a stable, upgradable, deployable and supp= ortable platform. JBoss Developer Studio is available for Windows, Linux and MacOS. Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Revision_Hist= ory.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xm= l 2010-04-27 23:14:11 UTC (rev 21771) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xm= l 2010-04-28 03:20:53 UTC (rev 21772) @@ -1,3 +1,23 @@ = -Revision History0Mon Dec 21 2009Isaac<= /firstname>Rooskovirooskov(a)redhat.comInitial creation of book by publ= ican + + Revision History + + + + 0 + Wed Apr 28 2010 + + Isaac + Rooskov + irooskov(a)redhat.com + + + + Initial creation of book by publican + + + + + + Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/master.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/JBDS_Release_Notes/en-US/master.xml 2010-04-= 27 23:14:11 UTC (rev 21771) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/master.xml 2010-04-= 28 03:20:53 UTC (rev 21772) @@ -34,7 +34,7 @@ JBoss by Red Hat - Version: 3.0.0.GA + Version: 3.0.1.GA