Post Calculator causing NPE in loadRelatiionshipOblects

[David Herman]

We have a preCalculator defined in our item price engine. I was
experimenting with adding a postCalculator so I created a new class/
component that extends ItemPriceCalculator have it set in our
ItemPriceEngine postCalculators=/path/to/my/component and it all looks
fine in dyn/admin - everything resolves. However, when I go to price
an item I end up with

CONTAINER:atg.service.pipeline.RunProcessException: An exception was
thrown from the context of the link named [loadRelationshipObjects].;
SOURCE:java.lang.NullPointerException
at atg.service.pipeline.PipelineChain.runProcess
(PipelineChain.java:371)
at atg.service.pipeline.PipelineChainContext.runProcess
(PipelineChainContext.java:185)
at atg.service.pipeline.PipelineManager.runProcess
(PipelineManager.java:453)
at atg.commerce.order.OrderImpl.ensureContainers
(OrderImpl.java:1262)
at atg.commerce.order.OrderImpl.getShippingGroups
(OrderImpl.java:815)


Currently this is the entire block of my priceItem method:
if(isLoggingWarning()){
logWarning(String.valueOf(price));
}

Any idea whats causing this. I have confirmed that it is indeed the
post calc since i can remove it and remove the error then add it back
and get the error again.

[manimozhian rathinam]

Hi,
  The pricing  is not set at all.If you check the price it may be 40.0.You can debug the code to get the root cause and also verify the configurations
Sai

---

From: David Herman <dst...@purpleasphalt.com>
To: ATG_Tech <atg_...@googlegroups.com>
Sent: Wednesday, February 18, 2009 4:34:21 AM
Subject: [atg_tech:3040] Post Calculator causing NPE in loadRelatiionshipOblects

[David Herman]

If i change config to remove post calc it prices fine. As soon as post calc exists it blows up so it def has something to do with that. We do have item price engine extended but i put a but i put a break in it and it doesnt get hit

Sent from my Windows Mobile® phone.

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[David Herman]

Found the issue
The new calc was missing these 2 properties

loggingIdentifier=TheCalc
pricePropertyName=listPrice