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 85354 - BPEL project can't be compiled after dragging a web service WSDL to it
Summary: BPEL project can't be compiled after dragging a web service WSDL to it
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Project (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Sreenivasan Genipudi
URL:
Keywords:
Depends on: 85451 86861
Blocks:
  Show dependency tree
 
Reported: 2006-09-20 16:07 UTC by Mikhail Kondratyev
Modified: 2006-10-11 06:25 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
resulting project (24.32 KB, application/octet-stream)
2006-09-20 16:11 UTC, Mikhail Kondratyev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Kondratyev 2006-09-20 16:07:44 UTC
Steps to reproduce:
 - create a new Sync sample
 - create a new JEE 5 Web service, add an operation there
 - deploy web service
 - drag web service node to the BPEL project
 - try to compile it
The compilation will fail
All the WSDLs are validated fine when validated separately
Comment 1 Mikhail Kondratyev 2006-09-20 16:11:59 UTC
Created attachment 34242 [details]
resulting project
Comment 2 Mikhail Kondratyev 2006-09-20 16:12:27 UTC
The resulting project is attached.
Comment 3 Mikhail Kondratyev 2006-09-21 08:55:18 UTC
Changing priority to P1 as this blocks end-to-end web services usage
Comment 4 Sreenivasan Genipudi 2006-09-21 20:04:52 UTC
Invoke Populate Catalog and try again. The reason to invoke is 
BPEL is importing external XML resource indirectly.. 

Populate Catalog is new feature added. This is how it works, it looks for all
the BPELs in the project, and it scans each BPEL and looks for the WSDLs and
XSDs that are imported in BPEL, if there are any external resource that imported
directly or indirectly by BPEL then this action will retrieve the XML resource
and make it available local.. 

User have to invoke this action if there are such XML resources imported by
BPELs in the project. 

The retrieved data will be packaged in SU.jar ( Meta-inf directory)  which will
enable the runtime to use the Catalog to look for the XML Resource. 

Catalog is an Oasis standard
http://www.oasis-open.org/committees/entity/spec-2001-08-06.html

This action will do nothing if there are no such BPELs.


Bpel -SynchronousSample3\src\SynchronousSample.bpel

    <import namespace="http://a/"
location="Partners/NewWebService/NewWebService_wsdl.wsdl"
importType="http://schemas.xmlsoap.org/wsdl/"/>


and that WSDL -
SynchronousSample3\src\Partners\NewWebService\NewWebService_wsdl.wsdl
imports external XML resource.
    <xsd:schema>
      <xsd:import namespace="http://a/"
schemaLocation="http://129.159.127.157:8080/NewWebServiceService/NewWebService/__container$publishing$subctx/META-INF/wsdl/NewWebServiceService_schema1.xsd"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
    </xsd:schema>

XML Resource -
http://129.159.127.157:8080/NewWebServiceService/NewWebService/__container$publishing$subctx/META-INF/wsdl/NewWebServiceService_schema1.xsd
is external to the project. 

User needs to invoke Populate Catalog Action on bpel project ( Right click bpel
project and invoke Populate Catalog ) this will retrieve the resource.. 

Please do the following - 

1)  Make sure
http://129.159.127.157:8080/NewWebServiceService/NewWebService/__container$publishing$subctx/META-INF/wsdl/NewWebServiceService_schema1.xsd

is valid

2) Invoke populate catalog on the project 

3) Build the project.



Comment 5 Sherry Barkodar 2006-09-21 20:48:19 UTC
I did D&D WS Today and first time I had no problem. However when I tried to do
it again it raised exception that I filed bug#85479. I filed it against wsdl
tool cuz it happened after I used that wsdl in different bpel process. Don't
know if the exception to bug#85479 will help.
Comment 6 Sreenivasan Genipudi 2006-09-21 22:48:15 UTC
I just wanted to add.. Populate Catalog action must be invoked if the catalog
needs to be packaged in the SU.jar..

The deployment catalog is only needed if the user needs to test the deployment
of a project with external imports offline or within a firewall blocking
internet access. If the user has the internet connection then the deployed
project should work fine without requiring any catalog support.

This is an optional action. Please try building the project again ( with
/without invoking Populate Catalog) , it should work.
Comment 7 Mikhail Kondratyev 2006-09-22 14:03:31 UTC
Can't verify because of bug 85451
Comment 8 Mikhail Kondratyev 2006-09-22 14:16:34 UTC
Although I can't compile the project because of bug 85451 from the sreeny's
description it looks like I will need to be on internet or press Populate
Catalog menu item to compile the project. This is not an acceptable criteria.
The scenario from description should work without any additional requirements
Comment 9 Sreenivasan Genipudi 2006-09-23 03:18:56 UTC
Fixed. Please use the next enterprise pack build. 
Comment 10 Mikhail Kondratyev 2006-09-29 12:05:16 UTC
Verified in build 2006.09.27
Comment 11 Sreenivasan Genipudi 2006-10-11 06:25:46 UTC
This has dependency on http://enterprise.netbeans.org/issues/show_bug.cgi?id=86861+