DevForce Community Forum : can't find compositionContext

can't find compositionContext : Thanks for your time. This...

Tue, 07 Jun 2011 07:23:15 -700

Author: jhoward
Subject: 2744
Posted: 07-Jun-2011 at 7:23am

Thanks for your time. This problem is solved.

can't find compositionContext : Thanks for the feedback regarding...

Mon, 06 Jun 2011 19:22:41 -700

Author: DenisK
Subject: 2744
Posted: 06-Jun-2011 at 7:22pm

Thanks for the feedback regarding the documentation. You're right that it is not properly documented. We will update it accordingly.

Currently, apart from the "+" char, any character is safe as long as it's valid for a file name.

can't find compositionContext : I should have mentioned that...

Mon, 06 Jun 2011 18:04:41 -700

Author: jhoward
Subject: 2744
Posted: 06-Jun-2011 at 6:04pm

I should have mentioned that the problem only occurs in n-tier. Sorry. It would have been helpful if I mentioned that the CompositionContext name should have been "Dmr" and the keyExtention, "RBV644+FIN". I'll try to enter a more thorough description in the future. :-)

It turns out that both "_" and "-" can occur in the two parts that are joined to make the DataSourceExtension so those are not good choices. I've given my testers a version that uses "|" to try out. It would be nice if there were something in the documentation that listed reserved characters. It's not in the API documentation for that constructor overload for EntityManager.

Is there somewhere I can find a list of safe characters (other than the two you've suggested)? Trial and error will work here but I don't want to pick something that IdeaBlade is going to scarf up later if I can help it. And I'd like to avoid the complication of double escaping.

Here's the entity manager constructor call you asked for earlier:

var entityManager = new GemModel(
true,

IafMgr.ThreadEnvironment.Environment + "|" + this.DatabaseId,

compositionContextName:GemModel.DmrCompositionContextName);

In the above the value of IafMgr.ThreadEnvironment.Environment is "Rbv644", this.DbatabaseId is "FIN", and DmrCompositionContextName is "Dmr".

can't find compositionContext : Hi jhoward;I was looking at this...

Mon, 06 Jun 2011 17:41:15 -700

Author: DenisK
Subject: 2744
Posted: 06-Jun-2011 at 5:41pm

Hi jhoward;

I was looking at this again, and was able to get the same exception in n-tier. You're correct, it is caused by the "+" char because we use that character to delimit the composition context name. I would suggest using "_" or "-" for your purposes. And depending on your environment, you may have to set "allowDoubleEscaping" to true in your web.config.

http://msdn.microsoft.com/en-us/library/ms689460(v=vs.90).aspx

Sorry for the confustion.

can't find compositionContext : Hi jhoward;I was not able to repro...

Mon, 06 Jun 2011 13:03:23 -700

Author: DenisK
Subject: 2744
Posted: 06-Jun-2011 at 1:03pm

Hi jhoward;

I was not able to repro your issue here in 6.1.0. I'm using the "+" character in both my custom CompositionContext name as well as my DataSourceExtension and I didn't have the exception thrown.

In my testing, I have the following debug log entry:

EntityServer created for DataSourceExtension: Customer01+XXX, CompositionContext: Admin+XXX

And I have the following custom CompositionContextResolver and CustomDataSourceKeyResolver:

namespace Server {
  public class CompositionContextResolver : BaseCompositionContextResolver {
    public static CompositionContext Admin = CompositionContext.Default
      .WithGenerator(typeof(CustomDataSourceKeyResolver))
      .WithName("Admin+XXX");
  }

  class CustomDataSourceKeyResolver : IDataSourceKeyResolver {

      public IDataSourceKey GetKey(string keyName, string keyExtension, bool onServer) {
         //Unnecessary details omitted
     }
  }

}

And I create an EntityManager as follows:

var entityManager = new DomainModelEntityManager(
        shouldConnect: true, 
        dataSourceExtension: "Customer01+XXX", 
        compositionContextName: CompositionContextResolver.Admin.Name);

EntityServer created for DataSourceExtension: RBV644, CompositionContext: FIN+Dmr

Could you clarify that FIN+Dmr is what you want for your keyExtension? Judging from the entry above, it sounds like you have RBV644 configured for your keyExtension, and FIN+Dmr for your custom CompositionContext name. Do you have a custom implementation of ICompositionContextResolver? If possible, I'd also like to see the whole debug log and your implementation of GetKey().

can't find compositionContext : Our application has implements...

Mon, 06 Jun 2011 05:11:42 -700

Author: jhoward
Subject: 2744
Posted: 06-Jun-2011 at 5:11am

Our application has implements IDataSourceGetKey.Get() and depends on a keyExtension with two parts concatenated together to give us what we need to resolve the data source key. We chose "+" as the separator for the two parts. Since upgrading to 6.1.0, we get the following exception:

IdeaBlade.Core.IdeaBladeException: Unable tofind a compositionContext with the name: FIN+Dmr

The exception immediately follows this entry in the debug log:

EntityServer created for DataSourceExtension:RBV644, CompositionContext: FIN+Dmr

Our testers believe this has something to do with the "+" character in the name in the composition context. Does that seem plausable? If so, how can we know what characters are safe to use for our purpose?