November 2007 - jbosstools-commits

JBoss Tools SVN: r5168 - trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2007-11-30 10:10:04 -0500 (Fri, 30 Nov 2007) New Revision: 5168 Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/AbstractSeamContentProvider.java Log: JBIDE-1391 Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/AbstractSeamContentProvider.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/AbstractSeamContentProvider.java 2007-11-30 15:09:23 UTC (rev 5167) +++ trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/AbstractSeamContentProvider.java 2007-11-30 15:10:04 UTC (rev 5168) @@ -163,8 +163,10 @@ for (ISeamComponent c : p.getComponents()) { children.add(c); } - for (ISeamPackage pc : p.getPackages().values()) { - children.add(pc); + if(!isPackageStructureFlat()) { + for (ISeamPackage pc : p.getPackages().values()) { + children.add(pc); + } } return children.toArray(new Object[0]); } else if(parentElement instanceof ISeamComponent) {

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5167 - trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2007-11-30 10:09:23 -0500 (Fri, 30 Nov 2007) New Revision: 5167 Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/SeamReferencedFilter.java Log: JBIDE-1392 Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/SeamReferencedFilter.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/SeamReferencedFilter.java 2007-11-30 15:06:56 UTC (rev 5166) +++ trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/SeamReferencedFilter.java 2007-11-30 15:09:23 UTC (rev 5167) @@ -10,6 +10,7 @@ ******************************************************************************/ package org.jboss.tools.seam.ui.views; +import java.util.Map; import java.util.Set; import org.eclipse.core.resources.IResource; @@ -17,6 +18,7 @@ import org.eclipse.jface.viewers.ViewerFilter; import org.jboss.tools.seam.core.ISeamComponent; import org.jboss.tools.seam.core.ISeamComponentDeclaration; +import org.jboss.tools.seam.core.ISeamPackage; /** * @@ -29,22 +31,42 @@ public boolean select(Viewer viewer, Object parentElement, Object element) { if(element instanceof ISeamComponent) { ISeamComponent component = (ISeamComponent)element; - Set<ISeamComponentDeclaration> ds = component.getAllDeclarations(); - for (ISeamComponentDeclaration d : ds) { - IResource r = d.getResource(); - if(r == null || !r.exists()) { - //do not filter out the component if we cannot be sure that - //its source is another project - return true; - } - if(r != null && r.getProject() == d.getSeamProject().getProject()) { - return true; - } - } - return false; + return isComponentDeclaredInThisProject(component); + } else if(element instanceof ISeamPackage) { + ISeamPackage pkg = (ISeamPackage)element; + return isPackageDeclaredInThisProject(pkg); } return true; } + + boolean isComponentDeclaredInThisProject(ISeamComponent component) { + Set<ISeamComponentDeclaration> ds = component.getAllDeclarations(); + for (ISeamComponentDeclaration d : ds) { + IResource r = d.getResource(); + if(r == null || !r.exists()) { + //do not filter out the component if we cannot be sure that + //its source is another project + return true; + } + if(r != null && r.getProject() == d.getSeamProject().getProject()) { + return true; + } + } + return false; + } + boolean isPackageDeclaredInThisProject(ISeamPackage pkg) { + Set<ISeamComponent> cs = pkg.getComponents(); + for (ISeamComponent c : pkg.getComponents()) { + if(isComponentDeclaredInThisProject(c)) return true; + } + Map<String,ISeamPackage> ps = pkg.getPackages(); + for (ISeamPackage p : ps.values()) { + if(isPackageDeclaredInThisProject(p)) { + return true; + } + } + return false; + } }

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5166 - trunk/seam/plugins/org.jboss.tools.seam.xml/schemas.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2007-11-30 10:06:56 -0500 (Fri, 30 Nov 2007) New Revision: 5166 Modified: trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/pageflow-2.0.xsd Log: JBIDE-1397 Modified: trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/pageflow-2.0.xsd =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/pageflow-2.0.xsd 2007-11-30 14:37:15 UTC (rev 5165) +++ trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/pageflow-2.0.xsd 2007-11-30 15:06:56 UTC (rev 5166) @@ -1,336 +1,333 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<xs:schema xmlns="http://jboss.com/products/seam/pageflow" - targetNamespace="http://jboss.com/products/seam/pageflow" - xmlns:xs="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified"> - -  -  - <xs:element name="pageflow-definition"> - <xs:complexType> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:group ref="start-node-elements" /> - <xs:group ref="node-elements" /> - <xs:group ref="end-node-elements" /> - <xs:group ref="action-elements" /> - <xs:element ref="event" /> - <xs:element ref="exception-handler" /> - </xs:choice> - <xs:attribute name="name" type="xs:string" use="required" /> - </xs:complexType> - </xs:element> - -  -  - <xs:element name="start-state"> - <xs:complexType> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:element ref="transition" /> - <xs:element ref="event" /> - <xs:element ref="exception-handler" /> - </xs:choice> - <xs:attribute name="name" type="xs:string" /> - </xs:complexType> - </xs:element> - - <xs:element name="end-state"> - <xs:complexType> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:element ref="event" /> - <xs:element ref="exception-handler" /> - </xs:choice> - <xs:attribute name="name" type="xs:string" use="required" /> - </xs:complexType> - </xs:element> - - <xs:element name="process-state"> - <xs:complexType> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:element ref="sub-process" /> - <xs:element ref="transition" /> - <xs:element ref="event" /> - <xs:element ref="exception-handler" /> - </xs:choice> - <xs:attribute name="name" type="xs:string" /> - </xs:complexType> - </xs:element> - - <xs:element name="sub-process"> - <xs:complexType> - <xs:attribute name="name" type="xs:string" use="required" /> - </xs:complexType> - </xs:element> - - <xs:element name="start-page"> - <xs:complexType> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:group ref="page-elements" /> - </xs:choice> - <xs:attributeGroup ref="page-attributes" /> - </xs:complexType> - </xs:element> - - <xs:element name="decision"> - <xs:complexType> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:element name="handler" type="delegation" /> - <xs:element ref="event" /> - <xs:element ref="exception-handler" /> - <xs:element name="transition"> - <xs:complexType> - <xs:choice minOccurs="0" - maxOccurs="unbounded"> - <xs:element name="condition"> - <xs:complexType mixed="true"> - <xs:sequence minOccurs="0" - maxOccurs="unbounded"> - <xs:any processContents="lax" - minOccurs="0" maxOccurs="unbounded" /> - </xs:sequence> - <xs:attribute name="expression" - type="xs:string" /> - </xs:complexType> - </xs:element> - <xs:group ref="action-elements" /> - <xs:element ref="exception-handler" /> - </xs:choice> - <xs:attribute name="to" type="xs:string" - use="required" /> - <xs:attribute name="name" type="xs:string" /> - </xs:complexType> - </xs:element> - </xs:choice> - <xs:attribute name="name" type="xs:string" use="required" /> - <xs:attribute name="expression" type="xs:string" /> - </xs:complexType> - </xs:element> - - <xs:element name="page"> - <xs:complexType> - <xs:sequence> - <xs:choice minOccurs="0" maxOccurs="1"> - <xs:element ref="end-conversation" /> - </xs:choice> - <xs:choice minOccurs="0" maxOccurs="1"> - <xs:element ref="end-task" /> - </xs:choice> - <xs:group ref="page-elements" /> - </xs:sequence> - <xs:attributeGroup ref="page-attributes" /> - </xs:complexType> - </xs:element> - - <xs:element name="redirect" /> - <xs:element name="description" type="xs:string" /> - - <xs:element name="end-conversation"> - <xs:complexType> - <xs:attribute name="before-redirect" type="booleanType" /> - <xs:attribute name="create-process" type="xs:string" /> - </xs:complexType> - </xs:element> - - <xs:element name="end-task"> - <xs:complexType> - <xs:attribute name="transition" type="xs:string" /> - </xs:complexType> - </xs:element> - -  -  - <xs:element name="transition"> - <xs:complexType> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:group ref="action-elements" /> - <xs:element ref="exception-handler" /> - </xs:choice> - <xs:attribute name="to" type="xs:string" use="required" /> - <xs:attribute name="name" type="xs:string" /> - </xs:complexType> - </xs:element> - -  -  - <xs:element name="action"> - <xs:complexType mixed="true"> - <xs:sequence> - <xs:any processContents="lax" minOccurs="0" - maxOccurs="unbounded" /> - </xs:sequence> - <xs:attribute name="class" type="xs:string" /> - <xs:attribute name="config-type" default="field"> - <xs:simpleType> - <xs:restriction base="xs:string"> - <xs:enumeration value="field" /> - <xs:enumeration value="bean" /> - <xs:enumeration value="constructor" /> - <xs:enumeration value="configuration-property" /> - </xs:restriction> - </xs:simpleType> - </xs:attribute> - <xs:attribute name="name" type="xs:string" /> - <xs:attribute name="ref-name" type="xs:string" /> - <xs:attribute name="accept-propagated-events" - type="booleanType" default="true" /> - <xs:attribute name="expression" type="xs:string" /> - </xs:complexType> - </xs:element> - - <xs:element name="script"> - <xs:complexType mixed="true"> - <xs:sequence> - <xs:any processContents="lax" minOccurs="0" - maxOccurs="unbounded" /> - </xs:sequence> - <xs:attribute name="name" type="xs:string" /> - <xs:attribute name="accept-propagated-events" - type="booleanType" default="true" /> - </xs:complexType> - </xs:element> - -  -  - <xs:element name="event"> - <xs:complexType> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:group ref="action-elements" /> - </xs:choice> - <xs:attribute name="type" use="required"> - <xs:simpleType> - <xs:union> - <xs:simpleType> - <xs:restriction base="xs:string" /> - </xs:simpleType> - <xs:simpleType> - <xs:restriction base="xs:string"> - <xs:enumeration value="node-enter" /> - <xs:enumeration value="node-leave" /> - <xs:enumeration value="process-start" /> - <xs:enumeration value="process-end" /> - <xs:enumeration value="task-create" /> - <xs:enumeration value="task-assign" /> - <xs:enumeration value="task-start" /> - <xs:enumeration value="task-end" /> - <xs:enumeration value="before-signal" /> - <xs:enumeration value="after-signal" /> - </xs:restriction> - </xs:simpleType> - </xs:union> - </xs:simpleType> - </xs:attribute> - </xs:complexType> - </xs:element> - -  -  - <xs:element name="exception-handler"> - <xs:complexType> - <xs:choice minOccurs="1" maxOccurs="unbounded"> - <xs:element ref="action" /> - <xs:element ref="script" /> - </xs:choice> - <xs:attribute name="exception-class" type="xs:string" /> - </xs:complexType> - </xs:element> - -  -  - <xs:complexType name="delegation" mixed="true"> - <xs:sequence> - <xs:any processContents="lax" minOccurs="0" - maxOccurs="unbounded" /> - </xs:sequence> - <xs:attribute name="class" type="xs:string" /> - <xs:attribute name="config-type" default="field"> - <xs:simpleType> - <xs:restriction base="xs:string"> - <xs:enumeration value="field" /> - <xs:enumeration value="bean" /> - <xs:enumeration value="constructor" /> - <xs:enumeration value="configuration-property" /> - </xs:restriction> - </xs:simpleType> - </xs:attribute> - </xs:complexType> - - <xs:simpleType name="configType"> - <xs:restriction base="xs:string"> - <xs:enumeration value="field" /> - <xs:enumeration value="bean" /> - <xs:enumeration value="constructor" /> - <xs:enumeration value="configuration-property" /> - </xs:restriction> - </xs:simpleType> - - <xs:simpleType name="booleanType"> - <xs:restriction base="xs:string"> - <xs:enumeration value="yes" /> - <xs:enumeration value="no" /> - <xs:enumeration value="true" /> - <xs:enumeration value="false" /> - <xs:enumeration value="on" /> - <xs:enumeration value="off" /> - </xs:restriction> - </xs:simpleType> - - <xs:simpleType name="enabledType"> - <xs:restriction base="xs:string"> - <xs:enumeration value="enabled" /> - <xs:enumeration value="disabled" /> - </xs:restriction> - </xs:simpleType> - - <xs:group name="start-node-elements"> - <xs:choice> - <xs:element ref="start-state" /> - <xs:element ref="start-page" /> - </xs:choice> - </xs:group> - - <xs:group name="node-elements"> - <xs:choice> - <xs:element ref="page" /> - <xs:element ref="decision" /> - <xs:element ref="process-state" /> - </xs:choice> - </xs:group> - - <xs:group name="end-node-elements"> - <xs:choice> - <xs:element ref="end-state" /> - </xs:choice> - </xs:group> - - <xs:group name="action-elements"> - <xs:choice> - <xs:element ref="action" /> - </xs:choice> - </xs:group> - - <xs:group name="page-elements"> - <xs:sequence> - <xs:choice minOccurs="0"> - <xs:element ref="description" /> - <xs:element ref="redirect" /> - </xs:choice> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:element ref="event" /> - <xs:element ref="exception-handler" /> - <xs:element ref="transition" /> - <xs:group ref="action-elements" /> - </xs:choice> - </xs:sequence> - </xs:group> - - <xs:attributeGroup name="page-attributes"> - <xs:attribute name="redirect" type="booleanType" /> - <xs:attribute name="switch" type="enabledType" /> - <xs:attribute name="no-conversation-view-id" type="xs:string" /> - <xs:attribute name="timeout" type="xs:int" /> - <xs:attribute name="back" type="enabledType" /> - <xs:attribute name="view-id" type="xs:string" use="required" /> - <xs:attribute name="name" type="xs:string" use="required" /> - </xs:attributeGroup> - -</xs:schema> +<?xml version="1.0" encoding="UTF-8"?> + +<xs:schema xmlns="http://jboss.com/products/seam/pageflow" + targetNamespace="http://jboss.com/products/seam/pageflow" + xmlns:xs="http://www.w3.org/2001/XMLSchema" + elementFormDefault="qualified"> + +  +  + <xs:element name="pageflow-definition"> + <xs:complexType> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:group ref="start-node-elements" /> + <xs:group ref="node-elements" /> + <xs:group ref="end-node-elements" /> + <xs:group ref="action-elements" /> + <xs:element ref="event" /> + <xs:element ref="exception-handler" /> + </xs:choice> + <xs:attribute name="name" type="xs:string" use="required" /> + <xs:attribute name="start-page" type="xs:string" /> + </xs:complexType> + </xs:element> + +  +  + <xs:element name="start-state"> + <xs:complexType> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:element ref="transition" /> + <xs:element ref="event" /> + <xs:element ref="exception-handler" /> + </xs:choice> + <xs:attribute name="name" type="xs:string" /> + </xs:complexType> + </xs:element> + + <xs:element name="end-state"> + <xs:complexType> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:element ref="event" /> + <xs:element ref="exception-handler" /> + </xs:choice> + <xs:attribute name="name" type="xs:string" use="required" /> + </xs:complexType> + </xs:element> + + <xs:element name="process-state"> + <xs:complexType> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:element ref="sub-process" /> + <xs:element ref="transition" /> + <xs:element ref="event" /> + <xs:element ref="exception-handler" /> + </xs:choice> + <xs:attribute name="name" type="xs:string" /> + </xs:complexType> + </xs:element> + + <xs:element name="sub-process"> + <xs:complexType> + <xs:attribute name="name" type="xs:string" use="required" /> + </xs:complexType> + </xs:element> + + <xs:element name="start-page"> + <xs:complexType> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:group ref="page-elements" /> + </xs:choice> + <xs:attributeGroup ref="page-attributes" /> + </xs:complexType> + </xs:element> + + <xs:element name="decision"> + <xs:complexType> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:element name="handler" type="delegation" /> + <xs:element ref="event" /> + <xs:element ref="exception-handler" /> + <xs:element name="transition"> + <xs:complexType> + <xs:choice minOccurs="0" + maxOccurs="unbounded"> + <xs:element name="condition"> + <xs:complexType mixed="true"> + <xs:sequence minOccurs="0" + maxOccurs="unbounded"> + <xs:any processContents="lax" + minOccurs="0" maxOccurs="unbounded" /> + </xs:sequence> + <xs:attribute name="expression" + type="xs:string" /> + </xs:complexType> + </xs:element> + <xs:group ref="action-elements" /> + <xs:element ref="exception-handler" /> + </xs:choice> + <xs:attribute name="to" type="xs:string" + use="required" /> + <xs:attribute name="name" type="xs:string" /> + </xs:complexType> + </xs:element> + </xs:choice> + <xs:attribute name="name" type="xs:string" use="required" /> + <xs:attribute name="expression" type="xs:string" /> + </xs:complexType> + </xs:element> + + <xs:element name="page"> + <xs:complexType> + <xs:sequence> + <xs:choice minOccurs="0" maxOccurs="1"> + <xs:element ref="end-conversation" /> + </xs:choice> + <xs:choice minOccurs="0" maxOccurs="1"> + <xs:element ref="end-task" /> + </xs:choice> + <xs:group ref="page-elements" /> + </xs:sequence> + <xs:attributeGroup ref="page-attributes" /> + </xs:complexType> + </xs:element> + + <xs:element name="redirect" /> + <xs:element name="description" type="xs:string" /> + + <xs:element name="end-conversation"> + <xs:complexType> + <xs:attribute name="before-redirect" type="booleanType" /> + <xs:attribute name="create-process" type="xs:string" /> + </xs:complexType> + </xs:element> + + <xs:element name="end-task"> + <xs:complexType> + <xs:attribute name="transition" type="xs:string" /> + </xs:complexType> + </xs:element> + +  +  + <xs:element name="transition"> + <xs:complexType> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:group ref="action-elements" /> + <xs:element ref="exception-handler" /> + </xs:choice> + <xs:attribute name="to" type="xs:string" use="required" /> + <xs:attribute name="name" type="xs:string" /> + </xs:complexType> + </xs:element> + +  +  + <xs:element name="action"> + <xs:complexType mixed="true"> + <xs:sequence> + <xs:any processContents="lax" minOccurs="0" + maxOccurs="unbounded" /> + </xs:sequence> + <xs:attribute name="class" type="xs:string" /> + <xs:attribute name="config-type" default="field"> + <xs:simpleType> + <xs:restriction base="xs:string"> + <xs:enumeration value="field" /> + <xs:enumeration value="bean" /> + <xs:enumeration value="constructor" /> + <xs:enumeration value="configuration-property" /> + </xs:restriction> + </xs:simpleType> + </xs:attribute> + <xs:attribute name="name" type="xs:string" /> + <xs:attribute name="ref-name" type="xs:string" /> + <xs:attribute name="accept-propagated-events" + type="booleanType" default="true" /> + <xs:attribute name="expression" type="xs:string" /> + </xs:complexType> + </xs:element> + + <xs:element name="script"> + <xs:complexType mixed="true"> + <xs:sequence> + <xs:any processContents="lax" minOccurs="0" + maxOccurs="unbounded" /> + </xs:sequence> + <xs:attribute name="name" type="xs:string" /> + <xs:attribute name="accept-propagated-events" + type="booleanType" default="true" /> + </xs:complexType> + </xs:element> + +  +  + <xs:element name="event"> + <xs:complexType> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:group ref="action-elements" /> + </xs:choice> + <xs:attribute name="type" use="required"> + <xs:simpleType> + <xs:union> + <xs:simpleType> + <xs:restriction base="xs:string" /> + </xs:simpleType> + <xs:simpleType> + <xs:restriction base="xs:string"> + <xs:enumeration value="node-enter" /> + <xs:enumeration value="node-leave" /> + <xs:enumeration value="process-start" /> + <xs:enumeration value="process-end" /> + <xs:enumeration value="task-create" /> + <xs:enumeration value="task-assign" /> + <xs:enumeration value="task-start" /> + <xs:enumeration value="task-end" /> + <xs:enumeration value="before-signal" /> + <xs:enumeration value="after-signal" /> + </xs:restriction> + </xs:simpleType> + </xs:union> + </xs:simpleType> + </xs:attribute> + </xs:complexType> + </xs:element> + +  +  + <xs:element name="exception-handler"> + <xs:complexType> + <xs:choice minOccurs="1" maxOccurs="unbounded"> + <xs:element ref="action" /> + <xs:element ref="script" /> + </xs:choice> + <xs:attribute name="exception-class" type="xs:string" /> + </xs:complexType> + </xs:element> + +  +  + <xs:complexType name="delegation" mixed="true"> + <xs:sequence> + <xs:any processContents="lax" minOccurs="0" + maxOccurs="unbounded" /> + </xs:sequence> + <xs:attribute name="class" type="xs:string" /> + <xs:attribute name="config-type" default="field"> + <xs:simpleType> + <xs:restriction base="xs:string"> + <xs:enumeration value="field" /> + <xs:enumeration value="bean" /> + <xs:enumeration value="constructor" /> + <xs:enumeration value="configuration-property" /> + </xs:restriction> + </xs:simpleType> + </xs:attribute> + </xs:complexType> + + <xs:simpleType name="configType"> + <xs:restriction base="xs:string"> + <xs:enumeration value="field" /> + <xs:enumeration value="bean" /> + <xs:enumeration value="constructor" /> + <xs:enumeration value="configuration-property" /> + </xs:restriction> + </xs:simpleType> + + <xs:simpleType name="booleanType"> + <xs:restriction base="xs:string"> + <xs:enumeration value="yes" /> + <xs:enumeration value="no" /> + <xs:enumeration value="true" /> + <xs:enumeration value="false" /> + <xs:enumeration value="on" /> + <xs:enumeration value="off" /> + </xs:restriction> + </xs:simpleType> + + <xs:simpleType name="enabledType"> + <xs:restriction base="xs:string"> + <xs:enumeration value="enabled" /> + <xs:enumeration value="disabled" /> + </xs:restriction> + </xs:simpleType> + + <xs:group name="start-node-elements"> + <xs:choice> + <xs:element ref="start-state" /> + <xs:element ref="start-page" /> + </xs:choice> + </xs:group> + + <xs:group name="node-elements"> + <xs:choice> + <xs:element ref="page" /> + <xs:element ref="decision" /> + <xs:element ref="process-state" /> + </xs:choice> + </xs:group> + + <xs:group name="end-node-elements"> + <xs:choice> + <xs:element ref="end-state" /> + </xs:choice> + </xs:group> + + <xs:group name="action-elements"> + <xs:choice> + <xs:element ref="action" /> + </xs:choice> + </xs:group> + + <xs:group name="page-elements"> + <xs:sequence> + <xs:element ref="description" maxOccurs="1" minOccurs="0"/> + <xs:element ref="redirect" maxOccurs="1" minOccurs="0"/> + <xs:element ref="event" minOccurs="0" maxOccurs="unbounded"/> + <xs:element ref="exception-handler" minOccurs="0" maxOccurs="unbounded"/> + <xs:element ref="transition" maxOccurs="unbounded" minOccurs="0"/> + <xs:group ref="action-elements" minOccurs="0" maxOccurs="1" /> + </xs:sequence> + </xs:group> + + <xs:attributeGroup name="page-attributes"> + <xs:attribute name="redirect" type="xs:boolean" /> + <xs:attribute name="switch" type="enabledType" /> + <xs:attribute name="no-conversation-view-id" type="xs:string" /> + <xs:attribute name="timeout" type="xs:int" /> + <xs:attribute name="back" type="enabledType" /> + <xs:attribute name="view-id" type="xs:string" use="required" /> + <xs:attribute name="name" type="xs:string" use="required" /> + </xs:attributeGroup> + +</xs:schema>

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5165 - trunk/seam/plugins/org.jboss.tools.seam.xml/schemas.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2007-11-30 09:37:15 -0500 (Fri, 30 Nov 2007) New Revision: 5165 Modified: trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/international-2.0.xsd Log: JBIDE-1397 Modified: trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/international-2.0.xsd =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/international-2.0.xsd 2007-11-30 14:26:41 UTC (rev 5164) +++ trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/international-2.0.xsd 2007-11-30 14:37:15 UTC (rev 5165) @@ -1,45 +1,45 @@ -<?xml version="1.0" encoding="UTF-8"?> -<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" - targetNamespace="http://jboss.com/products/seam/international" xmlns:international="http://jboss.com/products/seam/international" - xmlns:components="http://jboss.com/products/seam/components" attributeFormDefault="unqualified"> - <xs:import namespace="http://jboss.com/products/seam/components" schemaLocation="components-2.0.xsd"/> - - <xs:element name="locale-selector"> - <xs:complexType mixed="true"> - <xs:attributeGroup ref="components:attlist.component"/> - <xs:attributeGroup ref="international:attlist.localeSelector"/> - </xs:complexType> - </xs:element> - <xs:attributeGroup name="attlist.localeSelector"> - <xs:attribute name="locale-string"/> - <xs:attribute name="cookie-max-age"> - <xs:attribute name="cookie-enabled"> - <xs:simpleType> - <xs:restriction base="xs:token"> - <xs:enumeration value="true"/> - <xs:enumeration value="false"/> - </xs:restriction> - </xs:simpleType> - </xs:attribute> - </xs:attributeGroup> - - <xs:element name="time-zone-selector"> - <xs:complexType mixed="true"> - <xs:attributeGroup ref="components:attlist.component"/> - <xs:attributeGroup ref="international:attlist.timeZoneSelector"/> - </xs:complexType> - </xs:element> - <xs:attributeGroup name="attlist.timeZoneSelector"> - <xs:attribute name="time-zone-id"/> - <xs:attribute name="cookie-max-age"> - <xs:attribute name="cookie-enabled"> - <xs:simpleType> - <xs:restriction base="xs:token"> - <xs:enumeration value="true"/> - <xs:enumeration value="false"/> - </xs:restriction> - </xs:simpleType> - </xs:attribute> - </xs:attributeGroup> - -</xs:schema> +<?xml version="1.0" encoding="UTF-8"?> +<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" + targetNamespace="http://jboss.com/products/seam/international" xmlns:international="http://jboss.com/products/seam/international" + xmlns:components="http://jboss.com/products/seam/components" attributeFormDefault="unqualified"> + <xs:import namespace="http://jboss.com/products/seam/components" schemaLocation="components-2.0.xsd"/> + + <xs:element name="locale-selector"> + <xs:complexType mixed="true"> + <xs:attributeGroup ref="components:attlist.component"/> + <xs:attributeGroup ref="international:attlist.localeSelector"/> + </xs:complexType> + </xs:element> + <xs:attributeGroup name="attlist.localeSelector"> + <xs:attribute name="locale-string"/> + <xs:attribute name="cookie-max-age"/> + <xs:attribute name="cookie-enabled"> + <xs:simpleType> + <xs:restriction base="xs:token"> + <xs:enumeration value="true"/> + <xs:enumeration value="false"/> + </xs:restriction> + </xs:simpleType> + </xs:attribute> + </xs:attributeGroup> + + <xs:element name="time-zone-selector"> + <xs:complexType mixed="true"> + <xs:attributeGroup ref="components:attlist.component"/> + <xs:attributeGroup ref="international:attlist.timeZoneSelector"/> + </xs:complexType> + </xs:element> + <xs:attributeGroup name="attlist.timeZoneSelector"> + <xs:attribute name="time-zone-id"/> + <xs:attribute name="cookie-max-age"/> + <xs:attribute name="cookie-enabled"> + <xs:simpleType> + <xs:restriction base="xs:token"> + <xs:enumeration value="true"/> + <xs:enumeration value="false"/> + </xs:restriction> + </xs:simpleType> + </xs:attribute> + </xs:attributeGroup> + +</xs:schema>

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5164 - in trunk/seam/plugins/org.jboss.tools.seam.xml: schemas and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2007-11-30 09:26:41 -0500 (Fri, 30 Nov 2007) New Revision: 5164 Modified: trunk/seam/plugins/org.jboss.tools.seam.xml/resources/meta/seam-core.meta trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/core-2.0.xsd Log: JBIDE-1397 Modified: trunk/seam/plugins/org.jboss.tools.seam.xml/resources/meta/seam-core.meta =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.xml/resources/meta/seam-core.meta 2007-11-30 13:55:10 UTC (rev 5163) +++ trunk/seam/plugins/org.jboss.tools.seam.xml/resources/meta/seam-core.meta 2007-11-30 14:26:41 UTC (rev 5164) @@ -1316,6 +1316,55 @@ </XModelEntity> <XModelEntity ImplementingClass="%Custom%" PROPERTIES="formFactory=%Default%;formLayout=org.jboss.tools.seam.xml.ui.editor.form.core.SeamComponentsCoreFormLayoutData" + XMLSUBPATH="core:resource-loader" name="SeamCoreResourceLoader20"> + <XChildrenEntities> + <XChildEntity maxCount="1" name="SeamCoreBundleNames" required="yes"/> + </XChildrenEntities> + <XEntityRenderer> + <ICONS> + <ICON info="main.seam.core.bundle" type="main"/> + </ICONS> + </XEntityRenderer> + <XModelAttributes> + <XModelAttribute default="resource loader" loader="ElementType" name="element type"> + <Editor name="Uneditable"/> + </XModelAttribute> + <XModelAttribute PROPERTIES="id=true;category=general" + default="org.jboss.seam.core.resourceBundle" name="name" xmlname="name"/> + <XModelAttributeReference + attributes="class,scope,precedence,installed,auto-create" + entity="SeamComponent" name="component"/> + <XModelAttribute PROPERTIES="category=general" name="bundle-names" xmlname="bundle-names"/> + <XModelAttribute TRIM="no" name="comment" visibility="false" xmlname="#comment"> + <Editor name="Note"/> + </XModelAttribute> + </XModelAttributes> + <XActionItem kind="list"> + <XActionItem kind="list" name="CreateActions"/> + <XActionItem ICON="action.empty" displayName="Create" kind="list" name="EditActions"/> + <XActionItem ICON="action.copy" displayName="Copy" kind="list" name="CopyActions"> + <XActionItem BaseActionName="Copy" HandlerClassName="%Copy%" + ICON="action.copy" displayName="Copy" kind="action" name="Copy"/> + <XActionItem BaseActionName="Cut" HandlerClassName="%Cut%" + ICON="action.cut" displayName="Cut" kind="action" name="Cut"/> + </XActionItem> + <XActionItem ICON="action.delete" displayName="Delete" kind="list" name="DeleteActions"> + <XActionItem BaseActionName="Delete" HandlerClassName="%Delete%" + ICON="action.delete" displayName="Delete" kind="action" name="Delete"/> + </XActionItem> + <XActionItem ICON="action.empty" kind="list" name="Properties"> + <XActionItem HandlerClassName="%Properties%" ICON="action.empty" + displayName="Properties..." kind="action" name="Properties"/> + </XActionItem> + <XActionItem displayName="move" kind="list" name="MoveActions"> + <XActionItem HIDE="always" HandlerClassName="%Move%" + ICON="action.move" displayName="Move" kind="action" name="Move"/> + </XActionItem> + </XActionItem> + <XDependencies/> + </XModelEntity> + <XModelEntity ImplementingClass="%Custom%" + PROPERTIES="formFactory=%Default%;formLayout=org.jboss.tools.seam.xml.ui.editor.form.core.SeamComponentsCoreFormLayoutData" XMLSUBPATH="core:time-zone-selector" name="SeamCoreTimeZoneSelector"> <XChildrenEntities/> <XEntityRenderer> @@ -1709,7 +1758,7 @@ <XChildEntity name="SeamCoreInit"/> <XChildEntity name="SeamCoreManager"/> <XChildEntity name="SeamCorePojoCache"/> - <XChildEntity name="SeamCoreResourceBundle"/> + <XChildEntity name="SeamCoreResourceLoader20"/> <XChildEntity name="SeamBPMActor20"/> <XChildEntity name="SeamBPMJBPM20"/> </XChildrenEntities> @@ -1745,8 +1794,8 @@ </XActionItem> <XActionItem HandlerClassName="%Create%" ICON="action.empty" PROPERTIES="validator.add=true" WizardClassName="%Default%" - displayName="Resource Bundle..." kind="action" name="AddResourceBundle"> - <EntityData EntityName="SeamCoreResourceBundle"> + displayName="Resource Loader..." kind="action" name="AddResourceLoader"> + <EntityData EntityName="SeamCoreResourceLoader20"> <AttributeData AttributeName="name"/> <AttributeData AttributeName="bundle-names" Mandatory="no"/> </EntityData> @@ -1807,8 +1856,8 @@ </XActionItem> <XActionItem HandlerClassName="%Create%" ICON="action.empty" PROPERTIES="validator.add=true" WizardClassName="%Default%" - displayName="Resource Bundle..." kind="action" name="AddResourceBundle"> - <EntityData EntityName="SeamCoreResourceBundle"> + displayName="Resource Loader..." kind="action" name="AddResourceLoader"> + <EntityData EntityName="SeamCoreResourceLoader20"> <AttributeData AttributeName="name"/> <AttributeData AttributeName="bundle-names" Mandatory="no"/> </EntityData> Modified: trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/core-2.0.xsd =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/core-2.0.xsd 2007-11-30 13:55:10 UTC (rev 5163) +++ trunk/seam/plugins/org.jboss.tools.seam.xml/schemas/core-2.0.xsd 2007-11-30 14:26:41 UTC (rev 5164) @@ -1,71 +1,71 @@ -<?xml version="1.0" encoding="UTF-8"?> -<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" - targetNamespace="http://jboss.com/products/seam/core" xmlns:core="http://jboss.com/products/seam/core" - xmlns:components="http://jboss.com/products/seam/components" attributeFormDefault="unqualified"> - <xs:import namespace="http://jboss.com/products/seam/components" schemaLocation="components-2.0.xsd"/> - - <xs:element name="init"> - <xs:complexType mixed="true"> - <xs:attributeGroup ref="components:attlist.component"/> - <xs:attributeGroup ref="core:attlist.init"/> - </xs:complexType> - </xs:element> - <xs:attributeGroup name="attlist.init"> - <xs:attribute name="debug"> - <xs:simpleType> - <xs:restriction base="xs:token"> - <xs:enumeration value="true"/> - <xs:enumeration value="false"/> - </xs:restriction> - </xs:simpleType> - </xs:attribute> - <xs:attribute name="jndi-pattern"/> - <xs:attribute name="transaction-management-enabled"> - <xs:simpleType> - <xs:restriction base="xs:token"> - <xs:enumeration value="true"/> - <xs:enumeration value="false"/> - </xs:restriction> - </xs:simpleType> - </xs:attribute> - <xs:attribute name="user-transaction-name"/> - </xs:attributeGroup> - - <xs:element name="manager"> - <xs:complexType mixed="true"> - <xs:attributeGroup ref="components:attlist.component"/> - <xs:attributeGroup ref="core:attlist.manager"/> - </xs:complexType> - </xs:element> - <xs:attributeGroup name="attlist.manager"> - <xs:attribute name="concurrent-request-timeout" type="xs:integer"/> - <xs:attribute name="conversation-timeout" type="xs:integer"/> - <xs:attribute name="conversation-id-parameter"/> - <xs:attribute name="parent-conversation-id-parameter"/> - </xs:attributeGroup> - - <xs:element name="resource-bundle"> - <xs:complexType mixed="true"> - <xs:choice minOccurs="0" maxOccurs="unbounded"> - <xs:element ref="core:bundle-names"/> - </xs:choice> - <xs:attributeGroup ref="components:attlist.component"/> - <xs:attributeGroup ref="core:attlist.resourceBundle"/> - </xs:complexType> - </xs:element> - <xs:element name="bundle-names" type="components:multiValuedProperty"/> - <xs:attributeGroup name="attlist.resourceBundle"> - <xs:attribute name="bundle-names"> </xs:attribute> - </xs:attributeGroup> - - <xs:element name="pojo-cache"> - <xs:complexType mixed="true"> - <xs:attributeGroup ref="components:attlist.component"/> - <xs:attributeGroup ref="core:attlist.pojoCache"/> - </xs:complexType> - </xs:element> - <xs:attributeGroup name="attlist.pojoCache"> - <xs:attribute name="cfg-resource-name"/> - </xs:attributeGroup> - -</xs:schema> +<?xml version="1.0" encoding="UTF-8"?> +<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" + targetNamespace="http://jboss.com/products/seam/core" xmlns:core="http://jboss.com/products/seam/core" + xmlns:components="http://jboss.com/products/seam/components" attributeFormDefault="unqualified"> + <xs:import namespace="http://jboss.com/products/seam/components" schemaLocation="components-2.0.xsd"/> + + <xs:element name="init"> + <xs:complexType mixed="true"> + <xs:attributeGroup ref="components:attlist.component"/> + <xs:attributeGroup ref="core:attlist.init"/> + </xs:complexType> + </xs:element> + <xs:attributeGroup name="attlist.init"> + <xs:attribute name="debug"> + <xs:simpleType> + <xs:restriction base="xs:token"> + <xs:enumeration value="true"/> + <xs:enumeration value="false"/> + </xs:restriction> + </xs:simpleType> + </xs:attribute> + <xs:attribute name="jndi-pattern"/> + <xs:attribute name="transaction-management-enabled"> + <xs:simpleType> + <xs:restriction base="xs:token"> + <xs:enumeration value="true"/> + <xs:enumeration value="false"/> + </xs:restriction> + </xs:simpleType> + </xs:attribute> + <xs:attribute name="user-transaction-name"/> + </xs:attributeGroup> + + <xs:element name="manager"> + <xs:complexType mixed="true"> + <xs:attributeGroup ref="components:attlist.component"/> + <xs:attributeGroup ref="core:attlist.manager"/> + </xs:complexType> + </xs:element> + <xs:attributeGroup name="attlist.manager"> + <xs:attribute name="concurrent-request-timeout" type="xs:integer"/> + <xs:attribute name="conversation-timeout" type="xs:integer"/> + <xs:attribute name="conversation-id-parameter"/> + <xs:attribute name="parent-conversation-id-parameter"/> + </xs:attributeGroup> + + <xs:element name="resource-loader"> + <xs:complexType mixed="true"> + <xs:choice minOccurs="0" maxOccurs="unbounded"> + <xs:element ref="core:bundle-names"/> + </xs:choice> + <xs:attributeGroup ref="components:attlist.component"/> + <xs:attributeGroup ref="core:attlist.resourceLoader"/> + </xs:complexType> + </xs:element> + <xs:element name="bundle-names" type="components:multiValuedProperty"/> + <xs:attributeGroup name="attlist.resourceLoader"> + <xs:attribute name="bundle-names"> </xs:attribute> + </xs:attributeGroup> + + <xs:element name="pojo-cache"> + <xs:complexType mixed="true"> + <xs:attributeGroup ref="components:attlist.component"/> + <xs:attributeGroup ref="core:attlist.pojoCache"/> + </xs:complexType> + </xs:element> + <xs:attributeGroup name="attlist.pojoCache"> + <xs:attribute name="cfg-resource-name"/> + </xs:attributeGroup> + +</xs:schema>

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5163 - trunk/seam/docs/reference/en/modules.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-11-30 08:55:10 -0500 (Fri, 30 Nov 2007) New Revision: 5163 Modified: trunk/seam/docs/reference/en/modules/crud_application_walkthrough.xml Log: language correction Modified: trunk/seam/docs/reference/en/modules/crud_application_walkthrough.xml =================================================================== --- trunk/seam/docs/reference/en/modules/crud_application_walkthrough.xml 2007-11-30 13:34:36 UTC (rev 5162) +++ trunk/seam/docs/reference/en/modules/crud_application_walkthrough.xml 2007-11-30 13:55:10 UTC (rev 5163) @@ -32,7 +32,7 @@ <itemizedlist> - <listitem><para>Run project on the Server. </para></listitem> + <listitem><para>Run a project on the Server. </para></listitem> </itemizedlist> <para>On <emphasis><property>Package Explorer View </property></emphasis> right click on the <emphasis><property>crudapp</property></emphasis> project, select @@ -68,7 +68,7 @@ </mediaobject> </figure> - <para>After that you can use CRUD application with <property>employee</property> database.</para> + <para>After that you can use CRUD application with <property>"employee"</property> database.</para> <para>You can use internal JBDS Web Browser or your external Web Browser with the same link (<ulink url="http://localhost:8080/crudapp/home.seam">http://localhost:8080/crudapp/home.seam</ulink>). </para> <para>Click on the <emphasis><property>Employees List</property></emphasis> link and observe that data from <emphasis><property>employee</property></emphasis> database is displayed.</para>

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5162 - trunk/seam/docs/reference/en/images/crud_database_application.

by jbosstools-commits＠lists.jboss.org

Author: dgeraskov Date: 2007-11-30 08:34:36 -0500 (Fri, 30 Nov 2007) New Revision: 5162 Modified: trunk/seam/docs/reference/en/images/crud_database_application/crud_database_application_04.png Log: http://jira.jboss.com/jira/browse/RHDS-312 Modified: trunk/seam/docs/reference/en/images/crud_database_application/crud_database_application_04.png =================================================================== (Binary files differ)

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5161 - trunk/jsf/docs/userguide/en/images/more_editors.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2007-11-30 07:33:18 -0500 (Fri, 30 Nov 2007) New Revision: 5161 Modified: trunk/jsf/docs/userguide/en/images/more_editors/more_editors_32.png Log: http://jira.jboss.com/jira/browse/RHDS-327 - replacing the image Modified: trunk/jsf/docs/userguide/en/images/more_editors/more_editors_32.png =================================================================== (Binary files differ)

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5160 - trunk/jsf/docs/userguide/en/modules.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2007-11-30 04:46:42 -0500 (Fri, 30 Nov 2007) New Revision: 5160 Modified: trunk/jsf/docs/userguide/en/modules/editors.xml Log: http://jira.jboss.com/jira/browse/RHDS-327 - correcting the section 7.3.6. Spring IDE Modified: trunk/jsf/docs/userguide/en/modules/editors.xml =================================================================== --- trunk/jsf/docs/userguide/en/modules/editors.xml 2007-11-30 09:45:53 UTC (rev 5159) +++ trunk/jsf/docs/userguide/en/modules/editors.xml 2007-11-30 09:46:42 UTC (rev 5160) @@ -1,490 +1,639 @@ <?xml version='1.0' encoding='UTF-8'?> - <chapter id="jbds_editors" xreflabel="jbds_editors"> - <?dbhtml filename="jbds_editors.html"?> - <chapterinfo> +<chapter id="jbds_editors" xreflabel="jbds_editors"> + <?dbhtml filename="jbds_editors.html"?> + <chapterinfo> <keywordset> <keyword>JBoss Developer Studio</keyword> <keyword>JBDS</keyword> <keyword>Editor</keyword> - </keywordset> + </keywordset> </chapterinfo> - <title>Editors</title> + <title>Editors</title> -<para>JBDS is supplied with a huge range of various editors for different file types.</para> + <para>JBDS is supplied with a huge range of various editors for different file types.</para> -<section id="editors_features"> - <?dbhtml filename="editors_features.html"?> -<title>Editors Features</title> -<para>JBoss Developer Studio has powerful editor features that help you easily navigate within your application and make use of content and code assist no matter what project file (jsp, xhtml, xml, css, etc.) you are working on.</para> + <section id="editors_features"> + <?dbhtml filename="editors_features.html"?> + <title>Editors Features</title> + <para>JBoss Developer Studio has powerful editor features that help you easily navigate + within your application and make use of content and code assist no matter what project + file (jsp, xhtml, xml, css, etc.) you are working on.</para> -<section id="OpenOnSelection4Hyperlinknavigation"> -<?dbhtml filename="OpenOnSelection(Hyperlinknavigation)"?> -<title>OpenOn</title> + <section id="OpenOnSelection4Hyperlinknavigation"> + <?dbhtml filename="OpenOnSelection(Hyperlinknavigation)"?> + <title>OpenOn</title> -<para><property>OpenOn</property> let's you easily navigate through your project without using the Package Explorer view (project tree). With OpenOn, you can simply click on a reference to another file and that file will be opened.</para> + <para><property>OpenOn</property> let's you easily navigate through your + project without using the Package Explorer view (project tree). With OpenOn, you can + simply click on a reference to another file and that file will be opened.</para> -<para>OpenOn is available for the following files:</para> -<itemizedlist> -<listitem><para>XML files</para></listitem> -<listitem><para>JSP/XHTML Pages</para></listitem> - <listitem><para>Java files</para></listitem> -</itemizedlist> -<section id="XMLFiles232"> -<?dbhtml filename="XMLFiles"?> -<title>XML Files</title> + <para>OpenOn is available for the following files:</para> + <itemizedlist> + <listitem> + <para>XML files</para> + </listitem> + <listitem> + <para>JSP/XHTML Pages</para> + </listitem> + <listitem> + <para>Java files</para> + </listitem> + </itemizedlist> + <section id="XMLFiles232"> + <?dbhtml filename="XMLFiles"?> + <title>XML Files</title> -<para>Press and hold down the Ctrl key. As you move the mouse cursor over different file references in -the file, they display an underline. When you have the mouse cursor over the name of the file you want - to open, click and the file will open in its own editor. In this example the managed bean NameBean will - open.</para> -<figure> -<title>NameBean Managed Bean</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_1.png"/> - </imageobject> -</mediaobject> -</figure> -<para>This is the result of using OpenOn</para> -<figure> -<title>NameBean Java Class</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_2.png"/> - </imageobject> -</mediaobject> -</figure> -<para>You can also try OpenOn with defined attributes.</para> -<figure> -<title>OpenOn With Defined Attributes</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_3.png"/> - </imageobject> -</mediaobject> -</figure> -<para>You can also open any JSP pages.</para> -<figure> -<title>JSP Page OpenOn</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_4.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="JSPPages223"> -<?dbhtml filename="GettingStartedwithRHDS.html"?> -<title>JSP Pages</title> + <para>Press and hold down the Ctrl key. As you move the mouse cursor over different + file references in the file, they display an underline. When you have the mouse + cursor over the name of the file you want to open, click and the file will open + in its own editor. In this example the managed bean NameBean will open.</para> + <figure> + <title>NameBean Managed Bean</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>This is the result of using OpenOn</para> + <figure> + <title>NameBean Java Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>You can also try OpenOn with defined attributes.</para> + <figure> + <title>OpenOn With Defined Attributes</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>You can also open any JSP pages.</para> + <figure> + <title>JSP Page OpenOn</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_4.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="JSPPages223"> + <?dbhtml filename="GettingStartedwithRHDS.html"?> + <title>JSP Pages</title> -<para><property>OpenOn</property> is also very useful in JSP pages. It will allow you to quickly jump to the reference - instead of having to hunt around in the project structure.</para> + <para><property>OpenOn</property> is also very useful in JSP pages. It will allow + you to quickly jump to the reference instead of having to hunt around in the + project structure.</para> -<para>You can easily open the imported property files.</para> -<figure> -<title>OpenOn With Imported Property Files</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_5.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Use OpenOn to open a CSS file used with a JSP page:</para> -<figure> -<title>OpenOn With CSS File</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_6.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Open managed beans:</para> -<figure> -<title>OpenOn With Maneaged Beans</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_7.png"/> - </imageobject> -</mediaobject> -</figure> -<para>For JSP files in a JSF project, you can also easily open the navigation rules by applying <property>OpenOn</property> to the JSF tag for the navigation outcome:</para> -<figure> -<title>OpenOn With JSF Tag</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_8.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> + <para>You can easily open the imported property files.</para> + <figure> + <title>OpenOn With Imported Property Files</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_5.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Use OpenOn to open a CSS file used with a JSP page:</para> + <figure> + <title>OpenOn With CSS File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_6.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Open managed beans:</para> + <figure> + <title>OpenOn With Maneaged Beans</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_7.png"/> + </imageobject> + </mediaobject> + </figure> + <para>For JSP files in a JSF project, you can also easily open the navigation rules + by applying <property>OpenOn</property> to the JSF tag for the navigation + outcome:</para> + <figure> + <title>OpenOn With JSF Tag</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_8.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> -<section id="CodeAssistAndDynamicCodeAssist42BasedOnProjectData"> -<?dbhtml filename="CodeAssistAndDynamicCodeAssist(BasedOnProjectData).html"?> -<title>Code Assist and Dynamic Code Assist (based on project data)</title> -<section id="ContentAssistFeatures321"> -<?dbhtml filename="ContentAssistFeatures"?> -<title>Content Assist Features</title> -<section id="ContentAssist374"> -<?dbhtml filename="ContentAssist.html"?> -<title>Content Assist</title> -<para><property>Content assist</property> is available when working with</para> + <section id="CodeAssistAndDynamicCodeAssist42BasedOnProjectData"> + <?dbhtml filename="CodeAssistAndDynamicCodeAssist(BasedOnProjectData).html"?> + <title>Code Assist and Dynamic Code Assist (based on project data)</title> + <section id="ContentAssistFeatures321"> + <?dbhtml filename="ContentAssistFeatures"?> + <title>Content Assist Features</title> + <section id="ContentAssist374"> + <?dbhtml filename="ContentAssist.html"?> + <title>Content Assist</title> + <para><property>Content assist</property> is available when working with</para> -<itemizedlist> -<listitem><para>Seam project files</para></listitem> -<listitem><para>JSF project files</para></listitem> -<listitem><para>Struts project files</para></listitem> -<listitem><para>JSP files</para></listitem> -</itemizedlist> -</section> -<section id="JSFProjectFiles3087"> -<?dbhtml filename="JSFProjectFiles.html"?> -<title>JSF Project Files</title> + <itemizedlist> + <listitem> + <para>Seam project files</para> + </listitem> + <listitem> + <para>JSF project files</para> + </listitem> + <listitem> + <para>Struts project files</para> + </listitem> + <listitem> + <para>JSP files</para> + </listitem> + </itemizedlist> + </section> + <section id="JSFProjectFiles3087"> + <?dbhtml filename="JSFProjectFiles.html"?> + <title>JSF Project Files</title> - <para>When working with JSF project in JBoss Developer Studio, you can use various <property>Content Assist features</property> while developing:</para> -<itemizedlist> -<listitem><para>Content Assist for XML, JSP and JSF configuration files</para></listitem> -<listitem><para>Content Assist based on project data</para></listitem> -<listitem><para>Content Assist with graphical JSF editor</para></listitem> -</itemizedlist> -<section id="ContentAssistForXMLJSPAndJSFConfigurationFiles865"> -<?dbhtml filename="ContentAssistForXMLJSPAndJSFConfigurationFiles.html"?> -<title>Content Assist for XML, JSP and JSF configuration files</title> + <para>When working with JSF project in JBoss Developer Studio, you can use + various <property>Content Assist features</property> while developing:</para> + <itemizedlist> + <listitem> + <para>Content Assist for XML, JSP and JSF configuration files</para> + </listitem> + <listitem> + <para>Content Assist based on project data</para> + </listitem> + <listitem> + <para>Content Assist with graphical JSF editor</para> + </listitem> + </itemizedlist> + <section id="ContentAssistForXMLJSPAndJSFConfigurationFiles865"> + <?dbhtml filename="ContentAssistForXMLJSPAndJSFConfigurationFiles.html"?> + <title>Content Assist for XML, JSP and JSF configuration files</title> -<para>At any point when working with any XML, JSP and JSF configuration files Content Assist is available to help you. Simply type <emphasis><property>Ctrl-Space</property></emphasis> to see what is available.</para> + <para>At any point when working with any XML, JSP and JSF configuration + files Content Assist is available to help you. Simply type <emphasis> + <property>Ctrl-Space</property> + </emphasis> to see what is available.</para> -<para>Content Assist for JSF configuration file:</para> -<figure> -<title>Content Assist in JSF Configuration File</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_9.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Content Assist for JSF JSP file:</para> -<figure> -<title>Content Assist in JSP File</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_10.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Content Assist for other JSF XML project files (web.xml shown):</para> -<figure> -<title>Content Assist in web.xml File</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_11.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ContentAssistBasedOnProjectData86"> -<?dbhtml filename="ContentAssistBasedOnProjectData.html"?> -<title>Content Assist Based on Project Data</title> + <para>Content Assist for JSF configuration file:</para> + <figure> + <title>Content Assist in JSF Configuration File</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_9.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Content Assist for JSF JSP file:</para> + <figure> + <title>Content Assist in JSP File</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_10.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Content Assist for other JSF XML project files (web.xml shown):</para> + <figure> + <title>Content Assist in web.xml File</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_11.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ContentAssistBasedOnProjectData86"> + <?dbhtml filename="ContentAssistBasedOnProjectData.html"?> + <title>Content Assist Based on Project Data</title> -<para>JBoss Developer Studio takes Content Assist to the next level. Studio will - constantly scan your project and you will be able to insert code into the JSP page from your project that - includes:</para> -<itemizedlist> -<listitem><para>Values from Property files</para></listitem> -<listitem><para><emphasis role="italic"><property>"Managed beans"</property></emphasis> attributes and methods</para></listitem> -<listitem><para>Navigation Rule Outcomes</para></listitem> - <listitem><para>JSF variables (context, request etc...)</para></listitem> -</itemizedlist> -<para>The first screenshot shows how to insert message from a Properties files. You simply put the cursor - inside the <emphasis role="italic"><property>"value"</property></emphasis> attribute and press <emphasis><property>Ctrl-Space</property></emphasis>. JBoss Developer Studio will scan your project and show a list of possible values to insert.</para> -<figure> -<title>Inserting Message</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_12.png"/> - </imageobject> -</mediaobject> -</figure> -<para>In the following screen shot we are inserting a <emphasis role="italic"><property>"Managed bean"</property></emphasis> attribute value. Again, by simply clicking <emphasis><property>Ctrl-Space</property></emphasis>, JBoss Developer Studio will show a list of all possible values that you can insert:</para> + <para>JBoss Developer Studio takes Content Assist to the next level. Studio + will constantly scan your project and you will be able to insert code + into the JSP page from your project that includes:</para> + <itemizedlist> + <listitem> + <para>Values from Property files</para> + </listitem> + <listitem> + <para><emphasis role="italic"> + <property>"Managed beans"</property> + </emphasis> attributes and methods</para> + </listitem> + <listitem> + <para>Navigation Rule Outcomes</para> + </listitem> + <listitem> + <para>JSF variables (context, request etc...)</para> + </listitem> + </itemizedlist> + <para>The first screenshot shows how to insert message from a Properties + files. You simply put the cursor inside the <emphasis role="italic"> + <property>"value"</property> + </emphasis> attribute and press <emphasis> + <property>Ctrl-Space</property> + </emphasis>. JBoss Developer Studio will scan your project and show a + list of possible values to insert.</para> + <figure> + <title>Inserting Message</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_12.png"/> + </imageobject> + </mediaobject> + </figure> + <para>In the following screen shot we are inserting a <emphasis + role="italic"> + <property>"Managed bean"</property> + </emphasis> attribute value. Again, by simply clicking <emphasis> + <property>Ctrl-Space</property> + </emphasis>, JBoss Developer Studio will show a list of all possible + values that you can insert:</para> -<para>Once you select a Managed bean, it will show you a list of all available attributes for the selected Managed bean (userBean).</para> -<figure> -<title>Attributes List</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_13.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Code Assist based on project data will also prompt you for navigation rules that exist in your JSF - configuration file.</para> -<figure> -<title>Code Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_14.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ContentAssistWithinJSFGraphicalEditor44"> -<?dbhtml filename="ContentAssistWithinJSFGraphicalEditor.html"?> -<title>Content Assist within Tree JSF Editor</title> + <para>Once you select a Managed bean, it will show you a list of all + available attributes for the selected Managed bean (userBean).</para> + <figure> + <title>Attributes List</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_13.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Code Assist based on project data will also prompt you for navigation + rules that exist in your JSF configuration file.</para> + <figure> + <title>Code Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_14.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ContentAssistWithinJSFGraphicalEditor44"> + <?dbhtml filename="ContentAssistWithinJSFGraphicalEditor.html"?> + <title>Content Assist within Tree JSF Editor</title> -<para>JBoss Developer Studio also provides Content Assist when working within the Tree JSF -configuration editor. Just click <emphasis><property>Ctrl-Space</property></emphasis>.</para> -<figure> -<title>Content Assist in Tree JSF Configuration Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_15.png"/> - </imageobject> -</mediaobject> -</figure> -<para>If a field contains right class name and you click a link near the field you will come to the file with this class otherwise a new Java Class dialog will be shown:</para> -<figure> -<title>New Java Class</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_16.png"/> - </imageobject> -</mediaobject> -</figure> -<para>If you entered an incorrect name in the field error markers will be shown for field labels and tree items:</para> -<figure> -<title>Error Markers</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_17.png"/> - </imageobject> -</mediaobject> -</figure> -<itemizedlist> -<listitem><para>To add a new property to a managed bean expand <emphasis><property>Managed Beans</property></emphasis> and select <emphasis role="bold"><property><name_of_bean></property></emphasis></para></listitem> -<listitem><para>Click <emphasis><property>Add</property></emphasis> button in the Properties panel</para></listitem> -<listitem><para>In the dialog Add Property define a new property. From here also you can generate setters and getters methods:</para></listitem> -</itemizedlist> -<figure> -<title>Create New Property</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_18.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Here you can also add an additional navigation rule to the faces-config.xml file.</para> -<itemizedlist> -<listitem><para>Select <emphasis><property>Navigation Rules</property></emphasis></para></listitem> -<listitem><para>Click <emphasis><property>Add</property></emphasis> button</para></listitem> -<listitem><para>In the dialog <emphasis><property>Add Rule</property></emphasis> define a view and give a name to the rule. Click Finish:</para></listitem> -</itemizedlist> -<figure> -<title>Add New Navigation Rule</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_19.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> + <para>JBoss Developer Studio also provides Content Assist when working + within the Tree JSF configuration editor. Just click <emphasis> + <property>Ctrl-Space</property> + </emphasis>.</para> + <figure> + <title>Content Assist in Tree JSF Configuration Editor</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_15.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If a field contains right class name and you click a link near the + field you will come to the file with this class otherwise a new Java + Class dialog will be shown:</para> + <figure> + <title>New Java Class</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_16.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If you entered an incorrect name in the field error markers will be + shown for field labels and tree items:</para> + <figure> + <title>Error Markers</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_17.png"/> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>To add a new property to a managed bean expand <emphasis> + <property>Managed Beans</property> + </emphasis> and select <emphasis role="bold"> + <property><name_of_bean></property> + </emphasis></para> + </listitem> + <listitem> + <para>Click <emphasis> + <property>Add</property> + </emphasis> button in the Properties panel</para> + </listitem> + <listitem> + <para>In the dialog Add Property define a new property. From here + also you can generate setters and getters methods:</para> + </listitem> + </itemizedlist> + <figure> + <title>Create New Property</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_18.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Here you can also add an additional navigation rule to the + faces-config.xml file.</para> + <itemizedlist> + <listitem> + <para>Select <emphasis> + <property>Navigation Rules</property> + </emphasis></para> + </listitem> + <listitem> + <para>Click <emphasis> + <property>Add</property> + </emphasis> button</para> + </listitem> + <listitem> + <para>In the dialog <emphasis> + <property>Add Rule</property> + </emphasis> define a view and give a name to the rule. Click + Finish:</para> + </listitem> + </itemizedlist> + <figure> + <title>Add New Navigation Rule</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_19.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> -<section id="StrutsProjectFile46s3"> -<?dbhtml filename="StrutsProjectFiles.html"?> -<title>Struts Project Files</title> -<section id="ContentAssistForStrutsConfigurationFile75"> -<?dbhtml filename="ContentAssistForStrutsConfigurationFile.html"?> -<title>Content Assist for Struts Configuration File</title> -<figure> -<title>Struts Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_20.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ContentAssistForStrutsJSPFile07"> -<?dbhtml filename="ContentAssistForStrutsJSPFile.html"?> -<title>Content Assist for Struts JSP File</title> -<figure> -<title>Struts JSP Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_21.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> -<section id="JSPPages434"> -<?dbhtml filename="JSPPages.html"?> -<title>JSP Pages</title> -<section id="ContentAssistForJSFTags96"> -<?dbhtml filename="ContentAssistForJSFTags.html"?> -<title>Content Assist for JSF Tags</title> -<para>JBDS provides full code completion for JSF tags:</para> + <section id="StrutsProjectFile46s3"> + <?dbhtml filename="StrutsProjectFiles.html"?> + <title>Struts Project Files</title> + <section id="ContentAssistForStrutsConfigurationFile75"> + <?dbhtml filename="ContentAssistForStrutsConfigurationFile.html"?> + <title>Content Assist for Struts Configuration File</title> + <figure> + <title>Struts Content Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_20.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ContentAssistForStrutsJSPFile07"> + <?dbhtml filename="ContentAssistForStrutsJSPFile.html"?> + <title>Content Assist for Struts JSP File</title> + <figure> + <title>Struts JSP Content Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_21.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section id="JSPPages434"> + <?dbhtml filename="JSPPages.html"?> + <title>JSP Pages</title> + <section id="ContentAssistForJSFTags96"> + <?dbhtml filename="ContentAssistForJSFTags.html"?> + <title>Content Assist for JSF Tags</title> + <para>JBDS provides full code completion for JSF tags:</para> -<figure> -<title>JSF Tags Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_22.png"/> - </imageobject> -</mediaobject> -</figure> -<para>When the tag is selected the required attributes, if there any, are already inserted and the cursor is located to the first attribute. As this point you can ask for attribute proposals.</para> -<figure> -<title>Attributes Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_23.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>JSF Tags Content Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_22.png"/> + </imageobject> + </mediaobject> + </figure> + <para>When the tag is selected the required attributes, if there any, are + already inserted and the cursor is located to the first attribute. As + this point you can ask for attribute proposals.</para> + <figure> + <title>Attributes Content Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_23.png"/> + </imageobject> + </mediaobject> + </figure> -</section> -<section id="ContentAssistForJSTLTags6332"> -<?dbhtml filename="ContentAssistForJSTLTags.html"?> -<title>Content Assist for JSTL Tags</title> -<figure> -<title>JSTL Tags Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_24.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ContentAssistForHTMLTags7454"> -<?dbhtml filename="ContentAssistForHTMLTags.html"?> -<title>Content Assist for HTML Tags</title> -<para>Content assist for HTML tags has the same mechanism as for JSF tags:</para> -<figure> -<title>HTML Tags Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_25.png"/> - </imageobject> -</mediaobject> -</figure> -<para>You can use as well attributes proposals for HTML tags:</para> -<figure> -<title>HTML Tags Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_26.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ContentAssistForJavaScriptTags67433"> -<?dbhtml filename="ContentAssistForJavaScriptTags.html"?> -<title>Content Assist for JavaScript Tags</title> -<figure> -<title>JavaScript Tags Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_27.png"/> - </imageobject> -</mediaobject> -</figure> -</section> + </section> + <section id="ContentAssistForJSTLTags6332"> + <?dbhtml filename="ContentAssistForJSTLTags.html"?> + <title>Content Assist for JSTL Tags</title> + <figure> + <title>JSTL Tags Content Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_24.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ContentAssistForHTMLTags7454"> + <?dbhtml filename="ContentAssistForHTMLTags.html"?> + <title>Content Assist for HTML Tags</title> + <para>Content assist for HTML tags has the same mechanism as for JSF tags:</para> + <figure> + <title>HTML Tags Content Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_25.png"/> + </imageobject> + </mediaobject> + </figure> + <para>You can use as well attributes proposals for HTML tags:</para> + <figure> + <title>HTML Tags Content Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_26.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ContentAssistForJavaScriptTags67433"> + <?dbhtml filename="ContentAssistForJavaScriptTags.html"?> + <title>Content Assist for JavaScript Tags</title> + <figure> + <title>JavaScript Tags Content Assist</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_27.png"/> + </imageobject> + </mediaobject> + </figure> + </section> -<section id="ContentAssistWithinConfigurationEditor743"> -<?dbhtml filename="ContentAssistWithinConfigurationEditor.html"?> -<title>Content Assist within JSF Configuration Editor</title> -<figure> -<title>Content Assist in JSF Configuration Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_28.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> -<section id="ContentAssistForRF"> -<?dbhtml filename="ContentAssistForRF.html"?> -<title>Content Assist for Rich Faces components</title> -<para>JBDS indeed provides code completion for Rich Faces framework components. All you have to do is to install Rich Faces libraries into your project. See <ulink url="http://labs.jboss.com/file-access/default/members/jbossrichfaces/freezone...">here</ulink> how to install.</para> -<figure> -<title>Content Assist for Rich Faces Components</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_29.png"/> - </imageobject> -</mediaobject> -</figure> -<itemizedlist> - <listitem><para>To insert a Rich Faces component on a page expand <emphasis><property>JBoss Rich Faces</property></emphasis> group on the palette</para></listitem> - <listitem><para>Click on some component</para></listitem> - <listitem><para>Put the needed attributes in the <emphasis><property>Insert Tag</property></emphasis> dialog and click <emphasis><property>Finish</property></emphasis> button - <figure> -<title>Insert Tag</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_30.png"/> - </imageobject> -</mediaobject> -</figure> - </para></listitem> - </itemizedlist> - <para>The Rich Faces tag will be inserted on your page displayed in source and visual modes: </para> - <figure> -<title>Rich Faces Component</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_31.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> + <section id="ContentAssistWithinConfigurationEditor743"> + <?dbhtml filename="ContentAssistWithinConfigurationEditor.html"?> + <title>Content Assist within JSF Configuration Editor</title> + <figure> + <title>Content Assist in JSF Configuration Editor</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_28.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section id="ContentAssistForRF"> + <?dbhtml filename="ContentAssistForRF.html"?> + <title>Content Assist for Rich Faces components</title> + <para>JBDS indeed provides code completion for Rich Faces framework components. + All you have to do is to install Rich Faces libraries into your project. See + <ulink + url="http://labs.jboss.com/file-access/default/members/jbossrichfaces/freezone..." + >here</ulink> how to install.</para> + <figure> + <title>Content Assist for Rich Faces Components</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_29.png" + /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>To insert a Rich Faces component on a page expand <emphasis> + <property>JBoss Rich Faces</property> + </emphasis> group on the palette</para> + </listitem> + <listitem> + <para>Click on some component</para> + </listitem> + <listitem> + <para>Put the needed attributes in the <emphasis> + <property>Insert Tag</property> + </emphasis> dialog and click <emphasis> + <property>Finish</property> + </emphasis> button <figure> + <title>Insert Tag</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/editors_features/editors_features_30.png" + /> + </imageobject> + </mediaobject> + </figure> + </para> + </listitem> + </itemizedlist> + <para>The Rich Faces tag will be inserted on your page displayed in source and + visual modes: </para> + <figure> + <title>Rich Faces Component</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_31.png" + /> + </imageobject> + </mediaobject> + </figure> + </section> + </section> -<section id="AddingDynamicCodeAssistToCustomComponents8745"> -<?dbhtml filename="AddingDynamicCodeAssistToCustomComponentsThatWereAddedToJBossToolsPalette.html"?> -<title>Adding dynamic code assist to custom components that were added to JBoss Tools Palette</title> -<para>Here is what you need to do to add project based code assist to a custom component added in -JBoss Developer Studio:</para> -<orderedlist> - <listitem><para>Create a new xml file in <emphasis><property><JBDS_home>studio/eclipse/plugins/org.jboss.tools.common.kb_***/schemas/tld/</property></emphasis>. For example call it JeniaFaces.xml. The file should be written according to <emphasis><property><JBDS_home>/studio/eclipse/plugins/org.jboss.tools.common.kb/kb.jar/org/jboss/tools/common/kb/kb-schema_1.0.dtd</property></emphasis></para></listitem> -</orderedlist> - <para>Here is how you set what is available for code assist:</para> -<itemizedlist> -<listitem><para>Adds code assist for JSF pre-defined objects, such as value=<emphasis role="italic"><property>"#{param}"</property></emphasis>:</para></listitem> -</itemizedlist> -<programlisting role="XML"><![CDATA[<AttributeType ...> + <section id="AddingDynamicCodeAssistToCustomComponents8745"> + <?dbhtml filename="AddingDynamicCodeAssistToCustomComponentsThatWereAddedToJBossToolsPalette.html"?> + <title>Adding dynamic code assist to custom components that were added to JBoss + Tools Palette</title> + <para>Here is what you need to do to add project based code assist to a custom + component added in JBoss Developer Studio:</para> + <orderedlist> + <listitem> + <para>Create a new xml file in <emphasis> + <property><JBDS_home>studio/eclipse/plugins/org.jboss.tools.common.kb_***/schemas/tld/</property> + </emphasis>. For example call it JeniaFaces.xml. The file should be + written according to <emphasis> + <property><JBDS_home>/studio/eclipse/plugins/org.jboss.tools.common.kb/kb.jar/org/jboss/tools/common/kb/kb-schema_1.0.dtd</property> + </emphasis></para> + </listitem> + </orderedlist> + <para>Here is how you set what is available for code assist:</para> + <itemizedlist> + <listitem> + <para>Adds code assist for JSF pre-defined objects, such as value=<emphasis + role="italic"> + <property>"#{param}"</property> + </emphasis>:</para> + </listitem> + </itemizedlist> + <programlisting role="XML"><![CDATA[<AttributeType ...> <proposal type="jsfVariables"/> </AttributeType> ]]></programlisting> - <itemizedlist> -<listitem><para>Adds bundle resource (property file) <property>code assist</property>:</para></listitem> - </itemizedlist> -<programlisting role="XML"><![CDATA[<AttributeType ...> + <itemizedlist> + <listitem> + <para>Adds bundle resource (property file) <property>code + assist</property>:</para> + </listitem> + </itemizedlist> + <programlisting role="XML"><![CDATA[<AttributeType ...> <proposal type="bundleProperty"/> </AttributeType> ]]></programlisting> - <itemizedlist> -<listitem><para>Adds managed bean property <property>code assist</property>:</para></listitem> - </itemizedlist> -<programlisting role="XML"><![CDATA[<AttributeType ...> + <itemizedlist> + <listitem> + <para>Adds managed bean property <property>code assist</property>:</para> + </listitem> + </itemizedlist> + <programlisting role="XML"><![CDATA[<AttributeType ...> <proposal type="beanProperty"/> </AttributeType> ]]></programlisting> - <itemizedlist> -<listitem><para>Adds managed bean property but with a specified type:</para></listitem> - </itemizedlist> -<programlisting role="XML"><![CDATA[<AttributeType ...> + <itemizedlist> + <listitem> + <para>Adds managed bean property but with a specified type:</para> + </listitem> + </itemizedlist> + <programlisting role="XML"><![CDATA[<AttributeType ...> <proposal type="beanProperty"> <param name="type" value="java.lang.Boolean"/> </proposal> </AttributeType> ]]></programlisting> - <itemizedlist> -<listitem><para>Adds managed bean method with a signature:</para></listitem> - </itemizedlist> -<programlisting role="XML"><![CDATA[<AttributeType ...> + <itemizedlist> + <listitem> + <para>Adds managed bean method with a signature:</para> + </listitem> + </itemizedlist> + <programlisting role="XML"><![CDATA[<AttributeType ...> <proposal type="beanMethodBySignature"> <param name="paramType" value="javax.faces.context.FacesContext"/> <param name="paramType" value="javax.faces.component.UIComponent"/> @@ -493,323 +642,374 @@ </proposal> </AttributeType> ]]></programlisting> - <orderedlist continuation="continues"> - <listitem><para>Add information on your xml file in <emphasis><property><JBDS_home>/studio/eclipse/plugins/org.jboss.common.kb_***/plugin.xml</property></emphasis></para></listitem> - </orderedlist> - <programlisting role="XML"><![CDATA[ + <orderedlist continuation="continues"> + <listitem> + <para>Add information on your xml file in <emphasis> + <property><JBDS_home>/studio/eclipse/plugins/org.jboss.common.kb_***/plugin.xml</property> + </emphasis></para> + </listitem> + </orderedlist> + <programlisting role="XML"><![CDATA[ <tld jsf="true" name="Jenia Faces" schema-location="schemas/tld/myJSF.xml" uri="http://www.jenia.org/jsf/dataTools"/>]]> </programlisting> -<orderedlist continuation="continues"> -<listitem><para>Restart Eclipse. You should now have code assist for the component.</para></listitem> - </orderedlist> -</section> -</section> -<section id="FullControlOverSourceFiles-SynchronizedSourcAndVisualEditing74"> -<?dbhtml filename="FullControlOverSourceFiles-SynchronizedSourcAndVisualEditing.html"?> -<title>Full Control over Source Files - Synchronized Source and Visual Editing</title> + <orderedlist continuation="continues"> + <listitem> + <para>Restart Eclipse. You should now have code assist for the + component.</para> + </listitem> + </orderedlist> + </section> + </section> + <section id="FullControlOverSourceFiles-SynchronizedSourcAndVisualEditing74"> + <?dbhtml filename="FullControlOverSourceFiles-SynchronizedSourcAndVisualEditing.html"?> + <title>Full Control over Source Files - Synchronized Source and Visual Editing</title> -<para>JBoss Developer Studio offers the flexibility to edit any files in either source or extra visual - modes at the same time.</para> + <para>JBoss Developer Studio offers the flexibility to edit any files in either source + or extra visual modes at the same time.</para> -<para>The project is yours and so is the source. JBoss Developer Studio provides you many different - graphical editors to speed your application development. At the same time, you always have full control - over all project source files. Any changes you make in the source view, will immediately appear in - the graphical view.</para> + <para>The project is yours and so is the source. JBoss Developer Studio provides you + many different graphical editors to speed your application development. At the same + time, you always have full control over all project source files. Any changes you + make in the source view, will immediately appear in the graphical view.</para> -<para>The JSF configuration file editor has three views: Diagram, Tree and Source. All views are -synchronized, you can edit the file in any view.</para> -<figure> -<title>Diagram View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_32.png"/> - </imageobject> -</mediaobject> -</figure> -<figure> -<title>Tree View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_33.png"/> - </imageobject> -</mediaobject> -</figure> + <para>The JSF configuration file editor has three views: Diagram, Tree and Source. All + views are synchronized, you can edit the file in any view.</para> + <figure> + <title>Diagram View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_32.png"/> + </imageobject> + </mediaobject> + </figure> + <figure> + <title>Tree View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_33.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> -<title>Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_34.png"/> - </imageobject> -</mediaobject> -</figure> -<para>The same applies to all other JBoss Developer Studio editors.</para> + <figure> + <title>Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_34.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The same applies to all other JBoss Developer Studio editors.</para> -<para>Web XML editor is shown. Web XML editor has a graphical view (Tree) and source (Source).</para> + <para>Web XML editor is shown. Web XML editor has a graphical view (Tree) and source + (Source).</para> -<figure> -<title>Tree View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_35.png"/> - </imageobject> -</mediaobject> -</figure> -<figure> -<title>Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_36.png"/> - </imageobject> -</mediaobject> -</figure> -<para>JBoss Developer Studio TLD file editor shown in Tree view. At any point you can edit the source by going - switching to Source view.</para> -<figure> -<title>Tree Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_37.png"/> - </imageobject> -</mediaobject> -</figure> -<figure> -<title>Source Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_38.png"/> - </imageobject> -</mediaobject> -</figure> -<para>The Struts configuration file editor has three views: Diagram, Tree and Source. All views are synchronized, - you can edit the file in any view.</para> -<figure> -<title>Struts Diagram View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_39.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Source view. Any changes here will immediately appear in all other views.</para> -<figure> -<title>Struts Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/editors_features/editors_features_40.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> + <figure> + <title>Tree View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_35.png"/> + </imageobject> + </mediaobject> + </figure> + <figure> + <title>Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_36.png"/> + </imageobject> + </mediaobject> + </figure> + <para>JBoss Developer Studio TLD file editor shown in Tree view. At any point you can + edit the source by going switching to Source view.</para> + <figure> + <title>Tree Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_37.png"/> + </imageobject> + </mediaobject> + </figure> + <figure> + <title>Source Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_38.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The Struts configuration file editor has three views: Diagram, Tree and Source. + All views are synchronized, you can edit the file in any view.</para> + <figure> + <title>Struts Diagram View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_39.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Source view. Any changes here will immediately appear in all other views.</para> + <figure> + <title>Struts Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_40.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> -<section id="visual_page"> -<?dbhtml filename="visual_page.html"?> -<title>Visual Page Editor</title> -<para>JBoss Developer Studio comes with a powerful and customizable <property>Visual Page Editor</property> (VPE). You can use the Visual Page Editor to develop an application using any technology: JSF, Struts, JSP, HTML and others.</para> + <section id="visual_page"> + <?dbhtml filename="visual_page.html"?> + <title>Visual Page Editor</title> + <para>JBoss Developer Studio comes with a powerful and customizable <property>Visual Page + Editor</property> (VPE). You can use the Visual Page Editor to develop an + application using any technology: JSF, Struts, JSP, HTML and others.</para> -<section id="visual_tabs"> -<?dbhtml filename="visual_tabs.html"?> + <section id="visual_tabs"> + <?dbhtml filename="visual_tabs.html"?> -<para>Current VPE version has four tabs: Visual/Source, Visual, Source and Preview.</para> -<para>Split screen design with instant synchronization between source and visual views:</para> -<figure> -<title>Visual/Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_1.png" /> - </imageobject> -</mediaobject> -</figure> + <para>Current VPE version has four tabs: Visual/Source, Visual, Source and Preview.</para> + <para>Split screen design with instant synchronization between source and visual views:</para> + <figure> + <title>Visual/Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_1.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can also switch to pure Visual design:</para> -<figure> -<title>Visual View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_2.png" /> - </imageobject> -</mediaobject> -</figure> + <para>You can also switch to pure Visual design:</para> + <figure> + <title>Visual View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_2.png"/> + </imageobject> + </mediaobject> + </figure> -<para>Or work just in Source view. Note that selection bar is now available not only in Visual mode but also in Source one:</para> -<figure> -<title>Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_3.png" /> - </imageobject> -</mediaobject> -</figure> -<para>No matter what view you select, you get full integration with Properties and Outline views:</para> -<figure> -<title>Properties And Outline Views</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_4.png" /> - </imageobject> -</mediaobject> -</figure> -<para>Preview mode is read-only, it only shows how the page will look like in a browser.</para> -<figure> -<title>Preview Mode</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_5.png" /> - </imageobject> -</mediaobject> -</figure> -<para>Use the graphical toolbar to add inline styling to any tag.</para> -<figure> -<title>Graphical Toolbar</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_6.png" /> - </imageobject> -</mediaobject> -</figure> -<para>With just a click or drag-and-drop insert any tags from the palette on to the page you are editing.</para> -<figure> -<title>Inserting Tags From Palette</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_7.png" /> - </imageobject> -</mediaobject> -</figure> + <para>Or work just in Source view. Note that selection bar is now available not only in + Visual mode but also in Source one:</para> + <figure> + <title>Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>No matter what view you select, you get full integration with Properties and + Outline views:</para> + <figure> + <title>Properties And Outline Views</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_4.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Preview mode is read-only, it only shows how the page will look like in a browser.</para> + <figure> + <title>Preview Mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_5.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Use the graphical toolbar to add inline styling to any tag.</para> + <figure> + <title>Graphical Toolbar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_6.png"/> + </imageobject> + </mediaobject> + </figure> + <para>With just a click or drag-and-drop insert any tags from the palette on to the page + you are editing.</para> + <figure> + <title>Inserting Tags From Palette</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_7.png"/> + </imageobject> + </mediaobject> + </figure> -<section id="AdvancedSettings954"> -<?dbhtml filename="AdvancedSettings.html"?> -<title>Advanced Settings</title> - - <para>There are three buttons on the <property>Visual Page Editor</property> left side:</para> - - <figure> - <title>Visual Page Editor Buttons</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_8.png" /> - </imageobject> - </mediaobject> - </figure> - - <itemizedlist> - <listitem><para>Preferences</para></listitem> - </itemizedlist> - <para>Provides quick access to Visual Page Editor preferences.</para> - <figure> - <title>Visual Page Editor Preferences Window</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_9.png" /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem><para>Refresh</para></listitem> - </itemizedlist> - <para>Refresh displaying information with this button.</para> - - <itemizedlist> - <listitem><para>Page Design Options</para></listitem> - </itemizedlist> -<para>This button leads to page design options.</para> - <figure> - <title>Page Design Options</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_10.png" /> - </imageobject> - </mediaobject> - </figure> -<para>This dialog let's you set resources which are usually only resolved in runtime. To set a stylesheet, - click <emphasis><property>Add</property></emphasis> (for CSS File Path section) and add your stylesheet. It works when CSS is defined on your page in the following way:</para> + <section id="AdvancedSettings954"> + <?dbhtml filename="AdvancedSettings.html"?> + <title>Advanced Settings</title> -<para>Code:</para> - <programlisting role="XML"><![CDATA[<link rel="stylesheet" type="text/css" href="#{facesContext.externalContext.requestContextPath}/style.css"/> + <para>There are three buttons on the <property>Visual Page Editor</property> left + side:</para> + + <figure> + <title>Visual Page Editor Buttons</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_8.png"/> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para>Preferences</para> + </listitem> + </itemizedlist> + <para>Provides quick access to Visual Page Editor preferences.</para> + <figure> + <title>Visual Page Editor Preferences Window</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_9.png"/> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>Refresh</para> + </listitem> + </itemizedlist> + <para>Refresh displaying information with this button.</para> + + <itemizedlist> + <listitem> + <para>Page Design Options</para> + </listitem> + </itemizedlist> + <para>This button leads to page design options.</para> + <figure> + <title>Page Design Options</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_10.png"/> + </imageobject> + </mediaobject> + </figure> + <para>This dialog let's you set resources which are usually only resolved + in runtime. To set a stylesheet, click <emphasis> + <property>Add</property> + </emphasis> (for CSS File Path section) and add your stylesheet. It works when + CSS is defined on your page in the following way:</para> + + <para>Code:</para> + <programlisting role="XML"><![CDATA[<link rel="stylesheet" type="text/css" href="#{facesContext.externalContext.requestContextPath}/style.css"/> ]]></programlisting> -<para>This will work fine in runtime, but the Visual Page Editor doesn't know what requestContextPath in design time is.</para> + <para>This will work fine in runtime, but the Visual Page Editor doesn't + know what requestContextPath in design time is.</para> -<para>The next section (URI), let's you add URI taglibs if you are using includes so that the editor knows - where to find the tag libraries.</para> + <para>The next section (URI), let's you add URI taglibs if you are using + includes so that the editor knows where to find the tag libraries.</para> -<para>The first two sections let you define actual runtime folders. Here is an example.</para> + <para>The first two sections let you define actual runtime folders. Here is an + example.</para> -<para>Let's say you have the following project structure:</para> + <para>Let's say you have the following project structure:</para> -<programlisting role="XML"><![CDATA[WebContent/ + <programlisting role="XML"><![CDATA[WebContent/ pages/ img/ a.gif header.jsp main.jsp ]]></programlisting> -<para>header.jsp content:</para> -<programlisting role="XML"><![CDATA[My Header + <para>header.jsp content:</para> + <programlisting role="XML"><![CDATA[My Header <img src="img/a.gif"/> ]]></programlisting> -<para>main.jsp:</para> -<programlisting role="XML"><![CDATA[<jsp:include page="pages/header.jsp" /> + <para>main.jsp:</para> + <programlisting role="XML"><![CDATA[<jsp:include page="pages/header.jsp" /> ]]></programlisting> -<para> - When you open <emphasis><property>main.jsp</property></emphasis> in Visual Page Editor, it will not be able to resolve the image from the header, - however, it will work fine in runtime. To fix this in design time, click the <emphasis><property>Page Design Options</property></emphasis> button and - set <emphasis><property>Actual Run-Time Relative</property></emphasis> Folder to <emphasis><property><project>WebContent > pages</property></emphasis> and you will see the image appear.</para> -<para></para> - <itemizedlist> - <listitem><para>Hide Selection bar</para></listitem> - </itemizedlist> -<para> By clicking on the component in Visual view or selecting a code snippet in Source mode you can see the tags tree. If you want to hide the selection bar, use the "Hide Selection Bar" button on the lower right side.</para> - - <figure> - <title>Selection Bar</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_11.png"/> - </imageobject> - </mediaobject> - </figure> - </section> -</section> + <para> When you open <emphasis> + <property>main.jsp</property> + </emphasis> in Visual Page Editor, it will not be able to resolve the image from + the header, however, it will work fine in runtime. To fix this in design time, + click the <emphasis> + <property>Page Design Options</property> + </emphasis> button and set <emphasis> + <property>Actual Run-Time Relative</property> + </emphasis> Folder to <emphasis> + <property><project>WebContent > pages</property> + </emphasis> and you will see the image appear.</para> + <para/> + <itemizedlist> + <listitem> + <para>Hide Selection bar</para> + </listitem> + </itemizedlist> + <para> By clicking on the component in Visual view or selecting a code snippet in + Source mode you can see the tags tree. If you want to hide the selection bar, + use the "Hide Selection Bar" button on the lower right side.</para> -<section id="SetupnotesforLinu895x"> -<?dbhtml filename="SetupNotesforLinux.html"?> -<title>Setup notes for Linux</title> -<section id="HowToStartTheVisualPageEditorUnderLinux85"> -<?dbhtml filename="HowToStartTheVisualPageEditorUnderLinux.html"?> -<title>How to Start the Visual Page Editor under Linux</title> + <figure> + <title>Selection Bar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_11.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> -<para>Linux users may need to do the following to get the Visual Editor to work correctly on their machines.</para> + <section id="SetupnotesforLinu895x"> + <?dbhtml filename="SetupNotesforLinux.html"?> + <title>Setup notes for Linux</title> + <section id="HowToStartTheVisualPageEditorUnderLinux85"> + <?dbhtml filename="HowToStartTheVisualPageEditorUnderLinux.html"?> + <title>How to Start the Visual Page Editor under Linux</title> -<para> The Visual Page Editor requires the library libstdc++.so.5. This library is contained in the compat-libstdc++-33.i386 package.</para> + <para>Linux users may need to do the following to get the Visual Editor to work + correctly on their machines.</para> -<itemizedlist> -<listitem><para>To install this package on Fedora Core or Red Hat Enterprise Linux run the following command:</para> <programlisting role="JAVA"><![CDATA[yum install compat-libstdc++-33.i386 -]]></programlisting></listitem> + <para> The Visual Page Editor requires the library libstdc++.so.5. This library is + contained in the compat-libstdc++-33.i386 package.</para> + <itemizedlist> + <listitem> + <para>To install this package on Fedora Core or Red Hat Enterprise Linux run + the following command:</para> + <programlisting role="JAVA"><![CDATA[yum install compat-libstdc++-33.i386 +]]></programlisting> + </listitem> -<listitem><para>On any other rpm based distributions download libstdc++.so.5 and run the following command:</para><programlisting role="JAVA"><![CDATA[rpm -Uvh compat-libstdc++-33.i386 -]]></programlisting></listitem> + <listitem> + <para>On any other rpm based distributions download libstdc++.so.5 and run + the following command:</para> + <programlisting role="JAVA"><![CDATA[rpm -Uvh compat-libstdc++-33.i386 +]]></programlisting> + </listitem> -<listitem><para>On Debian based distributives run the following command: -</para><programlisting role="JAVA"><![CDATA[apt-get install compat-libstdc++-33.i386 -]]></programlisting></listitem> -</itemizedlist> + <listitem> + <para>On Debian based distributives run the following command: </para> + <programlisting role="JAVA"><![CDATA[apt-get install compat-libstdc++-33.i386 +]]></programlisting> + </listitem> -<para> In case you have the library installed and you still have issue with starting the visual page editor then close all browser views/editors and leave one visual page editor open and restart eclipse. This should force a load of the right XULRunner viewer.</para> + </itemizedlist> + <para> In case you have the library installed and you still have issue with starting + the visual page editor then close all browser views/editors and leave one visual + page editor open and restart eclipse. This should force a load of the right + XULRunner viewer.</para> -</section> -  -</section> + </section> -<section id="JSPsyntaxvalidation84"> -<?dbhtml filename="JSPsyntaxValidation.html"?> -<title>JSP syntax validation</title> -<para>When working in JBoss Tools JSP editor you are constantly provided with feedback and -contextual error checking as you type.</para> -</section> + <section id="JSPsyntaxvalidation84"> + <?dbhtml filename="JSPsyntaxValidation.html"?> + <title>JSP syntax validation</title> + <para>When working in JBoss Tools JSP editor you are constantly provided with feedback + and contextual error checking as you type.</para> + </section> -  -<section id="PageEditorWithPreview53"> -<?dbhtml filename="PageEditorWithPreview.html"?> -<title>JSP Page Preview</title> + <section id="PageEditorWithPreview53"> + <?dbhtml filename="PageEditorWithPreview.html"?> + <title>JSP Page Preview</title> -<para>JBoss Developer Studio comes with JSP design-time preview features. When designing JSP pages you - can easily preview how they will look during runtime. You can even attach your stylesheet to the preview.</para> + <para>JBoss Developer Studio comes with JSP design-time preview features. When designing + JSP pages you can easily preview how they will look during runtime. You can even + attach your stylesheet to the preview.</para> -<para>JSP preview is available for:</para> + <para>JSP preview is available for:</para> -<itemizedlist> -<listitem><para>Struts Pages</para></listitem> -<listitem><para>JSF Pages</para></listitem> -</itemizedlist> + <itemizedlist> + <listitem> + <para>Struts Pages</para> + </listitem> + <listitem> + <para>JSF Pages</para> + </listitem> + </itemizedlist> -<para>The preview features are available with <link linkend="VisualPageEditor">Visual Page Editor</link>.</para> -</section> -</section> + <para>The preview features are available with <link linkend="VisualPageEditor">Visual + Page Editor</link>.</para> + </section> + </section> -<section id="more_editors"> - <?dbhtml filename="more_editors.html"?> -<title>More Editors</title> -<para>Besides Visual Page Editor JBDS provides editors for editing project files of any types: properties, TLD, web.xml, tiles, and so on.</para> -<section id="GraphicalPropertiesEditor"> -<?dbhtml filename="GraphicalPropertiesEditor.html"?> -<title>Graphical Properties Editor</title> + <section id="more_editors"> + <?dbhtml filename="more_editors.html"?> + <title>More Editors</title> + <para>Besides Visual Page Editor JBDS provides editors for editing project files of any + types: properties, TLD, web.xml, tiles, and so on.</para> + <section id="GraphicalPropertiesEditor"> + <?dbhtml filename="GraphicalPropertiesEditor.html"?> + <title>Graphical Properties Editor</title> - <para><property>The Properties editor</property> allows you to work in two different modes and also supports unicode characters.</para> + <para><property>The Properties editor</property> allows you to work in two different + modes and also supports unicode characters.</para> - <para>To create a new properties file, in the Package Explorer view, select<emphasis><property> New > Properties File</property></emphasis> from the right-click context menu on the folder where you want to create the file.</para> -<figure> -<title>Selecting Properties File</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_1.png"/> - </imageobject> -</mediaobject> -</figure> + <para>To create a new properties file, in the Package Explorer view, select<emphasis> + <property> New > Properties File</property> + </emphasis> from the right-click context menu on the folder where you want to create + the file.</para> + <figure> + <title>Selecting Properties File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_1.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can edit the file using a table-oriented "Properties" viewer:</para> + <para>You can edit the file using a table-oriented "Properties" + viewer:</para> -<figure> -<title>"Properties" Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_2.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>"Properties" Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_2.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can also use a Source viewer for editing the file:</para> -<figure> -<title>Source Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_3.png"/> - </imageobject> -</mediaobject> -</figure> -</section> + <para>You can also use a Source viewer for editing the file:</para> + <figure> + <title>Source Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_3.png"/> + </imageobject> + </mediaobject> + </figure> + </section> -<section id="GraphicalTLDEditor"> -<?dbhtml filename="GraphicalTLDEditor.html"?> -<title>Graphical TLD Editor</title> + <section id="GraphicalTLDEditor"> + <?dbhtml filename="GraphicalTLDEditor.html"?> + <title>Graphical TLD Editor</title> - <para><property>The TLD editor</property> comes with same features you will find in all other JBoss Developer Studio editors:</para> + <para><property>The TLD editor</property> comes with same features you will find in all + other JBoss Developer Studio editors:</para> -<itemizedlist> -<listitem><para>Graphical and source edit modes</para></listitem> -<listitem><para>Validation and error checking</para></listitem> -</itemizedlist> -<section id="TreeView2"> -<?dbhtml filename="TreeView.html"?> -<title>Tree view</title> + <itemizedlist> + <listitem> + <para>Graphical and source edit modes</para> + </listitem> + <listitem> + <para>Validation and error checking</para> + </listitem> + </itemizedlist> + <section id="TreeView2"> + <?dbhtml filename="TreeView.html"?> + <title>Tree view</title> -<figure> -<title>Tree View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_4.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="SourceView1"> -<?dbhtml filename="SourceView.html"?> -<title>Source view</title> + <figure> + <title>Tree View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_4.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="SourceView1"> + <?dbhtml filename="SourceView.html"?> + <title>Source view</title> -<para>You can easily switch from Tree to Source by selecting the Source tab at the bottom of the editor.</para> + <para>You can easily switch from Tree to Source by selecting the Source tab at the + bottom of the editor.</para> -<figure> -<title>Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_5.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_5.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can easily add a <property>new tag</property>:</para> + <para>You can easily add a <property>new tag</property>:</para> -<figure> -<title>Adding a New Tag</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_6.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Adding a New Tag</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_6.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can also easily add a <property>new attribute</property> to an existing tag:</para> -<figure> -<title>Adding a New Attribute</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_7.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Content assist is available when editing the file using the Source viewer:</para> + <para>You can also easily add a <property>new attribute</property> to an existing + tag:</para> + <figure> + <title>Adding a New Attribute</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_7.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Content assist is available when editing the file using the Source viewer:</para> -<figure> -<title>Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_8.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Content Assist</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_8.png"/> + </imageobject> + </mediaobject> + </figure> -<para>In the Source viewer, if at any point a tag is incorrect or incomplete, an error will be indicated -next to the line and also in the Problems view below.</para> + <para>In the Source viewer, if at any point a tag is incorrect or incomplete, an + error will be indicated next to the line and also in the Problems view below.</para> -<figure> -<title>Error Reporting</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_9.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> + <figure> + <title>Error Reporting</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_9.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> -<section id="GraphicalWebApplicationFile(web.xml)Editor"> -<?dbhtml filename="GraphicalWebApplicationFile(web.xml)Editor.html"?> -<title>Graphical Web Application File (web.xml) Editor</title> + <section id="GraphicalWebApplicationFile(web.xml)Editor"> + <?dbhtml filename="GraphicalWebApplicationFile(web.xml)Editor.html"?> + <title>Graphical Web Application File (web.xml) Editor</title> -<para>The Web Application File editor comes with the same features you will find in all other -JBoss Developer Studio editors:</para> + <para>The Web Application File editor comes with the same features you will find in all + other JBoss Developer Studio editors:</para> -<itemizedlist> -<listitem><para>Graphical and source edit modes</para></listitem> -<listitem><para>Validation and error checking</para></listitem> -</itemizedlist> -<section id="TreeView1"> -<title>Tree View</title> + <itemizedlist> + <listitem> + <para>Graphical and source edit modes</para> + </listitem> + <listitem> + <para>Validation and error checking</para> + </listitem> + </itemizedlist> + <section id="TreeView1"> + <title>Tree View</title> -<figure> -<title>Tree View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_10.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Tree View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_10.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can add any new elements right in the <property>Tree viewer</property>:</para> + <para>You can add any new elements right in the <property>Tree viewer</property>:</para> -<figure> -<title>Adding New Elements</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_11.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="SourceView2"> -<?dbhtml filename="SourceView.html"?> -<title>Source View</title> + <figure> + <title>Adding New Elements</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_11.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="SourceView2"> + <?dbhtml filename="SourceView.html"?> + <title>Source View</title> -<para>Switch to the <property>Source viewer </property>to edit the web.xml file by hand at any time:</para> + <para>Switch to the <property>Source viewer </property>to edit the web.xml file by + hand at any time:</para> -<figure> -<title>Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_12.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ContentAssist"> -<?dbhtml filename="ContentAssist.html"?> -<title>Content Assist</title> + <figure> + <title>Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_12.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ContentAssist"> + <?dbhtml filename="ContentAssist.html"?> + <title>Content Assist</title> -<para>Content assist is available in the Source viewer. Simply click <emphasis><property>CTRL-Space</property></emphasis> anywhere in the file.</para> + <para>Content assist is available in the Source viewer. Simply click <emphasis> + <property>CTRL-Space</property> + </emphasis> anywhere in the file.</para> -<figure> -<title>Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_13.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ErrorCheckingAndValidation"> -<?dbhtml filename="ErrorCheckingAndValidation.html"?> -<title>Errors Checking and Validation</title> + <figure> + <title>Content Assist</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_13.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ErrorCheckingAndValidation"> + <?dbhtml filename="ErrorCheckingAndValidation.html"?> + <title>Errors Checking and Validation</title> -<para>If errors occur anywhere in the file, small red dots will appear next to the lines where the errors - occurred. Also, note that the file is marked by a small x in the Package Explorer view.</para> + <para>If errors occur anywhere in the file, small red dots will appear next to the + lines where the errors occurred. Also, note that the file is marked by a small x + in the Package Explorer view.</para> -<figure> -<title>Errors Reporting</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_14.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> -<section id="GraphicalTilesFilesEditor"> -<?dbhtml filename="GraphicalTilesFilesEditor.html"?> -<title>Graphical Tiles Files Editor</title> -<section id="GraphicalEditorForTilesFiles"> -<?dbhtml filename="GraphicalEditorForTilesFiles.html"?> -<title>Graphical Editor For Tiles Files</title> -<para>The Tiles configuration file editor has three main viewers (modes): Tree (shown), Diagram and Source. The modes can be selected via the tabs at the bottom of the editor. Any changes made in one mode are immediately visible when you switch to any other mode.</para> + <figure> + <title>Errors Reporting</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_14.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section id="GraphicalTilesFilesEditor"> + <?dbhtml filename="GraphicalTilesFilesEditor.html"?> + <title>Graphical Tiles Files Editor</title> + <section id="GraphicalEditorForTilesFiles"> + <?dbhtml filename="GraphicalEditorForTilesFiles.html"?> + <title>Graphical Editor For Tiles Files</title> + <para>The Tiles configuration file editor has three main viewers (modes): Tree + (shown), Diagram and Source. The modes can be selected via the tabs at the + bottom of the editor. Any changes made in one mode are immediately visible when + you switch to any other mode.</para> -<para>When working in Source view, you always have all following features available:</para> + <para>When working in Source view, you always have all following features available:</para> -<itemizedlist> -<listitem><para>Content Assist</para></listitem> -<listitem><para>Open On Selection</para></listitem> -</itemizedlist> -</section> -<section id="CreateNewTilesFile"> -<?dbhtml filename="GraphicalTilesFilesEditor.html"?> -<title>Create New Tiles File</title> + <itemizedlist> + <listitem> + <para>Content Assist</para> + </listitem> + <listitem> + <para>Open On Selection</para> + </listitem> + </itemizedlist> + </section> + <section id="CreateNewTilesFile"> + <?dbhtml filename="GraphicalTilesFilesEditor.html"?> + <title>Create New Tiles File</title> -<para>To create a new Tiles files, right click any folder and select <emphasis><property>New > Tiles Files</property></emphasis>:</para> + <para>To create a new Tiles files, right click any folder and select <emphasis> + <property>New > Tiles Files</property> + </emphasis>:</para> -<figure> -<title>Creating New Tiles File</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_15.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="TreeView3"> -<?dbhtml filename="TreeView.html"?> -<title>Tree View</title> + <figure> + <title>Creating New Tiles File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_15.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="TreeView3"> + <?dbhtml filename="TreeView.html"?> + <title>Tree View</title> -<para>In the Tree mode, the different elements of the Tiles file are organized into functional categories -on the left-hand side and a form for editing the properties of currently selected items on the right-hand - side.</para> + <para>In the Tree mode, the different elements of the Tiles file are organized into + functional categories on the left-hand side and a form for editing the + properties of currently selected items on the right-hand side.</para> -<figure> -<title>Tree View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_16.png"/> - </imageobject> -</mediaobject> -</figure> -<para>To edit the file, simply right click any node and select among the available actions:</para> + <figure> + <title>Tree View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_16.png"/> + </imageobject> + </mediaobject> + </figure> + <para>To edit the file, simply right click any node and select among the available + actions:</para> -<figure> -<title>Editing in Tiles Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_17.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="DiagramView"> -<?dbhtml filename="TreeView.html"?> -<title>Diagram View</title> + <figure> + <title>Editing in Tiles Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_17.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="DiagramView"> + <?dbhtml filename="TreeView.html"?> + <title>Diagram View</title> -<para>The Diagram mode is shown below:</para> -<figure> -<title>Diagram View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_18.png"/> - </imageobject> -</mediaobject> -</figure> + <para>The Diagram mode is shown below:</para> + <figure> + <title>Diagram View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_18.png"/> + </imageobject> + </mediaobject> + </figure> -<para>To create new definition, simply right click anywhere in the diagram:</para> -<figure> -<title>Creating New Definition</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_19.png"/> - </imageobject> -</mediaobject> -</figure> + <para>To create new definition, simply right click anywhere in the diagram:</para> + <figure> + <title>Creating New Definition</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_19.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can also use the Diagram toolbar to make editing easier:</para> + <para>You can also use the Diagram toolbar to make editing easier:</para> -<figure> -<title>Diagram Toolbar</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_20.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="Source"> -<?dbhtml filename="TreeView.html"?> -<title>Source</title> + <figure> + <title>Diagram Toolbar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_20.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="Source"> + <?dbhtml filename="TreeView.html"?> + <title>Source</title> - <para>The Tiles editor also comes with a <property>Source view</property> that gives you full control over the source. -Any changes here will immediately appear in when you switch to any of the other viewers.</para> -<figure> -<title>Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_21.png"/> - </imageobject> -</mediaobject> -</figure> + <para>The Tiles editor also comes with a <property>Source view</property> that gives + you full control over the source. Any changes here will immediately appear in + when you switch to any of the other viewers.</para> + <figure> + <title>Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_21.png"/> + </imageobject> + </mediaobject> + </figure> -<para>Content assist is available in the Source mode.</para> + <para>Content assist is available in the Source mode.</para> -<figure> -<title>Content Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_22.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Content Assist</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_22.png"/> + </imageobject> + </mediaobject> + </figure> -<para>Any errors are immediately reported as shown below:</para> -<figure> -<title>Error Reporting</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_23.png"/> - </imageobject> -</mediaobject> -</figure> + <para>Any errors are immediately reported as shown below:</para> + <figure> + <title>Error Reporting</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_23.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can also use the Outline view together with the editor's Source mode. Selecting any node in the Outline view will jump to that place in the source:</para> + <para>You can also use the Outline view together with the editor's Source + mode. Selecting any node in the Outline view will jump to that place in the + source:</para> -<figure> -<title>Outline View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_24.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> + <figure> + <title>Outline View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_24.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> -<section id="GraphicalEditorForStrutsValidationFiles"> -<?dbhtml filename="GraphicalStrutsValidationFilesEditor.html"?> -<title>Graphical Editor for Struts Validation Files</title> -<para>JBoss Developer Studio comes with a visual validation editor. To create a new validation file, -right click any folder and select <emphasis><property>File > Validation File</property></emphasis> from the context menu.</para> + <section id="GraphicalEditorForStrutsValidationFiles"> + <?dbhtml filename="GraphicalStrutsValidationFilesEditor.html"?> + <title>Graphical Editor for Struts Validation Files</title> + <para>JBoss Developer Studio comes with a visual validation editor. To create a new + validation file, right click any folder and select <emphasis> + <property>File > Validation File</property> + </emphasis> from the context menu.</para> -<figure> -<title>Creating Validation File</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_25.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Creating Validation File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_25.png"/> + </imageobject> + </mediaobject> + </figure> -<para>The validation editor works through a number of viewers.</para> + <para>The validation editor works through a number of viewers.</para> -<para>The Formsets viewer shows forms and their elements for which to define validation rules:</para> + <para>The Formsets viewer shows forms and their elements for which to define validation + rules:</para> -<figure> -<title>Formsets Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_26.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Formsets Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_26.png"/> + </imageobject> + </mediaobject> + </figure> -<para>The Constants viewer lets you set constant values for your validation rules:</para> + <para>The Constants viewer lets you set constant values for your validation rules:</para> -<figure> -<title>Constants viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_27.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Constants viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_27.png"/> + </imageobject> + </mediaobject> + </figure> -<para>The validation file also can be viewed in a Tree viewer:</para> + <para>The validation file also can be viewed in a Tree viewer:</para> -<figure> -<title>Tree Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_28.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Tree Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_28.png"/> + </imageobject> + </mediaobject> + </figure> -<para>At any point you have full control over the source by switching to the Source viewer. Any editing -in this viewer will immediately be available in the other viewers of this editor.</para> + <para>At any point you have full control over the source by switching to the Source + viewer. Any editing in this viewer will immediately be available in the other + viewers of this editor.</para> -<figure> -<title>Source Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_29.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Source Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_29.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can also open your own custom or Struts-standard validation-rules.xml file.</para> + <para>You can also open your own custom or Struts-standard validation-rules.xml file.</para> -<para>The Validators viewer shows the validation rules for a selected validator. You can of course add your - own rules.</para> + <para>The Validators viewer shows the validation rules for a selected validator. You can + of course add your own rules.</para> -<figure> -<title>Validation Rules</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_30.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Validation Rules</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_30.png"/> + </imageobject> + </mediaobject> + </figure> -<para>Here are the validation rules shown in the Source viewer.</para> + <para>Here are the validation rules shown in the Source viewer.</para> -<figure> -<title>Validation Rules in Source Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_31.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="SpringIDE"> -<?dbhtml filename="SpringIDE.html"?> -<title>Spring IDE</title> - <para>JBoss Developer Studio bundles a <property>Spring Framework editor</property> from <ulink url="http://springide.org/project">Spring IDE for Eclipse</ulink>. Visit this site for the latest versions and documentation.</para> + <figure> + <title>Validation Rules in Source Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_31.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="SpringIDE"> + <?dbhtml filename="SpringIDE.html"?> + <title>Spring IDE</title> + <para>JBoss Developer Studio bundles a <property>Spring Framework editor</property> from + <ulink url="http://springide.org/project">Spring IDE for Eclipse</ulink>. Visit + this site for the latest versions and documentation.</para> - <para>You can add a <property>Spring Project nature</property> to an existing project by right-clicking on the project and - selecting from the context menu:</para> + <para>You can add a <property>Spring Project Nature</property> to an existing project by + right-clicking on the project and selecting <emphasis><property>Adding Spring Project + Nature</property></emphasis> from the context menu:</para> -<figure> - <title>Adding Spring Project Nature</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_32.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Adding Spring Project Nature</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_32.png"/> + </imageobject> + </mediaobject> + </figure> - <para>Once the nature is added, you will see a small <property>"S"</property> decorating a Spring project in the Package Explorer - view. To remove the nature, right click the project and select <emphasis><property>Remove Spring Project Nature</property></emphasis>:</para> + <para>If you need to remove it you should select <emphasis> + <property>Remove Spring Project Nature</property></emphasis> from the context menu of your project.</para> + <para>Once the Nature is added, a Spring project will be decorated with a small + <property>"S"</property> in the + <emphasis><property>Package Explorer</property></emphasis> view. + </para> -<figure> - <title>Project with Spring Nature</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_33.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Project with Spring Nature</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_33.png"/> + </imageobject> + </mediaobject> + </figure> -<para>After creating a Spring configuration file with bean definitions:</para> + <para>To add a Spring Configuration File with bean definitions open Properties dialog + from the context menu of your project. Then select <emphasis><property>Spring > Beans Support</property></emphasis> on the left side.</para> + + <figure> + <title>Spring Beans</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_35.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> - <title>Spring Configuration File</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_34.png"/> - </imageobject> - </mediaobject> - </figure> + <para>Click + on <emphasis> + <property>Add</property> + </emphasis> button to choose the corresponding Spring Configuration File.</para> - <para>Select Spring Beans project with <emphasis><property>Project > Properties > Spring > Beans Support</property></emphasis> from the menu bar:</para> + <figure> + <title>Adding Configuration Files</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_36.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> - <title>Spring Beans</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_35.png"/> - </imageobject> - </mediaobject> - </figure> + <para>The added file will also be marked by an <property>"S"</property> + in the + <emphasis><property>Package Explorer</property></emphasis> view.</para> -<para> Now you can add the Spring bean configuration files to your project by clicking on <emphasis><property>Add</property></emphasis> button:</para> + <para>To activate the <emphasis> + <property>Spring Explorer</property></emphasis> view, select <emphasis> + <property>Window > Show View... > Other</property> + </emphasis> and then <emphasis> + <property>Spring > Spring Explorer</property> + </emphasis>.</para> -<figure> - <title>Adding Configuration Files</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_36.png"/> - </imageobject> - </mediaobject> -</figure> + <figure> + <title>Selecting Spring Beans View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_38.png"/> + </imageobject> + </mediaobject> + </figure> -<para>Once you add this file, the file will be marked by an "S" to indicate a Spring bean file:</para> + <para>This view shows a read-only outline view of the Spring Bean Configuration File.</para> + </section> -<figure> - <title>Spring Bean File</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_37.png"/> - </imageobject> - </mediaobject> -</figure> + <section id="CSSEditor"> + <?dbhtml filename="CSSEditor.html"?> + <title>CSS Editor</title> - <para>To activate the Spring Beans view, select <emphasis><property>Window > Show View... > Other</property></emphasis> and then <emphasis><property>Spring Explorer> Spring Beans</property></emphasis> from the - menu bar:</para> + <para>The <property>CSS editor</property> comes with the same features you will find in + all other JBoss Developer Studio editors.</para> -<figure> - <title>Selecting Spring Beans View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_38.png"/> - </imageobject> - </mediaobject> - </figure> + <itemizedlist> + <listitem> + <para>Content assist</para> + </listitem> + <listitem> + <para>Validation and error checking</para> + </listitem> + </itemizedlist> -<para>The Spring Beans view shows a read-only outline view of the Spring bean configuration file:</para> + <para>With the CSS (Cascading Style Sheet) editor, you can take advantage of code + prompting:</para> -<figure> - <title>Spring Beans View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_39.png"/> - </imageobject> - </mediaobject> -</figure> + <figure> + <title>CSS Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_41.png"/> + </imageobject> + </mediaobject> + </figure> -<para>Using a context menu, you can select a graph view of the Spring configuration file's referenced - beans:</para> +  -<section id="CSSEditor"> -<?dbhtml filename="CSSEditor.html"?> -<title>CSS Editor</title> + <para>And you can also use the Properties view next to the editor to edit existing + stylesheet declaration properties:</para> - <para>The <property>CSS editor</property> comes with the same features you will find in all other JBoss Developer Studio editors.</para> + <figure> + <title>Properties View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_43.png"/> + </imageobject> + </mediaobject> + </figure> -<itemizedlist> -<listitem><para>Content assist</para></listitem> -<listitem><para>Validation and error checking</para></listitem> -</itemizedlist> + </section> + <section id="JavaScriptEditor"> + <?dbhtml filename="JavaScriptEditor.html"?> + <title>JavaScript Editor</title> -<para>With the CSS (Cascading Style Sheet) editor, you can take advantage of code prompting:</para> + <para>The <property>JavaScript editor</property> includes a Preview viewer and a Source + viewer. In the Source viewer, you can use code assist:</para> -<figure> -<title>CSS Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_41.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>JavaScript Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_44.png"/> + </imageobject> + </mediaobject> + </figure> -<para>You can also use the Outline view next to the editor to navigate through the CSS file:</para> + <para>You can also use the Source viewer with the Outline view to navigate around the + file:</para> -<figure> -<title>Outline View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_42.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Source Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_45.png"/> + </imageobject> + </mediaobject> + </figure> -<para>And you can also use the Properties view next to the editor to edit existing stylesheet -declaration properties:</para> + </section> + <section id="ImageViewer"> + <?dbhtml filename="ImageViewer.html"?> + <title>Image Viewer</title> + <para>This simple image viewer allows you to view GIF and JPEG files individually in a + separate window:</para> -<figure> -<title>Properties View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_43.png"/> - </imageobject> -</mediaobject> -</figure> + <figure> + <title>Image Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_46.png"/> + </imageobject> + </mediaobject> + </figure> -</section> -<section id="JavaScriptEditor"> -<?dbhtml filename="JavaScriptEditor.html"?> -<title>JavaScript Editor</title> + </section> + <section id="XSDEditor"> + <?dbhtml filename="XSDEditor.html"?> + <title>XSD Editor</title> - <para>The <property>JavaScript editor</property> includes a Preview viewer and a Source viewer. In the Source viewer, you can use code assist:</para> + <para>JBoss Developer Studio comes with an <property>XSD Editor</property> for XML + Schema files. This editor comes from the Web Tools Project (WTP) (see <ulink + url="http://www.eclipse.org/webtools/testtutorials/gettingstarted/GettingStart..." + >WTP Getting Started</ulink>).</para> -<figure> -<title>JavaScript Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_44.png"/> - </imageobject> -</mediaobject> -</figure> + <para>To create a new XSD file, right-click a folder in the Package Explorer view, + select <emphasis> + <property>New > Other...</property> + </emphasis> from the context menu and then select <emphasis> + <property>XML > XML Schema</property> + </emphasis> in the dialog box.</para> -<para>You can also use the Source viewer with the Outline view to navigate around the file:</para> + <figure> + <title>Creating New XSD file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_47.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> -<title>Source Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_45.png"/> - </imageobject> -</mediaobject> -</figure> + <para>The XSD Editor includes two viewers for working on the file, a Design viewer and a + Source viewer:</para> -</section> -<section id="ImageViewer"> -<?dbhtml filename="ImageViewer.html"?> -<title>Image Viewer</title> -<para>This simple image viewer allows you to view GIF and JPEG files individually in a separate window:</para> + <figure> + <title>Source Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_48.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> -<title>Image Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_46.png"/> - </imageobject> -</mediaobject> -</figure> + <para>In the Design viewer, you can drill down on an element by double-clicking on it:</para> -</section> -<section id="XSDEditor"> -<?dbhtml filename="XSDEditor.html"?> -<title>XSD Editor</title> + <figure> + <title>Design Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_49.png"/> + </imageobject> + </mediaobject> + </figure> - <para>JBoss Developer Studio comes with an <property>XSD Editor</property> for XML Schema files. This editor comes from the Web Tools Project (WTP) (see <ulink url="http://www.eclipse.org/webtools/testtutorials/gettingstarted/GettingStart...">WTP Getting Started</ulink>).</para> + <para>Various edit options are available when you right-click an element in the diagram:</para> - <para>To create a new XSD file, right-click a folder in the Package Explorer view, select <emphasis><property>New > Other...</property></emphasis> from the context menu and then select <emphasis><property>XML > XML Schema</property></emphasis> in the dialog box.</para> + <figure> + <title>Edit Options</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_50.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> -<title>Creating New XSD file</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_47.png"/> - </imageobject> -</mediaobject> -</figure> + <para>You can also use the Properties view to edit a selected element:</para> - <para>The XSD Editor includes two viewers for working on the file, a Design viewer and a Source viewer:</para> + <figure> + <title>Properties View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_51.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> -<title>Source Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_48.png"/> - </imageobject> -</mediaobject> -</figure> + <para>You can also use a Source viewer for the file. In this viewer, along with direct + editing of the source code, you can also edit the file by using the Properties view + on the right:</para> - <para>In the Design viewer, you can drill down on an element by double-clicking on it:</para> + <figure> + <title>Source Viewer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_52.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> - <title>Design Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_49.png"/> - </imageobject> -</mediaobject> -</figure> + </section> + <section id="SupportforXMLSchema"> + <?dbhtml filename="SupportforXMLSchema.html"?> + <title>Support for XML Schema</title> -<para>Various edit options are available when you right-click an element in the diagram:</para> + <para>JBoss Developer Studio fully supports XML files based on schemas as well as DTDs:</para> + <figure> + <title>XML File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_53.png"/> + </imageobject> + </mediaobject> + </figure> -<figure> -<title>Edit Options</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_50.png"/> - </imageobject> -</mediaobject> -</figure> + </section> + </section> -<para>You can also use the Properties view to edit a selected element:</para> - -<figure> -<title>Properties View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_51.png"/> - </imageobject> -</mediaobject> -</figure> - -<para>You can also use a Source viewer for the file. In this viewer, along with direct editing of the - source code, you can also edit the file by using the Properties view on the right:</para> - -<figure> -<title>Source Viewer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_52.png"/> - </imageobject> -</mediaobject> -</figure> - -</section> -<section id="SupportforXMLSchema"> -<?dbhtml filename="SupportforXMLSchema.html"?> -<title>Support for XML Schema</title> - -<para>JBoss Developer Studio fully supports XML files based on schemas as well as DTDs:</para> -<figure> -<title>XML File</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/more_editors/more_editors_53.png"/> - </imageobject> -</mediaobject> -</figure> - -</section> -</section> - -</chapter> \ No newline at end of file +</chapter>

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r5159 - trunk/jsf/docs/userguide/en/modules.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2007-11-30 04:45:53 -0500 (Fri, 30 Nov 2007) New Revision: 5159 Modified: trunk/jsf/docs/userguide/en/modules/jsf_support.xml Log: http://jira.jboss.com/jira/browse/RHDS-327 - correcting The section 2.5. Managed Beans Modified: trunk/jsf/docs/userguide/en/modules/jsf_support.xml =================================================================== --- trunk/jsf/docs/userguide/en/modules/jsf_support.xml 2007-11-30 08:12:21 UTC (rev 5158) +++ trunk/jsf/docs/userguide/en/modules/jsf_support.xml 2007-11-30 09:45:53 UTC (rev 5159) @@ -1,43 +1,59 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="jsf_support" xreflabel="jsf_support"> <?dbhtml filename="jsf_support.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>Java</keyword> - <keyword>Tomcat</keyword> - </keywordset> - </chapterinfo> - <title>Java Server Faces Support</title> - <para>JBoss Developer Studio is especially designed for supporting JSF and JSF-related technologies. JBDS provides extensible and exemplary tools for building JSF-based applications as well as adding JSF capabilities to existing web projects, importing JSF projects (created outside JBDS) and choosing any JSF implementation while developing JSF application.</para> - <para>JBoss Developer Studio allows you to develop JSF applications much faster and with far fewer errors so sparing your time.</para> - <section id="SupportForJSFEnvironmentsJSF_RIMyFacesFaceletsShaleOrAnyCustom442"> - <?dbhtml filename="SupportForJSFEnvironmentsJSF-RIMyFacesFaceletsShaleOrAnyCustom.html"?> -<title>Support for JSF Environments: JSF-RI, MyFaces, Facelets or any Custom</title> - <para>With JBoss Developer Studio, we don't lock you into any one <property>JavaServer Faces</property> implementation. Select the one you want to use for your project.</para> -<para>When you:</para> -<itemizedlist> - <listitem><para>Create a new <property>JSF project</property></para></listitem> - <listitem><para>Add <property>JSF capability</property> to any existing Eclipse project</para></listitem> - <listitem><para>Add <property>JSF capability</property> to any existing project (created outside JBDS)</para></listitem> -</itemizedlist> -<para>You can always select which JSF implementation to use.</para> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>Java</keyword> + <keyword>Tomcat</keyword> + </keywordset> + </chapterinfo> + <title>Java Server Faces Support</title> + <para>JBoss Developer Studio is especially designed for supporting JSF and JSF-related + technologies. JBDS provides extensible and exemplary tools for building JSF-based + applications as well as adding JSF capabilities to existing web projects, importing + JSF projects (created outside JBDS) and choosing any JSF implementation while + developing JSF application.</para> + <para>JBoss Developer Studio allows you to develop JSF applications much faster and with far + fewer errors so sparing your time.</para> + <section id="SupportForJSFEnvironmentsJSF_RIMyFacesFaceletsShaleOrAnyCustom442"> + <?dbhtml filename="SupportForJSFEnvironmentsJSF-RIMyFacesFaceletsShaleOrAnyCustom.html"?> + <title>Support for JSF Environments: JSF-RI, MyFaces, Facelets or any Custom</title> + <para>With JBoss Developer Studio, we don't lock you into any one + <property>JavaServer Faces</property> implementation. Select the one + you want to use for your project.</para> + <para>When you:</para> + <itemizedlist> + <listitem> + <para>Create a new <property>JSF project</property></para> + </listitem> + <listitem> + <para>Add <property>JSF capability</property> to any existing + Eclipse project</para> + </listitem> + <listitem> + <para>Add <property>JSF capability</property> to any existing + project (created outside JBDS)</para> + </listitem> + </itemizedlist> + <para>You can always select which JSF implementation to use.</para> -<para>You can also create your own custom JSF environments.</para> -<figure> -<title>Choosing JSF Environment</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_1.png"/> - </imageobject> -</mediaobject> -</figure> + <para>You can also create your own custom JSF environments.</para> + <figure> + <title>Choosing JSF Environment</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_1.png"/> + </imageobject> + </mediaobject> + </figure> -<para>JBoss Developer Studio will add all the required libraries for the selected version to your project.</para> - </section> - - - -<section id="FaceletsSupport865"> -<?dbhtml filename="FaceletsSupport.html"?> -<title>Facelets Support</title> +--> -<para><property>Facelets</property> extends JavaServer Faces by providing a lightweight framework that radically simplifies the design of presentation pages for JSF. JBoss Developer Studio provides support for Facelets in a variety of ways.</para> + <section id="FaceletsSupport865"> + <?dbhtml filename="FaceletsSupport.html"?> + <title>Facelets Support</title> -<para>The Create New JSF Project wizard contains templates for creating Faceletsprojects based on -version 1.2 of the JSF Reference Implementation:</para> -<figure> -<title>Choosing Facelets Environment</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_2.png"/> - </imageobject> -</mediaobject> -</figure> + <para><property>Facelets</property> extends JavaServer Faces by providing a + lightweight framework that radically simplifies the design of presentation + pages for JSF. JBoss Developer Studio provides support for Facelets in a + variety of ways.</para> -<para>Once you select the environment, you can select one of the six available templates:</para> -<figure> -<title>Choosing Facelets Template</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_3.png"/> - </imageobject> -</mediaobject> -</figure> -<para>The JBoss Tools Palette comes with the Facelets components ready to use. A useful tip appears when you hover the mouse cursor over the tag:</para> + <para>The Create New JSF Project wizard contains templates for creating + Faceletsprojects based on version 1.2 of the JSF Reference Implementation:</para> + <figure> + <title>Choosing Facelets Environment</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_2.png"/> + </imageobject> + </mediaobject> + </figure> - -<figure> -<title>Facelets Components</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_4.png"/> - </imageobject> -</mediaobject> -</figure> - <para>Code assist for <property>Facelets tags</property> is available when editing xhtml files:</para> -<figure> -<title>XHTML File Code Assist</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_5.png"/> - </imageobject> -</mediaobject> -</figure> - - <itemizedlist> - <listitem><para>In any HTML tag you also get the code assist for <emphasis role="italic"><property>"jsfc"</property></emphasis> attribute</para></listitem> - </itemizedlist> + <figure> + <title>Facelets Components</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_4.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Code assist for <property>Facelets tags</property> is available when editing + xhtml files:</para> + <figure> + <title>XHTML File Code Assist</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_5.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> -<title>Code Assist for Jsfc Attribute</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_6.png"/> - </imageobject> -</mediaobject> - </figure> - - <itemizedlist> - <listitem><para>Then you get the code assist for JSF components are available on the page</para></listitem> - </itemizedlist> - -<figure> -<title>Code Assist for JSF Components</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_7.png"/> - </imageobject> -</mediaobject> -</figure> - - <itemizedlist> - <listitem><para>Then you will see all available attributes for the component.</para></listitem> - </itemizedlist> - - <figure> - <title></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_8.png"/> - </imageobject> - </mediaobject> - </figure> - -<para>Using JBoss Developer Studio OpenOn feature, you can easily navigate between the <property>Facelets - templates</property> and other parts of your projects. Just by holding down the Control key while hovering the - mouse cursor over a reference to a template, the reference becomes a hyperlink to open that template.</para> -<figure> -<title>Template Hyperlink</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_9.png"/> - </imageobject> -</mediaobject> -</figure> + <itemizedlist> + <listitem> + <para>In any HTML tag you also get the code assist for <emphasis + role="italic"> + <property>"jsfc"</property> + </emphasis> attribute</para> + </listitem> + </itemizedlist> -  - <para>See <link linkend="faq_facelets">FAQ</link> concerning Facelets support.</para> -</section> -<section id="WorkingWithProjects7844"> -<?dbhtml filename="WorkingWithProjects.html"?> -<title>Working with Projects</title> -<section id="CreatingANewJSFProject96"> -<?dbhtml filename="CreatingANewJSFProject.html"?> -<title>Creating a New JSF Project</title> + --> + <para>See <link linkend="faq_facelets">FAQ</link> concerning Facelets + support.</para> + </section> + <section id="WorkingWithProjects7844"> + <?dbhtml filename="WorkingWithProjects.html"?> + <title>Working with Projects</title> + <section id="CreatingANewJSFProject96"> + <?dbhtml filename="CreatingANewJSFProject.html"?> + <title>Creating a New JSF Project</title> -<para>JBoss Developer Studio provides the following when working with JSF:</para> + <para>JBoss Developer Studio provides the following when working with JSF:</para> -<itemizedlist> -<listitem><para>Create new JSF projects</para></listitem> -<listitem><para>Import (open) existing JSF projects</para></listitem> -<listitem><para>Add JSF capability to any existing Eclipse project</para></listitem> -<listitem><para>Import and add JSF capability to any existing project created outside Eclipse</para></listitem> -</itemizedlist> - <para>JBoss Developer Studio allows you to create brand new <emphasis><property>JSF projects</property></emphasis>. A new JSF project will have all JSF - libraries, tag libraries and a JSF configuration file.</para> + <itemizedlist> + <listitem> + <para>Create new JSF projects</para> + </listitem> + <listitem> + <para>Import (open) existing JSF projects</para> + </listitem> + <listitem> + <para>Add JSF capability to any existing Eclipse + project</para> + </listitem> + <listitem> + <para>Import and add JSF capability to any existing project + created outside Eclipse</para> + </listitem> + </itemizedlist> + <para>JBoss Developer Studio allows you to create brand new <emphasis> + <property>JSF projects</property> + </emphasis>. A new JSF project will have all JSF libraries, tag + libraries and a JSF configuration file.</para> -<para>JBoss Developer Studio comes with a number of predefined project templates. These templates are flexible and easily -customizable.</para> + <para>JBoss Developer Studio comes with a number of predefined project + templates. These templates are flexible and easily customizable.</para> -<para>To create a brand new JSF project, select<emphasis><property> File > New > Project > JBoos Tools Web > JSF > JSF Project</property></emphasis> and click <emphasis><property>Next</property></emphasis>:</para> -<figure> -<title>Choosing a JSF Project</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_10.png"/> - </imageobject> -</mediaobject> -</figure> + <para>To create a brand new JSF project, select<emphasis> + <property> File > New > Project > JBoos + Tools Web > JSF > JSF + Project</property> + </emphasis> and click <emphasis> + <property>Next</property> + </emphasis>:</para> + <figure> + <title>Choosing a JSF Project</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_10.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>On this form enter Project Name. You can also select where to create the project.</para> -<para>JSF Version allows you to select which JSF implementation to use:</para> -<figure> -<title>Creating a New JSF Project</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_11.png"/> - </imageobject> -</mediaobject> -</figure> + <para>On this form enter Project Name. You can also select where to create + the project.</para> + <para>JSF Version allows you to select which JSF implementation to use:</para> + <figure> + <title>Creating a New JSF Project</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_11.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>You can also pick a different template on which to base the project. Almost all templates come in two variations: with jsf libraries and without ones. Some servers already provide jsf libs and you take risk of getting conflicting libraries while deploying your project. So the idea here is to avoid such conflicts. Select a template without libs if you use a server with its own jsf libraries.</para> -<figure> -<title>JSF Templates</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_12.png"/> - </imageobject> -</mediaobject> -</figure> -<para>The JSFBlank template will create a standard Web project structure with all JSF capabilities.</para> + <para>You can also pick a different template on which to base the project. + Almost all templates come in two variations: with jsf libraries and + without ones. Some servers already provide jsf libs and you take + risk of getting conflicting libraries while deploying your project. + So the idea here is to avoid such conflicts. Select a template + without libs if you use a server with its own jsf libraries.</para> + <figure> + <title>JSF Templates</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_12.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>The JSFBlank template will create a standard Web project structure + with all JSF capabilities.</para> -<para>The JSFKickStart template will create the same standard structure but will also include a sample application - that is ready to run.</para> + <para>The JSFKickStart template will create the same standard structure but + will also include a sample application that is ready to run.</para> -<para>You can of course create your own custom templates. More information on templates creation could be found in <link linkend="CreatingCustomJSPTemplates">Chapter 5</link>.</para> -<figure> -<title>Choosing JSF Template</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_13.png"/> - </imageobject> -</mediaobject> -</figure> + <para>You can of course create your own custom templates. More information + on templates creation could be found in <link + linkend="CreatingCustomJSPTemplates">Chapter 5</link>.</para> + <figure> + <title>Choosing JSF Template</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_13.png" + /> + </imageobject> + </mediaobject> + </figure> - <para>On the next screen select what <emphasis><property>Servlet version</property></emphasis> to use and whether to register this application with JBoss AS (or other server) for running and testing of your application.</para> + <para>On the next screen select what <emphasis> + <property>Servlet version</property> + </emphasis> to use and whether to register this application with + JBoss AS (or other server) for running and testing of your + application.</para> - <para><emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed.</para> + <para><emphasis> + <property>Context Path</property> + </emphasis> is the name under which the application will be + deployed.</para> - <para>The <emphasis><property>Runtime</property></emphasis> value tells Eclipse where to find Web libraries in order to build (compile) the project. - It is not possible to finish project creation without selecting Runtime. If you don't have any values, - select <emphasis><property>New...</property></emphasis> to add new Runtime.</para> + <para>The <emphasis> + <property>Runtime</property> + </emphasis> value tells Eclipse where to find Web libraries in order + to build (compile) the project. It is not possible to finish project + creation without selecting Runtime. If you don't have any + values, select <emphasis> + <property>New...</property> + </emphasis> to add new Runtime.</para> - <para><emphasis><property>Target Server</property></emphasis> allows you specify whether to deploy the application. The Target Server corresponds to the Runtime value selected above.</para> + <para><emphasis> + <property>Target Server</property> + </emphasis> allows you specify whether to deploy the application. + The Target Server corresponds to the Runtime value selected above.</para> -<para>If you don't want to deploy the application, uncheck this value:</para> -<figure> -<title>Registering the Project on Server</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_14.png"/> - </imageobject> -</mediaobject> -</figure> + <para>If you don't want to deploy the application, uncheck this + value:</para> + <figure> + <title>Registering the Project on Server</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_14.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>When you are all done, you should have the project that has been created in the Package Explorer view:</para> -<figure> -<title>A New Project in the Package Explorer</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_15.png"/> - </imageobject> -</mediaobject> -</figure> + <para>When you are all done, you should have the project that has been + created in the Package Explorer view:</para> + <figure> + <title>A New Project in the Package Explorer</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_15.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>At this point you can open faces-config.xml and start working on your application.</para> -</section> + <para>At this point you can open faces-config.xml and start working on your + application.</para> + </section> - <section id="ImportingExsJSFProjWithAnyStr74447"> -<?dbhtml filename="ImportingExistingJSFProjectsWithAnyStructure.html"?> + <section id="ImportingExsJSFProjWithAnyStr74447"> + <?dbhtml filename="ImportingExistingJSFProjectsWithAnyStructure.html"?> -<title>Importing Existing JSF Projects with Any Structure</title> + <title>Importing Existing JSF Projects with Any Structure</title> - <para>For detailed information on migration projects to JBoss Developer Studio see <ulink url="http://www.redhat.com/developers/jbds/Exadel_Studio_Single/">Migration Guide</ulink>.</para> -</section> - <section id="AddingJSFCapabilityToAnyExistingEclipseProject"> -<?dbhtml filename="AddingJSFCapabilityToAnyExistingEclipseProject.html"?> -<title>Adding JSF Capability to Any Existing Eclipse Project</title> + <para>For detailed information on migration projects to JBoss Developer + Studio see <ulink + url="http://www.redhat.com/developers/jbds/Exadel_Studio_Single/" + >Migration Guide</ulink>.</para> + </section> + <section id="AddingJSFCapabilityToAnyExistingEclipseProject"> + <?dbhtml filename="AddingJSFCapabilityToAnyExistingEclipseProject.html"?> + <title>Adding JSF Capability to Any Existing Eclipse Project</title> -<para>With JBoss Developer Studio you can add <property>JSF capability</property> (JSF libraries, tag libraries) to any existing Eclipse project in your workspace.</para> + <para>With JBoss Developer Studio you can add <property>JSF + capability</property> (JSF libraries, tag libraries) to any existing + Eclipse project in your workspace.</para> -<para>By adding JSF capability to your project, you can now edit any file using JBoss Developer Studio editors, such as JSF configuration editor, JBoss Tools JSP editor and any others.</para> -<para>Right click the project and select <emphasis><property>JBoss Tools > Add JSF Capabilities</property></emphasis>. This will start the process of adding all necessary libraries, files to make this a Web JSF project:</para> -<figure> -<title>Adding JSF Capabilities</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_16.png"/> - </imageobject> -</mediaobject> -</figure> -<para>The wizard will first show you the web.xml file location and the project name:</para> -<figure> -<title>Project Location</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_17.png"/> - </imageobject> -</mediaobject> -</figure> -<para>On the last form you can set the different folders for your project as well as register this - application with a servlet container.</para> + <para>By adding JSF capability to your project, you can now edit any file + using JBoss Developer Studio editors, such as JSF configuration + editor, JBoss Tools JSP editor and any others.</para> + <para>Right click the project and select <emphasis> + <property>JBoss Tools > Add JSF Capabilities</property> + </emphasis>. This will start the process of adding all necessary + libraries, files to make this a Web JSF project:</para> + <figure> + <title>Adding JSF Capabilities</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_16.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>The wizard will first show you the web.xml file location and the + project name:</para> + <figure> + <title>Project Location</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_17.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>On the last form you can set the different folders for your project as + well as register this application with a servlet container.</para> - <para>Make sure to select <emphasis><property>Add JSF Libraries</property></emphasis> for JBoss Developer Studio to add all required JSF related libraries - to this project.</para> + <para>Make sure to select <emphasis> + <property>Add JSF Libraries</property> + </emphasis> for JBoss Developer Studio to add all required JSF + related libraries to this project.</para> - <para><emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed.</para> + <para><emphasis> + <property>Context Path</property> + </emphasis> is the name under which the application will be + deployed.</para> - <para>The <emphasis><property>Runtime</property></emphasis> value tells Eclipse where to find Web libraries in order to build (compile) the project. - It is not possible to finish project import without selecting Runtime. If you don't have any values, select <emphasis><property>New...</property></emphasis> to add new Runtime.</para> + <para>The <emphasis> + <property>Runtime</property> + </emphasis> value tells Eclipse where to find Web libraries in order + to build (compile) the project. It is not possible to finish project + import without selecting Runtime. If you don't have any + values, select <emphasis> + <property>New...</property> + </emphasis> to add new Runtime.</para> - <para><emphasis><property>Target Server</property></emphasis> allows you specify whether to deploy the application. The Target Server corresponds to the - Runtime value selected above.</para> + <para><emphasis> + <property>Target Server</property> + </emphasis> allows you specify whether to deploy the application. + The Target Server corresponds to the Runtime value selected above.</para> -<para>If you don't want to deploy the application, uncheck this value:</para> -<figure> -<title>Project Folders</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_18.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Once your project is imported you can see that JSF related libraries have been added to your - project jsf-api.jar and jsf-impl.jar.</para> -<para>You are now ready to work with JSF by creating a new JSF configuration file:</para> - - + <para>If you don't want to deploy the application, uncheck this + value:</para> <figure> - <title>Creating a New JSF Configuration File</title> - <mediaobject> - <imageobject > - <imagedata fileref="images/jsf_support/jsf_support_19.png"/> - </imageobject> - </mediaobject> + <title>Project Folders</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_18.png" + /> + </imageobject> + </mediaobject> </figure> - - -</section> -<section id="AddingYourOwnProjectTemplates853"> -<?dbhtml filename="AddingYourOwnProjectTemplates.html"?> -<title>Adding Your Own Project Templates</title> + <para>Once your project is imported you can see that JSF related libraries + have been added to your project jsf-api.jar and jsf-impl.jar.</para> + <para>You are now ready to work with JSF by creating a new JSF configuration + file:</para> -<para>JBoss Developer Studio has a powerful templating capability for creating new and importing existing - Struts and JSF projects. This templating facility has a variety of aspects to consider. But, let's start - with the most straightforward case.</para> -<para>Let's say you have a project that you want to use as the basis for a new <property>template</property>. Follow these steps to make a template out of it:</para> -<itemizedlist> -<listitem><para>In the Web Projects view, right-click the project and select <emphasis><property>JBoss Tools JSF > Save As Template</property></emphasis> as - template </para></listitem> -</itemizedlist> - <figure> - <title>Saving Your Project as Template</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_20.png"/> - </imageobject> - </mediaobject> - </figure> -<itemizedlist> -<listitem><para>In the first dialog box, you can choose a name for the template (defaults to the project name) - and confirm what run-time implementation of the project's technology will be used</para></listitem> - <listitem><para>Select <emphasis><property>Next</property></emphasis> and you will be sent to a dialog box with your project structure displayed with - check boxes. Here you can check only those parts and files in your project directory that should be part of - the template</para></listitem> -<listitem><para>At this point, unless you want to designate some extra files as having Velocity template - coding inside them, you should select Finish</para></listitem> -</itemizedlist> -<para>That's it. Now, you can use this template with any new or imported project that uses the same run-time implementation as the project you turned into a <property>template</property>.</para> -</section> -</section> -<section id="GraphicalEditorAndViewingForJSFConfigurationFiles76331"> -<?dbhtml filename="GraphicalEditorAndViewingForJSFConfigurationFiles.html"?> -<title>Graphical Editor and Viewing for JSF Configuration Files</title> -<para>The JSF configuration file editor has three main <property>viewers</property> (modes):</para> + <figure> + <title>Creating a New JSF Configuration File</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_19.png" + /> + </imageobject> + </mediaobject> + </figure> -<itemizedlist> -<listitem><para>Diagram</para></listitem> -<listitem><para>Tree</para></listitem> -<listitem><para>Source</para></listitem> -</itemizedlist> -<para>The modes can be selected via the tabs at the bottom of the editor.</para> + </section> + <section id="AddingYourOwnProjectTemplates853"> + <?dbhtml filename="AddingYourOwnProjectTemplates.html"?> + <title>Adding Your Own Project Templates</title> -<para>The JSF configuration editor also comes with a very useful <link linkend="OpenOnSelection4Hyperlinknavigation">OpenOn</link> selection feature.</para> + <para>JBoss Developer Studio has a powerful templating capability for + creating new and importing existing Struts and JSF projects. This + templating facility has a variety of aspects to consider. But, + let's start with the most straightforward case.</para> -<section id="Diagram9553"> -<?dbhtml filename="Diagram.html"?> -<title>Diagram</title> -<para>The Diagram view displays the navigation rules in the JSF configuration file:</para> -<figure> -<title>Diagram View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_21.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="CreatingNewViewPage85"> -<?dbhtml filename="CreatingNewViewPage.html"?> -<title>Creating New View (Page)</title> + <para>Let's say you have a project that you want to use as the + basis for a new <property>template</property>. Follow these steps to + make a template out of it:</para> + <itemizedlist> + <listitem> + <para>In the Web Projects view, right-click the project and + select <emphasis> + <property>JBoss Tools JSF > Save As + Template</property> + </emphasis> as template </para> + </listitem> + </itemizedlist> + <figure> + <title>Saving Your Project as Template</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_20.png" + /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>In the first dialog box, you can choose a name for the + template (defaults to the project name) and confirm + what run-time implementation of the + project's technology will be used</para> + </listitem> + <listitem> + <para>Select <emphasis> + <property>Next</property> + </emphasis> and you will be sent to a dialog box + with your project structure displayed with check + boxes. Here you can check only those parts and files + in your project directory that should be part of the + template</para> + </listitem> + <listitem> + <para>At this point, unless you want to designate some extra + files as having Velocity template coding inside + them, you should select Finish</para> + </listitem> + </itemizedlist> + <para>That's it. Now, you can use this template with any new or + imported project that uses the same run-time implementation as the + project you turned into a <property>template</property>.</para> + </section> + </section> + <section id="GraphicalEditorAndViewingForJSFConfigurationFiles76331"> + <?dbhtml filename="GraphicalEditorAndViewingForJSFConfigurationFiles.html"?> + <title>Graphical Editor and Viewing for JSF Configuration Files</title> + <para>The JSF configuration file editor has three main <property>viewers</property> + (modes):</para> -<para>To create a new page (view), you can click the page icon on this toolbar and then click anywhere on the diagram. A New Page Wizard will appear.</para> + <itemizedlist> + <listitem> + <para>Diagram</para> + </listitem> + <listitem> + <para>Tree</para> + </listitem> + <listitem> + <para>Source</para> + </listitem> + </itemizedlist> -<para>To create a transition (rule) connecting pages:</para> + <para>The modes can be selected via the tabs at the bottom of the editor.</para> + <para>The JSF configuration editor also comes with a very useful <link + linkend="OpenOnSelection4Hyperlinknavigation">OpenOn</link> + selection feature.</para> -<itemizedlist> -<listitem><para>Select the transition icon from the toolbar (2nd from the bottom).</para></listitem> -<listitem><para>Click the source page.</para></listitem> -<listitem><para>Click the target page.</para></listitem> -</itemizedlist> + <section id="Diagram9553"> + <?dbhtml filename="Diagram.html"?> + <title>Diagram</title> + <para>The Diagram view displays the navigation rules in the JSF + configuration file:</para> + <figure> + <title>Diagram View</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_21.png" + /> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="CreatingNewViewPage85"> + <?dbhtml filename="CreatingNewViewPage.html"?> + <title>Creating New View (Page)</title> -<para>A transition will appear between the two pages:</para> -<figure> -<title>Transition Between JSP Pages</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_22.png"/> - </imageobject> -</mediaobject> -</figure> + <para>To create a new page (view), you can click the page icon on this + toolbar and then click anywhere on the diagram. A New Page Wizard + will appear.</para> -<para>It is also possible to create a new page by right-clicking anywhere on the diagram and selecting <emphasis><property> -New View</property></emphasis>.</para> -<figure> -<title>Creating a New View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_23.png"/> - </imageobject> -</mediaobject> -</figure> + <para>To create a transition (rule) connecting pages:</para> -<para>To edit an existing transition, first select the transition line. Then, place the mouse cursor - over the last black dot (on the target page). The mouse cursor will change to a big +. At this point, - drag the line to a new target page:</para> -<figure> -<title>Editing Transition Between Views</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_24.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="TreeView11123"> -<?dbhtml filename="TreeView.html"?> -<title>Tree View</title> -<para>The Tree mode for the editor displays all JSF application artifacts referenced in the configuration - file in a tree format. Select any node and its properties will appear in the right-hand area:</para> -<figure> -<title>Tree View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_25.png"/> - </imageobject> -</mediaobject> -</figure> + <itemizedlist> + <listitem> + <para>Select the transition icon from the toolbar (2nd from + the bottom).</para> + </listitem> + <listitem> + <para>Click the source page.</para> + </listitem> + <listitem> + <para>Click the target page.</para> + </listitem> + </itemizedlist> -<para>To edit, right-click any node and select one of the available actions in the context menu. You can - also edit in the properties window to the right:</para> -<figure> -<title>Editing in Tree View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_26.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="SourceView4643"> -<?dbhtml filename="SourceView.html"?> -<title>Source View</title> + <para>A transition will appear between the two pages:</para> + <figure> + <title>Transition Between JSP Pages</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_22.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>The Source mode for the editor displays a text view of the JSF configuration file. All three viewers -are always synchronized, so any changes made in one of the viewers will immediately appear in the others:</para> -<figure> -<title>Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_27.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ContentAssist976"> -<?dbhtml filename="SendAnAJAXRequest.html"?> -<title>Content Assist</title> + <para>It is also possible to create a new page by right-clicking anywhere on + the diagram and selecting <emphasis> + <property> New View</property> + </emphasis>.</para> + <figure> + <title>Creating a New View</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_23.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>Content assist is always available in the Source viewer:</para> -<figure> -<title>Content Assist in Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_28.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -<section id="ErrorReporting3324"> -<?dbhtml filename="ErrorReporting.html"?> -<title>Error Reporting</title> + <para>To edit an existing transition, first select the transition line. + Then, place the mouse cursor over the last black dot (on the target + page). The mouse cursor will change to a big +. At this point, drag + the line to a new target page:</para> + <figure> + <title>Editing Transition Between Views</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_24.png" + /> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="TreeView11123"> + <?dbhtml filename="TreeView.html"?> + <title>Tree View</title> -<para>Errors will be reported by JBoss Developer Studio's <link linkend="VerificationandValidation"> verification</link> facility:</para> -<figure> -<title>Error Reporting in Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_29.png"/> - </imageobject> -</mediaobject> -</figure> + <para>The Tree mode for the editor displays all JSF application artifacts + referenced in the configuration file in a tree format. Select any + node and its properties will appear in the right-hand area:</para> + <figure> + <title>Tree View</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_25.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>Other errors are also reported.</para> -<figure> -<title>Others Errors Reporting</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_30.png"/> - </imageobject> -</mediaobject> -</figure> + <para>To edit, right-click any node and select one of the available actions + in the context menu. You can also edit in the properties window to + the right:</para> + <figure> + <title>Editing in Tree View</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_26.png" + /> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="SourceView4643"> + <?dbhtml filename="SourceView.html"?> + <title>Source View</title> - <para>You can also work in the Source viewer with the help of the <emphasis><property>Outline view</property></emphasis>. The Outline views show -a tree structure of the JSF configuration file. Simply select any element in the Outline view, and it will -jump to the same place in the Source viewer.</para> -<figure> -<title>Outline View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_31.png"/> - </imageobject> -</mediaobject> -</figure> + <para>The Source mode for the editor displays a text view of the JSF + configuration file. All three viewers are always synchronized, so + any changes made in one of the viewers will immediately appear in + the others:</para> + <figure> + <title>Source View</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_27.png" + /> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ContentAssist976"> + <?dbhtml filename="SendAnAJAXRequest.html"?> + <title>Content Assist</title> - <para>If your diagram is large, within Outline view you can switch to a <emphasis><property>Diagram Navigator</property></emphasis> mode by selecting - the middle icon at the top of the view window. It allows you to easily move around the diagram. Just move - the blue area in any direction, and the diagram on the left will also move:</para> -<figure> -<title>Outline View for Diagram</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_32.png"/> - </imageobject> -</mediaobject> -</figure> + <para>Content assist is always available in the Source viewer:</para> + <figure> + <title>Content Assist in Source View</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_28.png" + /> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="ErrorReporting3324"> + <?dbhtml filename="ErrorReporting.html"?> + <title>Error Reporting</title> - <para>You can also edit in the <emphasis><property>Tree</property></emphasis> viewer with the help of the Properties view as shown below:</para> -<figure> -<title>Properties View </title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_33.png"/> - </imageobject> -</mediaobject> -</figure> -</section> -</section> -<section id="ManagedBeans96453"> -<?dbhtml filename="ManagedBeans.html"?> -<title>Managed Beans</title> -<section id="CodeGenerationForManagedBeans421"> -<?dbhtml filename="CodeGenerationForManagedBeans.html"?> -<title>Code Generation for Managed Beans</title> + <para>Errors will be reported by JBoss Developer Studio's <link + linkend="VerificationandValidation"> verification</link> + facility:</para> + <figure> + <title>Error Reporting in Source View</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_29.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>JBoss Developer Studio gives you lots of power to work with <property>managed beans</property>.</para> -<itemizedlist> -<listitem><para>Add and generate code for new managed beans</para> -<itemizedlist> -<listitem><para>Generate code for attributes and getter/setter methods</para></listitem> -</itemizedlist></listitem> -<listitem><para>Add existing managed beans to JSF configuration file</para></listitem> -</itemizedlist> -<para>To start, create a new managed bean in JSF configuration file editor, in the Tree view.</para> -<figure> -<title>Creation of New Managed Bean</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_34.png"/> - </imageobject> -</mediaobject> -</figure> -<para>When you define a new managed bean, make sure that Generate Source Code is checked as shown in the - figure below:</para> -<figure> - <title>New Managed Bean</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_35.png"/> - </imageobject> -</mediaobject> -</figure> -<para>After the <emphasis role="italic"><property>"Java"</property></emphasis> class has been generated you can open it for additional editing. There are two ways to open the <emphasis role="italic"><property>"Java"</property></emphasis> class:</para> + <para>Other errors are also reported.</para> + <figure> + <title>Others Errors Reporting</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_30.png" + /> + </imageobject> + </mediaobject> + </figure> -<itemizedlist> - <listitem><para>Click on <emphasis><property>Managed-Bean-Class</property></emphasis> link in the editor -or-</para></listitem> - <listitem><para>Right click the <emphasis><property>managed bean</property></emphasis> and select <emphasis><property>Open Source</property></emphasis></para></listitem> -</itemizedlist> + <para>You can also work in the Source viewer with the help of the <emphasis> + <property>Outline view</property> + </emphasis>. The Outline views show a tree structure of the JSF + configuration file. Simply select any element in the Outline view, + and it will jump to the same place in the Source viewer.</para> + <figure> + <title>Outline View</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_31.png" + /> + </imageobject> + </mediaobject> + </figure> -<figure> -<title>Opening of Created Managed Bean</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_36.png"/> - </imageobject> -</mediaobject> -</figure> + <para>If your diagram is large, within Outline view you can switch to a <emphasis> + <property>Diagram Navigator</property> + </emphasis> mode by selecting the middle icon at the top of the view + window. It allows you to easily move around the diagram. Just move + the blue area in any direction, and the diagram on the left will + also move:</para> + <figure> + <title>Outline View for Diagram</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_32.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>The generated Java source:</para> + <para>You can also edit in the <emphasis> + <property>Tree</property> + </emphasis> viewer with the help of the Properties view as shown + below:</para> + <figure> + <title>Properties View </title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_33.png" + /> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section id="ManagedBeans96453"> + <?dbhtml filename="ManagedBeans.html"?> + <title>Managed Beans</title> + <section id="CodeGenerationForManagedBeans421"> + <?dbhtml filename="CodeGenerationForManagedBeans.html"?> + <title>Code Generation for Managed Beans</title> -<figure> -<title>Java Source Code</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_37.png"/> - </imageobject> -</mediaobject> -</figure> -<para>You can also generate source code for properties - this also includes <emphasis role="italic"><property>"getter"</property></emphasis> and <emphasis role="italic"><property>"setter"</property></emphasis> methods:</para> -<figure> -<title>Generation of Source Code for Properties</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_38.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Make sure that all the check boxes are selected:</para> -<itemizedlist> -<listitem>Add Java property</listitem> -<listitem>Generate Getter</listitem> -<listitem>Generate Setter</listitem> -</itemizedlist> - <para></para> -<figure> -<title>"Add Property" Form</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_39.png"/> - </imageobject> -</mediaobject> -</figure> -<para>Once the generation is complete, you can open the file and see the added property with <emphasis role="italic"><property>"getter"</property></emphasis> and <emphasis role="italic"><property>"setter"</property></emphasis> methods:</para> -<figure> -<title>Generated Java Source Code for Property</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_40.png"/> - </imageobject> -</mediaobject> -</figure> + <para>JBoss Developer Studio gives you lots of power to work with + <property>managed beans</property>.</para> + <itemizedlist> + <listitem> + <para>Add and generate code for new managed beans</para> + <itemizedlist> + <listitem> + <para>Generate code for attributes and + getter/setter methods</para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para>Add existing managed beans to JSF configuration + file</para> + </listitem> + </itemizedlist> + <para>To start, create a new managed bean in JSF configuration file editor, + in the Tree view.</para> + <figure> + <title>Creation of New Managed Bean</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_34.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>When you define a new managed bean, make sure that Generate Source + Code is checked as shown in the figure below:</para> + <figure> + <title>New Managed Bean</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_35.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>After the <emphasis role="italic"> + <property>"Java"</property> + </emphasis> class has been generated you can open it for additional + editing. There are two ways to open the <emphasis role="italic"> + <property>"Java"</property> + </emphasis> class:</para> -</section> -<section id="AddExistingJavaBeansToAJSFConfigurationFile74332"> -<?dbhtml filename="AddExistingJavaBeansToAJSFConfigurationFile.html"?> -<title>Add Existing Java Beans to a JSF Configuration File</title> -<para>If you already have a Java bean you can easily add it to a <property>JSF configuration file</property>.</para> -<para>You would start the same way you would create a new managed bean.</para> -<figure> -<title>Creation of New Managed Bean</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/CrManBean.png"/> - </imageobject> -</mediaobject> -</figure> -<para> On the next screen, type in or browse for your existing Java class.</para> + <itemizedlist> + <listitem> + <para>Click on <emphasis> + <property>Managed-Bean-Class</property> + </emphasis> link in the editor -or-</para> + </listitem> + <listitem> + <para>Right click the <emphasis> + <property>managed bean</property> + </emphasis> and select <emphasis> + <property>Open Source</property> + </emphasis></para> + </listitem> + </itemizedlist> -<para>Once the class is set, it's Name will be set as well. You can always change the name.</para> + <figure> + <title>Opening of Created Managed Bean</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_36.png" + /> + </imageobject> + </mediaobject> + </figure> -<para>Notice that Generate Source Code option is not available as the <emphasis role="italic"><property>"Java"</property></emphasis> class already exists. </para> -<figure> -<title>New Managed Bean Form</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_42.png"/> - </imageobject> -</mediaobject> -</figure> -<para>On the next screen you will see all properties from this class. Check the ones you want to add - managed properties to a <property>JSF configuration file</property>.</para> - <para>If you don't want to add any, just click <emphasis><property>Finish</property></emphasis>.</para> -<figure> -<title>Selection of Bean's Properties.</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_43.png"/> - </imageobject> -</mediaobject> -</figure> + <para>The generated Java source:</para> -</section> -</section> + <figure> + <title>Java Source Code</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_37.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>You can also generate source code for properties - this also includes + <emphasis role="italic"> + <property>"getter"</property> + </emphasis> and <emphasis role="italic"> + <property>"setter"</property> + </emphasis> methods:</para> + <figure> + <title>Generation of Source Code for Properties</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_38.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>Make sure that all the check boxes are selected:</para> + <itemizedlist> + <listitem>Add Java property</listitem> + <listitem>Generate Getter</listitem> + <listitem>Generate Setter</listitem> + </itemizedlist> + <para/> + <figure> + <title>"Add Property" Form</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_39.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>Once the generation is complete, you can open the file and see the + added property with <emphasis role="italic"> + <property>"getter"</property> + </emphasis> and <emphasis role="italic"> + <property>"setter"</property> + </emphasis> methods:</para> + <figure> + <title>Generated Java Source Code for Property</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_40.png" + /> + </imageobject> + </mediaobject> + </figure> -<section id="CreateAndRegisterACustomConverter94230"> -<?dbhtml filename="CreateAndRegisterACustomConverter.html"?> -<title>Create and Register a Custom Converter</title> + </section> + <section id="AddExistingJavaBeansToAJSFConfigurationFile74332"> + <?dbhtml filename="AddExistingJavaBeansToAJSFConfigurationFile.html"?> + <title>Add Existing Java Beans to a JSF Configuration File</title> + <para>If you already have a Java bean you can easily add it to a + <property>JSF configuration file</property>.</para> + <para>You should start the same way you create a new managed bean. Use + <emphasis>Browse...</emphasis> to add your existing Java + class.</para> + <figure> + <title>New Managed Bean Form</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_42.png" + /> + </imageobject> + </mediaobject> + </figure> + <para>Once the class is set, it's <emphasis><property>Name</property></emphasis> will be + set as well. But you can easily substitute it for the other one. + Notice that <emphasis><property>Generate Source Code</property></emphasis> option is not + available as the <emphasis role="italic"> + <property>"Java"</property> + </emphasis> class already exists. </para> + <para> After adding your class + <emphasis><property>Next</property></emphasis> button will be activated. + Pressing it you'll get <emphasis><property>Managed Properties</property></emphasis> dialog where all corresponding properties are displayed. + Check the necessary ones to + add them into your <property>JSF Configuration + File</property>.</para> + <para>If you don't want to add any, just click <emphasis> + <property>Finish</property> + </emphasis>.</para> + <figure> + <title>Selection of Bean's Properties.</title> + <mediaobject> + <imageobject> + <imagedata + fileref="images/jsf_support/jsf_support_43.png" + /> + </imageobject> + </mediaobject> + </figure> + </section> + </section> -<orderedlist> - <listitem><para>In the Project Explorer view open <emphasis><property>faces-config.xml</property></emphasis> and select <emphasis><property>Tree</property></emphasis> tab.</para></listitem> -</orderedlist> -<figure> -<title>Converters</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_44.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> - <listitem><para>Select <emphasis><property>Converters</property></emphasis> and click on<emphasis><property> Add</property></emphasis> button.</para></listitem> -<listitem><para>Type the name of your converter in the Converter-id field and name of the class for converters. - After clicking <emphasis><property>Finish</property></emphasis> button your custom converter is registered under entered name.</para></listitem> - </orderedlist> - <figure> -<title>Add Converter Form</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_45.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> - <listitem><para>Let's create <emphasis role="italic"><property>"converter"</property></emphasis> class. In the Converter section you should see your Converter-id and Converter-class. Click on <emphasis><property>Converter-class</property></emphasis> to generate the source code.</para></listitem> - </orderedlist> - <figure> -<title>Generation of Source Code for Converter Class</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_46.png"/> - </imageobject> -</mediaobject> -</figure> + <section id="CreateAndRegisterACustomConverter94230"> + <?dbhtml filename="CreateAndRegisterACustomConverter.html"?> + <title>Create and Register a Custom Converter</title> -<orderedlist continuation="continues"> - <listitem><para>Java class will be created automatically. Leave everything without changes and click <emphasis><property>Finish</property></emphasis>.</para></listitem> -</orderedlist> -<figure> -<title>New Java Class Form</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_47.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> -<listitem><para>To open converter class click again on Converter-class link in the Converter section. Now - you are able to write business logic of converter.</para></listitem> -</orderedlist> -<figure> - <title>Converter Class</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_48.png"/> - </imageobject> -</mediaobject> -</figure> -</section> + <orderedlist> + <listitem> + <para>In the Project Explorer view open <emphasis> + <property>faces-config.xml</property> + </emphasis> and select <emphasis> + <property>Tree</property> + </emphasis> tab.</para> + </listitem> + </orderedlist> + <figure> + <title>Converters</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_44.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>Select <emphasis> + <property>Converters</property> + </emphasis> and click on<emphasis> + <property> Add</property> + </emphasis> button.</para> + </listitem> + <listitem> + <para>Type the name of your converter in the Converter-id field and + name of the class for converters. After clicking <emphasis> + <property>Finish</property> + </emphasis> button your custom converter is registered under + entered name.</para> + </listitem> + </orderedlist> + <figure> + <title>Add Converter Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_45.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>Let's create <emphasis role="italic"> + <property>"converter"</property> + </emphasis> class. In the Converter section you should see + your Converter-id and Converter-class. Click on <emphasis> + <property>Converter-class</property> + </emphasis> to generate the source code.</para> + </listitem> + </orderedlist> + <figure> + <title>Generation of Source Code for Converter Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_46.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>Java class will be created automatically. Leave everything + without changes and click <emphasis> + <property>Finish</property> + </emphasis>.</para> + </listitem> + </orderedlist> + <figure> + <title>New Java Class Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_47.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>To open converter class click again on Converter-class link in + the Converter section. Now you are able to write business + logic of converter.</para> + </listitem> + </orderedlist> + <figure> + <title>Converter Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_48.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="CreateAndRegisterACustomValidator5632"> -<?dbhtml filename="CreateAndRegisterACustomValidator.html"?> -<title>Create and Register a Custom Validator</title> + <?dbhtml filename="CreateAndRegisterACustomValidator.html"?> + <title>Create and Register a Custom Validator</title> -<orderedlist> - <listitem><para>In the Project Explorer view open<emphasis><property> faces-config.xml</property></emphasis> and select <emphasis><property>Tree </property></emphasis>tab.</para></listitem> -</orderedlist> -<figure> -<title>Validator in Faces Config Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_49.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> - <listitem><para>Select <emphasis><property>Validators</property></emphasis>, and click on <emphasis><property>Add </property></emphasis>button.</para></listitem> -<listitem><para>Type the name of your validator in the Valifator-id field an - d name of the class for validators. After clicking <emphasis><property>Finish</property></emphasis> button your custom validator is registered under entered name.</para></listitem> -</orderedlist> -<figure> -<title>Adding Validator</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_50.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> - <listitem><para>Let's create <emphasis role="italic"><property>"validator"</property></emphasis> class. In the Validator section you should see your Validator-id and Validator-class. Click on <emphasis><property>Validator-class</property></emphasis> to generate the source code.</para></listitem> -</orderedlist> -<figure> - <title>Creating Validator Class</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_51.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> - <listitem><para>Java class will be created automatically. Leave everything without changes and click <emphasis><property>Finish</property></emphasis>.</para></listitem> -</orderedlist> -<figure> -<title>New Java Class Form</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_52.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> -<listitem><para>To open validator class click again on Validator-class in the Validator section. Now you are - able to write business logic of validator.</para></listitem> - </orderedlist> - <figure> - <title>Converter Class Editing</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_53.png"/> - </imageobject> -</mediaobject> -</figure> -</section> + <orderedlist> + <listitem> + <para>In the Project Explorer view open<emphasis> + <property> faces-config.xml</property> + </emphasis> and select <emphasis> + <property>Tree </property> + </emphasis>tab.</para> + </listitem> + </orderedlist> + <figure> + <title>Validator in Faces Config Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_49.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>Select <emphasis> + <property>Validators</property> + </emphasis>, and click on <emphasis> + <property>Add </property> + </emphasis>button.</para> + </listitem> + <listitem> + <para>Type the name of your validator in the Valifator-id field an d + name of the class for validators. After clicking <emphasis> + <property>Finish</property> + </emphasis> button your custom validator is registered under + entered name.</para> + </listitem> + </orderedlist> + <figure> + <title>Adding Validator</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_50.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>Let's create <emphasis role="italic"> + <property>"validator"</property> + </emphasis> class. In the Validator section you should see + your Validator-id and Validator-class. Click on <emphasis> + <property>Validator-class</property> + </emphasis> to generate the source code.</para> + </listitem> + </orderedlist> + <figure> + <title>Creating Validator Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_51.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>Java class will be created automatically. Leave everything + without changes and click <emphasis> + <property>Finish</property> + </emphasis>.</para> + </listitem> + </orderedlist> + <figure> + <title>New Java Class Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_52.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>To open validator class click again on Validator-class in the + Validator section. Now you are able to write business logic + of validator.</para> + </listitem> + </orderedlist> + <figure> + <title>Converter Class Editing</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_53.png"/> + </imageobject> + </mediaobject> + </figure> + </section> <section id="CreateAndRegisterReferencedBeans64322"> -<?dbhtml filename="CreateAndRegisterReferencedBeans.html"?> -<title>Create and Register Referenced Beans</title> -<orderedlist> - <listitem><para>In the Project Explorer view open<emphasis><property> faces-config.xml</property></emphasis> and select <emphasis><property>Tree </property></emphasis>tab.</para></listitem> -</orderedlist> -<figure> - <title>Validator in Faces Config Editor</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_54.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> -<listitem><para>Select <emphasis><property>Referenced Beans</property></emphasis> and click on <emphasis><property>Add</property></emphasis> button.</para></listitem> -<listitem><para>Type in the name of your Referenced Bean and type in or select Referenced-Bean-Class by -using Browse button.</para></listitem> -</orderedlist> -<figure> -<title>Add Validator Form</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_55.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> -<listitem><para>In the Referenced Bean section you should see your Referenced-Bean-Name and -Referenced-Bean-Class. Click on the link to open the Java creation wizard.</para></listitem> -</orderedlist> -<figure> - <title>Create Validator Class</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_56.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> - <listitem><para>Java class will be created automatically. Leave everything without changes and click <emphasis><property>Finish</property></emphasis>.</para></listitem> -</orderedlist> -<figure> -<title>New Java Class Form</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_57.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> -<listitem><para>To open Referenced Bean class click again on <emphasis><property>Referenced-Bean-Class</property></emphasis> in the Referenced Bean section. Now you are able to write business logic of Referenced Bean.</para></listitem> - </orderedlist> - <figure> - <title>Referenced Bean Class Editing</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_58.png"/> - </imageobject> -</mediaobject> -</figure> -</section> + <?dbhtml filename="CreateAndRegisterReferencedBeans.html"?> + <title>Create and Register Referenced Beans</title> + <orderedlist> + <listitem> + <para>In the Project Explorer view open<emphasis> + <property> faces-config.xml</property> + </emphasis> and select <emphasis> + <property>Tree </property> + </emphasis>tab.</para> + </listitem> + </orderedlist> + <figure> + <title>Validator in Faces Config Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_54.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>Select <emphasis> + <property>Referenced Beans</property> + </emphasis> and click on <emphasis> + <property>Add</property> + </emphasis> button.</para> + </listitem> + <listitem> + <para>Type in the name of your Referenced Bean and type in or select + Referenced-Bean-Class by using Browse button.</para> + </listitem> + </orderedlist> + <figure> + <title>Add Validator Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_55.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>In the Referenced Bean section you should see your + Referenced-Bean-Name and Referenced-Bean-Class. Click on the + link to open the Java creation wizard.</para> + </listitem> + </orderedlist> + <figure> + <title>Create Validator Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_56.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>Java class will be created automatically. Leave everything + without changes and click <emphasis> + <property>Finish</property> + </emphasis>.</para> + </listitem> + </orderedlist> + <figure> + <title>New Java Class Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_57.png"/> + </imageobject> + </mediaobject> + </figure> + <orderedlist continuation="continues"> + <listitem> + <para>To open Referenced Bean class click again on <emphasis> + <property>Referenced-Bean-Class</property> + </emphasis> in the Referenced Bean section. Now you are able + to write business logic of Referenced Bean.</para> + </listitem> + </orderedlist> + <figure> + <title>Referenced Bean Class Editing</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_58.png"/> + </imageobject> + </mediaobject> + </figure> + </section> </chapter>

17 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits November 2007