| <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> |
| <head> |
| <title>WTP bugzilla enhancement backlog - ordered by target milestone, priority, component</title> |
| <link rel="stylesheet" type="text/css" href="../milestone_plans/stylesheets/images/default_style.css"/> |
| <script src="../../popup.js" type="text/javascript"> |
| // script is linked |
| </script> |
| </head> |
| <body> |
| <table border="0" width="100%" cellPadding="2" cellSpacing="5"> |
| <tr> |
| <td> |
| <font class="indextop">WTP bugzilla enhancement backlog <br> - ordered by target milestone, priority, component</font> |
| <br/> |
| <font class="indexsub"/> |
| </td> |
| <td> |
| <br/> |
| </td> |
| <td width="28%"> |
| <img height="86" width="120" src="../milestone_plans/stylesheets/images/Idea.jpe"/> |
| </td> |
| </tr> |
| </table> |
| <table border="0" width="100%" cellPadding="2" cellSpacing="5"> |
| <tr> |
| <a name="Overall_Planning"> |
| <td rowspan="3" colSpan="2" bgColor="#0080c0" width="100%" align="left" valign="top"> |
| <b> |
| <font face="Arial,Helvetica"> |
| <font color="#ffffff">All Milestones</font> |
| </font> |
| </b> |
| </td> |
| </a> |
| </tr> |
| </table> |
| <table width="100%" cellspacing="5"> |
| <tr> |
| <td/> |
| </tr> |
| </table> |
| <tr> |
| <td> |
| <table> |
| <tr> |
| <td valign="top"> |
| <img height="16" border="0" nosave="" src="../milestone_plans/stylesheets/images/Adarrow.gif"/> |
| </td> |
| <td> |
| <b>---</b> |
| <ul> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92603"><description>[jst.ws] Support deployment of Axis Web services with JDK 1.5</description> |
| </a> |
| <font color="8080FF"> [high]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I get the following message when running a bottom up Web service creation scenario with Axis 1.1 and Tomcat 5.0 using the Sun JDK_1.5. IWAB0489E Error when deploying Web service to Axis runtime java.lang.NullPointerException --- Nested Exception --- java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.setProperty(SAX ParserImpl.java:395) at org.apache.axis.encoding.DeserializationContextImpl.parse(Deserializa tionContextImpl.java:246) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538) at org.apache.axis.Message.getSOAPEnvelope(Message.java:376) at org.apache.axis.client.Call.invokeEngine(Call.java:2583) at org.apache.axis.client.Call.invoke(Call.java:2553) at org.apache.axis.client.Call.invoke(Call.java:1672) at org.apache.axis.client.AdminClient.process(AdminClient.java:355) at org.apache.axis.client.AdminClient.process(AdminClient.java:334) at org.apache.axis.client.AdminClient.process(AdminClient.java:341) at org.apache.axis.client.AdminClient.process(AdminClient.java:292) at org.apache.axis.tools.ant.axis.AdminClientTask.execute(AdminClientTas k.java:308) at org.eclipse.jst.ws.internal.axis.consumption.core.command.AxisDeployC ommand.executeAntTask(AxisDeployCommand.java:111) Here is the java full version: java full version '1.5.0_01-b08' From the stack trace, it appears that Sun's Xerces is not compatible with Axis 1.1. The workaround would be to use JDK 1.4.x. (I'm running with '1.4.2'.) (sengpl@ca.ibm.com @ 2005-04-25 12:08) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95452"> |
| <description>[jst.jsp] add JSP "batch" validator to WTP</description> |
| </a> |
| <font color="8080FF"> [medium]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There is currently as-you-type source validation for JSP, but no batch validator (that adds problem markers to the problems view). Details need to be figured out to decide if we should be using a JSP compiler such as Jasper for more exact validation, or if our as-you-type approach would be sufficient for batch validation as well (which may be faster than using a JSP compiler...) If the batch validator is in place for JSP, we will get the desired 'gray' icons when a problem from the problems view is fixed in the live editor. (pavery@us.ibm.com @ 2005-05-16 16:30) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95454"> |
| <description>[jst.jsp] JSP should support variables declared by custom tags</description> |
| </a> |
| <font color="8080FF"> [medium]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Variables declared by a custom tag as defined in a TagExtraInfo class should be honored by the JSP editor. This either requires prereq-ing servlet.jar to get Taglib TagExtraInfo... APIs, or some kind of smart reflection to create these API classes at runtime. One problem w/ the prereq-ing approach is that the version of the APIs might not be the correct version that the user is actually running with... One problem I've run into with the reflection approach is that TagLibraryInfo is an abstract class, so I'm not able to reflect it (in any way that I know of). Need to resolve this stuff by M5. (pavery@us.ibm.com @ 2005-05-16 16:37) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91866"> |
| <description>[wst.xml] Schema-based Content Assist should be stricter</description> |
| </a> |
| <font color="8080FF"> [medium]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The content assist in the XML editor makes many more suggestions than might be expected, e.g. for a content model with a sequence (A?, B?, C?), the content assist will always suggest A, B and C regardless of the existing content (e.g. B and C may already be present). This means you can create invalid documents in no time at all. This turns out to be partly because AbstractContentAssistProcessor:1593 (in o.e.wst.xml.ui.internal.contentassist) hardcodes the value ModelQuery.EDIT_MODE_UNCONSTRAINED in all calls to getInsertActions, which returns actions for the legal completions. Setting the value to EDIT_MODE_CONSTRAINED_STRICT is better, but runs into a bug: the text used for starting the completion ('<') is erroneously considered #PCDATA, and so all suggestions are evaluated as invalid by the schema validator used to sieve away illegal suggestions (this happens in DOMValidator.createContentSpecification:144, in xml.core.internal.contentmodel.internal.util). Further, it seems that the DOMValidator determines if something is a valid insert by inserting it and validating the result. This is a problem if the content model requires a sequence of elements (e.g. (A, B, C)?). You will never be allowed to insert 'A' by the validator since A by itself is invalid. So this is really one enhancement request (stricter validation) and, should that suggestion be accepted, two bug reports. (slehmann@novell.com @ 2005-04-19 07:12) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92551"> |
| <description>[wst.xml] Allow extension or usage of XMLMultiPageEditor</description> |
| </a> |
| <font color="8080FF"> [medium]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Today XMLMultiPageEditor and all its 'relatives' are marked as internal API + not very much suited for extension. Thus its not possible to add pages to this editor nor redo what the XMLMultiPageEditorPart does since all its editors also are internal. My usecase is I want to add a multipageeditor like PDE has for plugin.xml and use the WTP xml editor in it - but this is not possible with any public API. (max.andersen@jboss.com @ 2005-04-25 03:55) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=77344"> |
| <description>[FAQ] List plug-in prereqs for using WTP</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> (bnfb@superboy.org @ 2004-10-30 18:17) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93543"> |
| <description>[J2EE Standard Tools] struts-config.xml should support code navigation</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I don't know which component this belongs so please forgive if it is in a bad component... The editor should of struts-config.xml should allow the navigation to the code through Ctrl+Click as in the Java editor. It should be possible to: - Ctrl+Click on an action type value and open the selected Action - Ctrl+Click on an action name value and open the selected class for the form (or jump to its definition and from there Ctrl+Click on the form-bean type value open the selected class) - Ctrl+Click on a forward path value and open the selected file (ric.almeida@gmail.com @ 2005-05-03 11:16) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96594"> |
| <description>[J2EE Standard Tools] Websphere server support</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I would like to have more application servers supported on 1.0 final version, in special Websphere 5-6. (luctor@gmail.com @ 2005-05-25 08:20) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=77568"> |
| <description>[Web Standard Tools] Update Management Extension</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> WTP should have a feature that allows tool/server-runtime developers to advertise their wtp-related software maintained outside the eclipse foundation. This feature should follow the 'plugin' pattern; it should be a extension that provides the URL of the updatable software and a list of WTP extension-points that it is related to. This will allow WTP tools to discover external software in a consistent and simple manner WTP can use this feature to provide users for clickable convenient access/installation of external software with minimal discovery effort. The feature would also allow tool providers to maintain their point releases without strong ties to WTP release process. (naci.dai@eteration.com @ 2004-11-03 02:36) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85251"> |
| <description>[Web Standard Tools] plugin documentation is missing</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Is it okay, that WebTools plugin doesn't contain no documentation? Or is it just not merged with Eclipse documentation yet? WebTools 1.0M2 (tomasz@rtsoftware.com @ 2005-02-15 08:22) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90728"> |
| <description>[Web Standard Tools] Investigate: Use single jar packaging</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core- home/documents/3.1/run_from_jars.html Eclipse 3.0 and previous was shipped such that each plug-in was a directory that contained code in a JAR, along with multiple other files. In order to improve the number of files that we ship along with the size of the Eclipse distributions, we would like to be able to ship each plug-in as a single JAR file containing its code and other resources. (jeffliu@ca.ibm.com @ 2005-04-07 17:34) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90730"> |
| <description>[Web Standard Tools] Investigate: Improve the performance of our resource bundles</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core- home/documents/3.1/message_bundles.html Standard Java ResourceBundles have quite inefficient space characteristics. Since a running Eclipse tends to have many externalized messages we have implemented a new message bundle story to be used in Eclipse. (jeffliu@ca.ibm.com @ 2005-04-07 17:37) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92587"> |
| <description>[Web Standard Tools] Performance Logs collected from WTP M4 Scenerios</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This is a meta-bug for gathering information about performance failures using the performance instrumentation. Attach your performance.log files to this bug. (david_williams@us.ibm.com @ 2005-04-25 10:55) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93328"> |
| <description>[Web Standard Tools] Set the "derived" file attribute for copied resources</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> WTP copies over all resources to the .deployables directory. Unfortunately, this causes them to be doubled in the 'Open Resource' view (Ctrl-Shift-R). It is easy to edit the wrong version (happened to me dozends of times), which means that your changes will never make it to version control (but they will appear in your development web server, which makes issue very nasty). If WTP would set the 'derived' file attribute on all copied resources, they would not appear doubled (except if the user checks 'show derived resources'). What do you think? (andreas@schildbach.de @ 2005-04-29 18:06) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96848"> |
| <description>[Web Standard Tools] Bundles, jarring, messages</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Very few plugins in WTP make use of performance and memory improvements in Eclipse v3.0 and v3.1: * Switch to pure bundles (manifest.mf) instead of plugins to save Eclipse startup and management overhead. * Jar up plugins to save disk footprint and install time. * Switch to Messages.properties to lower memory use and improve startup time. We need to slowly start doing each one of these across WTP to improve our performance and memory use. (deboer@ca.ibm.com @ 2005-05-26 14:58) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91792"> |
| <description>[documentation] separate jovadoc download</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Jeff, Currently, to see the javadoc in progress, we need to download the SDK build. It will be great if we can download javadoc in a separate zip file to see the document work in progress. (kboo@ca.ibm.com @ 2005-04-18 16:32) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81771"> |
| <description>[jst.jsp] Java templates not shown in scriptlet Content Assist</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> wtp-sdk-I20041221.zip Inside of a scriptlet: <% String foo = '5'; foo.toString(); int a[]; if| %> At the '|', I should see Java templates proposed. (nitind@us.ibm.com @ 2004-12-22 03:42) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81772"> |
| <description>[jst.jsp] Italic settings not honored in Java code sections</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> wtp-sdk-I20041221.zip Inside of a scriptlet: <% String foo = '5'; foo.toString(); int a[]; if| %> If I've set 'keywords excluding 'return'' to be italicized in the Java Syntax Coloring preferences, the JSP editor does not reflect this nor does it change colors immediately. (nitind@us.ibm.com @ 2004-12-22 03:43) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82308"> |
| <description>[jst.jsp] JSP scriplet sections should use Java preferences</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The edition of java code in jsp scriplet gives some useful functionalities, like compilation or code assists. But it seems to do not reuse the java editor preferences. I would like to have the same functionnalities and same comportement that I have when I edit a classic Java class. For example, keeping 'completion overwrites' or the 'automatically insert on correct position' the semicolon and braces would be more comfortable. It would be great if the java formatter could also work on java code in scriplets. In other words, the WTP project should integrate with existing functionality in the Eclipse base :) (chabert@fimasys.fr @ 2005-01-06 04:44) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82537"> |
| <description>[jst.jsp] It should be possible to define a style for the content of jsp delimeters too</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> In Window > Preferences > Web and XML > JSP Files > JSP Styles it is not possible to define style for the content of scriptlets e.g. <% this text here %> to make it possible to set it visually appart from other (html) content of a .jsp page for instance by choosing a background color. Currently it is only possible to define a style for Attribute Names, Attribute Values, Comment Content, Comment Delimiters, JSP Delimiters, Tag Delimiters and Tag Names. Missing are JSP Content (the stuff inside scriptlets, e.g. inside JSP Delimiters and inside Scriptlet Tags) and Tag Content (see the equal signs?). See attached screenshot. regards, Lars (lars.sonchocky-helldorf@interone.de @ 2005-01-11 05:42) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86169"> |
| <description>[jst.jsp] [ca] JSP Java content assist should auto-import necessary class</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> JSP Java content assist should auto-import a necessary package/class if a class is selected from content assist who is not imported already. In regular JSP syntax it would insert <%@page import='org.foo.Class'%> in XML-JSP syntax it would <jsp:directive.page import='org.foo.Class'/> These would probably be inserted at the top of the file (if that's convention) and under <jsp:root> if it's XML-JSP. (pavery@us.ibm.com @ 2005-02-22 12:57) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86656"> |
| <description>[jst.jsp] content assist for <%@page import=""%> would be nice</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be nice to have conent assist for <%@page import='|'%>, similar to what we have for <jsp:useBean class='|'>. (pavery@us.ibm.com @ 2005-02-25 11:49) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86841"> |
| <description>[jst.jsp] RFE: generate error on missing taglib-directive</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> When I delete the <%@ taglib...> directives of a JSP-document JST does not generate on error. Expected/recommended behaviour: E.g. with no taglib-directive in the page I would expect jst to generate an error if <bean:write name='item' property='yardProject' /> is used. Current behaviour: No error / warning is generated and the Tomcat servlet container throws a NullPointerException in _jspService() (holbitlan@gmx.de @ 2005-02-28 10:27) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88389"> |
| <description>[jst.jsp] Improve cursor position after inserting tag with required attirbute and no default value</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> 1. Create J2EE Web Project. 2. Place files from attachment to correspond project's folders. 3. Open index.jsp file, place cursor into body tag and ask for completion proposals by CTRL+SPACE. 4. Select a:tagName1 from list, so <a:tagName |action=''></a:tagName> is inserted. This is Ok, but cursor is located just before 'action' attribute. It's supposed to be inside 'action' attribute value. (dgolovin@exadel.com @ 2005-03-17 17:07) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95237"> |
| <description>[jst.jsp] add EL support for the JSP editor</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This bug is to track progress for initial EL support in the JSP Editor planned for M5. This will include: - syntax highlihting - content assist - error reporting - (some) auto edit More details to come. (pavery@us.ibm.com @ 2005-05-13 17:41) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95450"> |
| <description>[jst.jsp] add extract include file for JSP source refactoring</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be cool to have source 'refactoring' for extracting includes. It could work by: - highlighting desired text - possibly check if selection is valid - extract to the contents to another file - add static or dynamic include tag (pavery@us.ibm.com @ 2005-05-16 16:23) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96769"> |
| <description>[jst.jsp] Extendible content assist in JSP editor</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There are a lot of framevorks that require additional proposals are showed in proposal list for JSP tag attribute. For example, if JSF is used to build WEB application. There is a JSP page looks like: <!-- JSP begin --> <%@ taglib uri='http://java.sun.com/jsf/html' prefix='h' %> <%@ taglib uri='http://java.sun.com/jsf/core' prefix='f' %> <f:loadBundle basename='demo.bundle.Messages' var='Message'/> <HTML> <HEAD> <title>Input Name Page</title> </HEAD> <body bgcolor='white'> <f:view> <h1><h:outputText value='#{Message.inputname_header}'/></h1> <h:messages style='color: red'/> <h:form id='helloForm'> <h:outputText value='#{Message.prompt}'/> <h:inputText id='userName' value='|' required='true'> <f:validateLength minimum='2' maximum='20'/> </h:inputText> <h:commandButton id='submit' action='sayhello' value='Say Hello' /> </h:form> </f:view> </body> </HTML> <!-- JSP end --> Now if user is asking by CTRL+Space for proposal list in attribute value (position marked as | in line below) <h:inputText id='userName' value='|' required='true'> proposal list contains only implicit objects, but for this use-case, I'd like to add some managed beans from JSF configuration file and demo.bundle.Messages resource bundle keys to the proposal list. Now I can do this only using the internal API. This would be more convenient to use extension point or public API for this matter, so third-party vendors can use it. (dgolovin@exadel.com @ 2005-05-26 08:42) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=97089"> |
| <description>[jst.jsp] Add support for tagx extension.</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> jsp, jspx, jspf, tag, tag are supported and resolve to the JSAP editor. tagx -a tag file in jsp 2.0 xml syntax- is not part of the file associations. I would suggest to add it. There are the natural (pombredanne@nexb.com @ 2005-05-27 17:47) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82920"> |
| <description>[jst.server] Deployments don't support dependent projects</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> BAD: Auto server deployments don't support dependent projects. I wonder why JST can't support such a simple but important feature! (caozj@sunline.cn @ 2005-01-15 21:54) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88045"> |
| <description>[jst.server] Launching server with specific user</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I'm working on a linux OS, and I use JBoss as application server. Eclipse is running with my own user, as jboss runs with a specific jboss user (in order to be run by other user on my computer). The fact is that when I launch jboss with eclipse web tool server tools, it try to launch eclipse with my user. I would like to specify the user which launch the server (eg jboss user). A solution may be to add a parameter in front of the launching command line. In my case, it would be a 'sudo -u jboss' to execute the server with my jboss user. (chabert@fimasys.fr @ 2005-03-15 08:41) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90100"> |
| <description>[jst.server] JBoss 4.0.1 support</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be nice to be able to start and stop JBoss 4.0.1 from with in web tools. So, I created a server definition for it. Please see attachements. (eclipse@juddsolutions.com @ 2005-04-02 22:35) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96438"> |
| <description>[jst.server] Generic Server Support for WebLogic Server 9.0</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Patch org.eclipse.jst.server.generic.serverdefinitions plugin to include support for WebLogic Server 9.0 (rfrost@bea.com @ 2005-05-24 11:10) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88627"> |
| <description>[jst.ws] Webservice Explorer does not support Cookies</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I´ve tried to use the Webservice Explorer from WTP M3 with a Webservice that uses two cookies to work properly. At the first request (which is a login) the load balancing server sets a cookie with the server used for communication and a second cookie is set after I logged in at the webservice successfully. By using the TCP/IP Monitor I figured out that the Webservice Explorer ignores the cookies set by the webservice provider. (klaus.kierer@tiscover.com @ 2005-03-21 06:53) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89102"> |
| <description>[jst.ws] Plug Web service wizards into Web Service Consumer framework</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The Web Service client and skeleton wizards should be plugged into the Web service consumer framework (89085) so that the wizards can be launched from the Web Services Explorer. Detailed requirements and design are forthcoming in a design document, a link to which will be appended to this defect. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=89085 (cbrealey@ca.ibm.com @ 2005-03-25 10:30) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89103"> |
| <description>[jst.ws] Exploit Web Service Finder framework from WSDL selection page</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The WSDL selection page (page 2) of the Web Service wizard client and skeleton wizards should be updated to exploit the Web service finder framework (89084) to simplify the process of finding and selecting WSDL. Detailed requirements and design are forthcoming in a design document, a link to which will be appended to this defect. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=89084 (cbrealey@ca.ibm.com @ 2005-03-25 10:33) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89922"> |
| <description>[jst.ws] Support Axis Web service creation from EJBs</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Apache Axis supports the creation of Web services bottom-up from EJBs. The tools in WTP for Apache Axis should support this as well. Further details are forthcoming in a design document, a link to which will be added to this bug. (cbrealey@ca.ibm.com @ 2005-04-01 00:00) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89923"> |
| <description>[jst.ws] Support Axis JUnit testcase generation</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Apache Axis' WSDL2Java tool has support for generating JUnit tests via its '-t' or '-testcase' options. This should be plugged into the Web services framework as a kind of test facility, along side the Sample JSP generator and the Web services explorer. (cbrealey@ca.ibm.com @ 2005-04-01 00:04) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89924"> |
| <description>[jst.ws] Support generation of Axis clients to non-Web projects</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The current tools in WTP for generating Axis clients restricts their generation to Web projects/modules. The tools should allow the generation of Axis clients to other module types like EJB, Client-Application and plain Java. (cbrealey@ca.ibm.com @ 2005-04-01 00:06) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92294"> |
| <description>[jst.ws] Web Service creation wizard does not return newly created web service</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Web Service creation wizard does not return the newly created web service after clicking Finish button (because it does not use any data model but the dynamic wizard/WizardPageManager unlike EJB creation wizard). Hence there is no way to get the newly created web service from the wizard. For example, I want get the ServiceImplBean object reference from the wizard after creating java bean web service. Here is the snippet of code: DynamicWizard wizard = new DynamicWizard(); wizard.setInitialData('org.eclipse.jst.ws.creation.ui.wizard.serverwizard'); wizard.init( PlatformUI.getWorkbench(), new StructuredSelection(service)); WizardDialog dialog= new WizardDialog(PlatformUI.getWorkbench ().getActiveWorkbenchWindow().getShell(), wizard); dialog.create(); dialog.open(); //when user click the finish button I want to get the newly created ServiceImplBean from the wizard. (sdatta@ca.ibm.com @ 2005-04-21 17:08) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92828"> |
| <description>[jst.ws] Enhance Web service Server selection dialog/wizard ui</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This is in response to a comment. The server selection on page 3 should appear similarly in look and feel to the server tools' server selection/targeting UI. (sengpl@ca.ibm.com @ 2005-04-26 16:51) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93111"> |
| <description>[jst.ws] Performance: Use the Eclipse 3.1 message bundle facility</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Eclipse has created a new and more efficient message bundling mechanism. Here is a brief description: Standard Java ResourceBundles have quite inefficient space characteristics. Since a running Eclipse tends to have many externalized messages we have implemented a new message bundle story to be used in Eclipse. The mechanism is quite simple and completely generic - it can be used anywhere. Summary of the new approach: -vmessages.properties - this file is same as before except all keys need to be valid Java identifiers. -Each message file has a corresponding Java class. -Each key/value pair in the file has a public static String field whose name is the same as the message key. -When message bundles are loaded, the values of the fields are set to be the values from the messages.properties files. -The message properties files are purged from memory. -When creating a new message: create a field in your Messages.java file create a key/value pair in your messages.properties file where the key name matches the field name to reference the message, simply reference the field (e.g. Messages.my_key) rather than the standard lookup More info at: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform- core-home/documents/3.1/message_bundles.html (sengpl@ca.ibm.com @ 2005-04-28 08:46) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96812"> |
| <description>[jst.ws] Enhance Web service wizard to determine supported servers based on spec levels</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently Web service runtime extensions need to explicitly identify their supported servers by listing the server type ids. This means that when a new server is in the picture, the extension XML for the Web service has to be modified to include the new server's type id if the WS runtime wants to expose support for that server. This enhancement would allow to WS runtime to simply spec levels (servlet, JSP, ejb, J2EE) . The wizard would expose support for all servers that support those spec levels. The WS runtime would still be able use server type ids to state support for only certain servers or to exclude specific servers. Determining whether this enhancement is feasible for M5 requires a discussion with server tools team about whether they have (or could provide) API that lets us ask questions about whether a certain server type supported a certain spec. level. (rsinha@ca.ibm.com @ 2005-05-26 11:29) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82185"> |
| <description>[releng] map files should be automatically tagged each build</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> As long as we're discussing improving the build process ... I think the map files should be tagged with the build identifier for each build. Well, obviously more important for Milestones, less so for Integration builds, and not important for nightlies ... but if easier to do automatically each time, then I'd suggest tagging each automatically is better than not tagging any automatically, since the later is subject to someone remembering to do it for the important cases. (david_williams@us.ibm.com @ 2005-01-04 16:03) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82434"> |
| <description>[releng] Include Base Eclipse automated unit tests in WebTools unit tests</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Seems it would be 'good practice' to run base eclipse unit tests and performance tests, and, I guess pre-reqs automated tests (eventually) at the same time we run the webtools automated tests. I thought of this since there's been a few other bugs that apparently only happen 'in combination' with base things (e.g. conflicts between ant documents, and xml documents). I'm not sure the current tests would have caught those particular problems, but just seems like a good idea. The automated base performance tests, in particular, would be interesting to make sure base function runs at same rate whether or not WTP is added. (david_williams@us.ibm.com @ 2005-01-08 20:21) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82851"> |
| <description>[releng] Test scripts should be versioned/in map file</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently, the org.eclipse.wtp.releng/testScripts folder is not versioned. Whenever someone creates a new JUnit test and checks it into the HEAD stream, adding it to the test.xml file will cause it to show up in all builds, including the integration build. We need to have a way to allow JUnit plugins to be checked in or modified in the nightly builds, so that they can be tested and only moved to the integration build along with the corresponding code plugins. (deboer@ca.ibm.com @ 2005-01-14 11:11) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89366"> |
| <description>[releng] Add "extension point capabilities" to the Eclipse API scanner</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Here's a thread that discuss this issue: I think extension points and their related schemas should be part of the API definition. Component.xml does not cover them except in the case that you need to access a Java class or implement a Java interface. I agree that we need to expand our tool coverage to include extension points. Of course, there is still flexibility in declaring an extension point as API. Same goes for any resource that's included in a plug-in. For example, there may be a set of standard icons that we want people to use. Clearly we can't just delete those since it would break clients. Concerning our implementations of other APIs, I think we don't have to do anything since our implementations are already constrained by the semantics of the APIs they implement. We need to preserve that. I think there is a simple way to determine what we need to document as part of our 'API'. Just ask yourself, 'If I change this can I break clients?' If the answer is 'Yes' then we need to document how clients are allowed to use it, and we need to add tool support if possible to help us manage it. To get this process going, I'd like to ask Jeffrey to extend component.xml to include the declaration of extension points (and their schemas), and resources that we are proposing as API. Jeffrey, pls come up with a proposal and post it for review. Arthur Ryman, Rational Desktop Tools Development phone: +1-905-413-3077, TL 969-3077 assistant: +1-905-413-2411, TL 969-2411 fax: +1-905-413-4920, TL 969-4920 mobile: +1-416-939-5063, text: 4169395063@fido.ca intranet: http://labweb.torolab.ibm.com/DRY6/ David M Williams <david_williams@us.ibm.com> Sent by: wtp-dev-admin@eclipse.org 03/17/2005 01:27 PM Please respond to wtp-dev To wtp-dev@eclipse.org cc Subject [wtp-dev] Questions on component.xml There's probably already been discussion and answers provided for some questions that immediately came to my mind while starting (and just staring, mind you :) to define our component.xml files .... but figured if I didn't know the answer, perhaps it might be worth asking here so the answers would be repeated for everyone. One part of our API that gets focus in our component.xml files are classes or interfaces we implement that we want docs, junits, and java doc. That's clear enough. But what about extension points? That's a critical part of a specified API ... how are they represented in component.xml files? A more minor case is 'ids' ... there's some strings defined via plugins or extensions that we expect others to use as API (editor IDs, content menuIDs, are obvious cases). While these can sometimes be redundantly specified in JavaCode to be used as constants (eg. we've done that for our contentTypeIds) there's no hard and fast rule that it has to be, or that it is even always desirable. Its there a suggested way to capture these IDs which are not defined in Java Code? Lastly, the hardest, what about our implementations of other's interfaces? These may be some critical areas to have JUnit test coverage for, but as far as I can tell, that's a whole other problem not related to component.xml and our measurements? But in some cases we may need some amount of doc for? I see this strongly in org.w3c.dom API's ... since we have our own DOM implementation ... we don't expose our implementation as API per se, but we do expose it through the org.w3c.dom interface ... that is, obviously, we expect clients to write code to the org.w3c.dom interface which uses our implementation (our instance being obtained from one API, naturally). If this one is carried to extreme, I think we'd find thousands of cases where we implement base eclipse APIs (either interfaces, or subclassing such popular classes as 'Plugin', 'ITextEditor', etc). Are any of these 'implementations of others APIs' part of the component.xml files? [I don't think so, but its a pretty fine line, sometimes, or gives a distorted picture of 'coverage' if not]. Thanks for any advice. (jeffliu@ca.ibm.com @ 2005-03-29 11:14) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91587"> |
| <description>[releng] Component tool could check naming conventions too</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be a nice extra check on 'Eclipse quality code' if the component tool could check for some naming convention violations. For example, if component tool had a list of 'API Classes', then all other classes should have 'internal' in their name, or be default (package) access protected, or marked private. There might be other rules that could be checked, but thought I'd post this here as a general enhancement to consider. (david_williams@us.ibm.com @ 2005-04-15 14:49) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91599"> |
| <description>[releng] Best to have "X build declared" flag on webpage</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This was discussed on wtp-dev, and I see similar confusion on newsgroup, because we do I-build 'warm-ups' many people get an I-build as soon as its on download page, even though we haven't yet determined its suitability. Would be best to have some 'status' on build page, such as 'doing I-build warm-ups', which eventually changes to 'xxx build declared I-build', which would be 'manually' set by one of the project leaders. (david_williams@us.ibm.com @ 2005-04-15 15:50) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96465"> |
| <description>[releng] Performance: Pre-build help indexes to improve the performance of the help system</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Pre-build help indexes to improve the performance of the help system. Here's an example: https://bugs.eclipse.org/bugs/show_bug.cgi?id=91695 (jeffliu@ca.ibm.com @ 2005-05-24 13:18) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=96874"> |
| <description>[releng] API Tool "component" should be seperate from releng component</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Just thought I'd suggest, the API checking tools in releng could (probably) be put in its own component and then 'pulled' into the build, based on version in some map file, like we do other components. This has the advantage 1) that changes released to head would not effect I-build (until 'released'). 2) it would be a more re-usable tool for other teams that might want to make it part of their build process. (david_williams@us.ibm.com @ 2005-05-26 16:56) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=74782"> |
| <description>[website] Most wanted enhancements / most hated bugs</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I'd like to see two top lists either easily accessible from or placed directly on http://bugs.eclipse.org/bugs/. One should list the top N (20?) most voted for non-fixed enhancement requests. One should list the top N (20?) most voted for non-fixed bug reports. The point would be to make information about what's bothering people more accessible. (walles@mailblocks.com @ 2004-09-23 11:01) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89081"> |
| <description>[wst.command] Design a unified wizard/model/command framework</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There are currently two frameworks in WTP designed to help extenders of the platform create dynamic and extensible wizards, models and commands/operations. An effort is already underway to converge these frameworks, developed under the J2EE and Web services components, into one. This enhancement is being opened to track this work. A design document will be drafted and a link to it appended to this bug. (cbrealey@ca.ibm.com @ 2005-03-25 00:48) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93869"> |
| <description>[wst.common] Add a WTP startup performance test</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Add a WTP startup performance test (jeffliu@ca.ibm.com @ 2005-05-05 22:50) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86437"> |
| <description>[wst.css] RFE: Add captilization preference for selectors</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> (nitind@us.ibm.com @ 2005-02-24 02:09) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93445"> |
| <description>[wst.css] RFE: Add Template support to Content Assist and New Wizard</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The HTML component has support for Templates in its editor's Content Assist and in its New wizard. Could the same kind of support be added for CSS? (nitind@us.ibm.com @ 2005-05-02 15:41) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93446"> |
| <description>[wst.dtd] RFE: Add Template support to New DTD Wizard</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The HTML component has support for Templates in its editor's Content Assist and in its New wizard. Could the same kind of support be added at least in the New DTD wizard? (nitind@us.ibm.com @ 2005-05-02 15:42) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88442"> |
| <description>[wst.html] WYSIWYG HTML Editor</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Besides the structural HTML editor that already exists, it would be great to have a WYSIWYG (X)HTML editor. This editor could help in quickly designing (X)HTML documents from within Eclipse. The WYSIWYG HTML editing component could also be used in Rich Client applications that are Eclipse-based and thus would benefit a broad user base. There exists a WYSIWYG editing feature (work still in progress) in the GEF subproject (http://www.eclipse.org/gef/team/wysiwyg.html?cvsroot=Tools_Project) that could be used as a basis here. (tderflinger@gmx.net @ 2005-03-18 07:58) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94283"> |
| <description>[wst.internet] v1.1/2: TCP/IP monitor</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The TCP/IP monitor is similar to function provided by TPTP. I'm opening this bug to look at ways to make this function common in future releases - do we rely on TPTP, provide simple function in WTP that is extended by TPTP, or are there other options? We'll investigate post v1.0. (deboer@ca.ibm.com @ 2005-05-10 08:32) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86434"> |
| <description>[wst.javascript] RFE: Add Show In... target for Outline view</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> M3 test builds Show In... Outline is useful if Link with Editor is disabled. (nitind@us.ibm.com @ 2005-02-24 01:54) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88902"> |
| <description>[wst.javascript] Feature Request: More intelligent JS code outlining</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> As it stands, the Javascript editor (while useful) cannot properly outline OO-style javascript, e.g.: function foo(bar) { this.baz = bar; } foo.prototype.buz(bletch) { alert(this.baz + ': ' + bletch); } The current JS outliner doesn't see much - it recognizes foo as a global function, but does not show any of the arguments, members, or methods added to that function's prototype or instance. The Sourceforge JS editor (https://sourceforge.net/projects/jseditor/) actually has a fairly good outlining system which includes some (not all) of this desired functionality, but it would be really excellent to see this kind of thing make it into the WTE. (ctembreull@gmail.com @ 2005-03-23 13:42) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92331"> |
| <description>[wst.javascript] Need to document JavaScript parser generator procedure</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> In the interest of 'open' development, we should improve and better document parser generation procedure for java script. What's there now is some heavily hand tweaked code originally generated by sablecc. We should move to more consistent/standard/ non-hand-tweaked methods (and perhaps move to JFlex methodology used elsewhere). (david_williams@us.ibm.com @ 2005-04-22 00:43) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79045"> |
| <description>[wst.rdb] Execute single SQL statement in Scrapbook</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Using the execute in the Scrapbook should only execute the currently selected SQL code. If nothing is selected it should then execute the whole thing. (eclipse@juddsolutions.com @ 2004-11-18 20:48) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79046"> |
| <description>[wst.rdb] SQL Execute</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The SQL Execute should have a key like ctrl+e for quick execution. Using the menu takes to much time. (eclipse@juddsolutions.com @ 2004-11-18 20:53) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81035"> |
| <description>[wst.rdb] DB Qutput SQL History pane should be enhanced</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The pane of the DB Output that should the SQL history need to broken out into its own window. This window should be tied to the SQL Editor windows. This history should be kept from one session to the next. Currently, if you close Eclipse all the history is lost. Error should either be in sent to the Eclipse Error Log or the Console view. This view should just be a history of SQL command executed. Double Clicking on a query should either open a new SQL Editor or load the query in the current SQL Editor. This option should be configurable. (jeff@duska.com @ 2004-12-14 18:45) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81036"> |
| <description>[wst.rdb] SQL Editor/ SQL Scrapbook should include its own toolbar</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The SQL Editor could use a handy toolbar on the top of eidt view. I would move the select connection to this toolbar. Here are the buttons I would suggestion * An execute query * An execute selected SQL * Convert to Uppercase * Convert to Lowercase * Standard cut, copy and paste * Convert to langauge - this would take the SQL turn it into the string for Java. This should extendable, so other the community could add other lanaguages. * Cancel for a runnaway query. I would also change it to a dropdown list. We have no need to display a new dialog for such a simple bit of information. I think the execute button would be here. (jeff@duska.com @ 2004-12-14 18:54) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=84858"> |
| <description>[wst.rdb] The Database connection.</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The available options for the DB is the tied to a DB. I was wondering if we can have a generic category where the end users can try to connect to other databases as their needs specify. e.g. I work with the open source or inmemory DBs like the HSQL and others to get the basic functionality up and then migrate to other DBs. I find it difficult to corelate the DBs at different categories when I am not working with the same. If there is a generic environment which can make the connection based on the driver and classes i link to the connection. (tjmaven@yahoo.com @ 2005-02-09 21:51) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85094"> |
| <description>[wst.rdb] SQL Scrapbook editor should provide standard text editing facilities</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently the scrapbook editor directly extends the abstract editor which provides none of the standard text editing capabilities such as hyperlinking, hovers, and quickdiff. These are the changes i made to get it going: - SQLScrapbookEditor should extend TextEditor - Use a combined preference store when creating the source viewer (SQLScrapbookEditor constructor) new ChainedPreferenceStore(new IPreferenceStore[] { SqlscrapbookPlugin.getDefault().getPreferenceStore(), EditorsUI.getPreferenceStore()}) - SQLSourceViewerConfiguration should extend TextSourceViewerConfiguration More changes may be required but this gives you basic functionality (brockj@tpg.com.au @ 2005-02-12 19:38) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85099"> |
| <description>[wst.rdb] Enable syntax colouring of multiline comments</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently only single line comments are hilighted in the SQL scrapbook editor. It would be nice if multiline comments (/* */) were hilighted too. - Add a multiline rule in SQLSourceScanner and SQLCommentScanner for the multiline comment rules.add(new MultiLineRule('/*', '*/', comment)); - Uncomment the multiline rule for multiline comments in SQLPartitionScanner (brockj@tpg.com.au @ 2005-02-12 22:19) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87488"> |
| <description>[wst.rdb] Data and Schema Export</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There should a the possibility to export data from individual tables or from the whole database. Important export formats would be XML (dbunit compatible) or CSV. Also, the generation of a 'create table' schema file would be useful to export the database schema. (tderflinger@gmx.net @ 2005-03-09 08:26) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90376"> |
| <description>[wst.rdb] Flexibility to customize SQL keywords by User.</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There should be a flexibility to customize the keyword list for the SQL or PL/SQL. This gives the user the flexibility to include the keywords which is available in some of the database which may not be included in the default list of the editor. One possible approach would be allow the user to associate a syntax file with a specific structure as define by the editor to the sql editor. As in Textpad. (tjmaven@yahoo.com @ 2005-04-05 16:54) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=94068"> |
| <description>[wst.server] Action to move servers between workspace and metadata</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> By default, servers (the files containing server definitions) are stored in metadata. There is a preference that allows future servers to be created in the workspace instead, but it is clunky and does not allow existing servers to be moved into the workspace. This feature request is to add an action that allows servers to be moved between workspace and metadata. This will make it easier to share servers across a team. (deboer@ca.ibm.com @ 2005-05-08 16:19) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=73271"> |
| <description>[wst.sse] Folding for XML/HTML family languages editors</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be very useful to have folding functionality for XML type elements in editors like JEdit does. (eclipse-dev@telus.net @ 2004-09-03 16:02) </detail>")"/> |
| </li> |
| <ul> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85776"> |
| <description href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85776">depends on 85776</description> |
| </a> |
| </li> |
| </ul> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82119"> |
| <description>[wst.sse] ReadOnly state in DOM should be "pay as you go"</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently the read-only controller in XMLNode's *always* traverses nodes to keep read-only state accurate. See for example syncChildEditableState(Node child) in NodeContainer If there is never any read-only nodes in document, this can cause *lots* of extra DOM traversals. While these ultimately result in 'no-ops', so not too expensive, for large documents, with lots of elements, can result in a million 'no-ops' for no good reason. A better design would be to quickly decide to do nothing, until at least one node was set to be read-only. (david_williams@us.ibm.com @ 2005-01-03 22:14) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83449"> |
| <description>[wst.sse] Put the snippets view into the platform project</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Hello, The snippets view is very useful. It would be good to migrate this plugin from the wst project to the platform project as a basic plugin which can be used for everything else than web projects too... best regards Xavier (xavier.mehaut@free.fr @ 2005-01-21 15:19) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89085"> |
| <description>[wst.ws] Design Web Services Consumer framework</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This enhancement is being opened to track work in progress on the definition of a Web Services Consumer framework that, initially, will allow the Web services wizards to add themselves as launchable tools from Web services discovered in the Web Services Explorer, however, the framework will also allow other extenders to contribute tools that eat WSDL to the Web Services Explorer. Further details are forthcoming in a design document, a link to which will be appended to this enhancement. (cbrealey@ca.ibm.com @ 2005-03-25 01:06) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89086"> |
| <description>[wst.ws] Design extensible Web services validation profile framework</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This enhancement is being opened to track work in progress on the definition of an extensible preference page and related plumbing that allows the plugging-in of WSDL/XSD conformance or 'ruleset' profiles, initially to be exemplified by the WS-I SSBP and AP profiles. Further details are forthcoming in a design document, a link to which will be appended to this enhancement. (cbrealey@ca.ibm.com @ 2005-03-25 01:10) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89100"> |
| <description>[wst.ws] Web Services Explorer should use WSFinder framework</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The Web Services Explorer should exploit the WSFinder framework to drive its 'Browse WSDL' feature. Detailed requirements and design are forthcoming in a design document, a link to which will be appended to this defect. (cbrealey@ca.ibm.com @ 2005-03-25 10:22) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82569"> |
| <description>[wst.wsdl] Need a WSDL 1.1 to WSDL 2.0 converter</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> As the WSDL 2.0 specification is almost final, we need to prepare a WSDL 1.1 to WSDL 2.0 converter so that already existing WSDL 1.1 document assets can be reused. (kboo@ca.ibm.com @ 2005-01-11 11:09) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82595"> |
| <description>[wst.wsdl] Need a JUnit test plugin</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> We need a JUnit test plugin for testing the WSDL model and its bindings. (kboo@ca.ibm.com @ 2005-01-11 14:03) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90895"> |
| <description>[wst.wsdl] Enhancement to the WSDL validator</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> We would like the WSDL validator to provide a reporter mechanism that provides error keys. Thanks much -Chida (chidan@us.ibm.com @ 2005-04-09 02:14) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91288"> |
| <description>[wst.wsdl] Resizing of WSDL-Graph View</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The current WSDL-Graph Editorview cannot be resized. I am often working on a 1280x1024 display (i.e. 90deg rotated) when editing documents/sources. The current WSDL-editorview items have a fixed size and only use the upper third part of my screen. This is very annoying when the WSDL has a lot of Ports/Messages. Possible enhancements: * Resize the selection-boxes(service/bindings/ports/..) according the current windowsize. Horizontally the itemnamelengths could also be a measure. * Hide/Collapse options for all boxes (currently there is only a hide-button for the 'Bindings') * Graph-Display properties/preferences: Sizes, Fonts, ... Regards, Guus (ggerrits@mtg.de @ 2005-04-13 11:38) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=78369"> |
| <description>[wst.xml] Selection dtd files in Xml Catalog</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> In Xml catalog make a ability to select dtd file from anywhere in filesystem because very offen we donn't need dtd files in project, but need Tag Completion while edit xml file. (yatsuk@ua.fm @ 2004-11-11 03:57) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79627"> |
| <description>[wst.xml] pluggable validator using "services" pattern</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> [this is a captured requirement from news:eclipse.technology.wsvt] > The default validators should probably be registered automatically. I would like to suggest that you employ the Service Discovery pattern made famous by JavaMail and embodied in the commons-discovery framework (although commons-discovery is certainly NOT a prerequisite for this pattern). The short version (for those not familiar) is that your delegate is an interface and you discover (at runtime) those who provide such an interface by asking the ClassLoader for /META-INF/services/${fq_javaInterfaceName} which is a Properties file whose keys are a (possibly singular) list of the concrete implementing class(es) that should be instantiated and used. I have seen this used more and more (I believe wsdl4j uses it also) and I am really sold on its usefulness. (eclipse@mdaniel.scdi.com @ 2004-11-27 15:00) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81925"> |
| <description>[wst.xml] add nodes' XPath</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> add a node's XPath to its properties (david_fire4@hotmail.com @ 2004-12-27 05:41) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81955"> |
| <description>[wst.xml] add XML graph view</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Add an XML view which is similar to xsd's 'graph' view. (david_fire4@hotmail.com @ 2004-12-28 02:01) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83071"> |
| <description>[wst.xml] Make elements/attribute/etc. names in design view editable</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I would find it very useful to be able to edit an XML document using just the design view. For this to be really feasible, I should be able to change an element(/attribute/etc.) name on the fly, without inserting a new element, preferably by just clicking on the name (lorenzo.donati.bz@tiscali.it @ 2005-01-18 05:19) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83073"> |
| <description>[wst.xml] allow word-wrap in design view content column </description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> In order to work on XML files just using the design view, I would find very useful to have the right-hand column of the design view supporting a 'word-wrapping' mode. This would allow to see and edit, in particular, the whole text content of an element without resorting to scrollbars or the like. This will, I think, really speed up editing without messing up the source (important when editing is done by non-developer people) (lorenzo.donati.bz@tiscali.it @ 2005-01-18 05:27) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83074"> |
| <description>[wst.xml] Define views to edit attributes and to show text content</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I would find very useful a view that allows editing of all the attributes of an element selected in the design view of the editor. In some kind of jobs I find myself changing lots of attributes, and having a separate view (maybe together with an option to filter them out of the editor design view, to reduce clutter) would speed things up. For the same reasons, a view allowing editing of just the text content of a node would be great. Some other hints for improving the user interaction could be taken from the xmlshell editor (from www.softgauge.com), which seems to be discontinued (I tried to get a license for it, but that company never replied to me), I used a demo for a while and I really miss many of those features in eclipse. (lorenzo.donati.bz@tiscali.it @ 2005-01-18 05:39) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=84671"> |
| <description>[wst.xml] Allow copy/paste on XML nodes also between different editors</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I would find very useful if the design view in XML editor allowed to use copy/cut/paste on nodes. More specifically, I'd like to cut/copy a node and paste it somewhere else, in the same tree or even in a tree in a different XML editor. This would allow quick editing of XML documents as trees. I could, for example, move/copy an entire subtree from an XML file to another without messing with the source view, which would require a lot of error-prone text selection if the subtree to be copied/moved were too big. This would also facilitate insertion of the subtree in the right place, because it would be done looking at the tree model and not at the raw XML source text. If all these operations were supported also through drag and drop, this would be great, but I don't really know if D&D support in eclipse would easily allow a node to be dragged from an open editor to another one. Thanks. (lorenzo.donati.bz@tiscali.it @ 2005-02-08 08:44) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85348"> |
| <description>[wst.xml] Need a way to extend schema-derived content assist</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I need a way to add additional content assist proposals to those generated from the schema in an XML file. On the newsgroup, Nitin wrote: >> For .xml files, we haven't yet defined a way to contribute proposals to our existing Content Assist. and the behavior with conflicting org.eclipse.wst.sse.ui.extendedconfiguration extensions is undefined. << (rrodseth@mac.com @ 2005-02-15 17:53) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87465"> |
| <description>[wst.xml] honor system XML Catalogs, please!</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> At the moment, it is quite annoying and a lot of work to add all catalog entries to the XML Catalog Preferences. Also on almost any *x OS/developer machine, there is already an or more system xml catalog[s] with appropriate mappings for the most common doctypes. So it would be very useful, to be able to tell the XML editor, that it should lookup and use DTDs via one or more user specified catalogs (e.g. file:///etc/xml/catalog). BTW: Those catalogs have of course the format specified in http://www.oasis-open.org/committees/entity/spec.html - see also http://xml.apache.org/commons/components/resolver/ (elkner@linofee.org @ 2005-03-08 22:29) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88444"> |
| <description>[wst.xml] XML Editor: Display first attribute for an element in design / outline views</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Using 1.0M3 with Eclipse 3.1M5a. Both the outline view and the design editor for XML documents show the tree of XML elements. It would be nice if the first attribute of the element is also displayed, as shown below: - classes - class name='SomeClass' - properties - property name='name' - property name='length' - class name='SomeClassA' - class name='SomeClassB' When you have a lot of similar elements, this little thing makes it very quick to navigate XML documents. Right now I find myself clicking element after element in the outline view until I find the one I want. (cw_murray@yahoo.com @ 2005-03-18 08:14) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88445"> |
| <description>[wst.xml] XML Editor: Display first attribute for an element in design / outline views</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Using 1.0M3 with Eclipse 3.1M5a. Both the outline view and the design editor for XML documents show the tree of XML elements. It would be nice if the first attribute of the element is also displayed, as shown below: - classes - class name='SomeClass' - properties - property name='name' - property name='length' - class name='SomeClassA' - class name='SomeClassB' When you have a lot of similar elements, this little thing makes it very quick to navigate XML documents. Right now I find myself clicking element after element in the outline view until I find the one I want. (cw_murray@yahoo.com @ 2005-03-18 08:15) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89392"> |
| <description>[wst.xml] Customizable keyboard shortcuts for jumping to and selecting matching items in xml.</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be nice to be able to jump to the matching item (quote, bracket, close tag) within an xml document. Also it would be nice to select those things using customizable keyboard shortcuts. I believe you can already select tag contents and contents of parent tags, etc with a keyboard shortcut, but I don't think it is customizable, and was awkward to use. (mbditt@plauditdesign.com @ 2005-03-29 14:35) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89469"> |
| <description>[wst.xml] [Contribution] XSLT Support, Configurable XML Outline</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Attached is a zip containing my initial contribution of XSLT support for the Eclipse Platform. the archive contains source, class files and documentation(html). the documentation including screenshots is also online at http://eclipsexslt.sourceforge.net/ Features: - Some useful editor extensions making XML/XSLT editing more comfortable. - Configurable XML editor outline - XSLT Launch Configuration. XSLT transformations files can be started immediately via Run/Run As/Orangevolt XSLT , using the Run action in the toolbar or by using the Resource Navigator context menu. - The XSLT process console provides syntax colored XSLT process output supporting hyperlinks for error messages/warnings ( For example if an error occures in file foo.xsl, line 138 you can move the mouse over this the error line and after clicking it the XSLT process console opens/acitvates the file in the editor and jumps to the right line). - XSLT Processor Preferences for controlling/tuning the processor behaviour. - Pluggable XSLT processor support. Use the XSLT processor you want. - XPATH Navigator View. This view is used to execute XPATH expressions against a XML document (or XML selection) opened in Eclipse (see XPATH Navigator). (lars.gersmann@orangevolt.com @ 2005-03-30 03:21) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91628"> |
| <description>[wst.xml] Should XML Examples be converted to Eclipse Samples?</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Seems it might be more consistent 'face', more of an 'Eclipse citizen' for WTP. See Help, Welcome for other cases. I'm not positive what the 'platform strategy' is, but writing this up not to forget to investigate. (david_williams@us.ibm.com @ 2005-04-15 21:35) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92503"> |
| <description>[wst.xml] xerces config conflicts not well handled.</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Greetings: Im thinking the JKD im using must be missing the parser eclipse is looking for. I had this exception when attempting to open an htm file in the eclipse editor. I believe I'm running the latest builds for everything. I'll attach my configuration as a .txt file. Let me know what else I can do to help here. javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:113) at org.eclipse.wst.xml.uriresolver.internal.XMLCatalogPersistence.load(XMLCatalogPersistence.java:93) at org.eclipse.wst.xml.uriresolver.internal.XMLCatalogPersistence.load(XMLCatalogPersistence.java:64) at org.eclipse.wst.xml.uriresolver.internal.XMLCatalogPersistence.load(XMLCatalogPersistence.java:56) at org.eclipse.wst.xml.uriresolver.internal.DefaultCatalogImpl.<init>(DefaultCatalogImpl.java:33) at org.eclipse.wst.xml.uriresolver.XMLCatalogPlugin.getDefaultXMLCatalog(XMLCatalogPlugin.java:42) at org.eclipse.wst.xml.core.modelquery.XMLCatalogIdResolver.resolveId(XMLCatalogIdResolver.java:62) at org.eclipse.wst.xml.core.modelquery.XMLCatalogIdResolver.resolveId(XMLCatalogIdResolver.java:55) at org.eclipse.wst.html.core.modelquery.XHTMLAssociationProvider.getXHTMLCMDocument(XHTMLAssociationProvider.java:59) at org.eclipse.wst.html.core.modelquery.HTMLModelQueryCMProvider.getCorrespondingCMDocument(HTMLModelQueryCMProvider.java:65) at org.eclipse.wst.common.contentmodel.modelqueryimpl.SimpleAssociationProvider.getCorrespondingCMDocument(SimpleAssociationProvider.java:36) at org.eclipse.wst.common.contentmodel.modelqueryimpl.ModelQueryImpl.getCorrespondingCMDocument(ModelQueryImpl.java:96) at org.eclipse.wst.html.core.commentelement.handlers.CommentElementHandlerForSSI.createElement(CommentElementHandlerForSSI.java:41) at org.eclipse.wst.xml.core.commentelement.impl.CommentElementConfiguration.createElement(CommentElementConfiguration.java:77) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.createCommentElement(XMLModelParser.java:718) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertComment(XMLModelParser.java:917) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertStructuredDocumentRegion(XMLModelParser.java:1517) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.replaceStructuredDocumentRegions(XMLModelParser.java:2300) at org.eclipse.wst.xml.core.internal.document.XMLModelImpl.newModel(XMLModelImpl.java:575) at org.eclipse.wst.xml.core.internal.document.XMLModelImpl.setStructuredDocument(XMLModelImpl.java:838) at org.eclipse.wst.sse.core.AbstractModelLoader.createModel(AbstractModelLoader.java:115) at org.eclipse.wst.sse.core.internal.FileBufferModelManager.getModel(FileBufferModelManager.java:444) at org.eclipse.wst.sse.core.ModelManagerImpl._getModelFor(ModelManagerImpl.java:400) at org.eclipse.wst.sse.core.ModelManagerImpl.getModelForEdit(ModelManagerImpl.java:1163) at org.eclipse.wst.sse.ui.StructuredTextEditor.doSetInput(StructuredTextEditor.java:1294) at org.eclipse.ui.texteditor.AbstractTextEditor$16.run(AbstractTextEditor.java:2345) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:346) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:291) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:624) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:621) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1975) at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(AbstractTextEditor.java:2363) at org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTextEditor.java:2390) at org.eclipse.wst.sse.ui.StructuredTextEditor.init(StructuredTextEditor.java:1924) at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:857) at org.eclipse.ui.internal.EditorManager.busyRestoreEditorHelper(EditorManager.java:1223) at org.eclipse.ui.internal.EditorManager.busyRestoreEditor(EditorManager.java:1102) at org.eclipse.ui.internal.EditorManager$7.run(EditorManager.java:1064) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.EditorManager.restoreEditor(EditorManager.java:1062) at org.eclipse.ui.internal.EditorManager$Editor.getEditor(EditorManager.java:1648) at org.eclipse.ui.internal.EditorManager$Editor.getPart(EditorManager.java:1639) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:260) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:126) at org.eclipse.ui.internal.presentations.newapi.PresentablePartFolder.select(PresentablePartFolder.java:268) at org.eclipse.ui.internal.presentations.newapi.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.newapi.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:391) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1070) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1019) at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1223) at org.eclipse.ui.internal.PartStack.add(PartStack.java:406) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:109) at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:267) at org.eclipse.ui.internal.EditorManager$4.run(EditorManager.java:829) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:809) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:697) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:660) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2236) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2165) at org.eclipse.ui.internal.WorkbenchPage.access$7(WorkbenchPage.java:2157) at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2143) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2138) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2123) at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:278) at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:270) at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:177) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2778) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2472) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1570) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1534) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:306) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:228) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:315) at org.eclipse.core.launcher.Main.basicRun(Main.java:268) at org.eclipse.core.launcher.Main.run(Main.java:942) at org.eclipse.core.launcher.Main.main(Main.java:926) (wbrown@colorfulsoftware.com @ 2005-04-23 16:55) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=93150"> |
| <description>[wst.xml] Sax content extension point for XML Validator</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This extension point allows users to implement their own content handlers to the XML Validator so they can add their own validation checking. Using this extension users would add custom validation messages. A patch for the cheat sheet editor plugin will be attached as an example. The extended cheat sheet validator will check to see that the pluginid attribute value in the cheat sheet is valid. (mhutchin@ca.ibm.com @ 2005-04-28 13:43) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95903"> |
| <description>[wst.xml] Allow jar: uri's in mappinginfo</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be valuable to be able to refer to DTD/XSD's inside a jar file inside a plugin and not just as now a concrete file. something like: jar:platform:/plugin/my.plugin.id/xsd/schemas.jar!/myschema.xsd (max.andersen@jboss.com @ 2005-05-19 03:49) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86595"> |
| <description>[wst.xsd] Export XSD graph view as graphic</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It would be real nice to be able to export the xsd graph view as some sort of graphics file, for instance jpg or tiff. (vredeveld@imst.de @ 2005-02-25 02:56) </detail>")"/> |
| </li> |
| </ul> |
| </td> |
| </tr> |
| </table> |
| </td> |
| </tr> |
| <tr> |
| <td> |
| <table> |
| <tr> |
| <td valign="top"> |
| <img height="16" border="0" nosave="" src="../milestone_plans/stylesheets/images/Adarrow.gif"/> |
| </td> |
| <td> |
| <b>1.0 M4</b> |
| <ul> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79655"> |
| <description>[jst.ejb] Provide for generation of CMP/CMR via JDBC</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I have some code that may be used as a basis for writing CMP Beans with CMR directly from any existing database schema available via JDBC. It currently works with Oracle 9i and automatically generates LomBoz-style CMP beans complete with XDoclet directives for JBOSS 4.0. It also generates: An XMI file suitable for importing into Poseidon UML and Argo UML. Local and Remote J2EE Service Locators compliant with the Service Locator J2EE Pattern XDoclet code for CMR based on the Fireign Constraints defined in the DB Schema XDoclet code for extra finder methods defined in a supplemental text file An SQL script for regenerating the original schema on other servers I couldn't see any other plans for this, so do you think it would be useful? (matthew@robinsonfamily-au.org @ 2004-11-29 05:23) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85175"> |
| <description>[jst.jsp] Access to external Javadoc in JSP pages</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> When coding Java methods within files in the JSP editor (for example, in scriptlets), users should be able to access external Javadoc just like they can in Java files (using Navigate > Open External Javadoc (Shift+F2). (stevebang@gmail.com @ 2005-02-14 14:27) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=81026"> |
| <description>[wst.rdb] RDB SQL Editor as a replace for SQL Scrapbook</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The SQL Scrapbook UI is nothing like any SQL tool I've used. I would like to see a SQL Editor window. When I do this, I don't expect a wizard to start. Nor do I expect to be saving the query. Most of the time I'm looking for data, I'm not writing SQL that I want to keep. I should be able to save the query, but it should not be forced on me. I would also like to have the multi-pane approach. The user can select what panes are show, but I would expect the top to be a SQL pane, the bottom to be the results grid. (jeff@duska.com @ 2004-12-14 18:11) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=84413"> |
| <description>[wst.rdb] db output limits row size</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> when accessing an oracle d/b using jdbc and the view server explorer category. the db output when viewing the actual data in table is limited to a fixed number of rows. this ideally would be configurable. i couldn't find a place in the jdbc connection that would cause the rows size to be limited, so it must be in eclipse. eclipse Version: 3.1.0 webtools M2 (stuart_mellanby@hotmail.com @ 2005-02-04 03:54) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89084"> |
| <description>[wst.ws] Design Web Service Finder framework</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> This enhancement is being opened to track work in progress on the definition of a Web Services Finder framework that will allow extenders to plug-in mechanisms for locating Web services and callers to perform basic lookups. Amongst other things, this will lead to the appearance of Apache Axis Web services in the Project Explorer. Further details are forthcoming in a design document, a link to which will be appended to this enhancement. (cbrealey@ca.ibm.com @ 2005-03-25 01:03) </detail>")"/> |
| </li> |
| </ul> |
| </td> |
| </tr> |
| </table> |
| </td> |
| </tr> |
| <tr> |
| <td> |
| <table> |
| <tr> |
| <td valign="top"> |
| <img height="16" border="0" nosave="" src="../milestone_plans/stylesheets/images/Adarrow.gif"/> |
| </td> |
| <td> |
| <b>1.0 M5</b> |
| <ul> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82261"> |
| <description>[J2EE Standard Tools] F: Inlcude standard schemas</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> I understand standard schemas like J2EE Deployment Descriptor ones should be included with WTP so you don't need to be connected to Internet to get some features like Code Assist editing the deployment descriptors. Regards, Chemi. (ordax@es.ibm.com @ 2005-01-05 12:24) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83459"> |
| <description>[jst.j2ee] J2EE Project Explorer should be a superset of Package Explorer</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Project Explorer should be a superset of Package Explorer. Here are some things that are missing in Project Explorer * Working Sets * The New History Working Set view * Filters should be a superset of the Java filters dialog. * Go into * Back and Forward history (jeff@duska.com @ 2005-01-21 16:57) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=83530"> |
| <description>[jst.j2ee] Web-app directory option</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Give the end-user the option to change the web-app-directory for each project (guilherme.silveira@caelum.com.br @ 2005-01-24 09:00) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85114"> |
| <description>[jst.j2ee] No progress on WAR import</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> There is no progress monitor on the WAR import wizard. When importing large WAR files, it's annoying because there's no way to tell how long it is going to take. (deboer@ca.ibm.com @ 2005-02-13 15:21) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85252"> |
| <description>[jst.j2ee] import an existing project or allow to change its nature</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> While there are many things that can be imported into a new J2EE project, one that is not possible is to import an existing workspace project, that has been created as non-J2EE project. Import is probably a wrong notion for this action, I guess being able to change the project nature of an existing project would be enough. (tomasz@rtsoftware.com @ 2005-02-15 08:27) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92861"> |
| <description>[jst.j2ee] add an extension point for constributing a new appserver to "window->preferences->XDoclet->ejbdoclet"</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> ... (navy@shekou.com @ 2005-04-26 23:13) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86389"> |
| <description>[wst.common] Change presentation of filtering items in Project Navigator filter dialog [CommonNavigator]</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Currently, the Project Navigator’s filter dialog uses a table to display items that can be individually filtered. This approach is not visually scalable. Using a tree structure to visually organize individual filter contributions by group is more practical. This would allow clients to create filter groups and specify contributions to those groups. The tree items should also support icons. (jcorchis@ca.ibm.com @ 2005-02-23 17:19) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86391"> |
| <description>[wst.common] Add support for TabbedPropertyViewer [CommonNavigator]</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Add CommonNavigator support for the TabbedPropertyViewer. Support would include a set of default categories (say general, core, appearance, advanced) for clients contributions. (jcorchis@ca.ibm.com @ 2005-02-23 17:27) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86385"> |
| <description>[wst.validation] validation framework should utilize content type</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> Validation framework should utilize content type instead of the object filter class for IFile. eg. <filter objectClass='org.eclipse.core.resources.IFile' nameFilter='*.jspf'> </filter> Since content type is more robust, it handles (multiple) file extensions among other things. Also on a side note, it seems that the 'caseSensitive' attribute default value should be 'false', since it doesn't seem likely that someone will NOT want to validate a file if it has an uppcase extension. (pavery@us.ibm.com @ 2005-02-23 17:07) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=86810"> |
| <description>[wst.validation] Allow exclusions of paths during validation</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> It should be possible to specify exclude settings for the validators. For example, I have a project with a folder where I put all 3-party libs and docs into. If I enable HTML validation this folder should not be scanned. Currently a lot errors and warnings are generated for 3 party docs. (gunnar@wagenknecht.org @ 2005-02-28 04:13) </detail>")"/> |
| </li> |
| <li> |
| <a target="_blank" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=90565"> |
| <description>[wst.validation] Add lightbulb help when validate on save is greyed out</description> |
| </a> |
| <font color="8080FF"> [low]</font> |
| <img width="16" height="15" src="../milestone_plans/stylesheets/images/detail.gif" onmouseout="hidePopup()" onmouseover="showPopup("<detail> The validate on save option on the validation preferences page will be greyed out if auto build is not enabled. While this function makes sense it is confusing for users as they do not know how to enable this function. I suggest that a lightbulb help item be placed next to the validate on save preference when it is greyed out informing the user that they must enable auto build to enable this preference. (lmandel@ca.ibm.com @ 2005-04-07 01:55) </detail>")"/> |
| </li> |
| </ul> |
| </td> |
| </tr> |
| </table> |
| </td> |
| </tr> |
| <table border="0" width="100%" cellpadding="2" cellspacing="5"> |
| <tbody> |
| <tr> |
| <td colspan="4" bgcolor="#0080c0" width="100%" align="left" valign="top"> |
| <b> |
| <font face="Arial,Helvetica"> |
| <font color="#ffffff">Legend</font> |
| </font> |
| </b> |
| </td> |
| </tr> |
| <tr> |
| <td valign="top"> |
| <img width="14" height="5" src="../milestone_plans/stylesheets/images/progress.gif"/> |
| </td> |
| <td width="50%">item is under development.</td> |
| <td valign="top"> |
| <img width="10" height="10" src="../milestone_plans/stylesheets/images/glass.gif"/> |
| </td> |
| <td width="50%">item is under investigation.</td> |
| </tr> |
| <tr> |
| <td valign="top"> |
| <img width="10" height="10" src="../milestone_plans/stylesheets/images/ok.gif"/> |
| </td> |
| <td width="50%">item is finished.</td> |
| <td valign="top"> |
| <img width="40" height="12" src="../milestone_plans/stylesheets/images/help.gif"/> |
| </td> |
| <td width="50%">help wanted</td> |
| </tr> |
| <tr> |
| <td valign="top"> |
| <img width="10" height="10" src="../milestone_plans/stylesheets/images/defer.gif"/> |
| </td> |
| <td width="50%">item is deferred.</td> |
| <td valign="top"> |
| <font class="indexsub"> |
| <img src="../milestone_plans/stylesheets/images/new.gif"/> |
| </font> |
| </td> |
| <td width="50%">new</td> |
| </tr> |
| </tbody> |
| </table> |
| <br/> |
| </body> |
| </html> |
