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 114958 - XSLT service problem with imported wsdl
Summary: XSLT service problem with imported wsdl
Status: RESOLVED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: XSLT (show other bugs)
Version: 6.x
Hardware: PC All
: P2 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-06 23:04 UTC by Tientien Li
Modified: 2007-10-22 13:14 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
fail to access imported wsdl elements (46.57 KB, application/octet-stream)
2007-09-06 23:05 UTC, Tientien Li 		Details
test projects (36.83 KB, application/octet-stream)
2007-09-06 23:06 UTC, Tientien Li 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tientien Li 2007-09-06 23:04:58 UTC 
The xslt editor does not process wsdl imported using XML cross-project references correctly. This problem causes 
elements from imported wsdl to be inaccessible within the xslt project.

Steps to reproduce this error:
1. create a project reference
- create a Sync sample project
- create a bpel project, BpelModule1
- open bpel project reference and add sync sample's bpel project

2. test cross-project reference in WSDL
- in BpelModule1, create a new empty WSDL, newWSDL.wsdl
- open it in wsdl editor
- right click on Imports to add WSDL import
- select ByFile/SynchronousSample/ProcessFiles/SynchronousSample.wsdl
- after the import, all child elements from SynchronousSample.wsdl are accessible in newWSDL.wsdl

3. test cross-project reference in XSLT
- create a xslt project, XsltModule1
- open xslt project reference and add BpelModule1 project
- create a new xslt service
- use Request-Reply service
- select [BpelModule1] newWSDL.wsdl
- xslt project failed to access elements imported from newWSDL.wsdl (see attached image)

In general, the xslt project does not process wsdl imported from XML cross-project reference correctly.
Comment 1 Tientien Li 2007-09-06 23:05:49 UTC 
Created attachment 48337 [details]
fail to access imported wsdl elements
Comment 2 Tientien Li 2007-09-06 23:06:18 UTC 
Created attachment 48338 [details]
test projects
Comment 3 Sergey Lunegov 2007-09-07 16:46:23 UTC 
Vladimir, I'll explain you more when I come back to the office.
Comment 4 Vladimir Yaroslavskiy 2007-09-14 14:43:29 UTC 
The description is not accurate. The problem is not in using XML cross-project reference,
the problem is that elements from imported wsdl file are not accessible. It doesn't matter
if imported wsdl file from reference project or not.

Steps to reproduce:

1. Create XSLT module
2. Create (or copy from Sync project) WSDL with necessary data (+ schema).
3. Create empty wsdl, add via import data wsdl file in empty wsdl.
4. Create xslt service
5. use Request-Reply service
6. select empty wsdl, it will not be acceptable,
   though imported wsdl is in the same project.

I'm correcting the description
Comment 5 Vladimir Yaroslavskiy 2007-09-14 14:57:05 UTC 
While creating of XSLT service you can see wsdl files from current and cross-referenced projects.
Comment 6 Sergey Lunegov 2007-09-19 14:22:49 UTC 
Resolution is the same as for 114955. Complete and aligned over all SOA modules solution of the problem requires deep
analysis and more investigation.  Now only partial solution can be implemented and it can cause other bugs. Will be
addressed in Sierra timeframes. Marked as ENHANCEMENT.
Comment 7 Vladimir Yaroslavskiy 2007-10-22 13:14:25 UTC 
fixed in sierra.