Blog Application
2 posts • Page 1 of 1
Blog Application
Hello,
I want to implement a blog application which will probably be available under Apache License 2. I'll probably implement some wrapper between castle and postsharp. For example, Castle has transaction facility, which I make use of, but the problem here is it intercepts runtime, so if a class calls a method of itself, it wont run in transaction.
I mean
public class Service:IService
{
[Transaction]
public void ATransactionalMethod(){}
public void ANonTransactionalMethod(){SomeTransactionalMethod()}
}
IService serv=container.Resolve<IService>();
service.ANonTransactionalMethod();
nothing will happen in transaction because it wont be intercepted.
Postsharp will take place here, making it compiletime will prevent this situation.
Castle Project is licensed under Apache 2 License.
My application will be released under Apache 2 License.
I wonder if those collide.
Thanks
I want to implement a blog application which will probably be available under Apache License 2. I'll probably implement some wrapper between castle and postsharp. For example, Castle has transaction facility, which I make use of, but the problem here is it intercepts runtime, so if a class calls a method of itself, it wont run in transaction.
I mean
public class Service:IService
{
[Transaction]
public void ATransactionalMethod(){}
public void ANonTransactionalMethod(){SomeTransactionalMethod()}
}
IService serv=container.Resolve<IService>();
service.ANonTransactionalMethod();
nothing will happen in transaction because it wont be intercepted.
Postsharp will take place here, making it compiletime will prevent this situation.
Castle Project is licensed under Apache 2 License.
My application will be released under Apache 2 License.
I wonder if those collide.
Thanks
- tehlike
- Posts: 1
- Joined: Sun Feb 24, 2008 11:29 pm
- Full Name: Tuna Toksoz
Re: Blog Application
It would be good to build some bridge between Castle and PostSharp, indeed (see PostSharp4EntLib for your inspiration).
No licensing problem, since:
1. PostSharp Compile-Time Components is "GPL + OSS exemption", and Apache 2 is OSI-recognized.
2. I suppose you will anyway reference only Runtime components, which are LGPLicensed.
Good luck!
Gael
No licensing problem, since:
1. PostSharp Compile-Time Components is "GPL + OSS exemption", and Apache 2 is OSI-recognized.
2. I suppose you will anyway reference only Runtime components, which are LGPLicensed.
Good luck!
Gael
Gael Fraiteur, project leader
got good support? consider donating to the project.
got good support? consider donating to the project.
- gfraiteur
- Site Admin
- Posts: 608
- Joined: Tue Dec 18, 2007 3:09 pm
- Full Name: Gael Fraiteur
- Company: postsharp.org
2 posts • Page 1 of 1