enter image description here
Following issue is faced when trryin to hit mule app through postman using get api
which has following screenshot of error.
You are trying to execute a Mule project with Java JDK or OpenJDK 17. Neither Anypoint Studio nor any version of Mule supports Java 17. Please select a supported version of Java. For Mule 4.4 -the version that your project is using- the versions supported are mentioned in the requirements: JDK 1.8.0 or JDK 11.
To resolve it either use the default version or configure a compatible version to execute the project.
Does SignalR support .NET 4.0. Or is it support only from .NET 4.5 upwards. Is there any link which provides with minimum requirements for SignalR.
This is not the case any more, and the 2.x releases require .NET 4.5.
https://github.com/SignalR/SignalR/issues/1723
The last .NET 4.0 support for SignalR is version 1.2.2. Version 2 only works with .NET 4.5
Open the NuGet Package Manager Console and type:
Install-Package Microsoft.AspNet.SignalR.Client -Version 1.2.2
Install-Package Microsoft.AspNet.SignalR -Version 1.2.2
This will install the SignalR (Client and Server) in your selected project (web project) automatically.
Yes .NET 4.0 supports SignalR. The minimum requirements:
*Visual Studio 2010 SP1
*Since template installer is not available in VS2010 you need to install SignalR NuGet package
One thing to watch here is client/server .Net versions.
Most people know (but it's worth repeating) signalR can be hosted on Windows 2008R2 upwards. Windows 2008R2 has IIS7 and thus when hosted on IIS7 signalR cannot use WebSockets (as the old Windows http stack has no support for WebSockets). So that's ServerSentEvents or LongPolling. Not great for performance.
Windows 2012 upwards (and thus at least IIS8) offers support for WebSockets, which gets the amaziong C10K perf we're all after.
Now the interesting bit.
.NET clients.
If you only care about the browser skip this bit.
Any .Net clients that connect to a signalR back-end MUST use
Windows8 upwards to use WebSockets The Microsoft networking stack (for
.Net) in Windows7 does not contain WebSockets.
So don't use signalR with WebSockets if your client is Windows7.
OR... like us you'll need to use a custom WebSocket stack coupled with WebClient to handle the http handshake.
Hopefully this will help someone else!
You can download entire web stack from codeplex and SignalR from github and compile it under .net4.0
There is one sample project at http://www.bluelemoncode.com/2013/02/default.aspx
It is good SignalR sample and working vs 2010 sp1 and .net framework 4.0. working properly.
http://www.bluelemoncode.com/file.axd?file=2013%2f3%2fSignalR_OneOneChat.zip
The minimum requirements for SignalR is described here,
Which means your client can be WinForm/WPF application running on Windows XP.
I wanted to upgrade from Servlet 2.4 to Servlet 3.0. Currently we are using ESAPI in our application and would like to upgrade.
Latest ESAPI release depends on servlet-api-2.4.jar. Does ESAPI support Servlet 3.0?
I upgraded my application to support Servlet 3.0 and ESAPI seems to work. So it is backwards compatible.
Does anyone know what servlet api version is jboss 5.1.0 GA runnning?
Servlet 2.5
See version matrix.
is jbos5.1.0 compatible with jdk6 and spring2.5.X.
I am also integraion acegi security and not spring security 3.0 as i am using spring 2.5.0?
IS jboss 5.1.0 comaptible with spribng3.0 andjdk6 ?
A few months ago, I've tried JBoss 5 with Spring 2.5.6 and couldn't deploy my application, because of this bug. The comments on the issue, mention the problem only happens with EJB, but my application didn't make use of EJB and it was packed as a war.
According to the JIRA, this was fixed in spring 3.0RC1, but I haven't tried it (for now, I gave up updating to a new version of JBoss).