| <?xml version="1.0" encoding="UTF-8"?> |
| <faq xmlns="http://www.eclipse.org/webtools/faq" |
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
| xsi:schemaLocation="http://www.eclipse.org/webtools/faq schemas/faq.xsd" |
| name="eclipse web tools platform faq"> |
| <about> |
| Many of the FAQ's found on this page have been pulled from the <a href="../community/community.html#help">WTP newsgroup</a>. Thank you to everyone that took |
| the time to answer these questions. |
| </about> |
| <category name="General" /> |
| <category name="Data Tools" /> |
| <category name="J2EE"/> |
| <category name="Server/Internet" /> |
| <category name="Web"/> |
| <category name="Web Services"/> |
| <category name="XML" /> |
| <entry category="General" id="about_1"> |
| <question>How is the Eclipse Web Tools Platform licensed?</question> |
| <answer> |
| The Eclipse Web Tools Platform consists of software produced by the |
| Eclipse Project combined with third party software from other open |
| source projects. The software produced by the Eclipse Project is made |
| available under the <a href="http://www.eclipse.org/legal/epl-v10.html">Eclipse |
| Public License</a>. Third party components are made available under |
| their own licenses. The detailed licensing information can be found in |
| the <a href="http://www.eclipse.org/legal/epl/notice.html">Eclipse.org |
| Software User Agreement</a> (notice.html) file in the root directory of |
| the SDK download. Licensing for third party components is described in |
| about.html files in the respective subdirectories. |
| </answer> |
| </entry> |
| <entry id="about_2" category="General"> |
| <question >Who are the contributors to the Eclipse Web Tools Platform Project?</question> |
| <answer> |
| We have a <a href="../people/contributors.html">whole page</a> |
| listing the hard working contributors to this project. See the |
| <a href="CommitterFAQ.html">Committer FAQ</a> if you are a committer. |
| </answer> |
| </entry> |
| <entry id="about_3" category="General"> |
| <question>What version of Eclipse does WTP work with?</question> |
| <answer> |
| WTP 0.7 works with Eclipse 3.1.<br/> |
| WTP 1.0 currently plans to support Eclipse 3.1.x.<br/> |
| To use WTP with Eclipse 2.1.x see the alphaWorks project <a href="http://www.alphaworks.ibm.com/tech/webtools" target="_top">IBM Web Tools for Eclipse</a>. |
| </answer> |
| </entry> |
| <entry id="about_5" category="General"> |
| <question>Which zip file should I download?</question> |
| <answer> |
| The WTP SDK (wtp-sdk-*.zip) includes both the <a href="http://eclipse.org/webtools/wst/main.html">Web Standard Tools</a> |
| and <a href="http://eclipse.org/webtools/jst/main.html">J2EE Standard Tools</a>, |
| including source and both user and programmer documentation. <b>If you |
| aren't sure which download you need, you should probably get this one.</b><br/><br/> |
| The software development kit (SDK) downloads are for developers |
| wishing to build solutions on top of the Web Tools Platform, while the |
| non-SDK (e.g.: wtp-0.7.zip) downloads are suitable for everyone else's use. The |
| project also provides separate builds of the |
| <a href="http://eclipse.org/webtools/wst/main.html">Web Standard Tools</a> |
| (wtp-wst-*.zip) by themselves for those uninterested in the tooling for J2EE standards. |
| </answer> |
| </entry> |
| <entry id="about_6" category="General"> |
| <question>How do I install WTP?</question> |
| <answer> |
| <ul> |
| <li><a href="http://www.eclipse.org/webtools/development/updatesite/updatesite.html">Automatic installation using the Update Manager in Eclipse 3.1</a></li> |
| <br/><br/> |
| <li>Manual installation<br/> |
| The Web Tools Platform has several required projects that must all be |
| installed for proper operation. Each WTP |
| <a href="http://download.eclipse.org/webtools/downloads/" target="_top">build</a> is |
| built and tested with specific versions of these "prereqs" (the |
| <i>Requirements</i> section) and it's |
| recommended that only those versions be installed and active when used |
| with a particular WTP build. The WTP download page for each build |
| details the complete list of requirements and provides links to download the |
| supported versions. Downloading and unpacking each should place |
| its contents into a folder named <b>eclipse</b>. |
| <ol> |
| <li>Unpack the Eclipse SDK</li> |
| <li>Unzip the Graphical Editor Framework (GEF)</li> |
| <li>Unzip the Eclipse Modeling Framework (EMF) / XML Schema Infoset Model (XSD) / Service Data Objects (SDO)</li> |
| <li>Unzip the Java EMF Model (JEM) from the Visual Editor Project</li> |
| <li>Unzip the Web Tools Platform build into the same location</li> |
| </ol> |
| WTP should now be installed. Launch Eclipse with the <i>-clean</i> |
| option one time to ensure all plugins are detected properly.<br/><br/> |
| <i>The identical version of the full |
| VE-SDK may be substituted for the listed JEM-SDK version if you wish to |
| use the Visual Editor and the Web Tools Platform at the same time. |
| </i><br/><br/> |
| |
| A <a href="http://www.eclipse.org/org/june05release/screencasts/5-webToolsInstallation/webToolsInstallation.html" target="_top"> |
| screencast</a> that includes setting up Xdoclet and a JBoss 3.x test server is also |
| available. |
| </li> |
| </ul> |
| </answer> |
| </entry> |
| <entry id="xml_1" category="XML"> |
| <question>How do I use my own filename extensions in the XML editor? It only works correctly if a file ends with .xml.</question> |
| <answer> |
| <i>Note: this also applies to the JSP and HTML editors and others in WTP</i><br/><br/> |
| Earlier versions of Eclipse only allowed users to associated editors |
| with custom file names using the <i>File Associations</i> preference page. |
| Eclipse 3.1 supports a more flexible notion of <i>Content |
| Types</i> that allows more than just editors to treat custom-named files |
| as XML, for example. Instead of using the <i>File Associations</i> preference page, |
| add the filename extension to the new <i>Content Types</i> preference page. |
| Doing so "teaches" Eclipse about that filename extension so that features |
| such as Validation and Task Tag detection also support those files correctly.<br/><br/> |
| See the |
| <a href="http://download.eclipse.org/eclipse/downloads/drops/R-3.1-200506271435/eclipse-news-part1.html" target="_top"> |
| Eclipse 3.1 New and Noteworthy</a> section regarding <i>Editor lookup |
| based on content type</i> for more information. |
| </answer> |
| </entry> |
| <entry category="Server/Internet" id="server_1"> |
| <question>Where are cached files located?</question> |
| <answer> |
| The cached files are located in WORKSPACE_DIR/.metadata/.plugins/org.eclipse.wst.internet.cache. |
| The entries are all named with numbers but you can see the mappings in the |
| cache.xml file located in the same directory. |
| </answer> |
| </entry> |
| <entry category="Server/Internet" id="server_2"> |
| <question>How do I debug JSPs with BEA WebLogic Server 8.x?</question> |
| <answer> |
| BEA WebLogic Server 8.x and earlier do not support JSR-45; WebLogic Server 9.x and later |
| do support JSR-45 so you can debug JSP files with them using WTP (note: there are outstanding issues with JSP |
| source lookup for the WLS Generic adapter in 0.7 - see |
| <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=104401" target="_top">bug 104401</a>). |
| </answer> |
| </entry> |
| <entry category="J2EE" id="j2ee_1"> |
| <question>Where can I find the New J2EE Web Module wizard?</question> |
| <answer> |
| J2EE Web Module has been renamed Dynamic Web Project. |
| </answer> |
| </entry> |
| <entry category="Web" id="web_1"> |
| <question>Why does the HTML editor show a validation error if I don't use closing </p> or </br> tags?</question> |
| <answer> |
| You're likely editing an XHTML file which requires that the file be well formed XML. |
| </answer> |
| </entry> |
| <entry category="XML" id="xml_2"> |
| <question>How do I programmatically add entries to the XML catalog?</question> |
| <answer> |
| The XML catalog extension point schema contains specific definitions of |
| how to use the extension point. You can view the schema <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/xml/plugins/org.eclipse.wst.xml.core/schema/catalogContributions.exsd?rev=1.4&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">here</a>.<br/> |
| <br/> |
| For easier viewing, checkout the org.eclipse.wst.xml.core plugin from the |
| repository and view this file with the Eclipse extension schema editor. |
| </answer> |
| </entry> |
| <entry category="J2EE" id="j2ee_2"> |
| <question>Does the WTP include a visual JSP editor?</question> |
| <answer> |
| There is no visual JSP editor today, although it's a frequently |
| requested enhancement. It's not currently in the plan for the 1.5 |
| release, but if someone wants to donate code or development time we'd |
| certainly be happy to take the contribution. |
| </answer> |
| </entry> |
| <entry category="Web Services" id="ws_1"> |
| <question>Can the WSDL validator be extended to validate extension elements, for example partnerLinks and properties from the WS-BPEL specification?</question> |
| <answer> |
| Yes! The WSDL validator has extension points (which should all be |
| considered internal, non-API at this point) which allow you to plug your |
| own extension validator for a given namespace into the WSDL validator.<br/> |
| <br/> |
| In this case, you can create a validator for the WS-BPEL namespace and |
| plug-it into the WSDL validator. Your validator will get called any time |
| an element from the WS-BPEL namespace is encountered.<br/> |
| <br/> |
| The WSDL <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/wsdl/plugins/org.eclipse.wst.wsdl.validation/src/wsdlvalidate/org/eclipse/wst/wsdl/validation/internal/wsdl11/http/HTTPValidator.java?rev=1.2&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">HTTP validator</a> |
| and <a href="http://dev.eclipse.org/viewcvs/index.cgi/wst/components/wsdl/plugins/org.eclipse.wst.wsdl.validation/src/wsdlvalidate/org/eclipse/wst/wsdl/validation/internal/wsdl11/soap/SOAPValidator.java?rev=1.2&cvsroot=WebTools_Project&content-type=text/vnd.viewcvs-markup" target="_top">SOAP validator</a> both use this extension mechanism. |
| To contribute your validator to the WSDL validator you need to specify an entry |
| in your plugin manifest as follows:<br/> |
| (I'm assuming http://schemas.xmlsoap.org/ws/2004/03/business-process/ is the BPEL namespace.)<br/> |
| <br/> |
| <extension point="org.eclipse.wst.wsdl.validation.wsdl11validator"><br/> |
|     <wsdl11validator<br/> |
|         class="org.example.WSBPELValidator"<br/> |
|         namespace="http://schemas.xmlsoap.org/ws/2004/03/business-process/"<br/> |
|         resourcebundle="wsbpelvalidator"/><br/> |
| </extension> |
| </answer> |
| </entry> |
| <entry id="data_1" category="Data Tools"> |
| <question>Where can I find the WTP Data Tools?</question> |
| <answer> |
| Select Window->Show View->Other...->Data. You can then open the Database Explorer and Data Output views. |
| </answer> |
| </entry> |
| <entry id="ws_2" category="Web Services"> |
| <question>Why does WTP produce errors for multiple import statements for the same namespace in WSDL 1.1?</question> |
| <answer> |
| The <a href="http://schemas.xmlsoap.org/wsdl/" target="_top">WSDL 1.1 schema</a> restricts |
| wsdl:import statements by specifying that they must contain unique |
| namespaces. This means one import per namespace per WSDL document. |
| </answer> |
| </entry> |
| <entry id="server_3" category="Server/Internet"> |
| <question>How do I debug JSPs with Apache Tomcat 4.x?</question> |
| <answer> |
| Apache Tomcat 4.x and earlier do not support JSR-45; Tomcat 5.x and later |
| do support JSR-45 so you can debug JSP files with them using WTP. |
| </answer> |
| </entry> |
| <entry id="web_2" category="Web"> |
| <question>Does WTP's JavaScript editor report syntax errors?</question> |
| <answer> |
| The JavaScript editor does not report syntax errors and the core teams have |
| no plans to add this for JavaScript. However, contributions are always welcome. |
| </answer> |
| </entry> |
| <entry id="j2ee_3" category="J2EE"> |
| <question>How do I install XDoclet in WTP?</question> |
| <answer> |
| To install XDoclet: |
| <ol> |
| <li>Download XDoctlet from <a href="http://sourceforge.net/project/showfiles.php?group_id=31602" target="_top"> |
| http://sourceforge.net/project/showfiles.php?group_id=31602</a>. |
| </li> |
| <li>Unzip XDoclet to a directory on your machine such as C:\XDoclet |
| </li> |
| <li>Specify the directory in which XDoclet is located in Window->Preferences->J2EE Annotations->XDoclet. |
| </li> |
| </ol> |
| </answer> |
| </entry> |
| <entry id="about_7" category="General"> |
| <question>Are there any WTP tutorials available?</question> |
| <answer> |
| Yes! See the <a href="../community/community.html#tutorials">WTP community page</a>. |
| </answer> |
| </entry> |
| <entry id="about_8" category="General"> |
| <question>What is New and Noteworthy in WTP 0.7?</question> |
| <answer> |
| <p>Refer to the <a href="../development/news/0.7.html">WTP 0.7 - New and Noteworthy</a> document |
| for what is new in WTP 0.7.</p> |
| </answer> |
| </entry> |
| <entry id="about_9" category="General"> |
| <question>Where can I find a list of known problems for WTP 0.7?</question> |
| <answer> |
| <p>Refer to the <a href="../development/news/0.7.html">WTP 0.7 - New and Noteworthy</a> document |
| for the list of known problems for WTP 0.7.</p> |
| </answer> |
| </entry> |
| <entry id="xml_3" category="XML"> |
| <question>Why does the XML catalog preference dialog only show URI Key type entry when no file is selected?</question> |
| <answer> |
| <p> |
| As Public ID and System ID are only applicable to DTD entity resolution in |
| order to see these options in addition to URI for the Key Type choice you must |
| first select a DTD file. |
| </p> |
| <p> |
| When you select an XSD file you will see Namespace Name and Schema Location for |
| the Key Type selection. |
| </p> |
| </answer> |
| </entry> |
| |
| </faq> |
