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 131528 - Project Segmentation
Summary: Project Segmentation
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Alexey Yarmolenko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-29 18:40 UTC by jjjjjj
Modified: 2008-04-04 22:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jjjjjj 2008-03-29 18:40:23 UTC
When segmenting xsd, wsdl, ejb-web services and soa-bpel into four different projects; cause name lookup problems in the
bpel project regardless of referneces; the proper solution is to combine the xsd into the wsdl project; the invalid bpel
import generated are:

<xsd:import namespace="http://xml.netbeans.org/schema/LogSchema" schemaLocation="Schemas/LogSchema.xsd"/>

in the wsdl project this is fine but the bpel cannot resolve above ?strange?; a fix would be to manually edit the
bpel-xsd to:

<xsd:import schemaLocation="../../Schemas/LogSchema.xsd" namespace="http://xml.netbeans.org/schema/LogSchema"/>

Further; in general project references are duplicated when dropping the same wsdl into the bpel flow causing various
errors - in other words only add a project reference when it does not already exist.
Comment 1 Venkat Chellasamy 2008-03-31 03:47:42 UTC
serge, looks like bpel project adds duplicate project references.
Comment 2 Sergey Lunegov 2008-03-31 08:35:58 UTC
We'll at this post Sierra.
Comment 3 jjjjjj 2008-04-04 22:03:45 UTC
Thanks guys.

I'm working around this for now my keeping both my xsd's and wsdl's into the same project.