December 2007 - jbosstools-commits

JBoss Tools SVN: r5203 - trunk/documentation/jboss-tools-docs.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-12-03 11:27:58 -0500 (Mon, 03 Dec 2007) New Revision: 5203 Modified: trunk/documentation/jboss-tools-docs/build.xml Log: build folder is deleted now Modified: trunk/documentation/jboss-tools-docs/build.xml =================================================================== --- trunk/documentation/jboss-tools-docs/build.xml 2007-12-03 16:07:55 UTC (rev 5202) +++ trunk/documentation/jboss-tools-docs/build.xml 2007-12-03 16:27:58 UTC (rev 5203) @@ -4,7 +4,7 @@ <property name="root-dir" location="${basedir}/../.."></property> <target name="clean"> -  + <delete dir="${build-dir}" failonerror="false"></delete> </target> <target name="build-documentation" depends="clean">

18 years

1
0
0 / 0

JBoss Tools SVN: r5202 - in trunk/hibernatetools/plugins: org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: achabatar Date: 2007-12-03 11:07:55 -0500 (Mon, 03 Dec 2007) New Revision: 5202 Modified: trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.veditor/src/org/jboss/tools/hibernate/ui/veditor/editors/parts/ShapeEditPart.java trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views/OrmLabelProvider.java trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views/OrmModelNameVisitor.java Log: http://jira.jboss.com/jira/browse/JBIDE-874 Modified: trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.veditor/src/org/jboss/tools/hibernate/ui/veditor/editors/parts/ShapeEditPart.java =================================================================== --- trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.veditor/src/org/jboss/tools/hibernate/ui/veditor/editors/parts/ShapeEditPart.java 2007-12-03 16:05:10 UTC (rev 5201) +++ trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.veditor/src/org/jboss/tools/hibernate/ui/veditor/editors/parts/ShapeEditPart.java 2007-12-03 16:07:55 UTC (rev 5202) @@ -28,11 +28,10 @@ import org.eclipse.gef.NodeEditPart; import org.eclipse.gef.Request; import org.eclipse.gef.RequestConstants; -import org.eclipse.gef.editparts.AbstractGraphicalEditPart; import org.eclipse.gef.editpolicies.SelectionEditPolicy; import org.eclipse.swt.graphics.Color; import org.eclipse.swt.graphics.RGB; -import org.hibernate.mapping.Any; +import org.hibernate.console.ConsoleConfiguration; import org.hibernate.mapping.Column; import org.hibernate.mapping.Component; import org.hibernate.mapping.DependantValue; @@ -46,6 +45,7 @@ import org.jboss.tools.hibernate.ui.veditor.editors.figures.TopLineBorder; import org.jboss.tools.hibernate.ui.veditor.editors.model.Connection; import org.jboss.tools.hibernate.ui.veditor.editors.model.ModelElement; +import org.jboss.tools.hibernate.ui.veditor.editors.model.OrmDiagram; import org.jboss.tools.hibernate.ui.veditor.editors.model.Shape; import org.jboss.tools.hibernate.ui.veditor.editors.model.SpecialRootClass; import org.jboss.tools.hibernate.ui.view.views.OrmLabelProvider; @@ -67,7 +67,15 @@ protected IFigure createFigure() { if (getModel() instanceof Shape) { Label label = new Label(); - label.setText(ormLabelProvider.getText(getElement())); + ModelElement model = (ModelElement) getModel(); + while (model.getParent() != null) { + model = model.getParent(); + } + ConsoleConfiguration consoleConfiguration = null; + if (model instanceof OrmDiagram) { + consoleConfiguration = ((OrmDiagram) model).getConsoleConfiguration(); + } + label.setText(ormLabelProvider.getText(getElement(), consoleConfiguration)); label.setBackgroundColor(getColor()); label.setIcon(ormLabelProvider.getImage(getElement())); label.setLabelAlignment(PositionConstants.LEFT); Modified: trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views/OrmLabelProvider.java =================================================================== --- trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views/OrmLabelProvider.java 2007-12-03 16:05:10 UTC (rev 5201) +++ trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views/OrmLabelProvider.java 2007-12-03 16:07:55 UTC (rev 5202) @@ -24,6 +24,8 @@ import org.eclipse.swt.graphics.Font; import org.eclipse.swt.graphics.Image; import org.eclipse.swt.widgets.Display; +import org.hibernate.cfg.Configuration; +import org.hibernate.console.ConsoleConfiguration; import org.hibernate.mapping.Any; import org.hibernate.mapping.Column; import org.hibernate.mapping.Component; @@ -84,7 +86,7 @@ return image; } - public String getText(Object element) { + public String getText(Object element, ConsoleConfiguration consoleConfiguration) { if (element instanceof RootClass) { String name = (String)ormModelNameVisitor.visitPersistentClass((RootClass)element, null); if (name == null) { @@ -114,7 +116,7 @@ return name; } } else if (element instanceof Column) { - String name = (String)ormModelNameVisitor.visitDatabaseColumn((Column)element, null); + String name = (String)ormModelNameVisitor.visitDatabaseColumn((Column)element, consoleConfiguration); if (name == null) { return "OrmElement"; } else { Modified: trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views/OrmModelNameVisitor.java =================================================================== --- trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views/OrmModelNameVisitor.java 2007-12-03 16:05:10 UTC (rev 5201) +++ trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view/src/org/jboss/tools/hibernate/ui/view/views/OrmModelNameVisitor.java 2007-12-03 16:07:55 UTC (rev 5202) @@ -1,160 +1,189 @@ -/******************************************************************************* - * 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.hibernate.ui.view.views; - -import java.sql.Types; -import java.util.ResourceBundle; - -import org.eclipse.core.runtime.IAdaptable; -import org.eclipse.jdt.core.Signature; -import org.eclipse.jface.text.TextUtilities; -import org.eclipse.jface.viewers.ContentViewer; -import org.hibernate.cfg.reveng.JDBCToHibernateTypeHelper; -import org.hibernate.eclipse.console.workbench.TypeNameValueVisitor; -import org.hibernate.mapping.Column; -import org.hibernate.mapping.Component; -import org.hibernate.mapping.DependantValue; -import org.hibernate.mapping.Property; -import org.hibernate.mapping.RootClass; -import org.hibernate.mapping.SimpleValue; -import org.hibernate.mapping.SingleTableSubclass; -import org.hibernate.mapping.Subclass; -import org.hibernate.mapping.Table; -import org.hibernate.mapping.Value; -import org.hibernate.type.EntityType; -import org.hibernate.type.ManyToOneType; - -public class OrmModelNameVisitor /*implements IOrmModelVisitor*/ { - - static private String SPACE = " "; - static private String POINTER = " -> "; - - private ResourceBundle BUNDLE = ResourceBundle - .getBundle(OrmModelNameVisitor.class.getPackage().getName() - + ".views"); - - public OrmModelNameVisitor() { - super(); - } - - public Object visitDatabaseColumn(Column column, Object argument) { - StringBuffer name = new StringBuffer(); - name.append(column.getName()); - -// String s = JDBCToHibernateTypeHelper.getJDBCTypeName(column.getSqlTypeCode().intValue()); - - return name.toString(); - - } - - public Object visitPersistentClass(RootClass clazz, Object argument) { - - StringBuffer name = new StringBuffer(); - name.append(clazz.getEntityName() != null ? clazz.getEntityName() : clazz.getClassName()); - - Table table = clazz.getTable(); // upd tau 06.06.2005 - if (table != null) { - String tableName = HibernateUtils.getTableName(table); - if (tableName != null) { - name.append(POINTER); - name.append(tableName); - } - } - - return name.toString(); - } - - public Object visitTable(Table table, Object argument) { - StringBuffer name = new StringBuffer(); - name.append(HibernateUtils.getTableName(table)); - return name.toString(); - } - - public Object visitPersistentClass(Subclass clazz, Object argument) { - - StringBuffer name = new StringBuffer(); - name.append(clazz.getEntityName()); - - Table table = clazz.getTable(); - if (table != null) { - String tableName = HibernateUtils.getTableName(table); - if (tableName != null) { - name.append(POINTER); - name.append(tableName); - } - } - - return name.toString(); - } - - public Object visitPersistentField(Property field, Object argument) { - StringBuffer name = new StringBuffer(); - name.append(field.getName()); - name.append(BUNDLE.getString("OrmModelNameVisitor.Colon")); - String typeString = null; - - try { - typeString = field.getType().getReturnedClass().getName(); - } catch (Exception e) { - if (field.getValue() instanceof Component) { - typeString = ((Component)field.getValue()).getComponentClassName(); - } else if (field.getValue().isSimpleValue()) { - typeString = ((SimpleValue)field.getValue()).getTypeName(); - } - } - - - - if (typeString != null) { - typeString = correctTypeString(typeString); - name.append(SPACE); - name.append(typeString); - } - -// return name.toString(); - - Value value = field.getValue(); - String typeName = (String) value.accept(new TypeNameValueVisitor(false)); - - if (typeName!=null) { - return field.getName() + " : " + typeName; - } - - return field.getName(); - } - - private String correctTypeString(String str) { - String ret = str; - while (ret.startsWith("[")) { - ret = ret.substring(1).concat("[]"); - } - switch (ret.toCharArray()[0]) { - case 'Z': ret = "boolean".concat(ret.substring(1));break; - case 'B': ret = "byte".concat(ret.substring(1));break; - case 'C': ret = "char".concat(ret.substring(1));break; - case 'L': ret = ret.substring(1);break; - case 'D': ret = "double".concat(ret.substring(1));break; - case 'F': ret = "float".concat(ret.substring(1));break; - case 'I': ret = "int".concat(ret.substring(1));break; - case 'J': ret = "long".concat(ret.substring(1));break; - case 'S': ret = "short".concat(ret.substring(1));break; - } - return ret; - } - - public Object visitCollectionKeyMapping(DependantValue mapping, Object argument) { - return "key"; - } - - public Object visitComponentMapping(Component mapping, Object argument) { - return "element"; - } +/******************************************************************************* + * 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.hibernate.ui.view.views; + +import java.util.ResourceBundle; + +import org.hibernate.HibernateException; +import org.hibernate.cfg.Environment; +import org.hibernate.console.ConsoleConfiguration; +import org.hibernate.dialect.Dialect; +import org.hibernate.eclipse.console.workbench.TypeNameValueVisitor; +import org.hibernate.engine.Mapping; +import org.hibernate.mapping.Column; +import org.hibernate.mapping.Component; +import org.hibernate.mapping.DependantValue; +import org.hibernate.mapping.Property; +import org.hibernate.mapping.RootClass; +import org.hibernate.mapping.SimpleValue; +import org.hibernate.mapping.Subclass; +import org.hibernate.mapping.Table; +import org.hibernate.mapping.Value; +import org.jboss.tools.hibernate.ui.view.ViewPlugin; + +public class OrmModelNameVisitor /*implements IOrmModelVisitor*/ { + + static private String SPACE = " "; + static private String POINTER = " -> "; + + private ResourceBundle BUNDLE = ResourceBundle + .getBundle(OrmModelNameVisitor.class.getPackage().getName() + + ".views"); + + public OrmModelNameVisitor() { + super(); + } + + public Object visitDatabaseColumn(Column column, Object argument) { + + ConsoleConfiguration consoleConfiguration = (ConsoleConfiguration) argument; + Mapping mapping = consoleConfiguration.getConfiguration() + .buildMapping(); + + String dialectName = null; + Dialect dialect = null; + + String type = null; + try { + dialectName = consoleConfiguration.getConfiguration().getProperty( + Environment.DIALECT); + dialect = (Dialect) Class.forName(dialectName).newInstance(); + type = column.getSqlType(dialect, mapping); + } catch (HibernateException e) { + ViewPlugin.getDefault().logError(e); + // ViewPlugin.getDefault().showError("Error", e); + } catch (InstantiationException e) { + ViewPlugin.getDefault().logError(e); + } catch (IllegalAccessException e) { + ViewPlugin.getDefault().logError(e); + } catch (ClassNotFoundException e) { + ViewPlugin.getDefault().logError(e); + } + + StringBuffer name = new StringBuffer(); + name.append(column.getName()); + + name.append(" ["); + name.append(type != null ? type.toUpperCase() : ""); + name.append(column.isNullable() ? " Nullable" : ""); + name.append(HibernateUtils.getTable(column) != null + && HibernateUtils.isPrimaryKey(column) ? " PK" : ""); + name.append(HibernateUtils.getTable(column) != null + && HibernateUtils.isForeignKey(column) ? " FK" : ""); + name.append("]"); + + return name.toString(); + + } + + public Object visitPersistentClass(RootClass clazz, Object argument) { + + StringBuffer name = new StringBuffer(); + name.append(clazz.getEntityName() != null ? clazz.getEntityName() : clazz.getClassName()); + + Table table = clazz.getTable(); // upd tau 06.06.2005 + if (table != null) { + String tableName = HibernateUtils.getTableName(table); + if (tableName != null) { + name.append(POINTER); + name.append(tableName); + } + } + + return name.toString(); + } + + public Object visitTable(Table table, Object argument) { + StringBuffer name = new StringBuffer(); + name.append(HibernateUtils.getTableName(table)); + return name.toString(); + } + + public Object visitPersistentClass(Subclass clazz, Object argument) { + + StringBuffer name = new StringBuffer(); + name.append(clazz.getEntityName()); + + Table table = clazz.getTable(); + if (table != null) { + String tableName = HibernateUtils.getTableName(table); + if (tableName != null) { + name.append(POINTER); + name.append(tableName); + } + } + + return name.toString(); + } + + public Object visitPersistentField(Property field, Object argument) { + StringBuffer name = new StringBuffer(); + name.append(field.getName()); + name.append(BUNDLE.getString("OrmModelNameVisitor.Colon")); + String typeString = null; + + try { + typeString = field.getType().getReturnedClass().getName(); + } catch (Exception e) { + if (field.getValue() instanceof Component) { + typeString = ((Component)field.getValue()).getComponentClassName(); + } else if (field.getValue().isSimpleValue()) { + typeString = ((SimpleValue)field.getValue()).getTypeName(); + } + } + + + + if (typeString != null) { + typeString = correctTypeString(typeString); + name.append(SPACE); + name.append(typeString); + } + +// return name.toString(); + + Value value = field.getValue(); + String typeName = (String) value.accept(new TypeNameValueVisitor(false)); + + if (typeName!=null) { + return field.getName() + " : " + typeName; + } + + return field.getName(); + } + + private String correctTypeString(String str) { + String ret = str; + while (ret.startsWith("[")) { + ret = ret.substring(1).concat("[]"); + } + switch (ret.toCharArray()[0]) { + case 'Z': ret = "boolean".concat(ret.substring(1));break; + case 'B': ret = "byte".concat(ret.substring(1));break; + case 'C': ret = "char".concat(ret.substring(1));break; + case 'L': ret = ret.substring(1);break; + case 'D': ret = "double".concat(ret.substring(1));break; + case 'F': ret = "float".concat(ret.substring(1));break; + case 'I': ret = "int".concat(ret.substring(1));break; + case 'J': ret = "long".concat(ret.substring(1));break; + case 'S': ret = "short".concat(ret.substring(1));break; + } + return ret; + } + + public Object visitCollectionKeyMapping(DependantValue mapping, Object argument) { + return "key"; + } + + public Object visitComponentMapping(Component mapping, Object argument) { + return "element"; + } } \ No newline at end of file

