facilities.
Tuna Toksöz
Eternal sunshine of the open source mind.
http://devlicio.us/blogs/tuna_toksozhttp://tunatoksoz.comhttp://twitter.com/tehlike
On Wed, Mar 24, 2010 at 5:44 PM, Konstantin konstantin.no...@gmail.comwrote:
I'm building application extensibility model on top of Windsor
...@kozmic.pl wrote:
Konstantin,
That's an interesting problem :)
What do you want to do when a plugin containing invalid configuration
is registered?
Container's events are actually not hacky - most facilities (incl.
these comming out of the box)
subscribe to, and act upon container events
'test' what a plugin provides, an additional test container seems to
be the way to go.
On 25 Mar, 12:59, Konstantin konstantin.no...@gmail.com wrote:
I do not like to reject plugins. The purpose is to reuse castle
configuration system but limit the scope that can be configured
Here is test demonstrating the issue
[Test]
public void Test()
{
var c = new WindsorContainer();
var myFacilty = new MyFacilty();
c.AddFacility(my, myFacilty);
c.Register(Component.ForA());
I'm using log4net for logging. LoggingFacility looks great to auto
inject logger. But the application utilizes ALERT log level which is
absent in ILogger interface. Is it possible to use LoggingFacility and
keep the ALERT log level ?
--
You received this message because you are subscribed to
calls to Alert
On 2010-04-16 10:04, Konstantin wrote:
I'm using log4net for logging. LoggingFacility looks great to auto
inject logger. But the application utilizes ALERT log level which is
absent in ILogger interface. Is it possible to use LoggingFacility and
keep the ALERT log level
When I have a class with public property, and several components of
property type are registered. I expected that castle to push the
component with name matching the property name if exists.
here is code illustrating that it is not so but at the same moment
DependencyKey of prop dependency is
I've solved it in a bit different way - I'm using the NonOptional
Attribute to marke properties that are mandatory dependencies so i've
added the following code to NonOptionalInspector
propSet.Dependency.IsOptional = false;
propSet.Dependency.DependencyType
I've noticed that in some cases DynamicProxy signes the generated
assembly and in some it does not . After examining the assemblies
returned by AppDomain.CurrentDomain.GetAssemblies() it turned out
that there are two assemblies
DynamicProxyGenAssembly2, Version=0.0.0.0, Culture=neutral,
After looking at DynamicProxy2 with reflector I've managed to restrict
assembly signing:
DynamicProxy code:
static StrongNameUtil()
{
signedAssemblyCache = new DictionaryAssembly, bool();
lockObject = new object();
try
{
new
Any ideas how to solve the problem?
--
You received this message because you are subscribed to the Google Groups
Castle Project Users group.
To post to this group, send email to castle-project-us...@googlegroups.com.
To unsubscribe from this group, send email to
, thus i
need ether make DPWindsor work in the same way whether DP is allowed
to sign assembly (native code permission is granted) or not
On Jun 23, 2:00 am, Krzysztof Koźmic krzysztof.koz...@gmail.com
wrote:
Konstantin,
sorry the the last reply, somehow this thread slipped from my
Krzysztof,
Could you please explain why 2 assemblies are are emitted?
--
You received this message because you are subscribed to the Google Groups
Castle Project Users group.
To post to this group, send email to castle-project-us...@googlegroups.com.
To unsubscribe from this group, send email
I do not think it is about signed assemblies - none of classes I
register in windsor belong to signed assembly...
--
You received this message because you are subscribed to the Google Groups
Castle Project Users group.
To post to this group, send email to castle-project-us...@googlegroups.com.
some tests illustrating the issue
using System;
using Castle.Core;
using Castle.Core.Interceptor;
using Castle.DynamicProxy;
using Castle.MicroKernel;
using Castle.MicroKernel.Registration;
using Castle.Windsor;
using NUnit.Framework;
namespace test
{
public interface IMyInterface1
{
I've ran into the following problem with DynamicProxy and Castle :
Application with plugins
When application loads plugin it uses Interceptors to perform some
routines on access to particular interface implementations. Plugin
publishes a class implementing such interface and references assembly
Just tested with latest castle , the same
ctor: Dependency
Expected values:
Dependency is disposed: true
container.Kernel.GraphNodes.Length: 0
Actual values:
Dependency is disposed: False
container.Kernel.GraphNodes.Length: 1
Ppress enter...
On 29 ноя, 14:26, Konstantin konstantin.no
Issue on tracker http://issues.castleproject.org/issue/IOC-253
On 30 ноя, 04:57, Krzysztof Koźmic krzysztof.koz...@gmail.com wrote:
Konstantin
That's odd.
While the console app you provided exposes faulty behavior, when I
copied the code, verbatim, to a test, the test passes, in other
I've ran into similar issue some time ago .
Here is the
discussion
https://groups.google.com/d/topic/castle-project-users/40_6x7i1VBU/discussion
In few words it is most likely .NET 3.5 issue and reproducable only under
debugger.
--
You received this message because you are subscribed to the
I'm not using xnl config, all components are registerd fluently. Thus I've
implemented IConfigurationBuilder that returns a configuration for the db
(when there is no xml configuration NHibernateFacility creates single
factory and uses ConfigurationBuilder to init it). Now I need to work with
lets say I have some service contract
[ServiceContract]
public interface ISecurityProvider
{
[OperationContract]
void DoSomething();
}
following code throws
exception: Castle.MicroKernel.Facilities.FacilityException : The client
model requires an endpoint.
, Krzysztof Koźmic wrote:
I don't think there's a switch that controls that (Craig may have some
input here)
I think if you want that you might need to override some logic in the
facility
--
Krzysztof Kozmic
On Monday, 1 April 2013 at 6:22 AM, Konstantin wrote:
lets say I have some service
kind of DynamicWcfClientModel to defer or delay selection of the
WcfClientModel.
On Sun, Mar 31, 2013 at 3:22 PM, Konstantin
konstant...@gmail.comjavascript:
wrote:
lets say I have some service contract
[ServiceContract]
public interface ISecurityProvider
I register service only when recieve first heartbeat from it.
On Monday, April 1, 2013 4:48:16 PM UTC+4, Craig Neuwirt wrote:
Aren't you explicitly registering ISecurityProvider in your case?
On Mon, Apr 1, 2013 at 6:56 AM, Konstantin konstant...@gmail.comjavascript:
wrote:
I'd like
, Krzysztof Koźmic wrote:
can you reproduce that in a test?
--
Krzysztof Kozmic
On Saturday, 21 September 2013 at 8:50 PM, Konstantin wrote:
I have a manager that creates component instanses. To instantiated
componenets the typed factory is used, but once component is instanciated
Any update?
--
You received this message because you are subscribed to the Google Groups
Castle Project Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to castle-project-users+unsubscr...@googlegroups.com.
To post to this group, send email to
do anything the container won't itself do anyway
--
Krzysztof Kozmic
On Monday, 30 September 2013 at 3:37 AM, Konstantin wrote:
Any update?
--
You received this message because you are subscribed to the Google Groups
Castle Project Users group.
To unsubscribe from this group
UTC+4, Krzysztof Koźmic wrote:
Hi Konstantin
Are there any generics involved? When the issue happens once, does it keep
happening everytime after that?
The stack trace is quite misleading here. The exception comes from WCF
itself, and WCFFacility merely rethrows it (which erases original
it.
At this point I don't really know what might be the cause or solution to
it.
@K
On 11/05/2012 12:35 AM, Konstantin Alexandroff wrote:
Hi, Krzystof
sorry for delay.
Neither services nor any 'operations' are generic in our case.
When issue happens, every call to every method
interested in understand what or how we can
resolve the issue.
Thanks,
Swami
On Tuesday, May 15, 2012 7:39:49 AM UTC-4, Krzysztof Koźmic wrote:
ok
keep us posted
@K
On 15/05/2012 9:38 PM, Konstantin Alexandroff wrote:
Greetings,
I've tried to isolate the problem really hard
30 matches
Mail list logo
