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 161585 - Relative path XSD reference resolution
Summary: Relative path XSD reference resolution
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Venkat Chellasamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-31 13:38 UTC by ashishgodani
Modified: 2009-05-05 01:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample bpel project to replicate issue (15.95 KB, application/x-compressed)
2009-03-31 13:40 UTC, ashishgodani
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ashishgodani 2009-03-31 13:38:59 UTC
I created a simple bpel project with casa app and deployed it on glassfish test env. 

I am not able to access the XSD's referenced in the wsdl from the browser.

XSD file is there in the archive which is being deployed to the server. However once the archive is deployed on 
GlassFish and the WSDL is opened via HTTP in a browser and then trying to open the schema (also in the browser) results 
in "500 Internal Server Error".

I have attached the sample application to replicate the issue.

WSDL URL: http://<<HOSTNAME:PORT_NUMBER>>/MapperCASA-sun-http-binding/MapperSample/wsdl/MapperSampleWS.wsdl
XSD URL: http://<<HOSTNAME:PORT_NUMBER>>/MapperCASA-sun-http-binding/MapperSample/xsd/PersonList.xsd

Basically accessing xsd with the above mentioned url results in the error.
Comment 1 ashishgodani 2009-03-31 13:40:05 UTC
Created attachment 79135 [details]
Sample bpel project to replicate issue
Comment 2 ashishgodani 2009-04-08 10:20:21 UTC
The issue stands resolved. Please refer: https://open-esb.dev.java.net/issues/show_bug.cgi?id=1544
Comment 3 fmartinez1 2009-05-05 01:24:25 UTC
Tested the "Steps To Reproduce" and verified that this issue is resolved. I can now access the referenced XSDs from 
the browser. Tested with 20090503-0720 build