18 years

1
0
0 / 0

JBoss Tools SVN: r5201 - trunk/documentation/guides/userguide/GettingStartedGuide/en/modules.

by jbosstools-commits＠lists.jboss.org

Author: afedosik Date: 2007-12-03 11:05:10 -0500 (Mon, 03 Dec 2007) New Revision: 5201 Modified: trunk/documentation/guides/userguide/GettingStartedGuide/en/modules/manage.xml Log: http://jira.jboss.com/jira/browse/RHDS-292 section 2.2 renaming Modified: trunk/documentation/guides/userguide/GettingStartedGuide/en/modules/manage.xml =================================================================== --- trunk/documentation/guides/userguide/GettingStartedGuide/en/modules/manage.xml 2007-12-03 16:01:38 UTC (rev 5200) +++ trunk/documentation/guides/userguide/GettingStartedGuide/en/modules/manage.xml 2007-12-03 16:05:10 UTC (rev 5201) @@ -110,8 +110,10 @@ </section> <section id="JBossInstances"> <?dbhtml filename="JBossInstances.html"?> - <title>How to Manage JBoss AS Instances in JBDS</title> - <para>Although JBoss Developer Studio works closely with <property>JBoss EAP 4.2</property> we do not ultimately tie you to any particular server for deployment. There are some servers that Studio supports directly (via the bundled Eclipse WTP plug-ins). Suppose you want to deploy the application to <property>JBoss 4.2.1 server</property>. First of all you need to install it.</para> + <title>How to Use Your Own JBoss AS Instance with JBDS</title> + <para>Although JBoss Developer Studio works closely with <property>JBoss EAP 4.2</property> we do not ultimately tie you to any particular server for deployment. There are some servers that Studio supports directly (via the bundled Eclipse WTP plug-ins). + + In this section we discuss how to manage self-installed JBoss AS. Suppose you want to deploy the application to <property>JBoss 4.2.1 server</property>. First of all you need to install it.</para> <section id="JBossInstalling"> <?dbhtml filename="JBossInstalling.html"?> <title>JBoss AS Installation</title>

