JBoss Tools SVN: r7138 - trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers.
by jbosstools-commits＠lists.jboss.org
Author: rob.stryker(a)jboss.com
Date: 2008-03-26 18:55:15 -0400 (Wed, 26 Mar 2008)
New Revision: 7138
Modified:
trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers/PackagesPublisher.java
Log:
organized inputs + parametized refactor
Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers/PackagesPublisher.java
===================================================================
--- trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers/PackagesPublisher.java 2008-03-26 22:35:20 UTC (rev 7137)
+++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers/PackagesPublisher.java 2008-03-26 22:55:15 UTC (rev 7138)
@@ -34,18 +34,15 @@
import org.eclipse.wst.server.core.IServer;
import org.eclipse.wst.server.core.model.IModuleResource;
import org.eclipse.wst.server.core.model.IModuleResourceDelta;
-import org.eclipse.wst.server.core.model.ServerBehaviourDelegate;
import org.jboss.ide.eclipse.archives.core.model.IArchive;
import org.jboss.ide.eclipse.as.core.JBossServerCorePlugin;
import org.jboss.ide.eclipse.as.core.extensions.events.EventLogModel.EventLogTreeItem;
import org.jboss.ide.eclipse.as.core.modules.PackageModuleFactory.ExtendedModuleFile;
import org.jboss.ide.eclipse.as.core.modules.PackageModuleFactory.IExtendedModuleResource;
import org.jboss.ide.eclipse.as.core.modules.PackageModuleFactory.PackagedModuleDelegate;
-import org.jboss.ide.eclipse.as.core.publishers.PublisherEventLogger.PublishEvent;
import org.jboss.ide.eclipse.as.core.publishers.PublisherEventLogger.PublisherFileUtilListener;
import org.jboss.ide.eclipse.as.core.server.IDeployableServer;
import org.jboss.ide.eclipse.as.core.server.IJBossServerPublisher;
-import org.jboss.ide.eclipse.as.core.server.internal.JBossServer;
import org.jboss.ide.eclipse.as.core.util.FileUtil;
import org.jboss.ide.eclipse.as.core.util.ServerConverter;
@@ -129,13 +126,13 @@
protected void publishFromDelta(IModule module, IPath destPathRoot, IPath sourcePrefix,
IModuleResourceDelta[] delta, PublisherFileUtilListener listener) {
- ArrayList changedFiles = new ArrayList();
+ ArrayList<IPath> changedFiles = new ArrayList<IPath>();
for( int i = 0; i < delta.length; i++ ) {
publishFromDeltaHandle(delta[i], destPathRoot, sourcePrefix, changedFiles, listener);
}
}
protected void publishFromDeltaHandle(IModuleResourceDelta delta, IPath destRoot,
- IPath sourcePrefix, ArrayList changedFiles, PublisherFileUtilListener listener) {
+ IPath sourcePrefix, ArrayList<IPath> changedFiles, PublisherFileUtilListener listener) {
switch( delta.getKind()) {
case IModuleResourceDelta.REMOVED:
// removed might not be IExtendedModuleResource
18 years
- 1
- 0
JBoss Tools SVN: r7137 - trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers.
by jbosstools-commits＠lists.jboss.org
Author: rob.stryker(a)jboss.com
Date: 2008-03-26 18:35:20 -0400 (Wed, 26 Mar 2008)
New Revision: 7137
Modified:
trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers/JstPublisher.java
Log:
JBIDE-1954 - connector / rar extension
Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers/JstPublisher.java
===================================================================
--- trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers/JstPublisher.java 2008-03-26 22:01:37 UTC (rev 7136)
+++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers/JstPublisher.java 2008-03-26 22:35:20 UTC (rev 7137)
@@ -188,7 +188,9 @@
root = root.append(name + ".war");
else if( "jst.utility".equals(type) && i >= 1 && "jst.web".equals(moduleTree[i-1].getModuleType().getId()))
root = root.append("WEB-INF").append("lib").append(name + ".jar");
- else
+ else if( "jst.connector".equals(type)) {
+ root = root.append(name + ".rar");
+ } else
root = root.append(name + ".jar");
}
return root;
18 years
- 1
- 0
JBoss Tools SVN: r7136 - trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/widget/editor.
by jbosstools-commits＠lists.jboss.org
Author: rob.stryker(a)jboss.com
Date: 2008-03-26 18:01:37 -0400 (Wed, 26 Mar 2008)
New Revision: 7136
Modified:
trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/widget/editor/SeamRuntimeListFieldEditor.java
Log:
JBIDE-1956 - ui error
Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/widget/editor/SeamRuntimeListFieldEditor.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/widget/editor/SeamRuntimeListFieldEditor.java 2008-03-26 19:44:24 UTC (rev 7135)
+++ trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/widget/editor/SeamRuntimeListFieldEditor.java 2008-03-26 22:01:37 UTC (rev 7136)
@@ -53,6 +53,9 @@
import org.eclipse.swt.events.SelectionEvent;
import org.eclipse.swt.events.SelectionListener;
import org.eclipse.swt.graphics.Image;
+import org.eclipse.swt.layout.FormAttachment;
+import org.eclipse.swt.layout.FormData;
+import org.eclipse.swt.layout.FormLayout;
import org.eclipse.swt.layout.GridData;
import org.eclipse.swt.layout.GridLayout;
import org.eclipse.swt.widgets.Button;
@@ -98,6 +101,8 @@
private Composite root = null;
+ private ActionPanel actionPanel;
+
private Map<SeamRuntime, SeamRuntime> changed = new HashMap<SeamRuntime, SeamRuntime>();
private List<SeamRuntime> checkedElements = new ArrayList<SeamRuntime>();
@@ -172,22 +177,34 @@
public Object[] getEditorControls(Object composite) {
root = new Composite((Composite) composite, SWT.NONE);
- root.setLayout(new GridLayout(GL_COLUMNS, false));
GridData gd = new GridData();
gd.horizontalAlignment = GridData.FILL;
gd.grabExcessHorizontalSpace = true;
root.setLayoutData(gd);
+ root.setLayout(new FormLayout());
+ createTableView();
+ createActionBar();
+
+ FormData tableData = new FormData();
+ tableData.left = new FormAttachment(0,5);
+ tableData.right = new FormAttachment(actionPanel, -5);
+ tableData.top = new FormAttachment(0,5);
+ tableData.bottom = new FormAttachment(100,-5);
+ tableView.getControl().setLayoutData(tableData);
+
+ FormData actionsData = new FormData();
+ actionsData.top = new FormAttachment(0,5);
+ actionsData.bottom = new FormAttachment(100,-5);
+ actionsData.right = new FormAttachment(100,-5);
+ actionPanel.setLayoutData(actionsData);
+ return new Control[] {root};
+ }
+
+ protected void createTableView() {
tableView = CheckboxTableViewer.newCheckList(root, SWT.V_SCROLL
| SWT.BORDER | SWT.FULL_SELECTION | SWT.SINGLE);
- gd = new GridData();
- gd.heightHint = GL_HINT_HEIGHT;
- gd.horizontalAlignment = GridData.FILL;
- gd.grabExcessHorizontalSpace = true;
-
- tableView.getControl().setLayoutData(gd);
-
TableColumn tc1 = new TableColumn(tableView.getTable(), SWT.CENTER);
tc1.setWidth(TC_DEFAULT_WIDTH);
tc1.setResizable(false);
@@ -316,10 +333,12 @@
checkedElements.add(rt);
}
}
- ActionPanel actionPanel = new ActionPanel(root, new BaseAction[] {
+ }
+
+ protected void createActionBar() {
+ actionPanel = new ActionPanel(root, new BaseAction[] {
new AddAction(), new EditAction(), new RemoveAction()});
tableView.addSelectionChangedListener(actionPanel);
- return new Control[] {root};
}
/**
@@ -866,11 +885,6 @@
super(parent, style);
this.actions = actions;
setLayout(new GridLayout(1, false));
- GridData gd = new GridData();
- gd.horizontalAlignment = GridData.FILL;
- gd.verticalAlignment = GridData.FILL;
- gd.grabExcessVerticalSpace = true;
- setLayoutData(gd);
for (BaseAction action : this.actions) {
new ActionButton(this, SWT.PUSH, action);
}
@@ -912,10 +926,7 @@
*/
public static class ActionButton implements IPropertyChangeListener {
- private static final int DEFAULT_WIDTH_HINT = 50;
-
private Button button;
-
private BaseAction action;
/**
@@ -938,7 +949,6 @@
gd.horizontalAlignment = GridData.FILL;
gd.verticalAlignment = GridData.VERTICAL_ALIGN_BEGINNING;
- gd.widthHint = DEFAULT_WIDTH_HINT;
this.button.setLayoutData(gd);
this.action.addPropertyChangeListener(this);
this.button.setText(action.getText());
18 years
- 1
- 0
JBoss Tools SVN: r7135 - trunk/vpe/features/org.jboss.tools.xulrunner.feature.
by jbosstools-commits＠lists.jboss.org
Author: mculpepper(a)jboss.com
Date: 2008-03-26 15:44:24 -0400 (Wed, 26 Mar 2008)
New Revision: 7135
Modified:
trunk/vpe/features/org.jboss.tools.xulrunner.feature/feature.xml
Log:
added 64 bit xulrunner plugin to the xulrunner feature
Modified: trunk/vpe/features/org.jboss.tools.xulrunner.feature/feature.xml
===================================================================
--- trunk/vpe/features/org.jboss.tools.xulrunner.feature/feature.xml 2008-03-26 19:18:57 UTC (rev 7134)
+++ trunk/vpe/features/org.jboss.tools.xulrunner.feature/feature.xml 2008-03-26 19:44:24 UTC (rev 7135)
@@ -424,7 +424,7 @@
<update label="JBossTools Update Site" url="http://download.jboss.org/jbosstools/updates/stable"/>
<discovery label="JBossTools Development Update Site" url="http://download.jboss.org/updates/development"/>
</url>
-
+
<plugin
id="org.mozilla.xpcom"
download-size="0"
@@ -449,6 +449,15 @@
version="1.8.1.3-20070904"/>
<plugin
+ id="org.mozilla.xulrunner.gtk.linux.x86_64"
+ os="linux"
+ ws="gtk"
+ arch="x86_64"
+ download-size="0"
+ install-size="0"
+ version="1.8.1.4-20080112"/>
+
+ <plugin
id="org.mozilla.xulrunner.win32.win32.x86"
os="win32"
ws="win32"
18 years
- 1
- 0
JBoss Tools SVN: r7134 - in trunk/jsf/docs/jsf_tools_ref_guide/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2008-03-26 15:18:57 -0400 (Wed, 26 Mar 2008)
New Revision: 7134
Added:
trunk/jsf/docs/jsf_tools_ref_guide/en/modules/cust_converters_validators.xml
trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_config_file.xml
trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_support.xml
trunk/jsf/docs/jsf_tools_ref_guide/en/modules/managed_beans.xml
trunk/jsf/docs/jsf_tools_ref_guide/en/modules/projects.xml
trunk/jsf/docs/jsf_tools_ref_guide/en/modules/referenced_beans.xml
Modified:
trunk/jsf/docs/jsf_tools_ref_guide/en/master.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-261 - several chapters were organized from the one
Modified: trunk/jsf/docs/jsf_tools_ref_guide/en/master.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/master.xml 2008-03-26 19:10:17 UTC (rev 7133)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/master.xml 2008-03-26 19:18:57 UTC (rev 7134)
@@ -3,8 +3,13 @@
"../../resources/support/docbook-dtd/docbookx.dtd"
[
-<!ENTITY intoduction SYSTEM "modules/introduction.xml">
-<!ENTITY jsf_tools SYSTEM "modules/jsf_tools.xml">
+<!ENTITY introduction SYSTEM "modules/introduction.xml">
+<!ENTITY jsf_support SYSTEM "modules/jsf_support.xml">
+<!ENTITY projects SYSTEM "modules/projects.xml">
+<!ENTITY jsf_config_file SYSTEM "modules/jsf_config_file.xml">
+<!ENTITY managed_beans SYSTEM "modules/managed_beans.xml">
+<!ENTITY cust_converters_validators SYSTEM "modules/cust_converters_validators.xml">
+<!ENTITY referenced_beans SYSTEM "modules/referenced_beans.xml">
<!ENTITY jsf_project_verification SYSTEM "modules/jsf_project_verification.xml">
]>
<book>
@@ -22,6 +27,11 @@
<toc/>
&introduction;
- &jsf_tools;
+ &jsf_support;
+ &projects;
+ &jsf_config_file;
+ &managed_beans;
+ &cust_converters_validators;
+ &referenced_beans;
&jsf_project_verification;
</book>
\ No newline at end of file
Added: trunk/jsf/docs/jsf_tools_ref_guide/en/modules/cust_converters_validators.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/modules/cust_converters_validators.xml (rev 0)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/modules/cust_converters_validators.xml 2008-03-26 19:18:57 UTC (rev 7134)
@@ -0,0 +1,250 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="cust_converters_validators">
+ <?dbhtml filename="cust_converters_validators.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JSF Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Create and Register Custom Converters and Validators</title>
+
+ <section id="CreateAndRegisterACustomConverter94230">
+
+ <title>Create and Register a Custom Converter</title>
+
+ <para>To create and register a custom converter it's necessary to
+ go through the following steps:</para>
+
+ <itemizedlist>
+ <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>
+ </itemizedlist>
+ <figure>
+ <title>Converters</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_44.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Select <emphasis>
+ <property>Converters</property>
+ </emphasis> and click on<emphasis>
+ <property> Add</property>
+ </emphasis> button.</para>
+ </listitem>
+ <listitem>
+ <para>On the form type the name of your converter in the <emphasis>
+ <property>Converter-id</property>
+ </emphasis> field and name of the class for
+ converters. After clicking <emphasis>
+ <property>Finish</property>
+ </emphasis> button your custom converter is
+ registered under the entered name.</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Add Converter Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_45.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Now you can create <emphasis role="italic">
+ <property>"converter"</property>
+ </emphasis> class. In the Converter section you
+ should see your <emphasis>
+ <property>Converter-id</property>
+ </emphasis> and
+ <emphasis><property>Converter-class</property>.</emphasis>
+ Click on <emphasis>
+ <property>Converter-class</property>
+ </emphasis> to generate the source code.</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Generation of Source Code for Converter Class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_46.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem>
+ <para>A usual wizard for creating a Java class will appear.
+ All needed fields here will be adjusted
+ automatically. Just leave everything without changes
+ and click <emphasis>
+ <property>Finish</property>.
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>New Java Class Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_47.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>To open a converter class click again on <emphasis>
+ <property>Converter-class</property>
+ </emphasis> link in the Converter section. Now you
+ are able to add a business logic of converter in the
+ Java editor.</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Converter Class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_48.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+ <section id="CreateAndRegisterACustomValidator5632">
+
+ <title>Create and Register a Custom Validator</title>
+
+ <para>With the help of JBDS it's also quite easy to develop your
+ own custom Validators. You should perform the actions similar to
+ previous. Go through the following steps:</para>
+ <itemizedlist>
+ <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>
+ </itemizedlist>
+ <figure>
+ <title>Validator in Faces Config Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_49.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <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 <emphasis>
+ <property>Validator-id</property>
+ </emphasis> field and name of the class for
+ validators. After clicking <emphasis>
+ <property>Finish</property>
+ </emphasis> button your custom validator is
+ registered under the entered name.</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Adding Validator</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_50.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Now you can create the "validator" class. </para>
+ <itemizedlist>
+ <listitem>
+ <para>In the Validator section you can see your <emphasis>
+ <property>Validator-id</property>
+ </emphasis> and <emphasis>
+ <property>Validator-class</property>
+ </emphasis>. To generate the source code click on <emphasis>
+ <property>Validator-class</property>.
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Creating Validator Class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_51.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Java class will be created automatically. Leave
+ everything without changes and click <emphasis>
+ <property>Finish</property>.
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>New Java Class Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_52.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>To open validator class click again on <emphasis>
+ <property>Validator-Class</property>
+ </emphasis> link in the Validator section. Now you
+ are able to write a business logic of validator in
+ the Java editor.</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Converter Class Editing</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_53.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+</chapter>
Added: trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_config_file.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_config_file.xml (rev 0)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_config_file.xml 2008-03-26 19:18:57 UTC (rev 7134)
@@ -0,0 +1,288 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jsf_config_file">
+ <?dbhtml filename="jsf_config_file.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JSF Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>JSF Configuration File</title>
+
+ <para>First, we should mention that JSF configuration file (<emphasis>
+ <property>faces-config.xml</property>
+ </emphasis>) is intended for registering JSF application resources
+ such as Converters, Validators, Managed Beans and page-to-page
+ navigation rules.</para>
+ <para>Now, let's look at how you can easily configure this file by
+ means of a special graphical editor. The editor has three main
+ viewers (modes):</para>
+
+ <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>
+
+ <para>The JSF configuration editor also comes with a very useful <link
+ linkend="OpenOnSelection4Hyperlinknavigation">OpenOn</link>
+ selection feature.</para>
+
+ <section id="Diagram9553">
+
+ <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">
+
+ <title>Creating New View (Page)</title>
+
+ <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>To create a transition (rule) connecting pages:</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>
+
+ <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>It is also possible to create a new page with context menu 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 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">
+
+ <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. By selecting any node you can see and edit its
+ properties which will appear in the right-hand area. For
+ example, a Managed Bean:</para>
+ <figure>
+ <title>Tree View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_25.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>To edit some artifact, 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>
+ <para>The same way you can create a new artifact:</para>
+ <figure>
+ <title>Creating a New Artifact in Tree View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_59.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="SourceView4643">
+
+ <title>Source View</title>
+
+ <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"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="ContentAssist976">
+
+ <title>Code Assist</title>
+ <para>Code Assist provides pop-up tip to help you complete your code
+ statements. It allows you to write your code faster and with
+ more accuracy.</para>
+ <para>Code assist is always available in the Source mode:</para>
+ <figure>
+ <title>Code Assist in Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_28.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="ErrorReporting3324">
+
+ <title>Error Reporting</title>
+ <para>When you are developing your project, JBoss Developer Studio
+ constantly provides error checking. This greatly reduces
+ your development time as it allows you to catch many of the
+ errors during development.</para>
+ <para>Errors will be reported by JBoss Developer Studio's
+ <link linkend="verif_valid"> verification</link>
+ facility:</para>
+ <figure>
+ <title>Error Reporting in Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_29.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Other errors are also reported.</para>
+ <figure>
+ <title>Other Errors Reporting</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_30.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can also work in the Source editor 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 editor, so you can
+ navigate through the source code with Outline view.</para>
+ <figure>
+ <title>Outline View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_31.png"
+ scale="60"/>
+ </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"
+ scale="60"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can also edit the properties of the selected element in
+ the <property>Tree</property> mode 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"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+</chapter>
Added: trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_support.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_support.xml (rev 0)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_support.xml 2008-03-26 19:18:57 UTC (rev 7134)
@@ -0,0 +1,352 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jsf_support">
+ <?dbhtml filename="jsf_support.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JSF Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>JavaServer 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>With Developer Studio, we don't lock you into any one <property>JavaServer
+ Faces</property> implementation. You can select the one which is necessary
+ for you while <link linkend="new_jsf_project">creating a new JSF project</link> or
+ <link linkend="add_jsf_capability">adding JSF capability</link> to any
+ existing Eclipse project.</para>
+
+ <para>The spacial wizard will prompt you to specify a proper JSF environment. It may be
+ JSF 1.1.02 RI or JSF 1.2 which is integrates a number of new features and
+ changes. The wizard also lets you select JSF implementations with a component orientation such as JSF 1.2 with
+ Facelets or MyFaces 1.1.4.</para>
+
+ <figure>
+ <title>Choosing JSF Environment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_11.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>After specifying a proper JSF environment all the required libraries for the selected version will be added to
+ your project.</para>
+
+ <!--
+<section id="AddingSupportForTheOracleADFComponentsLibraryOrAnyOtherSupport64">
+<?dbhtml filename="AddingSupportForTheOracleADFComponentsLibraryOrAnyOtherSupport.html"?>
+<title>Adding Support for the Oracle ADF Components Library or Any Other Support</title>
+
+<para>JBoss Developer Studio is set up to work with the <property>ADF Faces Component Library</property>, but still requires a few extra
+ steps to complete the support. First, you will need to download the 2 jar files for the library from the
+ Oracle site down to your system. Then, you just need to follow these steps to add ADF Faces support to your projects:</para>
+
+<itemizedlist>
+ <listitem><para>Select <emphasis><property>Window > Preferences > Red Hat > Library Sets</property></emphasis> from the menu bar.</para></listitem>
+ <listitem><para>Select <emphasis><property>OracleADF</property></emphasis> in the upper pane.</para></listitem>
+ <listitem>Then, click <emphasis><property>Add</property></emphasis> in the lower pane and browse to the location where you have both ADF jar files:
+<itemizedlist>
+ <listitem><para>adf-faces-api-eaXX.jar</para></listitem>
+ <listitem><para>adf-faces-impl-eaXX.jar</para></listitem>
+ </itemizedlist></listitem>
+ <listitem>In Preferences, select <emphasis><property>Custom Capability</property></emphasis>. Notice that Custom Capability ADF has the OracleADF
+ library set to which we just added the required Jar libraries. We don't need to do anything here.</listitem>
+ <listitem><para>Click <emphasis><property>OK</property></emphasis> and then click <emphasis><property>OK</property></emphasis> again.</para></listitem>
+<listitem>After this is done, you can always add in the library files to a project by just right-clicking
+ your project and selecting <emphasis><property>JBoss Developer Studio > Add Custom Capability...</property></emphasis> from the context menu and select a needed capability.</listitem>
+</itemizedlist>
+
+<para>You can add any custom capability (support) to your project using Library Sets in the same fashion. </para>
+</section>
+-->
+
+ <section id="FaceletsSupport865">
+
+ <title>Facelets Support</title>
+ <para>This section will perform you all concepts that JBDS involves to use the
+ Facelets.</para>
+
+ <para>The Facelets 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>
+ <title>Facelets templates</title>
+
+ <para>The New JSF Project wizard contains templates for creating Facelets
+ projects based on version 1.2 of the JSF Reference Implementation.
+ Select the <emphasis>
+ <property>JSF 1.2 with Facelets</property>
+ </emphasis> in JSF Environment section.</para>
+
+ <figure>
+ <title>Choosing Facelets Environment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_2.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Once you select the environment, you can specify the one of three
+ 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 following table lists possible Facelets templates for any JSF
+ project and gives a proper description for each one.</para>
+ <table>
+ <title>Facelets Templates</title>
+ <tgroup cols="2">
+ <colspec colnum="1" colwidth="2*"/>
+ <colspec colnum="2" colwidth="3*"/>
+
+
+ <thead>
+ <row>
+ <entry align="center">
+ <para>Template</para>
+ </entry>
+
+ <entry align="center">
+ <para>Description</para>
+ </entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>
+ <para>
+ <emphasis>
+ <property>FaceletsBlankWithoutLibs</property>
+ </emphasis>
+ </para>
+ </entry>
+
+ <entry>
+ <para>Some servers already provide
+ jsf libs and you take risk
+ of getting conflicting
+ libraries while deploying
+ your project. To avoid such
+ conflicts, use a template
+ without libs if you have a
+ server with its own jsf
+ libraries</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>
+ <emphasis>
+ <property>FaceletsKickStartWithRILibs</property>
+ </emphasis>
+ </para>
+ </entry>
+
+ <entry>
+ <para>a sample application with
+ Facelets that is ready to
+ run</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>
+ <emphasis>
+ <property>FaceletsKickStartWithoutLibs</property>
+ </emphasis>
+ </para>
+ </entry>
+
+ <entry>
+ <para>a sample application without
+ libraries</para>
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+ </section>
+ <section>
+ <title>Facelets components</title>
+
+ <para>The <link linkend="palette">JBoss Tools Palette</link> comes with the
+ Facelets components ready to use. A useful tip appears when you
+ hover the mouse cursor over the tag, the tip includes a detailed
+ description of the tag component, the syntax and available
+ attributes.</para>
+
+ <!-- JBoss Developer Studio does not provide templates for MyFaces right out of the box, but you can easily do it
+ yourself with the "Save As Template" feature (available on the File submenu). Just create a small project
+ with MyFaces and Facelets and then save it as a template for future use.
+
+ How can I add Facelets support to an existing project?</para>
+ <para>A: Right-click on the folder of existing project and select <emphasis>JBoss Tools > Add Custom Capabilities.. > Facelets</emphasis>. </para>
+ -->
+ <figure>
+ <title>Facelets Components</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_4.png"
+ scale="85"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>Code assist</title>
+
+ <para>Code assist (Ctrl + Space) for <property>Facelets tags</property> is
+ available when editing <emphasis>
+ <property>.xhtml</property>
+ </emphasis> files.</para>
+
+ <figure>
+ <title>XHTML File Code Assist</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_5.png"
+ scale="70"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>What's more, code assist is also available for <emphasis
+ role="italic">
+ <property>"jsfc"</property>
+ </emphasis> attribute in any HTML tag.</para>
+
+ <figure>
+ <title>Code Assist for Jsfc Attribute</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_6.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>After selecting <emphasis role="italic">
+ <property>"jsfc"</property>
+ </emphasis> you get the code assist for JSF components available on
+ a page.</para>
+
+ <figure>
+ <title>Code Assist for JSF Components</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_7.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>When a component is chosen you will see all available attributes for
+ it.</para>
+
+ <figure>
+ <title>Available Attributes for the Component</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_8.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>Open On feature</title>
+ <para>JBDS provides Eclipse's <emphasis>
+ <property>OpenOn</property>
+ </emphasis> feature for editing Facelets files. Using this 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"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <!-- <para>Additionally, when hovering the mouse cursor over <emphasis role="italic"><property>"Facelets tag"</property></emphasis> attributes, JBoss Developer Studio provides a pop-up help tip:</para>
+ <figure>
+<title>Pop-up Help Tip for Facelets Tag Attributes</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/defaultImage.png"/>
+ </imageobject>
+</mediaobject>
+ </figure>
+
+ -->
+ <!-- <para>See <link linkend="faq_facelets">FAQ</link> concerning Facelets
+ support.</para>
+ -->
+ </section>
+
+ <!--section>
+ <title>Relevant Resources Links</title>
+ <para>Necessary information and support for Facelets find out <ulink
+ url="https://facelets.dev.java.net/"
+ >here</ulink>.</para>
+ </section-->
+ </section>
+
+
+
+
+
+
+
+
+
+
+ <!--section>
+ <title>Relevant Resources Links</title>
+ <para>If you don't familiar with <ulink
+ url="http://java.sun.com/javaee/javaserverfaces/">JSF
+ technology</ulink>, we suggest that you walk through the
+ information on the topic.</para>
+ </section-->
+</chapter>
Added: trunk/jsf/docs/jsf_tools_ref_guide/en/modules/managed_beans.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/modules/managed_beans.xml (rev 0)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/modules/managed_beans.xml 2008-03-26 19:18:57 UTC (rev 7134)
@@ -0,0 +1,232 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="managed_beans">
+ <?dbhtml filename="managed_beans.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JSF Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Managed Beans</title>
+
+ <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>Thus, in this section we will guides you through all this possibilities.</para>
+
+ <section id="CodeGenerationForManagedBeans421">
+
+ <title>Code Generation for Managed Beans</title>
+
+ <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>
+ <note>
+ <title>Note:</title>
+ <para>When you define a new managed bean, make sure that <emphasis>
+ <property>Generate Source Code</property>
+ </emphasis> is checked as shown in the figure
+ below.</para>
+ </note>
+ <figure>
+ <title>New Managed Bean</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_35.png"
+ scale="75"/>
+ </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>
+
+ <itemizedlist>
+ <listitem>
+ <para>click on <emphasis>
+ <property>Managed-Bean-Class</property>
+ </emphasis> link in the editor</para>
+ </listitem>
+ </itemizedlist>
+ <para>or</para>
+ <itemizedlist>
+ <listitem>
+ <para>right click the <emphasis>
+ <property>managed bean</property>
+ </emphasis> and select <emphasis>
+ <property>Open Source</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Opening of Created Managed Bean</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_36.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The generated Java source:</para>
+
+ <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, also
+ includes <emphasis role="italic">
+ <property>"getter"</property>
+ </emphasis> and <emphasis role="italic">
+ <property>"setter"</property>
+ </emphasis> methods. Right click on the bean and select <emphasis>
+ <property>New > Property</property>
+ </emphasis>. You will see <property>Add Property</property>
+ dialog.</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>When the form is open 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"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Thus, we've discussed everything which comes to
+ creating a new Managed Bean. Further we will show you how to
+ add an existing Bean into a JSF configuration file.</para>
+ </section>
+ <section id="AddExistingJavaBeansToAJSFConfigurationFile74332">
+
+ <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 the <emphasis>
+ <property>Browse...</property>
+ </emphasis> button 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>
+
+ <figure>
+ <title>Selection of Bean's Properties.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_43.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>If you don't want to add any, just click <emphasis>
+ <property>Finish</property>. </emphasis></para>
+ </section>
+ <para>Above-listed steps have demonstrated specifying an existing Bean in
+ the JSF configuration file, i.e. <emphasis>
+ <property>faces-config.xml</property>. </emphasis> In the
+ next section you'll know how to organize and register a
+ custom Converter to specify your own converting rules.</para>
+
+</chapter>
Added: trunk/jsf/docs/jsf_tools_ref_guide/en/modules/projects.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/modules/projects.xml (rev 0)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/modules/projects.xml 2008-03-26 19:18:57 UTC (rev 7134)
@@ -0,0 +1,472 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="projects">
+ <?dbhtml filename="projects.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JSF Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Projects</title>
+ <para>To take an advantage of JSF support in <property>JBoss Developer
+ Studio</property> firstly you should perform one of the next
+ steps:</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>In this section we're going to stop on each of them in
+ detail.</para>
+
+ <section id="new_jsf_project">
+
+ <title>Creating a New JSF Project</title>
+
+ <para>If you want your project has already contained all JSF
+ libraries, tag libraries and JSF configuration file, just
+ organize a new brand JSF project. <property>JBoss Developer
+ Studio</property> allows to do this easily with the
+ help of the special wizard. To get it, 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 the next form you'll be prompted to enter
+ <property>Project Name</property> and select a
+ location for the project or just leave a default path.</para>
+ <para>Here, JSF Version also 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><property>JBoss Developer Studio</property> comes with a
+ number of predefined project templates that are flexible and
+ easily customizable. Thus you can pick a different template
+ on which the project should be based to. Almost all
+ templates come in two variations: with jsf libraries and
+ without ones.</para>
+ <figure>
+ <title>Choosing JSF Templates</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_12.png "
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The table below provides description for each possible JSF
+ template.</para>
+ <table>
+ <title>JSF Project Templates</title>
+ <tgroup cols="2">
+ <colspec colnum="1" colwidth="1*"/>
+ <colspec colnum="2" colwidth="3*"/>
+
+
+ <thead>
+ <row>
+ <entry align="center">
+ <para>Template</para>
+ </entry>
+
+ <entry align="center">
+ <para>Description</para>
+ </entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>
+ <para>
+ <emphasis>
+ <property>JSFBlankWithLibs</property>
+ </emphasis>
+ </para>
+ </entry>
+
+ <entry>
+ <para>This template will
+ create a standard
+ Web project
+ structure with all
+ JSF
+ capabilities</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>
+ <emphasis>
+ <property>JSFKickStartWithLibs</property>
+ </emphasis>
+ </para>
+ </entry>
+
+ <entry>
+ <para>This template will
+ create a standard
+ Web project
+ structure but will
+ also include a
+ sample application
+ that is ready to
+ run</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>
+ <emphasis>
+ <property>JSFKickStartWithoutLibs</property>
+ </emphasis>
+ </para>
+ </entry>
+
+ <entry>
+ <para>Some servers already
+ provide jsf libs and
+ you take risk of
+ getting conflicting
+ libraries while
+ deploying your
+ project. To avoid
+ such conflicts, use
+ a template without
+ libs if you have a
+ server with its own
+ jsf libraries</para>
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+
+ <!-- <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>
+ -->
+
+ <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>The <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>Target Server</property>
+ </emphasis> allows you specifying whether to deploy the
+ application. The Target Server corresponds to the Runtime
+ value selected above. 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 appeared 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 <emphasis>
+ <property>faces-config.xml</property>
+ </emphasis> and start working on your application.
+ <property>JBDS</property> provides a lot of features
+ to develop JSF applications. We will describe the features
+ further.</para>
+ </section>
+
+ <section id="ImportingExsJSFProjWithAnyStr74447">
+
+ <title>Importing Existing JSF Projects with Any Structure</title>
+
+ <para>For detailed information on migration projects to JBoss
+ Developer Studio see <ulink
+ url="../../../Exadel-migration/en/html_single/index.html"
+ >Migration Guide</ulink>. </para>
+
+ </section>
+ <section id="add_jsf_capability">
+
+ <title>Adding JSF Capability to Any Existing Eclipse Project</title>
+
+ <para>With <property>JBoss Developer Studio</property> it's
+ also possible to add <property>JSF capability</property>
+ (JSF libraries, tag libraries) to any existing Eclipse
+ project in your workspace. After that you'll be
+ able to make use of such <property>JBoss Developer
+ Studio</property> editors 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 ask you to show the <emphasis>
+ <property>web.xml</property>
+ </emphasis> 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 Libraries</property>
+ </emphasis> for <property>JBoss Developer Studio</property>
+ to add all required JSF related libraries to this project.</para>
+
+ <para>The <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>Target Server</property>
+ </emphasis> allows you to specify whether to deploy the
+ application. The Target Server corresponds to the Runtime
+ value selected above. 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: <emphasis>
+ <property>jsf-api.jar</property>
+ </emphasis> and <emphasis>
+ <property>jsf-impl.jar</property>
+ </emphasis>.</para>
+ <note>
+ <title>Note:</title>
+ <para>Some application servers provide their own jsf
+ implementation libraries. So, to avoid conflicts you
+ should not add jsf libraries while adding jsf
+ capabilities.</para>
+ </note>
+ <para>You are now ready to work with JSF by creating a new JSF
+ configuration file:</para>
+
+
+ <figure>
+ <title>Creating a New JSF Configuration File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_19.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Once the file have been created, it should be open in a
+ special <link
+ linkend="GraphicalEditorAndViewingForJSFConfigurationFiles76331"
+ >Faces Config Editor</link>.</para>
+ </section>
+ <section id="AddingYourOwnProjectTemplates853">
+
+ <title>Adding Your Own Project Templates</title>
+ <para>Template is a set of files that serve as a basis to facilitate
+ the creation of a new project. Project templates provide
+ content and structure for a project.</para>
+ <para><property>JBoss Developer Studio</property> 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 and consider the
+ process of creating a template from your existing JSF
+ project.</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></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>
+
+ </itemizedlist>
+ <figure>
+ <title>Define Template Properties</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_20_1.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <itemizedlist>
+ <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>
+ </itemizedlist>
+ <figure>
+ <title>Define Template Properties</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_20_2.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>At this point, unless you want to designate
+ some extra files as having Velocity template
+ coding inside them, you should click <emphasis>
+ <property>Finish</property>
+ </emphasis>.</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
+ template.</para>
+ </section>
+
+ <para>At this point, you have a fully configured project and now you can
+ bring some new logic to it starting from JSF configuration
+ file.</para>
+</chapter>
\ No newline at end of file
Added: trunk/jsf/docs/jsf_tools_ref_guide/en/modules/referenced_beans.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/modules/referenced_beans.xml (rev 0)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/modules/referenced_beans.xml 2008-03-26 19:18:57 UTC (rev 7134)
@@ -0,0 +1,122 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="referenced_beans">
+ <?dbhtml filename="referenced_beans"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JSF Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Create and Register Referenced Beans</title>
+
+ <para>Creation of Referenced Beans is similar to creation of Custom
+ Validator.</para>
+
+ <itemizedlist>
+ <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>
+ </itemizedlist>
+ <figure>
+ <title>Referenced Beans in Faces Config Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_54.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <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 <emphasis>
+ <property>Referenced-Bean-Class</property>
+ </emphasis> by using <emphasis>
+ <property>Browse</property>
+ </emphasis> button.</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Add Referenced Bean</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_55.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>In the Referenced Bean section you should see your <emphasis>
+ <property>Referenced-Bean-Name</property>
+ </emphasis> and
+ <emphasis><property>Referenced-Bean-Class</property>.</emphasis>
+ Click on the link to open the Java creation
+ wizard.</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Create Referenced Bean Class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_56.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Java class will be created automatically. Leave
+ everything without changes and click <emphasis>
+ <property>Finish</property>.
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>New Java Class Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_57.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <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
+ in the Java editor.</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Referenced Bean Class Editing</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/jsf_support/jsf_support_58.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+</chapter>
\ No newline at end of file
18 years
- 1
- 0
JBoss Tools SVN: r7133 - trunk/jsf/docs/userguide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2008-03-26 15:10:17 -0400 (Wed, 26 Mar 2008)
New Revision: 7133
Modified:
trunk/jsf/docs/userguide/en/modules/palette.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-232 corrections in content (del the draft remarks)
Modified: trunk/jsf/docs/userguide/en/modules/palette.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/palette.xml 2008-03-26 18:55:20 UTC (rev 7132)
+++ trunk/jsf/docs/userguide/en/modules/palette.xml 2008-03-26 19:10:17 UTC (rev 7133)
@@ -186,7 +186,7 @@
</emphasis> from the pop-up menu that appears after you right-click on a
folder.</para>
<figure>
- <title>Creating Icons (retake screen with IMPORT ICON!!!)</title>
+ <title>Creating Icons</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/palette/palette_18.png"/>
@@ -392,9 +392,9 @@
<para>If libraries are not displayed in the palette, check whether they are selected.
Click the plus sign to expand the libraries of the group and make sure that a tick
is put next to the wanted libraries.</para>
- <para>(When you deactivate the group(s), the JBoss Palette remembers your last chose.
+ <!-- <para>(When you deactivate the group(s), the JBoss Palette remembers your last chose.
The libraries… )</para>
-
+ -->
<itemizedlist>
<listitem>
<para>Click <emphasis><property>OK</property>.</emphasis> The new groups will
18 years
- 1
- 0
JBoss Tools SVN: r7132 - in trunk/jsf/docs/userguide/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2008-03-26 14:55:20 -0400 (Wed, 26 Mar 2008)
New Revision: 7132
Modified:
trunk/jsf/docs/userguide/en/images/palette/palette_18.png
trunk/jsf/docs/userguide/en/images/palette/palette_7.png
trunk/jsf/docs/userguide/en/modules/palette.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-232 the structure of the chapter has been changed (the content was organized and added ) + new relevant links and screens
Modified: trunk/jsf/docs/userguide/en/images/palette/palette_18.png
===================================================================
(Binary files differ)
Modified: trunk/jsf/docs/userguide/en/images/palette/palette_7.png
===================================================================
(Binary files differ)
Modified: trunk/jsf/docs/userguide/en/modules/palette.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/palette.xml 2008-03-26 18:39:31 UTC (rev 7131)
+++ trunk/jsf/docs/userguide/en/modules/palette.xml 2008-03-26 18:55:20 UTC (rev 7132)
@@ -1,6 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<chapter id="palette" xreflabel="palette">
<?dbhtml filename="palette.html"?>
+
<chapterinfo>
<keywordset>
<keyword>Jboss Tools palette</keyword>
@@ -9,6 +10,9 @@
</keywordset>
</chapterinfo>
<title>JBoss Tools Palette</title>
+ <para>This chapter will introdus you to the functionality provide by <property>JBoss Tools
+ Palette</property>. Palette allowes you to quickly and easily creat your JSP or JSF
+ page. Now you can do it more faster without additional knowlege.</para>
<para>The <property>JBoss Tools Palette</property> allows you to:</para>
<itemizedlist>
@@ -20,260 +24,74 @@
</listitem>
</itemizedlist>
- <para>The <property>JBoss Tools Palette</property> contains a developer's project tag libraries and provides possibility to add any tag
- libraries to it. Or you can choose a necessary one from the list of already existent tag
- libraries:</para>
+ <para>The JBoss Tools Palette contains a developer's project tag libraries and provides
+ possibility to add any tag libraries to it. Also you can choose a necessary one from the
+ list of already existent tag libraries:</para>
<itemizedlist>
- <listitem><para>HTML</para></listitem>
- <listitem><para>JBoss</para></listitem>
- <listitem><para>JSF</para></listitem>
- <listitem><para>JSTL</para></listitem>
- <listitem><para>MyFaces</para></listitem>
- <listitem><para>Oracle ADF Faces</para></listitem>
- <listitem><para>Struts</para></listitem>
- <listitem><para>XHTML</para></listitem>
+ <listitem>
+ <para>HTML</para>
+ </listitem>
+ <listitem>
+ <para>JBoss</para>
+ </listitem>
+ <listitem>
+ <para>JSF</para>
+ </listitem>
+ <listitem>
+ <para>JSTL</para>
+ </listitem>
+ <listitem>
+ <para>MyFaces</para>
+ </listitem>
+ <listitem>
+ <para>Oracle ADF Faces</para>
+ </listitem>
+ <listitem>
+ <para>Struts</para>
+ </listitem>
+ <listitem>
+ <para>XHTML</para>
+ </listitem>
</itemizedlist>
-
+
<figure>
- <title>Pallete Editor</title>
+ <title>JBoss Tools Palette</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/palette/palette_14.png"/>
+ <imagedata fileref="images/palette/palette_1.png"/>
</imageobject>
</mediaobject>
</figure>
-
- <section id="UsingThePalette(IncludingOne-ClickTagInsertion)">
- <?dbhtml filename="UsingThePalette(IncludingOne-ClickTagInsertion).html"?>
- <title>Using the Palette</title>
-
- <section id="RedHatPalette">
- <?dbhtml filename="JBossToolsPalette.html"?>
- <title>JBoss Tools Palette</title>
- <para> Palette Editor window is divided into multiple groups, and every group consists of several subgroups. For example, JSF consists of Core, Facelets, HTML: </para>
- <figure>
- <title>Subgroups of JSF group</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_24.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>By default the Palette is represented in Web Development Perspective with four
- groups. If you can't see it, select <emphasis>
- <property>Window > Show View Other... > JBoos Tools Web >
- JBoss Tools Palette</property>
- </emphasis> from the menu bar.</para>
-
- <figure>
- <title>JBoss Tools Palette</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>By using <property>Show/Hide</property> button you can add any predefined group of
- tag libraries. It's also possible to create your own group. </para>
+ <para>By default the Palette is represented in Web Development Perspective with four groups. If
+ you can't see it, select <emphasis>
+ <property>Window > Show View Other... > JBoos Tools Web > JBoss
+ Tools Palette</property>
+ </emphasis> from the menu bar.</para>
- </section>
-
- <section id="InsertingTagsIntoAJSPFile">
- <?dbhtml filename="InsertingTagsIntoAJSPFile.html"?>
- <title>Inserting Tags into a JSP File</title>
-
- <para>A new tag can be added into any text file including jsp, htm, html and xhtml.</para>
- <para>It's very simple to do this. Open your JSP file and place the cursor in a place where you'd
- like to add a tag and then click that tag in the palette.
-
- In the <property>Insert Tag</property> window, that will appeared after that action, you can set the
- <emphasis><property>value</property></emphasis> of general and advanced <emphasis><property>attributes</property></emphasis> of the tag that you chose.</para>
-
- <figure>
- <title>Inserting Tag</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_25.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>In the example below, the <emphasis><property>commandButton</property></emphasis> tag has been inserted.</para>
-
- <figure>
- <title>Inserting Tag</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_2.png" scale="80"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <note><title>Note:</title>
- <para>if you place the cursor over
- any tag, a balloon tip is shown with all the <emphasis role="italic">
- <property>"tag"</property>
- </emphasis> attributes.</para>
- </note>
-
- <para>The cursor position after adding a tag into a file is specified by
- "|" symbol in the tag template on the right in the Palette Editor window. </para>
- <figure>
- <title>Palette Editor</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_15.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para> Above you can see where the cursor position for HTML/Form/input is set. Thus, after
- adding this tag into your file the cursor will be in the attribute
- "type". Then, you can straight use the combination of buttons <property>Ctrl
- + Space</property> to inquire about a prompting. </para>
-
- <figure>
- <title>Cursor position</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_16.png" scale="50"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- </section>
-
- <section id="AddingCustomJSFTagsToTheRedHatPalette7433">
- <?dbhtml filename="AddingCustomJSFTagsToTheJBossToolsPalette.html"?>
- <title>Adding Custom JSF Tags to the JBoss Tools Palette</title>
-
- <para>There are two ways to add any custom or 3rd party tag library to the
- <property>JBoss Tools Palette</property>:</para>
- <itemizedlist>
- <listitem>
- <para>Drag-and-drop from the Web Projects view</para>
- </listitem>
- <listitem>
- <para>The Import button on the JBoss Tools Palette</para>
- </listitem>
- </itemizedlist>
-
- <para>Before you can add your custom component library, you need to make sure it is
- included in your project. Either place the <emphasis role="italic">
- <property>".tld"</property>
- </emphasis> file or the <emphasis role="italic">
- <property>".jar"</property>
- </emphasis> that includes your tag library under the lib folder in your project.
- </para>
-
- <section id="Drag_and_Drop65332">
- <?dbhtml filename="DragAndDrop.html"?>
- <title>Drag-and-Drop</title>
- <para>Switch to the Web Projects view and expand the Tag Libraries folder. If the view
- not active, select <emphasis>
- <property>Window > Show View > Web Projects</property>
- </emphasis> from the menu bar.</para>
-
- <figure>
- <title>Web Projects View</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_3.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Also make sure that the JBoss Tools Palette is open. Select the tag library that
- you want to add and simply drag-and-drop it on to the JBoss Tools Palette.</para>
-
- <para>You will see the following dialog window. As you can see JBoss Developer Studio
- takes care of all the details. You just need to set the Group name to which you wish to place
- this tag library. You can either add this tag library to an existing Group or just
- create a new one.</para>
-
- <figure>
- <title>Import Tags From TLD File Form</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_4.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Once you are finished, you will see the new tag library added to the JBoss Tools
- Palette.</para>
-
- <figure>
- <title>JBoss Tools Palette with New Tag Library</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_5.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section id="ImportButton521">
- <?dbhtml filename="ImportButton.html"?>
- <title>Import Button</title>
- <para>The same you can do with <emphasis><property>Import</property></emphasis> button.
- You can see this button at the top right side of the JBoss Tools Palette.</para>
-
- <figure>
- <title>Import Button</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_6.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>By clicking on the <emphasis><property>Import button</property></emphasis> you will see the Import Tag window a similar like in the Drag-and-Drop method.
- On this Import Tag form you can select <emphasis><property>Browse...</property></emphasis> to locate the tag library that you want to add.
- Also you need to set the Group name to which you'd like to add your tag library. And like in the previous method you can add it to an existing Group or create a new one.</para>
-
- <figure>
- <title>Import Tags From TLD File Form</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_7.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Now select the TLD file you want to be added:</para>
- <figure>
- <title>Select TLD File</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_8.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- </section>
-
- </section>
-
<section id="PaletteOptions">
<?dbhtml filename="PaletteOptions.html"?>
<title>Palette Options</title>
+ <para>To case your work, you can configure the Palette for your own, by selecting the
+ corresponding icon on the Palette toolbar.</para>
+ <para>There is a possibility to configure the JBoss Tools Palette:</para>
- <para>There is possibility to configure the <property>JBoss Tools Palette</property>:</para>
-
<itemizedlist>
<listitem>
- <para> to edit the palette content by adding, removing or changing the palette
- elements</para>
+ <para> to <property>edit the palette</property> content by adding, removing or
+ changing the palette elements</para>
</listitem>
+
<listitem>
- <para> to show/hide groups, subgroups</para>
+ <para> to <property>show/hide groups</property>, subgroups</para>
</listitem>
+
<listitem>
- <para>to import groups, subgroups</para>
+ <para>to <property>import groups</property>, subgroups</para>
</listitem>
</itemizedlist>
-
+
<figure>
<title>Palette Buttons</title>
<mediaobject>
@@ -282,87 +100,239 @@
</imageobject>
</mediaobject>
</figure>
+
<section id="PaletteEditor">
<?dbhtml filename="PaletteEditor.html"?>
<title>Palette Editor</title>
- <para>To edit the Pallete view use <property>Edit</property> button. The Palette
- Editor provides following possibilities: <itemizedlist>
+ <para>JBoss Tools Palette contains existing libraries of tags, thus the
+ <property>Palette editor</property> is intended to work with them or create your
+ new one, as well.</para>
+ <para>To open the editor, click right mouse button on the <emphasis>
+ <property>Palette Editor</property>
+ </emphasis> icon: <itemizedlist>
+
+ <figure>
+ <title>Palette Editor Icon</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The window has two parts. There is a reflected grouped list of components
+ on the left side of the palette editor. Each group is divided into multiple
+ groups, every of which is a tag library. The right side of the palette
+ editor is an editing window where it's possible to change values of
+ group, tag library attributes that you've chosen on the left part
+ of the window. It can also be made by using <emphasis>
+ <property>Edit…</property>
+ </emphasis> button.</para>
+ <literallayout/>
+ <para> For example, <property>JSF</property> group consists of
+ <property>Core</property>, <property>Facelets</property>,
+ <property>HTML</property> tag libraries and the attributes as
+ <property>name</property>, <property>description</property> and
+ <property>hidden</property> which are available for editing: </para>
+
+ <figure>
+ <title>Tag Libraries of the JSF Group</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_24.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The Palette Editor provides the following possibilities when working with
+ existing tags or icons:</para>
<listitem>
- <para>to work with set of icons</para>
+ <para>to work with a set of icons</para>
+ <para><emphasis>
+ <property>Icons</property>
+ </emphasis> is the root folder for the icon sets. The first step is
+ creating the icon set. Right click on the <emphasis>
+ <property>Icons</property>
+ </emphasis> folder and select <emphasis>
+ <property>Create > Create Set...</property>
+ </emphasis></para>
+ <para>Set the value of the name in the <emphasis>
+ <property>Add Icons</property>
+ </emphasis> window and click <emphasis>
+ <property>Finish</property>
+ </emphasis> button. A new element will appear in the list.</para>
<figure>
- <title>Creating a set of icons</title>
+ <title>Creating a Set of Icons</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/palette/palette_17.png"/>
</imageobject>
</mediaobject>
</figure>
+ <para>Also you can delete the set. Right click on the set of icons that you
+ wish to remove and chose the <emphasis>
+ <property>Delete Set</property>
+ </emphasis> option from the pop-up menu or click the <emphasis>
+ <property>Delet</property>
+ </emphasis> keyboard button.</para>
</listitem>
-
-
+
<listitem>
<para>to edit icons in the chosen set</para>
+ <para>When the set of icons is created, new icons can be imported to it.
+ Choose the required set and select the option <emphasis>
+ <property>Create > Import Icon... </property>
+ </emphasis> from the pop-up menu that appears after you right-click on a
+ folder.</para>
<figure>
- <title>Editing icons</title>
+ <title>Creating Icons (retake screen with IMPORT ICON!!!)</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/palette/palette_18.png"/>
</imageobject>
</mediaobject>
</figure>
+ <para>Set the name of the icon and the path and click <emphasis>
+ <property>Finish</property>
+ </emphasis> button.</para>
</listitem>
-
+
<listitem>
- <para>to edit a group</para>
+ <para>to work with a group of tag libraries</para>
+ <para>The first step in work with the editor is creating a group of
+ libraries. It's very easy to do, right mouse button click on
+ the <emphasis>
+ <property>Palette</property>
+ </emphasis> folder and select <emphasis>
+ <property>Create > Create Group…</property>
+ </emphasis></para>
+ <para>Set a name of a group in the <property>Create Group</property> window
+ and click <emphasis>
+ <property>OK</property>
+ </emphasis> button. A new element will appear at the end of the list.</para>
<figure>
- <title>Editing a group</title>
+ <title>Creating a Group of Tag Libraries</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/palette/palette_19.png"/>
</imageobject>
</mediaobject>
</figure>
+ <para>You are allowed to edit or delete a group, as well. If you'd
+ like to change attributes of a group, use the right editing window of
+ the palette editor or the <emphasis>
+ <property>Edit...</property>
+ </emphasis> option, like it was mentioned before. In order to remove the
+ group, right click on the group that you wish to remove and chose the <emphasis>
+ <property>Delete</property>
+ </emphasis> option or click the <emphasis>
+ <property>Delete</property>
+ </emphasis> keyboard button.</para>
+ <important>
+ <title>Important:</title>
+ <para>The removal option is enabled only for custom folders.</para>
+ </important>
</listitem>
-
+
<listitem>
- <para>to edit a subgroup</para>
+ <para>to work with a tag library</para>
+
+ <para>The group maintains a list of tag libraries. If you'd like to
+ create your own library, click right mouse button on the group and
+ choose <emphasis>
+ <property>Create Group…</property>
+ </emphasis> option.</para>
<figure>
- <title>Editing a subgroup</title>
+ <title>Creating a tag library</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/palette/palette_20.png"/>
</imageobject>
</mediaobject>
</figure>
+ <para>After setting the attribute name and the path of the icon, click <emphasis>
+ <property>Ok</property>
+ </emphasis> button.</para>
+ <note>
+ <title>Note:</title>
+ <para>If you do not choose an icon the default one will be
+ assigned.</para>
+ </note>
+ <para>You are allowed to edit or delete the tag library, as well. If
+ you'd like to change attributes of the library or choose
+ another icon, use the right editing window of the palette editor or the <emphasis>
+ <property>Edit...</property>
+ </emphasis> option. In order to remove the tag library, right click on
+ the library that you wish to remove and chose the <emphasis>
+ <property>Delete</property>
+ </emphasis> option or click the <emphasis>
+ <property>Delete</property>
+ </emphasis> keyboard button.</para>
+ <important>
+ <title>Important:</title>
+ <para>The removal option is enabled only for custom tag
+ libraries.</para>
+ </important>
</listitem>
-
+
<listitem>
- <para>to edit a subgroup content</para>
+ <para>to work with a tag element</para>
+ <para>When the library folder is created, new tags can be added to it.
+ Choose the required library and select the option <emphasis>
+ <property>Create > Create Macro…</property>
+ </emphasis> from the pop-up menu that appears after you right-click on a
+ folder.</para>
<figure>
- <title>Editing a subgroup content</title>
+ <title>Creating a tag element</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/palette/palette_21.png"/>
</imageobject>
</mediaobject>
</figure>
- </listitem>
-
- <listitem>
- <para>to edit the Palette element or macro</para>
- <figure>
- <title>Editing the Palette element </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/palette/palette_22.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <para>In the <property>Add Palette Macro</property> window, you can
+ configure the tag element. Attribute <emphasis>
+ <property>Name</property>
+ </emphasis> is mandatory to fill and it will be the name of the tag
+ element. Other settings are optional. You can choose the icon and set
+ the <emphasis>
+ <property>Start Text</property>
+ </emphasis> and the <emphasis>
+ <property>End Text</property>
+ </emphasis> for your tag element. If your tag text is too long, use the <emphasis>
+ <property>Change...</property>
+ </emphasis> button to see it all. After all the attributes are set,
+ click <emphasis>
+ <property>Finish</property>
+ </emphasis> button.</para>
+ <note>
+ <title>Note:</title>
+ <para>If you do not choose the icon it will be assigned by
+ default.</para>
+ </note>
+ <para>You are allowed to edit or delete the tag . If you'd like to
+ change the attributes of the tag or choose another icon for it, use the
+ right editing window of the palette editor or the <emphasis>
+ <property>Edit...</property>
+ </emphasis> option from the pop-up menu. In order to remove the tag,
+ right click on the tag that you wish to remove and chose the <emphasis>
+ <property>Delete</property>
+ </emphasis> option or click the <emphasis>
+ <property>Delete</property>
+ </emphasis> keyboard button.</para>
+ <important>
+ <title>Important:</title>
+ <para>The removal option is enabled only for custom tags. JBoss Palette
+ tags can not be removed but can be modified.</para>
+ </important>
+
<para>Parameters of the Palette element are put into the table on the right.
Table cells are provided with editors and modal dialogue windows for
- choosing necessary icons. For 'start text' and 'end text'(or macro) there is
- possibility to control the cursor position by using "|" symbol. </para>
+ choosing necessary icons. For 'start text' and
+ 'end text'(or macro) there is a possibility to control
+ the cursor position by using "|" symbol. </para>
+
<figure>
<title>Parameters of the Palette element</title>
<mediaobject>
@@ -372,8 +342,7 @@
</mediaobject>
</figure>
</listitem>
-
-
+
</itemizedlist>
</para>
</section>
@@ -386,13 +355,15 @@
<property>Show/Hide</property>
</emphasis> is a very useful feature that allows you to control the number of tag
groups that are shown on the palette.</para>
+
<itemizedlist>
<listitem>
<para>Click <emphasis>
<property>Show/Hide</property>
- </emphasis> button</para>
+ </emphasis> button, at the top right side of the JBoss Tools Palette.</para>
</listitem>
</itemizedlist>
+
<figure>
<title>Show/Hide Button</title>
<mediaobject>
@@ -404,10 +375,11 @@
<itemizedlist>
<listitem>
- <para>In the dialog Show/Hide Drawers check the groups you want to be shown on
- the palette:</para>
+ <para>In the dialog Show/Hide Drawers check the groups the libraries of which
+ you want to be shown on the palette:</para>
</listitem>
</itemizedlist>
+
<figure>
<title>Show/Hide Drawers</title>
<mediaobject>
@@ -416,12 +388,20 @@
</imageobject>
</mediaobject>
</figure>
+
+ <para>If libraries are not displayed in the palette, check whether they are selected.
+ Click the plus sign to expand the libraries of the group and make sure that a tick
+ is put next to the wanted libraries.</para>
+ <para>(When you deactivate the group(s), the JBoss Palette remembers your last chose.
+ The libraries… )</para>
+
<itemizedlist>
<listitem>
- <para>Click <emphasis>
- <property>OK</property>.</emphasis> The new groups will now be displayed on the palette:</para>
+ <para>Click <emphasis><property>OK</property>.</emphasis> The new groups will
+ now be shown on the palette:</para>
</listitem>
</itemizedlist>
+
<figure>
<title>New Added Groups</title>
<mediaobject>
@@ -430,32 +410,229 @@
</imageobject>
</mediaobject>
</figure>
+
+ <para>The name of the elements is compound. The first part is the group’s name and the
+ second is the library’s name.</para>
</section>
+
<section id="Import">
<?dbhtml filename="Import.html"?>
<title>Import</title>
- <para>The Import button lets you add a custom or 3rd party tag library to
- JBoss Tools Palette. Find out more information on how to add the tags see the <link linkend="ImportButton521">Adding Custom JSF Tags</link> section.
+ <para>The Import button lets you add a custom or 3rd party tag library to JBoss Tools
+ Palette. Find out more information on how to add particular tags see the <link
+ linkend="ImportButton521">Adding Custom JSF Tags</link> section.
<!--<link linkend="CreatingAndWorkingCustomCapability">Learn how to import</link>. --></para>
</section>
</section>
+
+ <section id="UsingThePalette(IncludingOne-ClickTagInsertion)">
+ <?dbhtml filename="UsingThePalette(IncludingOne-ClickTagInsertion).html"?>
+ <title>Using the Palette</title>
+
+
+
+ <section id="InsertingTagsIntoAJSPFile">
+ <?dbhtml filename="InsertingTagsIntoAJSPFile.html"?>
+ <title>Inserting Tags into a JSP File</title>
+
+ <para>A new tag can be added into any text file including jsp, htm, html and xhtml.</para>
+ <para>It's very simple to do this. Open your JSP file and place the cursor in a
+ place where you'd like to add a tag and then click that tag in the palette.
+ In the <property>Insert Tag</property> window, that appears, you can set the value of<emphasis>
+ <property>general</property>
+ </emphasis> and <emphasis>
+ <property>advanced</property>
+ </emphasis> attributes of the tag that you chose.</para>
+
+ <figure>
+ <title>Inserting Tag</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_25.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In the example below, the <emphasis>
+ <property>commandButton</property>
+ </emphasis> tag has been inserted.</para>
+
+ <figure>
+ <title>Inserting Tag</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_2.png" scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <tip>
+ <title>Tipe:</title>
+ <para>if you place the cursor over any tag, a balloon hint is shown with all the
+ <emphasis role="italic">
+ <property>"tag"</property>
+ </emphasis> attributes.</para>
+ </tip>
+
+ <para>The cursor position after adding a tag into a file is specified by
+ "|" symbol in the tag template on the right in the Palette Editor
+ window. </para>
+ <figure>
+ <title>Palette Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_15.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> Above you can see where the cursor position for HTML/Form/input is set. Thus,
+ after adding this tag into your file the cursor will be in the attribute
+ "type". Then, you can straight use the combination of buttons
+ <property>Ctrl + Space</property> to inquire about a prompting. </para>
+
+ <figure>
+ <title>Cursor position</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_16.png" scale="50"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+ <section id="AddingCustomJSFTagsToTheRedHatPalette7433">
+ <?dbhtml filename="AddingCustomJSFTagsToTheJBossToolsPalette.html"?>
+ <title>Adding Custom JSF Tags to the JBoss Tools Palette</title>
+
+ <para>There are two ways to add any custom or 3rd party tag library to the
+ <property>JBoss Tools Palette</property>:</para>
+ <itemizedlist>
+ <listitem>
+ <para>Drag-and-drop from the Web Projects view</para>
+ </listitem>
+ <listitem>
+ <para>The Import button on the JBoss Tools Palette</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Before you can add your custom component library, you need to make sure it is
+ included in your project. Either place the <emphasis role="italic">
+ <property>".tld"</property>
+ </emphasis> file or the <emphasis role="italic">
+ <property>".jar"</property>
+ </emphasis> that includes your tag library under the lib folder in your project. </para>
+
+ <section id="Drag_and_Drop65332">
+ <?dbhtml filename="DragAndDrop.html"?>
+ <title>Drag-and-Drop</title>
+ <para>Switch to the Web Projects view and expand the Tag Libraries folder. If the
+ view is not active, select <emphasis>
+ <property>Window > Show View > Web Projects</property>
+ </emphasis> from the menu bar.</para>
+
+ <figure>
+ <title>Web Projects View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Also make sure that the JBoss Tools Palette is open. Select the tag library
+ that you want to add and simply drag-and-drop it on to the JBoss Tools Palette.</para>
+
+ <para>You will see the following dialog window. As you can see JBoss Developer
+ Studio takes care of all the details. Chosen TLD file, name and prefix of the
+ library and Library URL are detected, thus just need to set the Group name to
+ which you wish to place this tag library. You can either add this tag library to
+ an existing Group or just create a new one.</para>
+
+ <figure>
+ <title>Import Tags From TLD File Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Once you are finished, you will see the new tag library added to the JBoss
+ Tools Palette.</para>
+
+ <figure>
+ <title>JBoss Tools Palette with New Tag Library</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="ImportButton521">
+ <?dbhtml filename="ImportButton.html"?>
+ <title>Import Button</title>
+ <para>The same you can do with <emphasis>
+ <property>Import</property>
+ </emphasis> button. You can see this button at the top right side of the JBoss
+ Tools Palette.</para>
+
+ <figure>
+ <title>Import Button</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>By clicking on the <emphasis>
+ <property>Import button</property>
+ </emphasis> you will see the Import Tag window a similar like in the <link
+ linkend="Drag_and_Drop65332"> Drag-and-Drop</link> method. Set the name and
+ prefix of the library and Library URL. Also you need to set the Group name to
+ which you'd like to add your tag library. And like in the previous
+ method you can add it to an existing Group or create a new one. On this Import
+ Tag form you can use <emphasis>
+ <property>Browse...</property>
+ </emphasis>button to locate the tag library that you want to add:</para>
+
+ <figure>
+ <title>Select TLD File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/palette/palette_8.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ </section>
+
+ </section>
+
+
<section id="RichFacesSupport">
<?dbhtml filename="RichFacesSupport.html"?>
<title>Rich Faces Support</title>
-
- <para>JBoss Developer Studio comes with a tight integration with <emphasis><property>Rich Faces</property></emphasis> component framework.
- Rich Faces and Ajax4jsf in JBoss Tools Palette always exist, this palette is not dynamic and is not changed from file to file.
- JBoss Tools Palette supports only the last version of the Rich Faces components.
-
- <note><title>Note:</title>
- <para>If you'd like to know the last version of Rich Faces component framework see <ulink url="http://labs.jboss.com/jbossrichfaces/">JBoss RichFaces</ulink> site.</para>
- </note>
- After installing JBDS Rich Faces components as well as
- <emphasis><property>Ajax4jsf</property></emphasis> ones are already on the <property>JBoss Tools Palette</property>:</para>
-
+
+ <para>JBoss Developer Studio comes with a tight integration with <emphasis>
+ <property>Rich Faces</property>
+ </emphasis> component framework. Rich Faces and Ajax4jsf in JBoss Tools Palette always
+ exist, this palette is not dynamic and is not changed from file to file. JBoss Tools
+ Palette supports only the last version of the Rich Faces components. <tip>
+ <title>Tip:</title>
+ <para>If you'd like to know the last version of Rich Faces component
+ framework see <ulink url="http://labs.jboss.com/jbossrichfaces/">JBoss
+ RichFaces</ulink> site.</para>
+ </tip> After installing JBDS Rich Faces components, as well, as <emphasis>
+ <property>Ajax4jsf</property>
+ </emphasis> ones are already on the <property>JBoss Tools Palette</property>:</para>
+
<figure>
<title>Rich Faces Components</title>
<mediaobject>
@@ -464,9 +641,43 @@
</imageobject>
</mediaobject>
</figure>
-
- <!-- <para>Insert tag into JSP file </para>-->
-
+
+ <!-- <para>Insert tag into JSP file </para>-->
+
</section>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
</chapter>
18 years
- 1
- 0
JBoss Tools SVN: r7131 - in trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam: internal/core and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: scabanovich
Date: 2008-03-26 14:39:31 -0400 (Wed, 26 Mar 2008)
New Revision: 7131
Added:
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core/ISeamMessages.java
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamMessages.java
Modified:
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core/SeamCoreBuilder.java
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamProject.java
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamXMLConstants.java
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/scanner/lib/ClassScanner.java
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/scanner/lib/TypeScanner.java
Log:
JBIDE-1258
Added: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core/ISeamMessages.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core/ISeamMessages.java (rev 0)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core/ISeamMessages.java 2008-03-26 18:39:31 UTC (rev 7131)
@@ -0,0 +1,32 @@
+ /*******************************************************************************
+ * Copyright (c) 2007 Red Hat, Inc.
+ * Distributed under license by Red Hat, Inc. All rights reserved.
+ * This program is made available under the terms of the
+ * Eclipse Public License v1.0 which accompanies this distribution,
+ * and is available at http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributor:
+ * Red Hat, Inc. - initial API and implementation
+ ******************************************************************************/
+package org.jboss.tools.seam.core;
+
+import java.util.Collection;
+
+/**
+ * @author Viacheslav Kabanovich
+ */
+public interface ISeamMessages extends ISeamAnnotatedFactory {
+
+ /**
+ *
+ * @return collection of keys in resource bundles
+ */
+ public Collection<String> getPropertyNames();
+
+ /**
+ *
+ * @return collection of properties declared in resource bundles
+ */
+ public Collection<ISeamProperty> getProperties();
+
+}
Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core/SeamCoreBuilder.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core/SeamCoreBuilder.java 2008-03-26 16:31:16 UTC (rev 7130)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core/SeamCoreBuilder.java 2008-03-26 18:39:31 UTC (rev 7131)
@@ -12,6 +12,7 @@
import java.io.IOException;
import java.util.Map;
+import java.util.Set;
import org.eclipse.core.resources.IProject;
import org.eclipse.core.resources.IResource;
@@ -22,6 +23,7 @@
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.osgi.util.NLS;
import org.jboss.tools.common.model.util.TypeInfoCollector;
+import org.jboss.tools.seam.internal.core.SeamMessages;
import org.jboss.tools.seam.internal.core.SeamProject;
import org.jboss.tools.seam.internal.core.SeamResourceVisitor;
import org.jboss.tools.seam.internal.core.scanner.IFileScanner;
@@ -116,10 +118,13 @@
} catch (IOException e) {
SeamCorePlugin.getPluginLog().logError(NLS.bind(SeamCoreMessages.SeamCoreBuilder_1,sp.getProject().getName()), e); //$NON-NLS-1$
}
+
+ sp.postBuild();
} finally {
sp.fireChanges();
- }
+ }
+
return null;
}
Added: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamMessages.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamMessages.java (rev 0)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamMessages.java 2008-03-26 18:39:31 UTC (rev 7131)
@@ -0,0 +1,207 @@
+ /*******************************************************************************
+ * Copyright (c) 2007 Red Hat, Inc.
+ * Distributed under license by Red Hat, Inc. All rights reserved.
+ * This program is made available under the terms of the
+ * Eclipse Public License v1.0 which accompanies this distribution,
+ * and is available at http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributor:
+ * Red Hat, Inc. - initial API and implementation
+ ******************************************************************************/
+package org.jboss.tools.seam.internal.core;
+
+import java.io.File;
+import java.io.FileInputStream;
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Collection;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Properties;
+import java.util.Set;
+
+import org.eclipse.core.resources.IContainer;
+import org.eclipse.core.resources.IResource;
+import org.eclipse.core.runtime.CoreException;
+import org.eclipse.core.runtime.IPath;
+import org.eclipse.core.runtime.Path;
+import org.jboss.tools.common.model.util.EclipseResourceUtil;
+import org.jboss.tools.seam.core.ISeamComponent;
+import org.jboss.tools.seam.core.ISeamElement;
+import org.jboss.tools.seam.core.ISeamMessages;
+import org.jboss.tools.seam.core.ISeamProject;
+import org.jboss.tools.seam.core.ISeamProperty;
+import org.jboss.tools.seam.core.ISeamXmlComponentDeclaration;
+import org.jboss.tools.seam.core.SeamCorePlugin;
+import org.jboss.tools.seam.core.event.Change;
+import org.jboss.tools.seam.core.event.ISeamValue;
+import org.jboss.tools.seam.core.event.ISeamValueList;
+import org.jboss.tools.seam.core.event.ISeamValueString;
+import org.w3c.dom.Element;
+
+/**
+ * @author Viacheslav Kabanovich
+ */
+public class SeamMessages extends SeamAnnotatedFactory implements ISeamMessages {
+ static Map<String, IResource> EMPTY = new HashMap<String, IResource>();
+ Map<String, IResource> resources = EMPTY;
+ Map<String, Long> timestamps = null;
+ Set<String> keys = null;
+
+ public SeamMessages() {}
+
+ public void revalidate() {
+ Map<String, IResource> resources2 = getResources();
+ if(changed(resources2)) {
+ timestamps = new HashMap<String, Long>();
+ for (String n : resources2.keySet()) {
+ IResource r = resources2.get(n);
+ timestamps.put(n, r.getLocalTimeStamp());
+ }
+ resources = resources2;
+ keys = null;
+ }
+ }
+
+ private boolean changed(Map<String, IResource> resources2) {
+ if(resources == resources2) return false;
+ if(resources2.size() != resources.size()) return true;
+ if(timestamps == null) return true;
+ for (String s: resources2.keySet()) {
+ IResource r2 = resources2.get(s);
+ IResource r1 = resources.get(s);
+ if(r1 == null || !r2.equals(r1)) return true;
+ long l1 = r1.getLocalTimeStamp();
+ long l2 = timestamps.get(s);
+ if(l1 != l2) return true;
+ }
+
+ return false;
+ }
+
+ private Map<String, IResource> getResources() {
+ ISeamProject p = getSeamProject();
+ if(p == null) return EMPTY;
+ IResource[] srcs = EclipseResourceUtil.getJavaSourceRoots(p.getProject());
+ ISeamComponent c = p.getComponent("org.jboss.seam.core.resourceLoader");
+ if(c == null) return EMPTY;
+ List<String> names = new ArrayList<String>();
+ Set<ISeamXmlComponentDeclaration> ds = c.getXmlDeclarations();
+ for (ISeamXmlComponentDeclaration d: ds) {
+ ISeamProperty property = d.getProperty("bundleNames");
+ if(property == null) continue;
+ ISeamValue v = property.getValue();
+ if(v == null) continue;
+ if(v instanceof ISeamValueList) {
+ List<ISeamValueString> vs = ((ISeamValueList)v).getValues();
+ for (ISeamValueString s: vs) {
+ if(s.getValue() == null) continue;
+ String b = s.getValue().getValue();
+ names.add(b);
+ }
+ }
+ }
+ if(ds.size() == 0) {
+ names.add("messages");
+ }
+ return getResources(names, srcs);
+ }
+
+ public Collection<ISeamProperty> getProperties() {
+ throw new RuntimeException("Not implemented");
+ }
+
+ public Collection<String> getPropertyNames() {
+ if(keys == null) {
+ keys = new HashSet<String>();
+ for (IResource r: resources.values()) {
+ IPath p = r.getLocation();
+ if(p == null) continue;
+ File f = p.toFile();
+ Properties properties = new Properties();
+ try {
+ properties.load(new FileInputStream(f));
+ } catch (IOException e) {
+ //ignore
+ //TODO keep error for validation
+ }
+ Set<?> s = properties.keySet();
+ for (Object o : s) keys.add((String)o);
+ }
+ }
+ return keys;
+ }
+
+ private Map<String, IResource> getResources(List<String> names, IResource[] srcs) {
+ Map<String, IResource> rs = new HashMap<String, IResource>();
+ for (String name: names) {
+ String n = name.replace('.', '/');
+ int k = n.lastIndexOf('/');
+ String p = k < 0 ? null : n.substring(0, k);
+ if(k >= 0) n = n.substring(k + 1);
+ IResource result = null;
+ for (int j = 0; j < srcs.length && result == null; j++) {
+ result = find(p, n, srcs[j]);
+ }
+ if(result != null) {
+ rs.put(name, result);
+ }
+ }
+ return rs;
+ }
+
+ private IResource find(String pack, String name, IResource src) {
+ if(!(src instanceof IContainer)) return null;
+ IContainer c = (IContainer)src;
+ if(pack != null) {
+ c = c.getFolder(new Path(pack));
+ }
+ if(c == null || !c.exists()) return null;
+ String suffix = ".properties";
+ String name_ = name + "_";
+ String name_p = name + suffix;
+ IResource result = null;
+ try {
+ IResource[] rs = c.members();
+ for (int i = 0; i < rs.length; i++) {
+ String n = rs[i].getName();
+ if(name_p.equals(n)) return rs[i];
+ if(result == null && n.startsWith(name_) && n.endsWith(suffix)) {
+ result = rs[i];
+ }
+ }
+ } catch (CoreException e) {
+ SeamCorePlugin.getPluginLog().logError(e);
+ }
+
+ return result;
+ }
+
+ public SeamMessages clone() throws CloneNotSupportedException {
+ SeamMessages c = (SeamMessages)super.clone();
+ return c;
+ }
+
+ public void loadXML(Element element, Properties context) {
+ super.loadXML(element, context);
+
+ }
+
+ public List<Change> merge(ISeamElement s) {
+ List<Change> changes = super.merge(s);
+ keys = null;
+ return changes;
+ }
+
+ public String getXMLClass() {
+ return SeamXMLConstants.CLS_MESSAGES;
+ }
+
+ public Element toXML(Element parent, Properties context) {
+ Element e = super.toXML(parent, context);
+ return e;
+ }
+
+}
Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamProject.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamProject.java 2008-03-26 16:31:16 UTC (rev 7130)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamProject.java 2008-03-26 18:39:31 UTC (rev 7131)
@@ -623,6 +623,8 @@
d = new SeamXmlFactory();
} else if(SeamXMLConstants.CLS_JAVA.equals(cls)) {
d = new SeamAnnotatedFactory();
+ } else if(SeamXMLConstants.CLS_MESSAGES.equals(cls)) {
+ d = new SeamMessages();
}
if(d == null) continue;
d.loadXML(cs[j], context);
@@ -647,6 +649,7 @@
statistics.add(new Long(t2 - t1));
}
}
+ postBuild();
}
/*
@@ -857,6 +860,10 @@
for (int i = 0; i < factories.length; i++) {
AbstractContextVariable loaded = (AbstractContextVariable)factories[i];
AbstractContextVariable current = (AbstractContextVariable)currentFactories.remove(loaded.getId());
+ if(current != null && current.getClass() != loaded.getClass()) {
+ this.factories.removeFactory((ISeamFactory)current);
+ current = null;
+ }
if(current != null) {
List<Change> changes = current.merge(loaded);
fireChanges(changes);
@@ -1539,6 +1546,17 @@
return map;
}
+ public void postBuild() {
+ Set<ISeamFactory> fff = getFactoriesByName("org.jboss.seam.international.messages");
+ if(fff.size() > 0) {
+ ISeamFactory m = fff.iterator().next();
+ if(m instanceof SeamMessages) {
+ SeamMessages sm = (SeamMessages)m;
+ sm.revalidate();
+ }
+ }
+ }
+
/**
*
* @param builderID
Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamXMLConstants.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamXMLConstants.java 2008-03-26 16:31:16 UTC (rev 7130)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/SeamXMLConstants.java 2008-03-26 18:39:31 UTC (rev 7131)
@@ -23,6 +23,7 @@
public String CLS_PROPERTIES = "properties";
public String CLS_JAVA = "java";
+ public String CLS_MESSAGES = "messages";
public String CLS_MAP = "map";
public String CLS_LIST = "list";
Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/scanner/lib/ClassScanner.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/scanner/lib/ClassScanner.java 2008-03-26 16:31:16 UTC (rev 7130)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/scanner/lib/ClassScanner.java 2008-03-26 18:39:31 UTC (rev 7131)
@@ -30,6 +30,7 @@
import org.jboss.tools.seam.internal.core.BijectedAttribute;
import org.jboss.tools.seam.internal.core.SeamAnnotatedFactory;
import org.jboss.tools.seam.internal.core.SeamJavaComponentDeclaration;
+import org.jboss.tools.seam.internal.core.SeamMessages;
import org.jboss.tools.seam.internal.core.scanner.LoadedDeclarations;
import org.jboss.tools.seam.internal.core.scanner.Util;
import org.jboss.tools.seam.internal.core.scanner.java.SeamAnnotations;
@@ -184,7 +185,10 @@
if(name == null || name.length() == 0) {
name = m.getName();
}
- SeamAnnotatedFactory factory = new SeamAnnotatedFactory();
+ SeamAnnotatedFactory factory =
+ ("org.jboss.seam.international.messages".equals(name) && m.getName().equals("getMessages"))
+ ? new SeamMessages()
+ : new SeamAnnotatedFactory();
factory.setParentDeclaration(component);
ds.getFactories().add(factory);
IMethod im = findIMethod(component, m);
Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/scanner/lib/TypeScanner.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/scanner/lib/TypeScanner.java 2008-03-26 16:31:16 UTC (rev 7130)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/scanner/lib/TypeScanner.java 2008-03-26 18:39:31 UTC (rev 7131)
@@ -42,6 +42,7 @@
import org.jboss.tools.seam.internal.core.SeamAnnotatedFactory;
import org.jboss.tools.seam.internal.core.SeamComponentMethod;
import org.jboss.tools.seam.internal.core.SeamJavaComponentDeclaration;
+import org.jboss.tools.seam.internal.core.SeamMessages;
import org.jboss.tools.seam.internal.core.scanner.LoadedDeclarations;
import org.jboss.tools.seam.internal.core.scanner.Util;
import org.jboss.tools.seam.internal.core.scanner.java.SeamAnnotations;
@@ -205,7 +206,10 @@
if(name == null || name.length() == 0) {
name = new String(m.getSelector());
}
- SeamAnnotatedFactory factory = new SeamAnnotatedFactory();
+ SeamAnnotatedFactory factory =
+ ("org.jboss.seam.international.messages".equals(name) && new String(m.getSelector()).equals("getMessages"))
+ ? new SeamMessages()
+ : new SeamAnnotatedFactory();
factory.setParentDeclaration(component);
factory.setSourcePath(component.getSourcePath());
ds.getFactories().add(factory);
18 years
- 1
- 0
JBoss Tools SVN: r7130 - trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation.
by jbosstools-commits＠lists.jboss.org
Author: akazakov
Date: 2008-03-26 12:31:16 -0400 (Wed, 26 Mar 2008)
New Revision: 7130
Modified:
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1955 Fixed NullPointerException
Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java 2008-03-26 13:56:19 UTC (rev 7129)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java 2008-03-26 16:31:16 UTC (rev 7130)
@@ -595,7 +595,7 @@
if(dataModelName==null) {
// here must be the only one @DataModel in the component
Set<IBijectedAttribute> dataBinders = declaration.getBijectedAttributesByType(BijectedAttributeType.DATA_BINDER);
- if(dataBinders.size()>1) {
+ if(dataBinders!=null && dataBinders.size()>1) {
for (IBijectedAttribute dataBinder : dataBinders) {
addError(MULTIPLE_DATA_BINDER_MESSAGE_ID, SeamPreferences.MULTIPLE_DATA_BINDER, dataBinder, declaration.getResource());
}
18 years
- 1
- 0
JBoss Tools SVN: r7129 - trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/attribute/editor.
by jbosstools-commits＠lists.jboss.org
Author: mareshkau
Date: 2008-03-26 09:56:19 -0400 (Wed, 26 Mar 2008)
New Revision: 7129
Modified:
trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/attribute/editor/ComboBoxFieldEditor.java
Log:
http://jira.jboss.org/jira/browse/JBIDE-1948
Modified: trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/attribute/editor/ComboBoxFieldEditor.java
===================================================================
--- trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/attribute/editor/ComboBoxFieldEditor.java 2008-03-26 13:32:53 UTC (rev 7128)
+++ trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/attribute/editor/ComboBoxFieldEditor.java 2008-03-26 13:56:19 UTC (rev 7129)
@@ -16,11 +16,6 @@
import java.util.Arrays;
import java.util.List;
-import org.jboss.tools.common.model.ui.IAttributeErrorProvider;
-import org.jboss.tools.common.model.ui.IValueChangeListener;
-import org.jboss.tools.common.model.ui.IValueProvider;
-import org.jboss.tools.common.model.ui.attribute.IListContentProvider;
-import org.jboss.tools.common.model.ui.attribute.adapter.DefaultValueAdapter;
import org.eclipse.core.runtime.Platform;
import org.eclipse.jface.util.IPropertyChangeListener;
import org.eclipse.jface.viewers.ILabelProvider;
@@ -43,7 +38,11 @@
import org.eclipse.swt.widgets.Control;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Text;
-
+import org.jboss.tools.common.model.ui.IAttributeErrorProvider;
+import org.jboss.tools.common.model.ui.IValueChangeListener;
+import org.jboss.tools.common.model.ui.IValueProvider;
+import org.jboss.tools.common.model.ui.attribute.IListContentProvider;
+import org.jboss.tools.common.model.ui.attribute.adapter.DefaultValueAdapter;
import org.jboss.tools.common.model.ui.widgets.BorderedControl;
import org.jboss.tools.common.model.ui.widgets.IWidgetSettings;
import org.jboss.tools.common.model.ui.widgets.border.Border;
@@ -60,7 +59,7 @@
IListContentProvider listContentProvider;
private boolean dropDown = false;
- private String stringValue = "";
+ private String stringValue = ""; //$NON-NLS-1$
private boolean isValid;
public static int UNLIMITED = -1;
private int textLimit = UNLIMITED;
@@ -158,12 +157,12 @@
protected Combo getComboControl(Composite parent) {
if (comboField == null) {
- int style = getSettings().getStyle("Combo.Style");
- Color bg = getSettings().getColor("Combo.Background");
+ int style = getSettings().getStyle("Combo.Style"); //$NON-NLS-1$
+ Color bg = getSettings().getColor("Combo.Background"); //$NON-NLS-1$
if (bg==null) bg = Display.getCurrent().getSystemColor(SWT.COLOR_WHITE);// bug with gray bg
- Color fg = getSettings().getColor("Combo.Foreground");
- Font font = getSettings().getFont("Combo.Font");
- Border border = getSettings().getBorder("Combo.Border");
+ Color fg = getSettings().getColor("Combo.Foreground"); //$NON-NLS-1$
+ Font font = getSettings().getFont("Combo.Font"); //$NON-NLS-1$
+ Border border = getSettings().getBorder("Combo.Border"); //$NON-NLS-1$
if (style == SWT.DEFAULT) style = defaultStyle;
if (isDropDown()) style = style | SWT.READ_ONLY;
@@ -245,13 +244,17 @@
}
protected void valueChanged() {
- //added by Max Areshkau
- //hack which was applied for fix JBIDE-1694
+ /*added by Max Areshkau
+ *hack which was applied for fix JBIDE-1694
+ */
if(comboField!=null&&Platform.OS_LINUX.equals(Platform.getOS())) {
-
- comboField.forceFocus();
+ /*
+ * Fix for JBIDE-1948
+ */
+ Point point = comboField.getSelection();
+ comboField.setFocus();
+ comboField.setSelection(point);
}
- comboField.forceFocus();
setPresentsDefaultValue(false);
boolean oldState = isValid;
refreshValidState();
@@ -303,14 +306,7 @@
}
return tags;
}
-/*
- public int getStyle() {
- return style;
- }
- public void setStyle(int i) {
- style = i;
- }
-*/
+
protected void setStringValue(String newValue) {
if(modifyLock) return;
String oldValue = this.stringValue;
@@ -398,7 +394,7 @@
if (IPropertyEditor.VALUE.equals(evt.getPropertyName())) {
Object v = evt.getNewValue();
valueProvider.removeValueChangeListener(this);
- this.setStringValue((v == null) ? "" : v.toString());
+ this.setStringValue((v == null) ? "" : v.toString()); //$NON-NLS-1$
valueProvider.addValueChangeListener(this);
}
if (IPropertyEditor.LIST_CONTENT.equals(evt.getPropertyName())) {
@@ -412,7 +408,7 @@
if(i < 0 && tags != null && tags.length > 0) {
comboField.setText(tags[0]);
} else if(i < 0) {
- comboField.setText("");
+ comboField.setText(""); //$NON-NLS-1$
}
}
}
@@ -423,10 +419,10 @@
this.getComboControl().setEnabled(enabled);
Color bg;
if (enabled) {
- bg = getSettings().getColor("Combo.Background");
+ bg = getSettings().getColor("Combo.Background"); //$NON-NLS-1$
if (bg==null) bg = Display.getDefault().getSystemColor(SWT.COLOR_WHITE);
} else {
- bg = getSettings().getColor("Combo.Background.Disabled");
+ bg = getSettings().getColor("Combo.Background.Disabled"); //$NON-NLS-1$
if (bg==null) bg = Display.getDefault().getSystemColor(SWT.COLOR_WIDGET_BACKGROUND);
}
/// this.getComboControl().setBackground(bg);
@@ -462,7 +458,7 @@
private Text getInnerText() {
try {
- Field f = comboField.getClass().getDeclaredField("text");
+ Field f = comboField.getClass().getDeclaredField("text"); //$NON-NLS-1$
f.setAccessible(true);
Text text = (Text)f.get(comboField);
return (text != null && !text.isDisposed()) ? text : null;
18 years
- 1
- 0