This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 112118 - Cannot choose input/output schemas for XSL file
Summary: Cannot choose input/output schemas for XSL file
Status: REOPENED
Alias: None
Product: soa
Classification: Unclassified
Component: XSLT (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vitaly Bychkov
URL:
Keywords:
Depends on: 95642
Blocks:
  Show dependency tree
 
Reported: 2007-08-06 21:43 UTC by kevan1138
Modified: 2007-08-22 15:58 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kevan1138 2007-08-06 21:43:02 UTC
When I create a new XSL file, it comes up with error messages saying it cannot determine input/output schemas (Issue
112117).  This ticket refers to the inability to choose input/output schemas for XSL file.
Comment 1 Vitaly Bychkov 2007-08-07 07:25:57 UTC
The 3rd step of XSLT Service wizard acordingly to 112120 will allow to choose input/output schemas.

*** This issue has been marked as a duplicate of 112120 ***
Comment 2 kevan1138 2007-08-07 20:16:42 UTC
This is NOT a duplicate issue.  The user MUST be able to specify input/output schemas for existing XSL stylesheets,
which do not need the XSLT Service wizard.

Reopening issue.
Comment 3 Vitaly Bychkov 2007-08-07 22:30:59 UTC
The error message appears because of Xslt Project context.
Inside xslt project one can use XSLT Service wizard to specify input/output schemas.

In case if you mean inability to specify input/output schemas for any XSL stylesheets,
outside the xslt project context then there is enhacement(95642).
Comment 4 kevan1138 2007-08-07 23:24:52 UTC
User with existing XSL stylesheet (in Xslt project context) should NOT have to go through XSLT Service wizard to add
input/output schemas.  Each schema is a single property related to the stylesheet and should be editable as such (e.g.
properties window?).
Comment 5 Alexey Yarmolenko 2007-08-16 12:06:00 UTC
Kevan, this functionality was not planed for NB6.0. 
The plan was:
-When XSL file is found inside XSLT project context, we replace default XSL editor with ours, which have an additional
("mapper") tab.
-The content of "Mapper" tab(left and right trees) is generated based on information found in transformmap.xml.
-If transformap.xml is missing or corrupted, we showing error message inside mapper pane.

As far as i see, current implantation works according to this plan.

Your proposal is to add some metadata to xsl file, containing information about left and right schemas and make this
metadata editable thru property sheet, etc. This is a new feature, described by stand-alone feature request:
http://www.netbeans.org/issues/show_bug.cgi?id=95642



Comment 6 pvarghese 2007-08-22 15:58:07 UTC
reopening this for sierra, as this bug is a similar request to the bug 95642.
This has to be treated as an enhancement for Sierra, and done if time permits.