18 years

1
0
0 / 0

JBoss Tools SVN: r5200 - trunk/hibernatetools/docs/reference.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-12-03 11:01:38 -0500 (Mon, 03 Dec 2007) New Revision: 5200 Modified: trunk/hibernatetools/docs/reference/build.xml Log: builds now are generated in the correct folder Modified: trunk/hibernatetools/docs/reference/build.xml =================================================================== --- trunk/hibernatetools/docs/reference/build.xml 2007-12-03 16:00:30 UTC (rev 5199) +++ trunk/hibernatetools/docs/reference/build.xml 2007-12-03 16:01:38 UTC (rev 5200) @@ -2,7 +2,7 @@  <property name="modulename" value="hibernatetools"></property> - <condition property="build.dir" value="${doc-root}/${modulename}" else="${basedir}/../../build/reference"> + <condition property="build.dir" value="${doc-root}/${modulename}" else="${basedir}/../build/reference"> <isset property="doc-root"/> </condition>

18 years

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-12-03 11:00:30 -0500 (Mon, 03 Dec 2007) New Revision: 5199 Modified: trunk/jsf/docs/userguide/en/modules/editors.xml Log: image view chapter is deleted Modified: trunk/jsf/docs/userguide/en/modules/editors.xml =================================================================== --- trunk/jsf/docs/userguide/en/modules/editors.xml 2007-12-03 15:32:53 UTC (rev 5198) +++ trunk/jsf/docs/userguide/en/modules/editors.xml 2007-12-03 16:00:30 UTC (rev 5199) @@ -1742,7 +1742,7 @@ </figure> </section> - <section id="ImageViewer"> +  <section id="XSDEditor"> <?dbhtml filename="XSDEditor.html"?> <title>XSD Editor</title>

