Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What version of Castle? I recall, from the depths of what goes for my memory at 4am in the morning, that there was a resolution for constructor work in Castle 2.0.</p> <p>Humm, memory coming back a little now... Something tells me that Castle will construct the object with the first public ctor. May be as simple as moving what you want for Castle to load, to the top.</p> <p>If that doesn't work for you, perhaps refactor your code a little? </p> <p>Option 1) Make the first two constructors internal.</p> <p>Option 2) Use a Factory pattern for your complex objects, which will utilize castle on the backend to new up the more simple or complex version.</p> <p>Option 3) Create 3 classes from your base superclass, each having a more complicated constructor. This way, you can specific in the Castle config file exactly which service to load. For example:</p> <pre><code>public abstract class BaseClass { public BaseClass(String requiredParam) { ... } } public class SimpleClass : BaseClass { public SimpleClass(String requiredParam, String anotherParam) : base(requiredParam) { ... } } public class MoreComplexClass : SimpleClass { public MoreComplexClass (String requiredParam, String anotherParam, String yetAnother) : base(requiredParam, anotherParam) { ... } } </code></pre> <p>But, I myself have not run into this yet. Mainly because I stick to only public 1 ctor on my classes, with a few private/internal ctors for things such as Linq to new up my objects with an empty ctor (since Linq doesn't support Dependency Injection, boo).</p> <p>Note that in that last statement, internal ctors, that my SRP (Single Responsiblity Pattern) for resolving my IoC components is external, in a seperate higharchy assembly (i.e. an application or UI layer). Since it not internal to my domain objects, the internal ctors are not seen by Castle.</p>
    singulars
    1. This table or related slice is empty.
    1. POChoosing the correct constructor using an external configuration file in Windsor?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USeduncan911
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POChoosing the correct constructor using an external configuration file in Windsor?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi, I'm using 2.0. Changing my constructors via a wrapper class is working for me right now, though it feels like a bit of a dirty hack.
      singulars
      1. PO
      1. USDavid Montgomery
    2. COMaking a wrapper class just to get the right constructor is a dirty-hack, and not quite what I was going for. I was suggesting a seperation-of-concern by the 3 param ctor for a different class with different requirements. What about just moving the 3 param ctor to the top of the list?
      singulars
      1. PO
      1. USeduncan911
    3. COI think the Factory pattern is definitely the right way to go (thanks for the tip BTW). Changing the order of constructors (or altering the constructors by adding a bogus parameter like I did) would rely on Castle's ctor 'scoring' mechanism to remain constant indefinitely -- which is an implementation detail I hope to soon forget about and never remember again!
      singulars
      1. PO
      1. USDavid Montgomery
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload