I remember using Configuration Application Block in Enterprise Library 1.0.
What is the equivalent of it in 4.0 or 4.1 version?
No, there's no equivalent. When .NET 2.0 Framework came out, the Configuration Application Block has been deprecated in favor of System.Configuration.
On a separate note, are there any configuration scenarios that you feel you need help with, similarly to what Configuration Application Block offerred?
Related
How to exclude the org.json version in MULE 3.9.0 buildpath?
The version is json-20140107 I want to use the latest json version. I tried to exclude in mule-commons but it did not do any help.
The json-20140107.jar library is distributed with Mule 3.9.0. Because of how Mule implements classloading, at execution time classes loaded from that jar file will override a newer version in your application. You must not change the version provided because Mule was tested. Changing any provided library in the distribution can cause unexpected errors.
You could pack a new version of the library and try to use Fine Grain Classloader Control however that seems to be an Enterprise Edition feature not available in the community edition. If you have the Enterprise Edition it is highly recommended to use the last patch version (currently 3.9.4) instead of 3.9.0.
Another solution could be to migrate to Mule 4.x, which uses classloading isolation to avoid this kind of issues. You can use any version of libraries inside applications without conflicting with the provided libraries in the runtime. Again, using the last version available is the recommended way to go. Mule 3 applications are not compatible with Mule 4, so you will need to migrate existing applications.
I have to write a library that works with Couchbase 3.0.1 and 4.0. I know that to know if my code will works with each one, I will have to test them.
Anyway, what are the key differences between both versions?
If you are using the Java SDK, Couchbase server 4.0 is backwards compatible with the Java SDK 1.4.x. So using this version of the SDK should work across both Couchbase 3.0.x and 4.0.x servers, although you won't be able to use any of the cool new features with 4.0.x.
Other SDKs that were intended for Couchbase server 3.0.x should similarly be compatible with Couchbase server 4.0.x.
However, there could be some hidden "gotchas" when using an older SDK with the newer server version, although I have yet to encounter one myself.
As far as migrating from an older SDK intended for Couchbase server 3.0.x to a newer SDK intended for Couchbase server 4.0.x, this migration requires a significant effort for the Java SDK since they did a lot of refactoring. Although, I'm not certain if the same is true for SDKs in other languages.
Does PicketLink support all Application Servers?
I'm interested in using it on WebSphere 8.5.5. If not is there an equivalent library for WebSphere security offering?
In theory, you can use it in any JEE6+ container. CDI is the only requirement. You can even use Weld SE, for instance.
There are people using it in TomEE and Glassfish too.
I am newbie with WebSphere. Recently I downloaded WebSphere Community Edition version 3 (WASCE v3) but there is no description about using WASCE v3 with JSF2.0 in the guide "Getting started with WASCE". I already build my web in Apache Tomcat 7.0.11 with JSF2.0 and PrimeFaces 3.1. I am using eclipse INDIGO. Now i have to shift my server to WebSphere. Please suggest me the best version of WebSphere, which is suitable for JSF2.0 with PrimeFaces3.1?
Thank you.
WASCE 3 is a Java EE 6 container, so it has support for JSF 2.0 (if it wouldn't have this, it couldn't be called Java EE 6).
Do note that people typically don't mean WASCE when they refer to WebSphere. WASCE is another name for the server otherwise known as Apache Geronimo. The difference is that it's specifically supported by IBM.
What people do mean with WebSphere is the one you can find here: ibm.com/software/webservers/appserv/was
For JSF 2.0 you would need the latest version, which is version 8.
I have got a situation on the server where we are running applications that support asp.net version 1.0 and 2.0. I have recently developed an application in asp.net 4.0 using MVC (Razor Engine).
I am wondering if I install asp.net 4.0 on the server, would that affect the other websites that are already running?
If somebody could advise me on that would I'd appreciate it.
no it shouldn't just be sure, that in IIS configuration you set the right application pools. You can set a different app pool for every aspx website/application.
Each pool can be then set up for different .NET version.
nope if by applications you mean websites (you mentioned mvc) then you can configure in the app pool for each site seperatly on which framework they should run in IIS. If you are refering to windows desktop applications you can define the runtime environment when building the application in Visual studio.