18 years

1
0
0 / 0

JBoss Tools SVN: r5198 - trunk/jsf/docs/userguide/en/images/struts.

by jbosstools-commits＠lists.jboss.org

Author: ykryvinchanka Date: 2007-12-03 10:32:53 -0500 (Mon, 03 Dec 2007) New Revision: 5198 Added: trunk/jsf/docs/userguide/en/images/struts/struts_51.png Log: http://jira.jboss.com/jira/browse/RHDS-327 Visual guide. Screen added Added: trunk/jsf/docs/userguide/en/images/struts/struts_51.png =================================================================== (Binary files differ) Property changes on: trunk/jsf/docs/userguide/en/images/struts/struts_51.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream

18 years

1
0
0 / 0

JBoss Tools SVN: r5197 - trunk/as/docs/reference/en/modules.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-12-03 10:07:16 -0500 (Mon, 03 Dec 2007) New Revision: 5197 Modified: trunk/as/docs/reference/en/modules/modules.xml trunk/as/docs/reference/en/modules/perspective.xml trunk/as/docs/reference/en/modules/runtimes_servers.xml trunk/as/docs/reference/en/modules/webtools.xml Log: http://jira.jboss.com/jira/browse/RHDS-279 Modified: trunk/as/docs/reference/en/modules/modules.xml =================================================================== --- trunk/as/docs/reference/en/modules/modules.xml 2007-12-03 15:01:26 UTC (rev 5196) +++ trunk/as/docs/reference/en/modules/modules.xml 2007-12-03 15:07:16 UTC (rev 5197) @@ -2,17 +2,17 @@ <chapter id="modules"> <title>Deploying Modules</title> -<para>In this chapter it will be described how to deploy modules onto the server</para> +<para>In this chapter it will be described how to deploy modules onto the server.</para> <para> - Deploying to a server is mostly painless. - There are several ways to do it provided by Webtools, - and some additional methods provided by JBoss Tools. </para> + First of all it is necessary to say that deploying to a server is mostly painless. + There are several ways to do it provided by WTP, + and some additional methods provided by JBoss Tools. These methods are discribed further in this chapter</para> <section><title>WTP Projects</title> <section><title>Run On Server</title> <para> - The first WTP method is to right-click on a webtools project, + The first WTP method is to right-click on a WTP project, such as a dynamic web project, ejb project, or ear project - and then selecting <emphasis><property>Run As > Run on Server</property></emphasis>. + and then select <emphasis><property>Run As > Run on Server</property></emphasis>. The resulting dialog allows you to select which supporting server the project can be published to. </para> <figure> @@ -23,7 +23,7 @@ </imageobject> </mediaobject> </figure> - <para>Click <emphasis><property>Next</property></emphasis> button to see add or remove projects page where you can choose propjects to configure them on server.</para> + <para>Click <emphasis><property>Next</property></emphasis> button to see add or remove projects page where you can choose projects to configure them on server.</para> <figure> <title>Add or Remove Projects</title> <mediaobject> @@ -60,7 +60,7 @@ </figure> <para> - If the selected module is a webtools project, + If the selected module is a WTP project, it will be published as in the <emphasis><property>Run on Server</property></emphasis> option, with a best-guess full package. If, however, the selected element is an archive from the <emphasis>Project Archives View</emphasis>, Modified: trunk/as/docs/reference/en/modules/perspective.xml =================================================================== --- trunk/as/docs/reference/en/modules/perspective.xml 2007-12-03 15:01:26 UTC (rev 5196) +++ trunk/as/docs/reference/en/modules/perspective.xml 2007-12-03 15:07:16 UTC (rev 5197) @@ -203,12 +203,12 @@ <section id="Project_archivesView"> <title>Project archives View</title> <para>Every application, whether plain old Java, J2EE, or some other language altogether, needs to be packaged in some way. In Java-related projects, - many people use ANT. JBoss Developer Studio comes with our own archives tool with a bit easier and less-verbose XML and a handy user interface.</para> + many people use ANT. JBoss Tools comes with our own archives tool with a bit easier and less-verbose XML and a handy user interface.</para> <para>The Project Archives plugin consists primarily of a view to set up each packaging configuration. Each project can enable or disable its builder, or depend on the global setting.</para> <para>The packaging configuration for each project is stored in that project's root folder, and is in a file named <property>.packages</property>, which has a fairly simple XML structure. Modifying the file by hand is neither required nor recommended, and using the UI is the official way of modifying your packaging structure.</para> <para>Aside from the builder, the other preferences for the plugin are mostly cosmetic, allowing you to show full or truncated paths, show the project at the - root, etc. None of these have any effect on the functionality of the packaging plugin.</para> + root, etc. None of these has any effect on the functionality of the packaging plugin.</para> <section id="Creating an archive"> <title>Creating an Archive</title> Modified: trunk/as/docs/reference/en/modules/runtimes_servers.xml =================================================================== --- trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-12-03 15:01:26 UTC (rev 5196) +++ trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-12-03 15:07:16 UTC (rev 5197) @@ -18,18 +18,18 @@  - <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 + <para>The JBoss AS plugin makes use of WTP. This includes starting and stopping servers in run or debug mode. It also includes + targeting WTP 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> + <title>WTP Runtimes</title> <para>In JBoss Tools, the main purpose of Server Runtimes is 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:</para> <itemizedlist> - <listitem><para>it provides classpath additions to webtools projects that require them.</para></listitem> + <listitem><para>it provides classpath additions to WTP projects that require them.</para></listitem> <listitem><para>For JBoss server at least, it provides information necessary for the starting and stopping of the server, it tells which jars to run and which configuration to use.</para></listitem> </itemizedlist> @@ -47,7 +47,7 @@ <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 JBoss Tools are the ones we will focus on.</para> + of runtime we want to create. Most of the runtime options are provided by WTP, but those provided by JBoss Tools are the ones we will focus on.</para> <figure> <title>Adding a Runtime</title> <mediaobject> @@ -56,9 +56,9 @@ </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, JBoss Tools 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 + <para>As seen above, there appear to be two JBoss categories. The first is contributed by WTP, and is a generic adapter that is not upkept very well. + For this reason, JBoss Tools provides updated and supported adapters of our own. There is one for each of JBoss 3.2, 4.0, and 4.2. You'll also note a deploy-only + runtime type. This type provides no classpath for WTP 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> @@ -81,14 +81,14 @@ <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>After pressing finish, you'll see that your new runtime has been added to the list and can now be targeted by WTP type projects or servers, both of which we'll get to later.</para> </section> </section> <section> - <title>Webtools Servers</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) + <title>WTP Servers</title> + <para>WTP 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> Modified: trunk/as/docs/reference/en/modules/webtools.xml =================================================================== --- trunk/as/docs/reference/en/modules/webtools.xml 2007-12-03 15:01:26 UTC (rev 5196) +++ trunk/as/docs/reference/en/modules/webtools.xml 2007-12-03 15:07:16 UTC (rev 5197) @@ -1,14 +1,14 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="webtools"> - <title>Webtools Projects</title> + <title>WTP Projects</title> <para>This chapter covers how to select installed runtime/server in your web project</para> <section><title>Description</title> <para> - Webtools provides what are called "faceted" projects. + WTP provides what are called "faceted" projects. Their most popular of these projects are their J2EE projects, such as their <property>Dynamic Web Project</property>, their EJB Project, - or their EAR project. Web projects of JBoss Tools are: Stuts, JSF and Seam projects.</para> + or their EAR project. Web projects of JBoss Tools are Stuts, JSF and Seam projects.</para> <para> The idea behind faceted projects is that each project can accept units of functionality, or facets, which can be

