I deployed by ASP.NET MVC 3 applications which uses Castle Windsor for DI. The application is hosted on GoDaddy's shared web hosting. I am receiving the following exception when trying to load the site. Doing some search on Google, I found that it's caused because GoDaddy hosting is medium trust.
Is there any ways to solve this problem?
Inheritance security rules violated while overriding member: 'Castle.MicroKernel.DefaultKernel.InitializeLifetimeService()'. Security accessibility of the overriding method must match the security accessibility of the method being overriden.
Related
I have an Eclipse RCP application which I am planning to write in RAP so that I can allow my users to access it on web. I have just started with RAP and have gone through what RAP can provide and what it can't. Also I have seen the demo workbench application. Seems like a good fit for my use case but I still have some questions around the feasibility and workarounds possible in RAP.
Can RAP allow ports for existing views from eclipse like Package Explorer or Navigator. Also since the workspace would be shared can there be a way around to show different projects to different users.
The short answer is NO!
The Package Explorer or Navigator views itself wouldn't be hard to port to RAP. The Workspace/Resource API is the limiting factor here, as you already guessed. For RAP, a multi-user aware resource API would be desireable that provides a workspace for each seesion.
But until now, nobody put in the effort to implement this feature.
We have project developed in Silverlight/DevForce services, currently we plain to move code into HTML5. My question is it possible to reuse server side part of project, I means is it possible to reuse DevForce services or better migrate to WebAPI services? IdeaBlade has Breeze Js for HTML5, but it looks more as dataservice provider and not support DevForce services.
You might be asking whether BreezeJS offers a mechanism for handling arbitrary service calls between the client and the Web API running on the server ... in the manner of the DevForce "invokeServerMethod".
BreezeJS does not . The DevForce "invokeServerMethod" is helpful when you need to talk to the server for non-data reasons. You don't have to open and secure your own channel; instead you can share the DevForce secure data channel between client and server. It's also a convenient way to sent a package of entities. Setting up your own independent channel is not much fun.
But writing and communicating with a Web API service endpoint is much easier. Our thought is that you can manage your non-data communications quite well without the help of the BreezeJS EntityManager. So we don't see the need to implement the equivalent of "invokeServerMethod"
However, perhaps you have a scenario that would cause us to reconsider. We'd love to learn more.
Breeze doesn't integrate with DevForce today. I'd recommend adding the request to the Breeze UserVoice site. The Breeze team uses UserVoice to judge interest when incorporating new features.
A quick look shows me that there is already one DevForce related suggestion there: Support for DevForce models.
Just started with NServiceBus and I am trying to understand how the bus fits into my VS solution.
Let's assume an existing application, that has an ASP.Net front end and a BLL. I am using Windsor for DI and my BLL has no knowledge of the container. I wire the container up in a separate project I call "MyNamespace.IOC", and only this project and my web project have knowledge of Windsor.
I need access to the bus in my BLL (since that is where I will be sending/publishing/handling messages). I need to configure NSB using Windsor, and (I think) pass an instance of my container to the Configure.With().CastleWindorBuilder() method at app startup.
It seems odd to have all three projects have reference to the NSB DLLs. How does one normally wire this all together?
If you do not want to reference NSB in your BLL / domain layer you could have a look at 'domain events'. The domain event handlers can sit in their own implementation layer leaving your domain ignorant of the handling of the events and, therefore, requiring no knowledge of the service bus. From there you could publish your esb messages. It may not seem like much of a difference but the domain event-handling layer is more isolated from the domain.
Just as a side-note: since you are starting out with a service bus you could also have a look at my FOSS project over at http://shuttle.codeplex.com/ --- any feedback would be appreciated :)
You can abstract bus behind some interface and provide the implementation only in IoC and Web projects.
A couple of days back I was tasked with integrating Scribe and Spring Social for accessing LinkedIn APIs. Development environment being Windows, Spring and Java.
Spring Social's (spring-social-core-1.0.0.M1.jar) LinkedInTemplate uses org.scribe.extensions.linkedin.LinkedInBaseStringExtractorImpl. (Log messages showed "NoClassDefFoundError" for LinkedInBaseStringExtractorImpl) This class is present in scribe-1.0.7.jar but not in the latest jar i.e scribe-1.1.0.jar (downloaded at https://github.com/fernandezpablo85/scribe-java).
I couldn't find a way to fix this issue. But I was able to do a quick hack: on my local machine, I copied LinkedInBaseStringExtractorImpl from scribe-1.0.7.jar into scribe-1.1.0.jar. Everything works like a charm now.
I am curious to know if anyone else faced similar issues.
What you say is right. Scribe changed it's internals from 1.0 to 1.1 (and greater), though the public apis didn't change, some internals did, and this class LinkedInBaseStringExtractorImpl is no longer part of the lib.
Anyway, you don't need SpringSocial at all, check the LinkedIn example to see how to consume LinkedIn's Api using just scribe.
I have a legacy web application that I want to enhance by adding a message board. Is it possible to add the message board portlet of liferay into this external application.
I am a newbie so pardon my naivity if I've overlooked something obvious.
Many Thanks
No this is not possible. Liferay is a portlet container that implements JSR 268 portlet specification. All portlets that can be installed in Liferay conform to this specification.
So, if you have a legacy application, which obviously isn't a portlet container, you can't install portlets into it.
Embedding a portlet container in your webapp, just for being able to use Liferay's Message Boards (which isn't THAT good anyway), seems like a huge overkill...
In which language is your application written and which framework(s) do you use? Do a Google to see if there are any projects that you can start from or integrate in your app.
Both the answers in my view are correct limburgie and kgiannakakis, still I would like to add something which may be a little useful.
There is an interesting feature of "Sharing" in liferay with which you can embed portlets as widgets into any application.
But the only catch is that Liferay Server should also be running while your Application is also running on the same or another server.
For more information on sharing you can visit this link.