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 167155 - NPE while opening bpel mapper
Summary: NPE while opening bpel mapper
Status: CLOSED WORKSFORME
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Mapper (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Nikita Krjukov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-16 11:38 UTC by Vitaly Bychkov
Modified: 2009-10-23 19:46 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
I took the missing mentioned BPEL project from the referenced mails. (491.32 KB, application/octet-stream)
2009-09-30 12:16 UTC, Nikita Krjukov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vitaly Bychkov 2009-06-16 11:38:47 UTC
In some cases while opening bpel mapper occurs NPE resulted in empty mapper component.
Initial discussion is here:
http://n2.nabble.com/Mapping-of-attributes-disappear-td3066638.html#a3066638
Steps to reproduce:
Take the sample project from attachment.
1. Open otDispNotActivTabProcess.bpel from the sample project
2. select "AssignItems" assign
3. switch to the mapper
4. See there are empty mapper component and NPE:
java.lang.NullPointerException
	at org.netbeans.modules.xml.xpath.ext.impl.XPathModelImpl.resolveChildComponents(XPathModelImpl.java:375)
	at
org.netbeans.modules.xml.xpath.ext.impl.ReferenceResolutionVisitor.processLocationStep(ReferenceResolutionVisitor.java:281)
	at
org.netbeans.modules.xml.xpath.ext.impl.ReferenceResolutionVisitor.processLocationSteps(ReferenceResolutionVisitor.java:447)
	at org.netbeans.modules.xml.xpath.ext.impl.ReferenceResolutionVisitor.visit(ReferenceResolutionVisitor.java:146)
	at org.netbeans.modules.xml.xpath.ext.impl.XPathExpressionPathImpl.accept(XPathExpressionPathImpl.java:133)
	at org.netbeans.modules.xml.xpath.ext.impl.XPathModelImpl.resolveExtReferences(XPathModelImpl.java:1036)
	at org.netbeans.modules.xml.xpath.ext.impl.LocationStepImpl.getSchemaContext(LocationStepImpl.java:246)
	at org.netbeans.modules.xml.xpath.ext.impl.XPathExpressionPathImpl.getSchemaContext(XPathExpressionPathImpl.java:146)
	at org.netbeans.modules.bpel.mapper.tree.search.FinderListBuilder.build(FinderListBuilder.java:150)
	at org.netbeans.modules.bpel.mapper.model.GraphBuilderVisitor.connectToLeftTree(GraphBuilderVisitor.java:405)
	at org.netbeans.modules.bpel.mapper.model.GraphBuilderVisitor.visit(GraphBuilderVisitor.java:318)
	at org.netbeans.modules.xml.xpath.ext.impl.XPathExpressionPathImpl.accept(XPathExpressionPathImpl.java:133)
	at
org.netbeans.modules.bpel.mapper.model.BpelMapperModelFactory$PreprocessedExpression.populateGraph(BpelMapperModelFactory.java:601)
	at org.netbeans.modules.bpel.mapper.model.BpelMapperModelFactory.postProcess(BpelMapperModelFactory.java:472)
	at org.netbeans.modules.bpel.mapper.model.BpelMapperModelFactory.constructModelImpl(BpelMapperModelFactory.java:214)
	at org.netbeans.modules.bpel.mapper.model.BpelMapperModelFactory.constructModel(BpelMapperModelFactory.java:145)
	at
org.netbeans.modules.bpel.mapper.multiview.DesignContextControllerImpl2.setContextImpl(DesignContextControllerImpl2.java:349)
	at
org.netbeans.modules.bpel.mapper.multiview.DesignContextControllerImpl2.showMapper(DesignContextControllerImpl2.java:243)
	at org.netbeans.modules.bpel.mapper.multiview.MapperMultiviewElement.componentShowing(MapperMultiviewElement.java:260)
Comment 1 Vitaly Bychkov 2009-06-16 12:08:52 UTC
The issue is reproducable with the GFESB 2.1 RC2 but not reproducable with the GF ESB 2 latest nightly build.
Comment 2 Vitaly Bychkov 2009-06-16 13:35:14 UTC
The problem is in mapping of these elements:

                                <copy>
                                    <from>$otDispatchNotificationItemVar/ns1:ARTICLE_ID/ns1:INTERNATIONAL_AID/@type</from>
                                    <to>$ublDespatchLineVar/ns3:UUID/@schemeName</to>
                                </copy>
                                
                                <copy>
                                    <from>$otDispatchNotificationItemVar/ns1:ARTICLE_ID/ns1:BUYER_AID/@type</from>
                                    <to>$ublDespatchLineVar/ns5:Item/ns5:BuyersItemIdentification/ns3:ID/@schemeName</to>
                                </copy>
                                <copy>
                                    <from>$otDispatchNotificationItemVar/ns1:DELIVERY_DATE/@type</from>
                                    <to>$ublDespatchLineVar/ns5:Shipment/ns5:Delivery/ns3:ID/@schemeName</to>
                                </copy>
                                <copy>
                                    <from>$otDispatchNotificationItemVar/ns1:ORDER_REFERENCE/ns1:AGREEMENT/@type</from>
                                    <to>$ublDespatchLineVar/ns5:Item/ns5:TransactionConditions/ns3:ID/@schemeName</to>
                                </copy>

Looks like the XPath model can't succesfully resolve attributes in cases like this:
$ublDespatchLineVar/ns3:UUID/@schemeName

Comment 3 Nikita Krjukov 2009-06-16 16:52:07 UTC
There is a strong suspicions that the issue is a duplicate of the issue #165984 which already has fixed in soa-dev65
Comment 4 Vitaly Bychkov 2009-06-17 03:56:46 UTC
Actually this issue is not such specific as described in 165984.
Also the stacktraces little bit different. It looks like the prolem starts from
org.netbeans.modules.bpel.mapper.tree.search.FinderListBuilder.build(FinderListBuilder.java:150)
.
Comment 5 Nikita Krjukov 2009-09-30 12:16:32 UTC
Created attachment 88592 [details]
I took the missing mentioned BPEL project from the referenced mails.
Comment 6 Nikita Krjukov 2009-09-30 12:18:46 UTC
I've tried reproducing the specified steps and failed getting the NPE. Everything works fine with the current sources. 
Comment 7 terrybraun 2009-10-23 19:46:11 UTC
This issue is tested with the GFESB Build of 10/19/09, including NetBeans IDE 6.7.1 (Build 200910181801).

QA was also unable to reproduce this issue with the attached project. Given Nikita's suspicion that it is a variation 
of Issue #165984, which QA has verified as being fixed, this ticket is declared CLOSED as not reproducable.