18 years

1
0
0 / 0

JBoss Tools SVN: r5196 - in trunk/seam/docs/reference/en: modules and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: afedosik Date: 2007-12-03 10:01:26 -0500 (Mon, 03 Dec 2007) New Revision: 5196 Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards10.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards11.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards12.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards13.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards14.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards15.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards16.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards17.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards7.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards8.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards9.png Removed: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards3.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards6_1.png Modified: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards2.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards4.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards5.png trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards6.png trunk/seam/docs/reference/en/modules/seam_wizards.xml Log: http://jira.jboss.com/jira/browse/RHDS-289 Seam Wizards chapter update Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards10.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards11.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards11.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards12.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards12.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards13.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards13.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards14.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards14.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards15.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards15.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards16.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards16.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards17.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards17.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards2.png =================================================================== (Binary files differ) Deleted: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards3.png =================================================================== (Binary files differ) Modified: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards4.png =================================================================== (Binary files differ) Modified: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards5.png =================================================================== (Binary files differ) Modified: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards6.png =================================================================== (Binary files differ) Deleted: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards6_1.png =================================================================== (Binary files differ) Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards7.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards8.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards9.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/seam_wizards/seam_wizards9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/seam/docs/reference/en/modules/seam_wizards.xml =================================================================== --- trunk/seam/docs/reference/en/modules/seam_wizards.xml 2007-12-03 14:39:35 UTC (rev 5195) +++ trunk/seam/docs/reference/en/modules/seam_wizards.xml 2007-12-03 15:01:26 UTC (rev 5196) @@ -15,10 +15,10 @@ for creating various common Seam components:</para> <itemizedlist> - <listitem><para>Seam Action</para></listitem> - <listitem><para>Seam Form</para></listitem> - <listitem><para>Seam Entity</para></listitem> - <listitem><para>Seam Conversation</para></listitem> + <listitem><para><property>Seam Action</property></para></listitem> + <listitem><para><property>Seam Form</property></para></listitem> + <listitem><para><property>Seam Entity</property></para></listitem> + <listitem><para><property>Seam Conversation</property></para></listitem> </itemizedlist> <para>Go to <emphasis><property>File > New</property></emphasis> and select the component wizard.</para> @@ -33,115 +33,222 @@ </figure> <para>The wizards create multiple resources and place it in the appropriate folders depending on your project structure (WAR or EAR).</para> + <para>Let's create a WAR project using the New Seam Project wizard.</para> + + <figure> + <title>Seam Project WAR Deployment</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_wizards/seam_wizards2.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>After the project is created you need deploy it on server.</para> + <section id="seam_action"> <title>New Seam Action</title> - + <para>To create a New Seam Action you should select a necessary project, type a name for <property>Seam component</property>, <property>POJO class</property>, - <property>Method</property>, <property>Page</property> and select a <property>Package</property> using <emphasis><property>Browse</property></emphasis> button.</para> - - <para>WAR deployment:</para> - + <property>Method</property>, <property>Page</property> and select a <property>Package</property> using <emphasis><property>Browse</property></emphasis> button.</para> + <figure> <title>New Seam Action Wizard</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_wizards/seam_wizards2.png"/> + <imagedata fileref="images/seam_wizards/seam_wizards4.png"/> </imageobject> </mediaobject> </figure> - <para>The wizard for EAR deployment differs from WAR in <property>Local interface</property> and <property>Bean</property> fields so you need to fill them in.</para> + <para>You can see the action page in <property>WebContent</property> folder. Click on it to open in JBoss Tools HTML Editor.</para> - <para>EAR deployment:</para> - + <figure> + <title>Action Page in JBoss Tools HTML Editor.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_wizards/seam_wizards5.png"/> + </imageobject> + </mediaobject> + </figure> + + + <note> + <title>Note:</title> + <para>You don't need to restart the server to see how the action component works. Just use context menu + <emphasis><property>Run As > Run On Server</property>.</emphasis></para> + </note> + + <para>Action component was hot-deployed. Forms and Conversations will work the same way.</para> + <figure> - <title>New Seam Action Wizard</title> + <title>Action Component</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_wizards/seam_wizards3.png"/> + <imagedata fileref="images/seam_wizards/seam_wizards6.png"/> </imageobject> </mediaobject> </figure> + + </section> <section id="seam_form"> <title>New Seam Form</title> - - <para>To create a New Seam Form you should select a necessary project, type a name for <property>Seam component</property>, <property>POJO class</property>, + + <para>Click on <property>actionMethod</property> in the internal browser and add a form in your project using the New Seam Form wizard + <emphasis><property>File > New > Seam Form</property>.</emphasis></para> + <para>Select a necessary project, type a name for <property>Seam component</property>, <property>POJO class</property>, <property>Method</property>, <property>Page</property> and select a <property>Package</property> using <emphasis><property>Browse</property></emphasis> button.</para> - - <para>WAR deployment:</para> - <figure> <title>New Seam Form Wizard</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_wizards/seam_wizards4.png"/> + <imagedata fileref="images/seam_wizards/seam_wizards7.png"/> </imageobject> </mediaobject> </figure> + <para>The Form Page was created in <property>WebContent</property> folder.</para> - <para>The wizard for EAR deployment differs from WAR in <property>Local interface</property> and <property>Bean</property> fields so you need to fill them in.</para> - <para>EAR deployment is:</para> - - <figure> - <title>New Seam Form Wizard</title> + <figure> + <title>Form Page in JBoss Tools HTML Editor.</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_wizards/seam_wizards4_1.png"/> + <imagedata fileref="images/seam_wizards/seam_wizards8.png"/> </imageobject> </mediaobject> </figure> - </section> - <section id="seam_entity"> - <title>New Seam Entity</title> + <para>Deploy the form on server. Right click on Form Page, select <emphasis><property>Run As > Run On Server</property>.</emphasis></para> - <para>To create New Seam Entity you should select a necessary project, type a name for <property>Entity class</property>, select a - <property>Package</property> using <emphasis><property>Browse</property></emphasis> button, type a name for <property>Master Page</property> and <property>Page</property>.</para> - <figure> - <title>New Seam Entity Wizard</title> + <title>Form Component</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_wizards/seam_wizards5.png"/> + <imagedata fileref="images/seam_wizards/seam_wizards9.png"/> </imageobject> </mediaobject> </figure> - - </section> + + <para>Form component was hot-deployed.</para> + + </section> + <section id="seam_conversation"> <title>New Seam Conversation</title> - <para>To create a New Seam Conversation you should select a necessary project, type a name for <property>Seam component</property>, <property>POJO class</property>, + <para>Enter some value in the text field (e.g. <property>value1</property>) and click on <property>formMethod</property>.</para> + <para>Add a conversation using the New Seam Conversation wizard + <emphasis><property>File > New > Seam Form</property>.</emphasis></para> + <para>You should select a necessary project, type a name for <property>Seam component</property>, <property>POJO class</property>, <property>Method</property>, <property>Page</property> and select a <property>Package</property> using <emphasis><property>Browse</property></emphasis> button.</para> + - <para>WAR deployment:</para> - <figure> <title>New Seam Conversation Wizard</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_wizards/seam_wizards6.png"/> + <imagedata fileref="images/seam_wizards/seam_wizards10.png"/> </imageobject> </mediaobject> </figure> - <para>The wizard for EAR deployment differs from WAR in <property>Local interface</property> and <property>Bean</property> fields so you need to fill them in.</para> - <para>EAR deployment:</para> + <para>Conversation page was created in <property>WebContent</property> folder.</para> + + <figure> + <title>Conversation Page in JBoss Tools HTML Editor.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_wizards/seam_wizards11.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Right click on Conversation page, select <emphasis><property>Run As > Run On Server</property>.</emphasis></para> + <figure> - <title>New Seam Conversation Wizard</title> + <title>Conversation Component</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_wizards/seam_wizards6_1.png"/> + <imagedata fileref="images/seam_wizards/seam_wizards12.png"/> </imageobject> </mediaobject> </figure> + <para>Conversation component was hot-deployed.</para> + <para>Click on <property>Begin</property> and <property>Increment</property> buttons to check the conversation functionality.</para> + </section> + + + <section id="seam_entity"> + <title>New Seam Entity</title> + + <para>Entities cannot be hot-deployed, so we need to stop the server.</para> + <para>Create an Entity using the New Entity wizard <emphasis><property>File > New > Seam Entity</property>.</emphasis> </para> + + <para>You should select a necessary project, type a name for <property>Entity class</property>, select a + <property>Package</property> using <emphasis><property>Browse</property></emphasis> button, type a name for <property>Master Page</property> and <property>Page</property>.</para> + + <figure> + <title>New Seam Entity Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_wizards/seam_wizards13.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>The Master Page and the Entity were created in <property>WebContent</property> folder.</para> + + <figure> + <title>Master Page in JBoss Tools HTML Editor.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_wizards/seam_wizards14.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>The Entity page is:</para> + + <figure> + <title>Entity Page in JBoss Tools HTML Editor.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_wizards/seam_wizards15.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Run the Entity page on server. This is what you get:</para> + + <figure> + <title>Customer Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_wizards/seam_wizards16.png"/> + </imageobject> + </mediaobject> + </figure> + + </section> + + <para>Let's create two customers <property>c1</property> and <property>c2</property>. Enter the name in the text field and press the <property>Save</property> button. + Customer should be successfully created. Press <property>Done</property>. Do the same for <property>c2</property> customer. The result should be:</para> + + <figure> + <title>Two Customers Are Created</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_wizards/seam_wizards17.png"/> + </imageobject> + </mediaobject> + </figure> + + </chapter>

