JBoss Tools SVN: r4752 - trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template.
by jbosstools-commits＠lists.jboss.org
Author: mareshkau
Date: 2007-11-06 15:49:07 -0500 (Tue, 06 Nov 2007)
New Revision: 4752
Modified:
trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesSimpleTogglePanelTemplate.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1255, when we use combination of styles like <div style=" position : relative ;"><div style="overflow:auto">Some Elements</div></div>, it's reason of incorrect work of nIFlashe(native code). So we use workarond, we change style "overflow:auto" to "overflow:hidden".
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesSimpleTogglePanelTemplate.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesSimpleTogglePanelTemplate.java 2007-11-06 20:43:35 UTC (rev 4751)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesSimpleTogglePanelTemplate.java 2007-11-06 20:49:07 UTC (rev 4752)
@@ -96,7 +96,7 @@
//if(opened) {
nsIDOMElement bodyDiv = visualDocument.createElement("div");
div.appendChild(bodyDiv);
- bodyDiv.setAttribute("style", "overflow: auto; height: " + ComponentUtil.getAttribute(sourceElement, "height") + "; width: 100%;");
+ bodyDiv.setAttribute("style", "overflow: hidden; height: " + ComponentUtil.getAttribute(sourceElement, "height") + "; width: 100%;");
nsIDOMElement table = visualDocument.createElement("table");
bodyDiv.appendChild(table);
18 years, 5 months
JBoss Tools SVN: r4751 - trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template.
by jbosstools-commits＠lists.jboss.org
Author: mareshkau
Date: 2007-11-06 15:43:35 -0500 (Tue, 06 Nov 2007)
New Revision: 4751
Modified:
trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesPanelTemplate.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1213, fix for large font on seam login page
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesPanelTemplate.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesPanelTemplate.java 2007-11-06 20:25:57 UTC (rev 4750)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesPanelTemplate.java 2007-11-06 20:43:35 UTC (rev 4751)
@@ -13,12 +13,16 @@
import java.util.List;
import org.jboss.tools.jsf.vpe.richfaces.ComponentUtil;
+import org.jboss.tools.jsf.vpe.richfaces.HtmlComponentUtil;
import org.jboss.tools.vpe.editor.context.VpePageContext;
import org.jboss.tools.vpe.editor.template.VpeAbstractTemplate;
import org.jboss.tools.vpe.editor.template.VpeChildrenInfo;
import org.jboss.tools.vpe.editor.template.VpeCreationData;
import org.mozilla.interfaces.nsIDOMDocument;
import org.mozilla.interfaces.nsIDOMElement;
+import org.mozilla.interfaces.nsIDOMNode;
+import org.mozilla.interfaces.nsIDOMNodeList;
+import org.mozilla.xpcom.XPCOMException;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
@@ -73,4 +77,37 @@
return creationData;
}
+
+ /* (non-Javadoc)
+ * @see org.jboss.tools.vpe.editor.template.VpeAbstractTemplate#validate(org.jboss.tools.vpe.editor.context.VpePageContext, org.w3c.dom.Node, org.mozilla.interfaces.nsIDOMDocument, org.jboss.tools.vpe.editor.template.VpeCreationData)
+ */
+ @Override
+ public void validate(VpePageContext pageContext, Node sourceNode,
+ nsIDOMDocument visualDocument, VpeCreationData data) {
+ // FIX for JBIDE-1213 (Max Areshkau)
+ if(data.getNode()!=null) {
+ String bodyClass = ((Element)sourceNode).getAttribute("bodyClass");
+ applyStylesToTable(data.getNode(), bodyClass);
+ }
+ }
+
+ private void applyStylesToTable(nsIDOMNode node,String sourceClass) {
+
+ try {
+ nsIDOMNodeList list = node.getChildNodes();
+ nsIDOMElement element = (nsIDOMElement) node
+ .queryInterface(nsIDOMElement.NS_IDOMELEMENT_IID);
+
+ if (node.getNodeName().equalsIgnoreCase(
+ HtmlComponentUtil.HTML_TAG_TABLE)){
+ element.setAttribute("class", "dr-pnl-b rich-panel-body " + (sourceClass==null?"":sourceClass));
+ }
+ for (int i = 0; i < list.getLength(); i++) {
+ applyStylesToTable(list.item(i),sourceClass);
+ }
+ } catch (XPCOMException e) {
+ //Ignore
+ return;
+ }
+ }
}
\ No newline at end of file
18 years, 5 months
JBoss Tools SVN: r4750 - trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console.
by jbosstools-commits＠lists.jboss.org
Author: max.andersen(a)jboss.com
Date: 2007-11-06 15:25:57 -0500 (Tue, 06 Nov 2007)
New Revision: 4750
Modified:
trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/ComboContribution.java
Log:
hack for combobox in hql editor for MacOS
Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/ComboContribution.java
===================================================================
--- trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/ComboContribution.java 2007-11-06 17:48:24 UTC (rev 4749)
+++ trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/ComboContribution.java 2007-11-06 20:25:57 UTC (rev 4750)
@@ -1,5 +1,6 @@
package org.hibernate.eclipse.console;
+import org.eclipse.core.runtime.Platform;
import org.eclipse.jface.action.ControlContribution;
import org.eclipse.swt.SWT;
import org.eclipse.swt.events.SelectionListener;
@@ -33,6 +34,8 @@
gridLayout.verticalSpacing = 1;
gridLayout.marginHeight=0;
gridLayout.marginWidth=0;
+ gridLayout.marginTop=0;
+ gridLayout.marginBottom=0;
//gridLayout.
panel.setLayout( gridLayout );
@@ -49,10 +52,10 @@
comboControl.pack();
GridData gd = new GridData();
gd.grabExcessHorizontalSpace = true;
- //gd.verticalIndent = -8;
gd.widthHint = getComboWidth();
- gd.verticalAlignment = GridData.CENTER;
- gd.horizontalAlignment = GridData.END;
+ gd.verticalAlignment = GridData.VERTICAL_ALIGN_FILL;
+ gd.horizontalAlignment = GridData.HORIZONTAL_ALIGN_FILL;
+ if(Platform.getOS().equals(Platform.OS_MACOSX)) gd.verticalIndent=-9;
comboControl.setLayoutData( gd );
@@ -61,6 +64,7 @@
comboControl.addSelectionListener( getSelectionAdapter() );
}
+ panel.pack();
return panel;
}
18 years, 5 months
JBoss Tools SVN: r4749 - in trunk/as/docs/ServerManagerRef/reference/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-06 12:48:24 -0500 (Tue, 06 Nov 2007)
New Revision: 4749
Added:
trunk/as/docs/ServerManagerRef/reference/en/images/projects/newDynWeb.png
trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard1.png
trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard2.png
Removed:
trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard1.jpg
trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard2.jpg
Modified:
trunk/as/docs/ServerManagerRef/reference/en/modules/WebToolsprojects.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-279 Chapter Webtools Projects updated and screenshots added
Added: trunk/as/docs/ServerManagerRef/reference/en/images/projects/newDynWeb.png
===================================================================
(Binary files differ)
Property changes on: trunk/as/docs/ServerManagerRef/reference/en/images/projects/newDynWeb.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard1.jpg
===================================================================
(Binary files differ)
Added: trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard1.png
===================================================================
(Binary files differ)
Property changes on: trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard2.jpg
===================================================================
(Binary files differ)
Added: trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard2.png
===================================================================
(Binary files differ)
Property changes on: trunk/as/docs/ServerManagerRef/reference/en/images/projects/wizard2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/as/docs/ServerManagerRef/reference/en/modules/WebToolsprojects.xml
===================================================================
--- trunk/as/docs/ServerManagerRef/reference/en/modules/WebToolsprojects.xml 2007-11-06 17:36:18 UTC (rev 4748)
+++ trunk/as/docs/ServerManagerRef/reference/en/modules/WebToolsprojects.xml 2007-11-06 17:48:24 UTC (rev 4749)
@@ -1,11 +1,11 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="webtoolsProjects">
- <title>Webtools Projects (out of date!)</title>
+ <title>Webtools Projects</title>
<section><title>Description</title>
<para>
- Webtools provides what are called "faceted" projects,
+ Webtools provides what are called "faceted" projects.
Their most popular such projects are their J2EE projects,
- such as their Dynamic Web Project, their EJB Project,
+ such as their <property>Dynamic Web Project</property>, their EJB Project,
or their EAR project. </para>
<para>
The idea behind faceted projects is that each project
@@ -28,20 +28,30 @@
then known, and packaging it up *should* be trivial. However,
if your project is non-standard, or you feel too confined by
such rigid structural requirements, you can still choose to
- package your project using the Archives plugin as described
- in the last chapter</para>
+ package your project using the Archives plugin</para>
</section>
+
+
<section><title>Faceted Project Wizards</title>
- <figure id="faceted1"> <title>Faceted Project Wizard: First Page</title>
- <mediaobject>
- <alt>Faceted Project Wizard: First Page</alt>
- <imageobject>
- <imagedata width="5in" scalefit="0"
- fileref="..\..\..\..\reference\en\images\projects\wizard1.jpg"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <para>To create a new <property>Dynamic Web Project</property> select <emphasis><property>File > New > Other...</property></emphasis> then <emphasis><property>Web > Dynamic Web Project</property></emphasis></para>
+ <figure>
+ <title>New Dynamic Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/projects/newDynWeb.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click <emphasis><property>Next</property></emphasis> and you will see Dynamic Web Project page</para>
+ <figure>
+ <title>Faceted Project Wizard: First Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/projects/wizard1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<para>
The first page of most WTP projects allows you to target a specific runtime,
representing a server's library location. It will also provide you the ability to
@@ -50,21 +60,20 @@
<para>
Selecting the runtime, again, allows the project to install the proper
classpaths to the project so it knows what code to compile against.</para>
- <figure id="faceted2"> <title>Faceted Project Wizard: Second Page</title>
- <mediaobject>
- <alt>Faceted Project Wizard: Second Page</alt>
- <imageobject>
- <imagedata width="5in" scalefit="0"
- fileref="..\..\..\..\reference\en\images\projects\wizard2.jpg"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <figure>
+ <title>Faceted Project Wizard: Second Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/projects/wizard2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<para>
The second page of the wizard allows you to enable or disable specific facets, as
described above. Some facets may require others, and some may conflict with others,
but on the whole this page allows you to add any number of facets that don't conflict
with each other. </para>
<para>
- Further pages are specific to either hte project type, or the facets selected.</para>
+ Further pages are specific to either the project type, or the facets selected.</para>
</section>
</chapter>
18 years, 5 months
JBoss Tools SVN: r4748 - trunk/jsf/docs/jbossjsftools/userguide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: afedosik
Date: 2007-11-06 12:36:18 -0500 (Tue, 06 Nov 2007)
New Revision: 4748
Modified:
trunk/jsf/docs/jbossjsftools/userguide/en/modules/VisualPageEditor.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-175 In VPE chapter the code for style.css is corrected.
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/modules/VisualPageEditor.xml
===================================================================
--- trunk/jsf/docs/jbossjsftools/userguide/en/modules/VisualPageEditor.xml 2007-11-06 16:25:06 UTC (rev 4747)
+++ trunk/jsf/docs/jbossjsftools/userguide/en/modules/VisualPageEditor.xml 2007-11-06 17:36:18 UTC (rev 4748)
@@ -130,7 +130,7 @@
click <emphasis><property>Add</property></emphasis> (for CSS File Path section) and add your stylesheet. It works when CSS is defined on your page in the following way:</para>
<para>Code:</para>
-<programlisting role="XML"><![CDATA[<link rel="stylesheet" type="text/css" href="{requestContextPath}/style.css"/>
+ <programlisting role="XML"><![CDATA[<link rel="stylesheet" type="text/css" href="#{facesContext.externalContext.requestContextPath}/style.css"/>
]]></programlisting>
<para>This will work fine in runtime, but the Visual Page Editor doesn't know what requestContextPath in design time is.</para>
18 years, 5 months
JBoss Tools SVN: r4747 - trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/wizards.
by jbosstools-commits＠lists.jboss.org
Author: max.andersen(a)jboss.com
Date: 2007-11-06 11:25:06 -0500 (Tue, 06 Nov 2007)
New Revision: 4747
Modified:
trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/wizards/JBossRuntimeWizardFragment.java
Log:
JBIDE-1264 Create server/runtime gives NPE
Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/wizards/JBossRuntimeWizardFragment.java
===================================================================
--- trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/wizards/JBossRuntimeWizardFragment.java 2007-11-06 16:24:45 UTC (rev 4746)
+++ trunk/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/wizards/JBossRuntimeWizardFragment.java 2007-11-06 16:25:06 UTC (rev 4747)
@@ -470,6 +470,9 @@
}
private String getErrorString(int severity) {
+ if(nameText==null) { // We haven't yet been created so don't know any errors yet.
+ return null;
+ }
if (getRuntime(nameText.getText()) != null) {
return Messages.rwf_NameInUse;
}
18 years, 5 months
JBoss Tools SVN: r4746 - in trunk/as/docs/ServerManagerRef/reference/en: images/serverRuntimes and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-06 11:24:45 -0500 (Tue, 06 Nov 2007)
New Revision: 4746
Added:
trunk/as/docs/ServerManagerRef/reference/en/images/DeployingModules/
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/installedRuntimeEnv.png
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/installedRuntimes.png
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/new4.0Runtime.png
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newRuntime.png
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newServer.png
Removed:
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/installedRuntimes.JPG
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/new4.0Runtime.JPG
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newRuntime.JPG
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newServer.JPG
trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newServer2.JPG
Modified:
trunk/as/docs/ServerManagerRef/reference/en/modules/RuntimesAndServers.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-279 Chapter Runtimes and Servers in the JBoss AS plugin updated and screenshots added
Added: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/installedRuntimeEnv.png
===================================================================
(Binary files differ)
Property changes on: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/installedRuntimeEnv.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/installedRuntimes.JPG
===================================================================
(Binary files differ)
Added: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/installedRuntimes.png
===================================================================
(Binary files differ)
Property changes on: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/installedRuntimes.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/new4.0Runtime.JPG
===================================================================
(Binary files differ)
Added: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/new4.0Runtime.png
===================================================================
(Binary files differ)
Property changes on: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/new4.0Runtime.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newRuntime.JPG
===================================================================
(Binary files differ)
Added: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newRuntime.png
===================================================================
(Binary files differ)
Property changes on: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newRuntime.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newServer.JPG
===================================================================
(Binary files differ)
Added: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newServer.png
===================================================================
(Binary files differ)
Property changes on: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newServer.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/as/docs/ServerManagerRef/reference/en/images/serverRuntimes/newServer2.JPG
===================================================================
(Binary files differ)
Modified: trunk/as/docs/ServerManagerRef/reference/en/modules/RuntimesAndServers.xml
===================================================================
--- trunk/as/docs/ServerManagerRef/reference/en/modules/RuntimesAndServers.xml 2007-11-06 16:14:42 UTC (rev 4745)
+++ trunk/as/docs/ServerManagerRef/reference/en/modules/RuntimesAndServers.xml 2007-11-06 16:24:45 UTC (rev 4746)
@@ -10,198 +10,117 @@
<keyword>JBoss</keyword>
</keywordset>
</chapterinfo>
- <title>Runtimes and Servers in the JBoss AS plugin (out of date!)</title>
+ <title>Runtimes and Servers in the JBoss AS plugin</title>
- <para>The JBoss AS plugin makes use of Webtools. This includes
- starting and stopping servers in run or debug mode. It also includes
- targeting webtools projects, such as dynamic web projects,
- to certain server runtimes in order to ensure that the proper jars
- from a specific server are added to the project's classpath properly.
- </para>
- <para>
- In order to get started creating, running, and debugging J2EE
- applications, we must start with creating our runtime and
- server instances.
- </para>
+ <para>The JBoss AS plugin makes use of Webtools. This includes starting and stopping servers in run or debug mode. It also includes
+ targeting webtools projects, such as dynamic web projects, to certain server runtimes in order to ensure that the proper jars
+ from a specific server are added to the project's classpath properly.</para>
+ <para>In order to get started creating, running, and debugging J2EE applications, we must start with creating our <property>runtime</property> and
+ <property>server</property> instances.</para>
<section>
<title>Webtools Runtimes</title>
- <section><title>What is a runtime used for?</title>
- <para>
- In RHDS, Server Runtimes have one main purpose:
- to point to a server installation somewhere on disk.
- In our case, this will be a JBoss installation, and it
- can than be used for two primary purposes.
-
- First,
- it provides classpath additions to webtools projects that require them.
- Second, for JBoss server at least, it provides information necessary
- for the starting and stopping of the server, such as which jars
- to run and which configuration to use.
- </para>
- </section>
+ <para>In RHDS, Server Runtimes have one main purpose: to point to a server installation somewhere on disk.
+ In our case, this will be a JBoss installation, and it can than be used for two primary purposes.
+ First, it provides classpath additions to webtools projects that require them. Second, for JBoss server at least, it provides information necessary
+ for the starting and stopping of the server, such as which jars to run and which configuration to use. </para>
+
-
<section><title>Installing a new Runtime</title>
- <para>
- You can install runtimes into eclipse from the Window -> Preferences...
- menu, and then selecting Server -> Installed Runtimes from the categories available.
- </para>
- <figure id="installedRuntimeWindow"> <title>Installed Runtimes</title>
+ <para>You can install runtimes into eclipse from the <emphasis><property>Window > Preferences... </property></emphasis>
+ menu, and then selecting <emphasis><property>Server > Installed Runtimes</property></emphasis> from the categories available.</para>
+ <figure>
+ <title>Installed Runtimes</title>
<mediaobject>
- <alt>Installed Server Runtime Preferences</alt>
<imageobject>
- <imagedata
- fileref="..\..\..\..\reference\en\images\serverRuntimes\installedRuntimes.JPG"/>
+ <imagedata fileref="images/serverRuntimes/installedRuntimes.png"/>
</imageobject>
</mediaobject>
</figure>
-
-
- <para>
- From this preference page you can see what runtimes are declared,
- and what type they are. In the image shown above, there are three declared
- runtimes, including a Tomcat 5.5 instance and a JBoss 4.2 instance.
- </para>
-
- <para>
- To create a JBoss runtime, we begin by clicking the add button.
- This will open another dialog that allows us to choose what type
- of runtime we want to create. Most of the runtime options are provided
- by webtools, but those provided by RHDS are the ones we will focus on.
-
- </para>
-
- <figure id="addRuntimeWindow"> <title>Adding a Runtime</title>
+ <para>From this preference page you can see what runtimes are declared, and what type they are. In the image shown above, there are two declared
+ runtimes, including a JBoss 4.2 instance.</para>
+ <para>To create a JBoss runtime, we begin by clicking the <emphasis><property>Add</property></emphasis> button. This will open another dialog that allows us to choose what type
+ of runtime we want to create. Most of the runtime options are provided by webtools, but those provided by RHDS are the ones we will focus on.</para>
+ <figure>
+ <title>Adding a Runtime</title>
<mediaobject>
- <alt>Adding a Runtime</alt>
<imageobject>
- <imagedata
- fileref="..\..\..\..\reference\en\images\serverRuntimes\newRuntime.JPG"/>
+ <imagedata fileref="images/serverRuntimes/newRuntime.png"/>
</imageobject>
</mediaobject>
</figure>
-
- <para>
- As seen above, there appear to be two JBoss categories. The first is
- contributed by webtools, and is a generic adapter that is not upkept very well.
- For this reason, RHDS provides updated and supported adapters of our own.
- There is one for each of JBoss 3.2, 4.0, amd 4.2. You'll also note a deploy-only
- runtime type. This type provides no classpath for webtools projects.
- It is used solely by it's server type for the purpose of setting up a deploy directory
- for users who don't wish to make use of starting, stopping, or debugging their projects
- inside eclipse.
- </para>
-
-
- <figure id="add40RuntimeWindow"> <title>Adding a JBoss 4.0 Runtime</title>
+ <para>As seen above, there appear to be two JBoss categories. The first is contributed by webtools, and is a generic adapter that is not upkept very well.
+ For this reason, RHDS provides updated and supported adapters of our own. There is one for each of JBoss 3.2, 4.0, amd 4.2. You'll also note a deploy-only
+ runtime type. This type provides no classpath for webtools projects. It is used solely by it's server type for the purpose of setting up a deploy directory
+ for users who don't wish to make use of starting, stopping, or debugging their projects inside eclipse.</para>
+ <figure>
+ <title>Adding a JBoss 4.2 Runtime</title>
<mediaobject>
- <alt>Adding a JBoss 4.0 Runtime</alt>
<imageobject>
- <imagedata
- fileref="..\..\..\..\reference\en\images\serverRuntimes\new4.0Runtime.JPG"/>
+ <imagedata fileref="images/serverRuntimes/new4.0Runtime.png"/>
</imageobject>
</mediaobject>
</figure>
-
- <para>
- As shown above, all you need to do to create the runtime is to name it, browse to it's install directory,
- select a Java Runtime Environment, and select which configuration you want.
- As you browse to a valid installation folder, the list of configurations will
- update allowing you to select the configuration of your choice.
- </para>
- <para>
- Once the runtime is created, the configuration is an unchanging property
- of that runtime. This is because many of the jars
- necessary to provide for classpaths, such as the ejb3 jar locations or the servlet jar locations,
- are located in deploy directories of each configurations (depending on which
- version of JBoss is being used). Because of this, to compile against
- a different configuration's jars, you will need to create a new runtime from that configuration.
- </para>
- <para>
- Also, because of the open-source nature of JBoss, it is likely that a user may want to
- modify and repackage some of the configuration-specific jboss jars and create
- their own configuration using those modified jars. Rather than forcing the user to copy his
- entire JBoss installation, this structure allows them to create only a new configuration instead.
- </para>
- <para>
- As a result of having each runtime represent a specific configuration rather than
- the server installation as a whole, it is very likely you'll create several different runtimes
- to test each of your configurations. It becomes important to ensure your runtimes,
- and later your servers, are given descriptive names that help you remember which is which.
- It will do no good to try to remember if "JBoss-runtime 5" is the 4.0 install with ejb3? Or the
- 4.2 install's custom configuration you decided to create.
- </para>
- <para>
- After pressing finish, you'll see that your new runtime has been added to the list
- and can now be targeted by webtools type projects or servers, both of which we'll get to later.
- </para>
+ <para>As shown above, all you need to do to create the runtime is to name it, browse to it's install directory,
+ select a Java Runtime Environment, and select which configuration you want. As you browse to a valid installation folder, the list of configurations will
+ update allowing you to select the configuration of your choice.</para>
+ <para>Once the runtime is created, the configuration is an unchanging property
+ of that runtime. This is because many of the jars necessary to provide for classpaths, such as the ejb3 jar locations or the servlet jar locations,
+ are located in deploy directories of each configurations (depending on which version of JBoss is being used). Because of this, to compile against
+ a different configuration's jars, you will need to create a new runtime from that configuration.</para>
+ <para>Also, because of the open-source nature of JBoss, it is likely that a user may want to
+ modify and repackage some of the configuration-specific jboss jars and create their own configuration using those modified jars. Rather than forcing the user to copy his
+ entire JBoss installation, this structure allows them to create only a new configuration instead.</para>
+ <para>As a result of having each runtime represent a specific configuration rather than the server installation as a whole, it is very likely you'll create several different runtimes
+ to test each of your configurations. It becomes important to ensure your runtimes, and later your servers, are given descriptive names that help you remember which is which.
+ It will do no good to try to remember if "JBoss-runtime 5" is the 4.0 install with ejb3? Or the 4.2 install's custom configuration you decided to create.</para>
+ <para>After pressing finish, you'll see that your new runtime has been added to the list and can now be targeted by webtools type projects or servers, both of which we'll get to later.</para>
</section>
+
+ <section><title>Deleting a Runtime</title>
+ <para></para>
+ </section>
+
</section>
-
-
-
<section>
<title>Webtools Servers</title>
- <section>
- <title>What is a Server used for?</title>
- <para>
- Webtools servers are eclipse-representations of a backing server installation.
- They are used to start or stop servers, deploy to servers, or debug code
- that will run on the server. They keep track of what modules (jars, wars, etc)
+ <para>Webtools servers are eclipse-representations of a backing server installation. They are used to start or stop servers, deploy to servers, or debug code that will run on the server. They keep track of what modules (jars, wars, etc)
you deploy to the server and also allow you to undeploy those modules. </para>
- <para>
- Servers can be started or stopped with different command-line arguments.
- They are often backed by a runtime object representing that server's location. </para>
- </section>
- <section>
+ <para>Servers can be started or stopped with different command-line arguments. They are often backed by a runtime object representing that server's location.</para>
+ <section>
<title>Creating a New Server</title>
- <para>
- There are many ways to get to the new server wizard. One way
- is to use the old standard File -> New -> Other... wizard,
- and type in Server. This should show the screen below, which
- does not look that different from the initial screen when
- creating a new runtime. </para>
- <figure id="addServerWindow"> <title>Adding a JBoss Server</title>
- <mediaobject>
- <alt>Adding a JBoss Server</alt>
- <imageobject>
- <imagedata
- fileref="..\..\..\..\reference\en\images\serverRuntimes\newServer.JPG"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>
- Because the server object is what keeps track of things like command line arguments
- when starting or stopping, and runtimes keep track of the location of the installation,
+ <para>There are many ways to get to the new server wizard. One way is to use the old standard <emphasis><property>File -> New -> Other... </property></emphasis>wizard,
+ and type in <emphasis><property>Server</property></emphasis>. This should show the screen below, which does not look that different from the initial screen when creating a new runtime. </para>
+ <figure>
+ <title>Adding a JBoss Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/serverRuntimes/newServer.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Because the server object is what keeps track of things like command line arguments when starting or stopping, and runtimes keep track of the location of the installation,
each server instance must be backed by an appropriate runtime. </para>
- <para>
- Because there may be many runtimes of each type declared, the wizard allows you to select
- which runtime you want your server to be backed by. The combo box below the view lets you
- select which declared runtime to use. For example, if there were already multiple JBoss 4.0
- runtimes declared, the combo box would list all of the 4.0 runtimes available. </para>
- <para>
- If none of the runtimes declared are one you want to use, for example if
- you declared a default and a minimal runtime before but now want your server
- to be backed by the ALL configuration, then you can click on the
- <emphasis>Installed Runtimes... </emphasis> Button to bring up the preference page
+ <para>Because there may be many runtimes of each type declared, the wizard allows you to select which runtime you want your server to be backed by. The combo box below the view lets you
+ select which declared runtime to use. For example, if there were already multiple JBoss 4.2 runtimes declared, the combo box would list all of the 4.2 runtimes available. </para>
+ <para>If none of the runtimes declared are one you want to use, for example if you declared a default and a minimal runtime before but now want your server
+ to be backed by the ALL configuration, then you can click on the <emphasis><property>Installed Runtimes... </property></emphasis> button to bring up the preference page
shown at the beginning of this chapter. </para>
- <para>
- If the server you want to create doesn't have any installed runtime yet, the combo
- box and button will disappear, and the next page in the wizard will force you to create
+ <figure>
+ <title>Installed Server Runtime Environments</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/serverRuntimes/installedRuntimeEnv.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>If the server you want to create doesn't have any installed runtime yet, the combo box and button will disappear, and the next page in the wizard will force you to create
the associated runtime first. </para>
- <para>
- Either way, after targeting your server to a runtime, the final screen
- in this wizard is largely confirmational, giving the user a chance to verify
- that he's selected the appropriate runtime. It also allows the user
- to name the server appropriately. </para>
- </section>
+ <para>Either way, after targeting your server to a runtime, the final screen in this wizard is largely confirmational, giving the user a chance to verify
+ that he's selected the appropriate runtime. It also allows the user to name the server appropriately. </para>
</section>
- <section>
- <title>Well then...</title>
- <para>Now that we've created our runtimes and servers,
- we'll explore how to use them in future chapters. </para>
</section>
+
</chapter>
18 years, 5 months
JBoss Tools SVN: r4745 - trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench.
by jbosstools-commits＠lists.jboss.org
Author: max.andersen(a)jboss.com
Date: 2007-11-06 11:14:42 -0500 (Tue, 06 Nov 2007)
New Revision: 4745
Modified:
trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/BasicWorkbenchAdapter.java
trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/ConfigurationWorkbenchAdapter.java
trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java
trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/PersistentClassWorkbenchAdapter.java
trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/PropertyWorkbenchAdapter.java
trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/TableContainerWorkbenchAdapter.java
Log:
JBIDE-1265 Sorting mappings in Hibernate Console
Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/BasicWorkbenchAdapter.java
===================================================================
--- trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/BasicWorkbenchAdapter.java 2007-11-06 16:05:51 UTC (rev 4744)
+++ trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/BasicWorkbenchAdapter.java 2007-11-06 16:14:42 UTC (rev 4745)
@@ -23,6 +23,8 @@
import java.lang.reflect.Array;
import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Comparator;
import java.util.Enumeration;
import java.util.Iterator;
import java.util.List;
@@ -63,9 +65,15 @@
final static Object[] NO_CHILDREN = new Object[0];
- protected Object[] toArray(Iterator iterator, Class clazz) {
+
+ protected Object[] toArray(Iterator iterator, Class clazz, Comparator comparator) {
List obj = toList( iterator );
- return obj.toArray((Object[]) Array.newInstance(clazz, obj.size()));
+ Object[] array = obj.toArray((Object[]) Array.newInstance(clazz, obj.size()));
+
+ if(comparator!=null) {
+ Arrays.sort(array, comparator);
+ }
+ return array;
}
private List toList(Iterator iterator) {
Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/ConfigurationWorkbenchAdapter.java
===================================================================
--- trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/ConfigurationWorkbenchAdapter.java 2007-11-06 16:05:51 UTC (rev 4744)
+++ trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/ConfigurationWorkbenchAdapter.java 2007-11-06 16:14:42 UTC (rev 4745)
@@ -21,6 +21,7 @@
*/
package org.hibernate.eclipse.console.workbench;
+import java.util.Comparator;
import java.util.Iterator;
import org.eclipse.jface.resource.ImageDescriptor;
@@ -35,7 +36,17 @@
public Object[] getChildren(Object o) {
Configuration cfg = (Configuration) o;
Iterator classMappings = cfg.getClassMappings();
- return toArray(classMappings, PersistentClass.class);
+ return toArray(classMappings, PersistentClass.class, new Comparator() {
+
+ public int compare(Object arg0, Object arg1) {
+ PersistentClass p0 = (PersistentClass) arg0;
+ PersistentClass p1 = (PersistentClass) arg1;
+ String label0 = HibernateWorkbenchHelper.getLabelForClassName(p0.getEntityName());
+ String label1 = HibernateWorkbenchHelper.getLabelForClassName(p1.getEntityName());
+ return label0.compareTo(label1);
+ }
+
+ });
}
public ImageDescriptor getImageDescriptor(Object object) {
Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java
===================================================================
--- trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java 2007-11-06 16:05:51 UTC (rev 4744)
+++ trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java 2007-11-06 16:14:42 UTC (rev 4745)
@@ -22,6 +22,7 @@
package org.hibernate.eclipse.console.workbench;
import java.util.ArrayList;
+import java.util.Comparator;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
@@ -63,7 +64,14 @@
Map.Entry entry = (Map.Entry) qualifierEntries.next();
result.add(new TableContainer((String) entry.getKey(),(List)entry.getValue()));
}
- return toArray(result.iterator(), TableContainer.class);
+ return toArray(result.iterator(), TableContainer.class, new Comparator() {
+
+ public int compare(Object arg0, Object arg1) {
+
+ return ((TableContainer)arg0).getName().compareTo(((TableContainer)arg1).getName());
+ }
+
+ });
}
private LazyDatabaseSchema getLazyDatabaseSchema(Object o) {
Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/PersistentClassWorkbenchAdapter.java
===================================================================
--- trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/PersistentClassWorkbenchAdapter.java 2007-11-06 16:05:51 UTC (rev 4744)
+++ trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/PersistentClassWorkbenchAdapter.java 2007-11-06 16:14:42 UTC (rev 4745)
@@ -44,7 +44,7 @@
}
Iterator propertyClosureIterator = new JoinedIterator(properties.iterator(), pc.getPropertyClosureIterator());
- return toArray(propertyClosureIterator, Property.class);
+ return toArray(propertyClosureIterator, Property.class, null);
}
Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/PropertyWorkbenchAdapter.java
===================================================================
--- trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/PropertyWorkbenchAdapter.java 2007-11-06 16:05:51 UTC (rev 4744)
+++ trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/PropertyWorkbenchAdapter.java 2007-11-06 16:14:42 UTC (rev 4745)
@@ -58,7 +58,7 @@
}
public Object accept(Component component) {
- return toArray(component.getPropertyIterator(), Property.class);
+ return toArray(component.getPropertyIterator(), Property.class, null);
}
public Object accept(DependantValue value) {
Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/TableContainerWorkbenchAdapter.java
===================================================================
--- trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/TableContainerWorkbenchAdapter.java 2007-11-06 16:05:51 UTC (rev 4744)
+++ trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/TableContainerWorkbenchAdapter.java 2007-11-06 16:14:42 UTC (rev 4745)
@@ -21,6 +21,8 @@
*/
package org.hibernate.eclipse.console.workbench;
+import java.util.Comparator;
+
import org.eclipse.jface.resource.ImageDescriptor;
import org.hibernate.console.ImageConstants;
import org.hibernate.eclipse.console.utils.EclipseImages;
@@ -30,7 +32,14 @@
public Object[] getChildren(Object o) {
TableContainer tc = getTableContainer( o );
- return toArray(tc.getTables().iterator(), Table.class);
+ return toArray(tc.getTables().iterator(), Table.class, new Comparator() {
+
+ public int compare(Object arg0, Object arg1) {
+
+ return ((Table)arg0).getName().compareTo(((Table)arg1).getName());
+ }
+
+ });
}
private TableContainer getTableContainer(Object o) {
18 years, 5 months
JBoss Tools SVN: r4744 - trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template.
by jbosstools-commits＠lists.jboss.org
Author: mareshkau
Date: 2007-11-06 11:05:51 -0500 (Tue, 06 Nov 2007)
New Revision: 4744
Modified:
trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template/VpeDefineTemplate.java
trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template/VpeInsertTemplate.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1213, The red star position that indicates a required field was adjusted
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template/VpeDefineTemplate.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template/VpeDefineTemplate.java 2007-11-06 16:05:43 UTC (rev 4743)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template/VpeDefineTemplate.java 2007-11-06 16:05:51 UTC (rev 4744)
@@ -31,8 +31,9 @@
public VpeCreationData create(VpePageContext pageContext, Node sourceNode, nsIDOMDocument visualDocument) {
if (VpeDefineContainerTemplate.isDefineContainer(sourceNode.getParentNode())) {
- nsIDOMElement visualNewElement = visualDocument.createElement(HTML.TAG_DIV);
- return new VpeCreationData(visualNewElement);
+ //FIX for JBIDE-1213, we shouldn't wrap ui:define content( Max Areshkau)
+ //nsIDOMElement visualNewElement = visualDocument.createElement(HTML.TAG_SPAN);
+ return new VpeCreationData(null);
}
return createStub((Element)sourceNode, visualDocument);
}
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template/VpeInsertTemplate.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template/VpeInsertTemplate.java 2007-11-06 16:05:43 UTC (rev 4743)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/src/org/jboss/tools/jsf/vpe/facelets/template/VpeInsertTemplate.java 2007-11-06 16:05:51 UTC (rev 4744)
@@ -22,6 +22,7 @@
import org.jboss.tools.vpe.editor.util.HTML;
import org.mozilla.interfaces.nsIDOMDocument;
import org.mozilla.interfaces.nsIDOMElement;
+import org.mozilla.interfaces.nsIDOMNode;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
@@ -127,4 +128,14 @@
nsIDOMElement visualNewElement = visualDocument.createElement(HTML.TAG_DIV);
return new VpeCreationData(visualNewElement);
}
+
+ /* (non-Javadoc)
+ * @see org.jboss.tools.vpe.editor.template.VpeAbstractTemplate#setPseudoContent(org.jboss.tools.vpe.editor.context.VpePageContext, org.w3c.dom.Node, org.mozilla.interfaces.nsIDOMNode, org.mozilla.interfaces.nsIDOMDocument)
+ */
+ @Override
+ public void setPseudoContent(VpePageContext pageContext,
+ Node sourceContainer, nsIDOMNode visualContainer,
+ nsIDOMDocument visualDocument) {
+ // TODO Fix for JBIDE-1213
+ }
}
18 years, 5 months
JBoss Tools SVN: r4743 - trunk/jsf/plugins/org.jboss.tools.jsf.vpe.seam/templates.
by jbosstools-commits＠lists.jboss.org
Author: mareshkau
Date: 2007-11-06 11:05:43 -0500 (Tue, 06 Nov 2007)
New Revision: 4743
Modified:
trunk/jsf/plugins/org.jboss.tools.jsf.vpe.seam/templates/vpe-templates-seam.xml
Log:
http://jira.jboss.com/jira/browse/JBIDE-1213, The red star position that indicates a required field was adjusted
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.seam/templates/vpe-templates-seam.xml
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.seam/templates/vpe-templates-seam.xml 2007-11-06 15:30:18 UTC (rev 4742)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.seam/templates/vpe-templates-seam.xml 2007-11-06 16:05:43 UTC (rev 4743)
@@ -15,9 +15,41 @@
</vpe:tag>
<vpe:tag name="s:label" case-sensitive="yes">
- <vpe:template children="yes" modify="yes">
- <label class="{@styleClass}" style="{@style}"/>
- </vpe:template>
+ <vpe:template children="yes" modify="yes">
+ <label style="{@style}" class="{@styleClass}" title="{tagstring()}" for="{@for}">
+ <vpe:value expr="{jsfvalue(@value)}"/>
+ </label>
+ <vpe:dnd>
+ <vpe:drag start-enable="yes"/>
+ <vpe:drop container="yes">
+ <vpe:container-child tag-name="outputText"/>
+ </vpe:drop>
+ </vpe:dnd>
+ <vpe:textFormating>
+ <vpe:format type="BlockFormat" addChildren="deny" handler="org.jboss.tools.vpe.editor.toolbar.format.handler.BlockFormatHandler" />
+ <vpe:format type="UnderlineFormat">
+ <vpe:formatAttribute type="style"/>
+ </vpe:format>
+ <vpe:format type="BoldFormat">
+ <vpe:formatAttribute type="style"/>
+ </vpe:format>
+ <vpe:format type="ItalicFormat">
+ <vpe:formatAttribute type="style"/>
+ </vpe:format>
+ <vpe:format type="FontNameFormat">
+ <vpe:formatAttribute type="style"/>
+ </vpe:format>
+ <vpe:format type="FontSizeFormat">
+ <vpe:formatAttribute type="style"/>
+ </vpe:format>
+ <vpe:format type="BackgroundColorFormat">
+ <vpe:formatAttribute type="style"/>
+ </vpe:format>
+ <vpe:format type="ForegroundColorFormat">
+ <vpe:formatAttribute type="style"/>
+ </vpe:format>
+ </vpe:textFormating>
+ </vpe:template>
</vpe:tag>
<vpe:tag name="s:message" case-sensitive="yes">
18 years, 5 months