I am extending an existing Commerce Server 2002 UserObject profile
definition
to include an additional property. I added a column to the relevant
database
table, created a new data member corresponding to that column, then
created
the property in my profile definition and mapped it to the new data
member.
The issue I'm having is as follows:
My app is a provisioning .NET 1.1 web service. Since I don't want my web
service class tightly-coupled to Commerce Server, I've pushed that code as
far down the class hierarchy as possible. I have two sets of tests for
creating profiles: one using the middle-tier class directly (1), and one
which uses a .NET web service proxy class to call the web method, which in
turn calls the middle-tier class (2). Now, when I run Test 1, all
properties,
new and old, are set as expected. When I run Test 2, however, all
properties
are set correctly EXCEPT for my new property, which throws a COMException
including the message, "Invalid index." To clarify, I am using the string
indexer for the ProfilePropertyCollection. This behavior would seem to
indicate to me some kind of access security violation, except that only
the
new property seems to have a problem.
Does anyone have any ideas as to what could be causing this? I've run
out...
Thanks.
|