18 years

1
0
0 / 0

JBoss Tools SVN: r5195 - in trunk/jbpm/docs/reference/en/images: Test_Drive_Proc and 3 other directories.

by jbosstools-commits＠lists.jboss.org

Author: sabrashevich Date: 2007-12-03 09:39:35 -0500 (Mon, 03 Dec 2007) New Revision: 5195 Modified: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_1.png trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_2.png trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_1.png trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_2.png trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_3.png trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_4.png trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_5.png trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour1.png trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour2.png trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour4.png trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour5.png trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour6.png trunk/jbpm/docs/reference/en/images/runtime_installation/runtime_installation1.png Log: http://jira.jboss.com/jira/browse/RHDS-325 changed RHDS icons and dialogs title bars names on screenshots Modified: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_1.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_2.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_1.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_2.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_3.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_4.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/Test_Drive_Proc/test_driv_proc_5.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour1.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour2.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour4.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour5.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/guided_tour_jboss_jbpmgpd/guided_tour6.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en/images/runtime_installation/runtime_installation1.png =================================================================== (Binary files differ)

18 years

1
0
0 / 0

JBoss Tools SVN: r5194 - trunk/common/plugins/org.jboss.tools.common.model/resources/help.

by jbosstools-commits＠lists.jboss.org

