Message Pool in separate DC: error

[Former Member]

Hello all,

I have gone through <a href="https://admin.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f4d79e59-0601-0010-0689-89670315bc6b">this example</a> that shows how to use a Message Pool in a separate DC than the one that holds your application, so that you can share a Message Pool across multiple DCs. The same app worked fine for me when I was using local DCs.

I then tried to use the same concept in a non-local DC, and I keep getting the following error message whenever I deploy it:

java.lang.IllegalArgumentException: No such attribute Premise_Phone

Premise_Phone is (obviously) the attribute in the application DC that I'm trying to validate. Of course, it doesn't exist in the Message Pool DC - but I didn't have to have matching attributes in the example when using local DCs, so I didn't think that would be an issue.

Any ideas?

Thanks,

Jennifer

[former_member286976 · Accepted solution]

Hi Jennifer,

Did you mean to say that the same DC worked fine when it was local and the same code not working when you made it non-local. This shouldn't happen.

Check for the case of the attribute name and make sure that it's correct.

As far as the issue is concerned, I feel this is nothing to do with MessagePool DC.

Regards,

Sudeep

[Former Member · Accepted solution]

It's not exactly the same DC, no. I just followed the tutorial for the local DC project and then applied the concepts from that into my "real life" situation that I'm working on.

Now that I think about it, one of the major differences is that in the example, the attributes that were being validated were all Value attributes, directly off the context. In my "real life" case, they're all Model attributes, off of a model node that's directly off the context.

Maybe I DO need to add that same model node to the Messages DC?

[abhijeet_mukkawar · Accepted solution]

Hi,

yeah just check out that you are reffering them properly, in case of element :

wdContext.current<Modelnodename>Element //while giving in reportContextAttributeMessage

also check you are giving proper Attribute info as:

IWDAttributeInfo attrInfo = wdContext.node<modelnodename>.getNodeIfno().getAttribute("<Attribute name>") thn pass attrInfo in reportContextAttributeMessage

hope it helps

regards

[Former Member · Accepted solution]

D'oh! I can't believe I missed something so obvious! Thanks so much!

I had the Attribute Info part correct, but was just getting the currentContextElement instead of the model one.

Thanks again, points awarded!

Jennifer