Jboss Developer Studio 3.0 3.0.0 Release Notes

Transcript

JBoss D eveloper Studio 3.0 3.0.0 Release Notes JBoss Developer Studio 3.0 3.0.0 Release Notes Information about the changes made for this release of the JBoss Developer Studio. Isaac Rooskov [email protected] 1 2 Legal Notice Legal Notice Copyright © 2010 Red Hat. T he text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux® is the registered trademark of Linus T orvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners. JBoss D eveloper Studio 3.0 3.0.0 Release Notes Abstract T hese release notes contain important information related to the JBoss Developer Studio. New features, resources, and other current issues are addressed here. 3 4 Table of Contents Table of Contents 1. Overview 2. Component Versions 3. Features added and issues fixed in this release 4. Known Issues with this release A. Revision History 1. Overview JBoss Developer Studio provides an integrated development environment for developers to build rich Web and enterprise applications, and SOA services. T he technologies used include: Hibernate JBoss Seam RichFaces JBoss jBPM JBoss ESB JBoss Portal JBoss Drools JBoss Developer Studio includes both certified visual tooling and a runtime platform (that Red Hat supports for 3 years (Limited) and 5 years respectively), ensuring developers of a stable, upgradable, deployable and supportable platform. JBoss Developer Studio is available for Windows, Linux and MacOS. 2. Component Versions T his section details the versions of the components which create the JBoss Developer Studio that can be found in this release. Eclipse 3.5 (Galileo) JBoss T ools 3.1.0 JBoss Enterprise Application Platform 5.0 Note T he Enterprise Application Platform Server has been redefined for the enterprise market to a level where direct association to a community release can no longer be drawn. 3. Features added and issues fixed in this release Following is a list of new and noteworthy features and bug fixes in this release: Contexts and Dependency Injection (CDI) JBoss D eveloper Studio 3.0 3.0.0 Release Notes JBIDE-5770: T he EL code completion icon has been updated to use the JBoss Weld icon. JBIDE-5355: A Contexts and Dependency Injection Project Facet has been added to JBoss Developer Studio. T his makes it possible to enable CDI support for a faceted project via the New Dynam ic Web Project wizard or the Project Facets setting page available at Project → Properties → Project Facets. JBIDE-5276: T he Add CDI Support and Remove CDI Support items have been added to the Project menu. ESB JBIDE-5653: T he ESB Content Based Router dialog box has been modified so that the CBR Alias field is now mandatory, allowing the value of it to determine what other fields are available. T he 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. T he Rules Reload field will only apply when a Rule Set has been specified. T he table Route List found in the JBoss ESB Editor now lists the expression since this is a common undertaking by users. In the Add Route T o dialog box, the Service Category field has been made mandatory. Other changes to this dialog box include the Destination nam e only being 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-5627: 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-5548: 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, serviceInvokerT imeout and asyncResponse through the new child object Config. T hese new configurable properties allow a user increased control over the execution of the JBR components. JBIDE-5547: In the ESB Configuration Editor, when selecting a FT P Listener in read-only mode new functionality has been added to allow a user to configure the properties: maxNodes, timeT oLiveSeconds and maxAgeSeconds through the new child object Cache. In addition the following properties have been added to allow a user to select their own values for the: Class, Config File and Cache Listener available through the new child object Remote Filesystem Strategy. T hese new configurable properties allow a user increased control over the execution of the FT P Listener. JBIDE-5489: For the BPMProcessor within the ESB Editor, the Command property has been modified to include possible values of NewProcessInstanceCommand, StartProcessCommand and CancelProcessInstanceCommand in a drop-down box. JBIDE-5486: When a user would try to open an editor for a property that didn't exist nothing would occur. With this update, a New File wizard opens to guide the user through the creation of the property they 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-5427: In the ESB Editor, the items that displayed when right clicking and going to Provider → New were presented in a different order to those of the Listener → New list. T o ensure consistency the Provider list of items has been reordered to match the Listener menu. JBIDE-5229: ESB 4.7 that is contained within JBoss SOA Platform 5.0 is now officially supported in this version of the JBoss Developer Studio. JBIDE-5191: T he Smooks, Drools, jPDL, XSLT and Groovy editors have been linked to the ESB Editor, providing an improved user experience. Browse buttons that allow for file association and use have been added to the Smooks T ransformer, GroovyActionProcessor, Rule Set and Rule Language properties. 5 6 Table of Contents JBIDE-5108: T he JBoss Runtime Manager was setup to search for ESB Runtime files from a specified location regardless of how it was installed. T his caused issue when the ESB Runtime was installed as a user defined runtime. T he issue has been rectified by adding a Configuration field to the Preference page. If the user sets the Configuration field to the home location of the JBoss Enterprise Application Platform or JBoss SOA Platform, 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. T he ESB runtime classpath container now gathers configuration information from the selected server runtime and then selects JARs accordingly or the standalone ESB Runtime. JBIDE-4730: T he ESB project creation wizard receives a new logo following this update. Instead of using the generic JBoss Developer Studio logo within the ESB project wizard, a new ESB wizard logo is displayed. JBIDE-4320: ESB projects are now Web T ools Platform (WT P) modules. T his ensures that it is possible to use an ESB module inside a WAR or EAR archive within WT P. ESB project deployment has not been limited though and they can still be deployed as an individual module. JBIDE-4168: T he ability to select a directory using a browser window has been added for the FS Message Filter and the FT P Message filter attributes of directory, post-directory and error-directory. T his 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. JBIDE-2024: T he Process field f the Action tab in the ESB now includes a Browse button that allows a user to select which method of the Action class should be used for the process. T he list in the dialog will show all public methods that has a Message parameter. Multiple methods can be selected if necessary. JBIDE-2023: T he Class field of the Action tab now includes a Browse button that displays the possible classes that extend from the AbstractActionLifecycle class. jBPM JBIDE-5719: Now users can create a new jBPM action by right clicking the source directory in Package Explorer and selecting New ->Other -> JBoss jBPM-> jBPM 3 Action Handler . JBIDE-4904: T he runtime preference pages of jBPM 3 and jBPM 4 started to be unified. JBIDE-5622: Resolved the bug connected with the problem that Generate T ask View did not remember the state of some edited fields. Hibernate JBIDE-5824: T he reveng.xm l editor provided an option to Exclude colum n from reverse engineering. Selecting this option did not change any functioning of the column and the specified option should not have been part of the interface. T his update removes the unnecessary option as to not confuse users. JBIDE-5643: Within the Hibernate tab of the persistence.xm l editor, the button beside the Configuration file line was labeled Browse. T his was misleading as upon clicking the button the user would be asked setup a configuration file. T o provide an improved user experience, the button has now been altered to be called Setup and correctly guides the user through configuration file creation. JBIDE-5641: When specifying the persistence property: , an error could display saying that the hibernate.cfg.xm l file could not be found. T his occurred because the validator only considered full paths and not relative path naming. T his has since been corrected through the modification of the HibernatePersistenceUnit class. JBIDE-5499: Refactoring support has been added to Hibernate Code Generation Configurations. JBoss D eveloper Studio 3.0 3.0.0 Release Notes JBIDE-5411: T he New Hibernate XML Mapping file wizard used to show all available packages. T his update ensures that only packages containing java classes are shown. JBIDE-5408: T hree issues are fixed: T he new Hibernate XML Mapping file (hbm .xm l) would rewrite all hbm .xm l files without warning. T o correct this the entire result is written into the systems' temporary directory 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 this did not work. T he Finish without Preview now works as expected. After the merge, following the button clicks GoT o, Next, Back and then Finish would not work correctly. T his method of steps now functions as users would expect. JBIDE-5222: A new feature as been added that allows for support of filter configurations in closed projects for console configuration. T his option is available through Preferences → Run/Debug → Launching → Launch 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-5031: T o close a database connection a user would have to close the JBoss Developer Studio and then restart the application to continue work without the connection. T he database connection can now be closed from within the JBoss Developer Studio by choosing the Close Configuration menu item in Hibernate Console context m enu located in Hibernate Configurations View. JBIDE-4956: A feature has been added to the Mapping Diagram viewer so that it now displays relationships between database tables. JBIDE-4916: An editor for the hibernate.properties file has been added to the JBoss Developer Studio. T he editor supports content assist authoring. JBIDE-4899: T he Hibernate Configurations view was not updated after a hibernate console enabled project with console configuration was deleted from the workspace. T his meant that the console configuration was not removed along with the project. T his bug is rectified with this update. JBIDE-4780: T he Options tab now allows you to browse and set the NamingStrategy and EntityResolver. T he console configuration option has also been updated to react when one of the packages of a referenced class changes. JBIDE-4733: 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. JBIDE-4715: 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. T he toggle button interface ensures the experience remains consistent across all tools included within the JBoss Developer Studio. JBIDE-4662: Annotations support has been added to Hibernate T ools. T he addition of annotations support allows for interaction with the Eclipse Dali Java Persistence T ools Project plug-in. JBIDE-4451: T he 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 instance of each editor for each query. T his can be achieved by clicking the button of a tack to the right of the Max results: drop-won box in the editor. JBIDE-4450: T he Properties view has been updated with a new property called T ab name. T he addition of this property allows for a user to individually name each query tab, allowing for improved tab management. JBIDE-4227: T he Open Mapping File option now supports all possible configuration files. In the past only files called orm .xm l have been supported and this update now provides increased user 7 8 Table of Contents functionality. JavaServer Faces (JSF) JBIDE-5670: T he faceleted-taglib tag library was not supported in * taglib.xm l with XML Schema Definition (XSD). Support for this library has been added to this release of the JBoss Developers Studio, allowing for support of JavaServer Faces 2. JBIDE-5660: When setting the location of an within web.xm l, the location would not be recognized if it included a query string. For example the location views/error/error.xhtm l would be valid, whereas the location /views/error/error.xhtm l?statusCode=4 03 would not be valid. T his has been corrected by adding a test for a query string into the CheckResource.java file, allowing for locations to be specified that include a query string. JBIDE-5471: web-facesconfig_2_0.xsd support has been added to the JavaServer Faces Configuration editor. T his file provides the XML Schema for the JavaServer Faces Application Configuration File Version 2.0. JBIDE-5381: Content Assist has been added for use with the elements defined using the default namespace. JBIDE-5277: T he options to Add and Remove JSF support have been added to the project menu. JBIDE-5237: CSS Class Hyperlink for the class attribute of HT ML tags would not search through CSS loaded using JSF tags (for example: ). T his has now been fixed so that the searching of CSS classes returns the correct user expected results. JBIDE-5099: OpenOn support has been added for custom JSF 2.0 components. JBIDE-5097: Content Assist did not support multiple namespaces with the same Uniform Resource Identifier (URI).T his issue has been fixed by modifying Xm lContextIm pl class within the Xm lContextIm pl.java file from: nam eSpaces.get(region).put(nam eSpace.getURI(), nam eSpace); to nam eSpaces.get(region).put(nam eSpace.getPrefix(), nam eSpace);. JBIDE-5089: JSF Expression Language (EL) validation has been added for message bundles. T his improves the performance of the PageContextFactory. JBIDE-5015: Support for JSF 2.0 composition components has been added in this update. JBIDE-4978: JSF has been upgraded with the addition of Seam Expression Language (EL) support. T his now allows for JSF EL validation to use all available EL resolvers, providing increased validation over past releases. JBIDE-4970: KBbuilder now loads composite components from the JSF resource folders and adds them to the KB module. T his allows for the components to be available for code assistance. JBIDE-4771: T he Find Usages function has been improved to provide information about methods when inside an EL expression. JBIDE-2806: T he 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. T his limitation has now been corrected so that OpenOn works with all paths, including those set using the EL variable. T his is a great advantage to users as the Expression Language variable is 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. T he 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. T he bug has since been fixed by adding a schema for included page contexts. T his 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. T he information collected is as follows: Namespaces that are declared JBoss D eveloper Studio 3.0 3.0.0 Release Notes T ag libraries that are used Resource bundles that are declared JBIDE-512: T he drop-down box for context variable code completion has been upgraded for enhanced usability. T he 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. RichFaces JBIDE-5743: Content assistance in coding did not show anything for the tag . T he content assistance has been corrected by adding the icon attribute to the RichFaces.xm l tag library. JBIDE-5025: T he RichFaces libraries have been updated to version 3.3.2.SR1. Seam JBIDE-5275: T he Add Seam Support and Remove Seam Support items have been added to the Project menu. JBIDE-5221: T he JBoss Server View has now been replaced with the Server View in the Seam perspective. T his has occurred out of the JBoss Server View being deprecated. JBIDE-5192: T he name of the editor when using the Diagram Viewer was a concatenation of the names of the diagram entities, leading to a long name in some cases. T his issue has been corrected by modifying the Orm Diagram .java and Diagram Viewer.java files to display a name from the following three options (based on the number of entities): Console name: Entity name Console name: First Entity name and Second Entity name Console name: First Entity name and others JBIDE-5170: When changing, adding or removing a Seam runtime from within Window → Preferences → JBoss T ools → Web → Seam, Seam projects would not be built or validated. T he behavior has been changed to build and validate Seam projects upon changes in the Preferences section to ensure correct functioning of the project. T he Seam Runtim eManager.java file was updated to correct this. JBIDE-5012: T he Booking and DVDStore Seam examples have been updated for Seam 2.2 within the JBoss Enterprise Application Platform. JBIDE-4987: Seam and JPA Connection Profiles have been synchronized for this release. T he jpaconnection profile is used in the launch configuration instead of hibernate.properties if the JPA facet is installed. JBIDE-4985: Seam projects now create a Hibernate configuration that uses the selected connection profile directly (without copying its settings into the hibernate.properties file). JBIDE-4944: T he Seam wizards Action, Entity and Conversation had the ability to overwrite resources when they generated code. T he wizards would warn the user that some resources already existed and yet overwrite them. T his has been corrected through the modification of the Seam BaseOperation.java file. JBIDE-4856: Seam component methods and properties used in the Expression Language (EL) have been refactored. T his 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 search results. T he Renam e Participant 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 setter or getter method and have the Renam e Participant warn the user of the consequences of renaming a paired method. JBIDE-4136: Classloading issues were being faced by users of Seam T ools because the JBoss Developer Studio used the MANIFEST .MF file for creating an artifact classpath instead of using 9 10 Table of Contents the EAR lib/ directory that is recommended by Seam. Until now the JBoss Developer Studio has not been able to use the EAR lib/ 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 lib/ directory is now supported and the process of creating an artifact classpath has been updated. JBIDE-2807: An option is now provided when creating a New Seam Project, to not create a test project. T his 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 Create T est Project check box within the New Seam Project wizard. JBIDE-1452: Support has been added for the Seam PDF Facelet tag library. T his Facelet library allows for PDF creation from within Seam. JBIDE-1451: 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:message and mail:body as these components are rendered as divisions (using the

tag). JBIDE-1176: T he Seam Web Project now supports the JPA facet. Addition of the Java Persistence API allows for the management of relational data within applications. Smooks JBIDE-5259: T he Smooks configuration has received a test facility through the modification of the Run button to output a java result to the Console. T his allows a user to test Smooks projects in a simplified way. JBIDE-5088: When opening an existing Smooks configuration file it wouldn't contain any process information. T o correct this an input task is automatically created and the Smooks configuration file is analyzed to add any missing task types if necessary. During the course of this update a NullPointerException was also fixed. JBIDE-5086: A default layout is added in the Java-Mapping viewer. T his allows for the layout of the information in the Smooks editor to be rearranged into a predefined default layout. JBIDE-4878: T he Smooks Reader page has been replaced with a new Input page. While the Input page inherits many functions from the Reader page there are some differences as follows: T he Reader page allowed for multiple Readers to be created. Input page only allows for one Reader. T he Reader page supported the addition of multiple input data , where each was usable. T he Input page only allows for one piece of input data to be used, while still allowing for multiple pieces of input data. T he Reader page could view the transformation results of the Reader. T he new Input page utilizes an input model view to check the transform result. Struts JBIDE-5278: T he options to Add and Remove Struts support have been added to the project menu. Visual Page Editor JBIDE-5184: A memory leak existed in the Visual Page Editor. T o fix this leak, the following plug-ins have been modified: org.jboss.tools.vpe org.jboss.tools.vpe.xulrunner org.jboss.tools.jst.jsp T he issues that caused the memory leak were: JBoss D eveloper Studio 3.0 3.0.0 Release Notes 11 JSPMultiPageEditorSite: T he constructor created the serviceLocator that wasn't disposed of after use. T he XulRunnerBrowser.dispose() method would remove the progressListener, however this would only be done after all SWT objects and controls were already disposed. T his meant the method had no effect. T he dispose method is now called before the SWT objects and controls are disposed. T he MozillaEditor.getEditor() madethe Mozilla window editable using nsIEditingSession.setupEditorOnWindow(). T o counteract this the objects created are now removed by using nsIEditingSession.tearDownEditorOnWindow(). T he createPartControl() method in the MozillaEditor and MozillaPreview classes create XullRunnerEditor as an inner class. T he issue was that the XullRunnerEditor class retained a reference to MozillaEditor(MozillaPreview) that caused it not to be released and instead retain references to WST and EMF classes. T his has now been corrected so that MozillaEditor(MozillaPreview) is now released after use and references are not retained. JBIDE-5100: Support for JSF 2.0 attributes have been added to the Visual Page Editor. JBIDE-5091: Support for JSF 2.0 Composition components that come packaged into the Web Application Root has been added to the Visual Page Editor. JBIDE-5065: T he icons in the Visual Page Editor have been redesigned for improved aesthetic appearance. JBIDE-4945: A new feature has been added to the Visual Page Editor that allows a user to select both the element before and the element after a central element. T his has been achieved through the modification of the SelectionBar.java file. JBIDE-4934: Facelets tag library support has been added to the Palette for the Visual Page Editor. JBIDE-4914: T he Visual Page Editor has been redesigned so that all drop-down menu items are placed in the toolbar as buttons. JBIDE-4323: Z oom 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. JBIDE-2820: Support for new JSF 2.0 elements has been added to the Visual Page Editor. T he 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-2571: Selection of the 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 and unable to be selected from within the Visual Page Editor. Correction of the two clicks necessary to select the component has been completed by removing the check within VpeController.java that ensures the node is of type text. T he issue that did not allow for the selection of the and components was found to be a bug in XULRunner. T o correct this the XULRunner component has 12 Table of Contents been updated to version 1.9, which corrects this error and provides numerous other small bug fixes (JBIDE-2248. JBIDE-2248: T he XULRunner component has been upgraded to version 1.9. T his new version of XULRunner adds support for the newest HT ML and CSS features to the Visual Page Editor. Included in this is support for CSS3. JBIDE-1592: A new feature has been added that allows for Facelets tag libraries from file.jar/MET A-INF/* .tablib.xm l or those that are registered within web.xm l by the facelets.LIBRARIES context parameter to now be used within content assist 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 detected occurrences of searched annotations to not function correctly. T he action of these buttons has now been corrected so that a user can navigate their way through all found occurrences of a searched annotation. T his functionality works in the Visual Page Editor as it would work in a text editor. XHT ML Editor JBIDE-4946: T ool tips for tags and attributes in the XHT ML Editor have been added. XML Structured Editor JBIDE-5521: T he Web Servlet Mapping dialog box now contains a drop-down list for the ServletNam e field so that servlets that have been entered into the web.xm l file can be selected easily. JBIDE-5426: T he Servlet Mapping Editor Servlet-Nam e field has been improved with a drop-down menu to fill it in. General Issues JBIDE-5743: T he Web Servlet Mapping dialog box now contains a drop-down list for the ServletNam e field so that servlets that have been entered into the web.xm l file can be selected easily. JBIDE-5734: T he 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 Alt+Shift+Y. From this menu press F to full publish the project or B to build the full archive. JBIDE-5690: T he Full-Publish 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 Full-Publish would only re-deploy it to the first server returned in the list. T o solve this issue a user interface has been added for the Full-Publish 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. JBIDE-5383: Expression Language Code Assistance has been added for the @Name beans. T his allows for users to begin typing code and for suggestions of automatic completion to be suggested, improving user efficiency. JBIDE-5267: T he JBoss Enterprise Application Platform server would start correctly, however the JBoss Developer Studio would not acknowledge that it had started. T o counteract this the JMXPoller.java timeout behavior has been modified to always return that the server succeeded in starting instead of ignoring the timeout. T his fix ensures that a user is not informed that the server did not start correctly when it did. JBIDE-5153: A JavaMain tab has been added to the tab group to allow for customization of the main class of the server. T he changes to the main class are verified to persist by server startup checks. JBIDE-5122: JBoss Servers View has been removed with this release. All the functionality provided by this view can be found in the Servers View. JBoss D eveloper Studio 3.0 3.0.0 Release Notes 13 JBIDE-5048: SSH deployment has been added to the JBoss Developer Studio with this update. Specifically the following improvements have been made: A server type has been created that accepts SSH deployment for Eclipse Web T ools Platform (WT P) archives WT P, 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 interface (an IStatus object represents the outcome of an operation) JBIDE-5041: T he m enu key on the keyboard would not work in the Web Projects view, Seam Com ponents view or JBoss T ools XML Editor. T he functioning of this key has now been corrected so it behaves as a user would expect. JBIDE-5005: A new export wizard has been added to the JBoss Developer Studio. T he new wizard allows the export operation to utilize IModule objects. T his added feature reduces redundancy and inconsistency for the export operation. JBIDE-4976: T he JBoss T ools Palette has been intergrated into the standard Eclipse GEF Palette view. T he standard Palette view, accessible at Window → Show View → Others → General → Palette is now shown in the right top part of the Web Developm ent and Seam perspectives. T he JBoss T ools Palette remains at Window → Show View → Others → JBoss T ools Web → JBoss T ools Palette. T he differences in behavior between the palettes are: T he new Palette is filled only when the Visual Page Editor is open and activated. T he old palette remains static. T he expanded and collapsed state of tabs in the new palette is associated with the opened instance of the Visual Page Editor and not globally set as they were in the old palette. T his allows for the state of tabs to be different for individual files. Each new file opened in the Visual Page Editor will have the default Palette state with all tabs collapsed. T hough 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 Visual Page Editor, the old palette will remain accessible. JBIDE-4955: BPEL and ESB projects can now be excluded from deployment through the addition of new fileset capability. When the fileset is referenced the includes, excludes and root folder layout is implemented just as it is for archives. JBIDE-4888: T he portlet facets configuration utility has been added for m2eclipse. T his configuration utility allows for the following: If the pom .xm l file contains a portlet-api dependency, the JBoss Core Portlet facet is added. If the pom .xm l file contains portletbridge dependencies, the JBoss JSF Portlet facet is added. If the project contains Seam, JBoss Core Portlet and JBoss JSF Portlet facet, the JBoss Seam Portlet facet is added. JBIDE-4877: T ag completion has been upgraded so that partial matches are displayed and selectable following direct tag matches. JBIDE-4850: A new feature has been added to the CSS Views with this release that allows a user to edit styles inside HT ML and xhtm. JBIDE-3563: Code assist has been added for classes that are defined in linked CSS. T he schema for included page contexts has been added. T his 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. T he included page contexts are created and the following information is collected within the included contexts: Namespaces are declared within the included pages T ag libraries are used in the included pages 14 Table of Contents Resource bundles are declared within the included pages JBIDE-3125: OpenOn support has been added to the code editors. T his 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. JBIDE-2541: 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. T he JavaDoc comments are also available if they originated from a projects source folders. 4. Known Issues with this release Following is a list of known issues at the time of release. General Known Issues JBDS-1155: EAR projects that use classpath variable references to JAR files get packaged in /lib/lib instead of /lib. T his is due to a bug in Eclipse WT P, for which a bug fix will be released shortly. Until the bug fix is made available, it is possible to avoid this issue by editing the .settings/org.eclipse.wst.com m on.com ponent file and removing the archiveName attributes. JBIDE-3623: If you use the community Seam versions 2.1.0.SP1 or 2.1.1 T estNG for WAR projects they will fail with the error T wo components with the same name and precedence. T here is no known workaround, however all other Seam releases work correctly and all Seam 2.1 EAR projects are successful. JBIDE-779: Currently Facelet pages contain false warnings.T his has occured due to Eclipse WT P's HT ML Syntax Validation not allowing for Facelet specific attributes. T hese warnings can be stopped by disabling validation. T o disable validation follow Windows → Preferences → Validation → HT ML Syntax Validation . Important Disabling validation has the potential to remove useful warning information. JBoss D eveloper Studio 3.0 3.0.0 Release Notes A. Revision History Revision 0-4 Rebuild for Publican 3.0 2012-07-18 Revision 0-0 Mon Dec 21 2009 Initial creation of book by publican Anthony T owns Isaac Rooskov 15