Author: akazakov Date: 2007-12-03 09:28:23 -0500 (Mon, 03 Dec 2007) New Revision: 5194 Modified: trunk/common/plugins/org.jboss.tools.common.model/resources/help/keys-model.properties Log: http://jira.jboss.com/jira/browse/JBIDE-1315 "JBoss Tools" instead of "Red Hat" in warning message Modified: trunk/common/plugins/org.jboss.tools.common.model/resources/help/keys-model.properties =================================================================== --- trunk/common/plugins/org.jboss.tools.common.model/resources/help/keys-model.properties 2007-12-03 14:23:34 UTC (rev 5193) +++ trunk/common/plugins/org.jboss.tools.common.model/resources/help/keys-model.properties 2007-12-03 14:28:23 UTC (rev 5194) @@ -439,7 +439,7 @@ SharableEditors.tabWidth=Displayed tab width SharableEditors.replaceTab=Insert space for tabs SharableEditors.selectSourceTab=Use Source tab as a default for mutli-tab editors -SharableEditors.natureWarning=Show warning when project has no Red Hat capabilities +SharableEditors.natureWarning=Show warning when project has no JBoss Tools capabilities SharableEditors.natureWarning.message=In order to use the full power of JBoss Tools editors (including any GUI tabbed viewers), the current project needs to have an JBoss Tools capabilities (for instance, JBoss Tools JSF or JBoss Tools Struts) associated with it. SharableEditors.natureWarning.jsf.message=In order to use the full power of Faces Config editor (including Diagram and Tree viewers), the current project needs to have JSF capabilities associated with it. SharableEditors.natureWarning.struts.message=In order to use the full power of Struts Config editor (including GUI tabbed viewers), the current project needs to have Struts capabilities associated with it.

18 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits December 2007