Implementing WS-Security Using JBoss EAP 6.3 - Dfiferences between 6.3 and 7? - cxf

Recently I worked out a SOAP Web Service/WS-Security solution using JBoss EAP 7 and its JBossWS version (with CXF). This reference was very helpful:
https://docs.jboss.org/author/display/JBWS/WS-Security
The solution is based on a WSDL file that contains a WS-SecurityPolicy.
Now I've been asked to implement a solution based on the same WSDL file, but using JBoss EAP 6.3.
JBoss EAP 7 is the only version of JBoss EAP that I've worked with thus far. I would like to avoid re-inventing the wheel, so to speak, so I'm looking for a hopefully minimal set of configuration changes from the EAP 7 solution.
Does anyone have recommendations for doing this? I've struggled even to find documentation or tutorials, in part because I'm unclear about which version of WildFly, JBossWS, and JBossWS-CXF is included in a JBoss EAP 6.3 installation.

In order to find out which component have been integrated into every JBoss EAP version, open the following URL:
https://access.redhat.com/articles/112673
You can check also The WS-Security introduction page on the CXF website

Related

Will ClickOnce be ported to .NET Core 3 or .NET 5 as well as WinForms?

Now that Winforms is being ported to .NET Core 3, what technology will be used for deploying those apps? Will ClickOnce also be ported?
Many of the properties used by ClickOnce are currently stored in the .csproj file, but those project files change significantly between .NET Framework and .NET Core, so presumably this would require changes to Microsoft's ClickOnce code to make it work?
Has there been any official word from Microsoft on this, I can't find anything in the documentation?
Current status
It appears that ClickOnce won't be ported to .NET core 3, but will be ported to .NET 5 as per Matthew Steeples' answer below.
Original answer relating to .NET Core 3
Microsoft's Scott Hunter addressed this in the comments of the .NET Core is the Future of .NET blog post. He was asked:
What about ClickOnce? Will that be a supported distribution system for
.NET 5 desktop applications?
To which he gave the response:
We are going to recommend MSIX for installation and support for MSIX
will be added for Windows 7 so it should work on all the platforms you
that .NET Core runs on.
More details MSIX can be found in Microsoft's MSIX documentation and in it's GitHub repo.
Other installation frameworks exist too, such as Squirrel.
All other answers answer the question for .NET Core 3, but this is changing for .NET 5. Microsoft are providing support for ClickOnce as described in this GitHub issue (July 20th 2020): https://github.com/dotnet/deployment-tools/issues/9
It's not full support (ApplicationDeployment class will not be available) but it's a start.
It looks like it's going to be available as of RC2 - https://devblogs.microsoft.com/dotnet/announcing-net-5-0-preview-8/
There is no mention of anything about .net core 3 winforms working with Clickonce. The answer provided above had a link that had Scott Hunter who redirected to Microsoft's MSIX technology. Based on my readings the only way to deploy to end users without using the Microsoft store is to "sideload" your application and that seems to involve many steps that may make the user hesitant even if you sign the package it seems that users have to enable sideloading first. Not my idea of user friendly.
As the previous anwers stated, Microsoft is not going to continue Clickonce support but they have provided msix as a replacement. You can deploy a .NET Core application internally in your organization by using an msix package. I'm successfully using it as a Clickonce replacement.
You can check my post explaining how to create an msix package for a .NET Core project. You can even target Windows 7 SP1 and later.
EDIT: Microsoft is going to continue support of ClickOnce in .NET 5.
Update status:
Microsoft Announcing .NET 5.0,
Some of the newly released features also include ClickOnce:
"It’s now supported for .NET Core 3.1 and .NET 5.0 Windows apps."
You can take a look Here

How to identify the installed version of Sitecore Media Framework of Ooyala?

I have upgraded Sitecore Media Framework 1.4 from Media Framework 1.2. I got some warnings on the installation. i.e Sitecore has no necessary permissions for reading/creating counters. I am not sure whether the new version has been upgraded or not. However, I see some differences in the content videos. Got more videos than the existing Media Framework version. I would like to verify on Sitecore What version of Sitecore Media Framework Ooayala Edition installed on my sitecore instance.
Kindly help me on this.
Thanks in advance.
Annadurai
You can check the version of Sitecore Media Framework by looking at the properties of the DLL files (Sitecore.MediaFramework.Ooyala.dll and Sitecore.MediaFramework.dll). The version is located in the Details tab.
If you don't have access to the bin files, you can also have a look at the items under /sitecore/system/Packages/Installation history/ in the Core database.
Also, be sure you have installed the correct framework according to your Sitecore version. See Sitecore SDN for details.

Silverlight plugin install base with version breakdown

I would like to choose which versions of Silverlight plugin to target, but can't find any recent statistics on the install base, let alone the version break down. Statowl.com/silverlight.php isn't returning any data and riastats.com is down. Some articles are referencing a 76% web clients installation base around 2012 with high Silverlight version 4 usage, but that's pretty outdated information. Does anyone have up to date information for the Silverlight plugin install base, preferably with version breakdown?
The client is backwards compatible. I think you will find most users are running the V5 client as that is pushed out with MS updates and was released 2+ years ago. You can set the min runtime version on the html Silverlight plugin element to alert users running an older version to upgrade to a version compatible with the version your app is compiled against.
http://msdn.microsoft.com/en-us/library/cc917842(v=vs.95).aspx

java.lang.UnsupportedClassVersionError in Google App Engine

I'm running windows 7 and juno. Jdk 1.7, gwt 2.4, app engine 1.7.
I did the stockwatcher tutorial here and everything worked great. I then deployed it to app engine. Everything still worked great!
However, I then did the RPC part of the tutorial here. When I ran locally, I got a java.lang.VerifyError that I fixed by following this thread (putting -XX:-UseSplitVerifier in default VM arguments). It then worked locally and I deployed to app engine.
In app engine, I get a java.lang.UpsupportedClassVersionError. I found two threads that seem to have the same problem, here and here. I'm using a fresh install of windows 7 and the only jdk I downloaded was 1.7. Looking through eclipse, I see jre7, jdk 1.7, and app engine 1.7.
I read somewhere that app engine doesn't work with 1.7. However the app engine sdk version on the downloads page is 1.7 (I think that might be super recent) but I don't really know if those things are related. I went ahead and downloaded java 6 and app engine sdk 1.6.6, added jre6 to the installed jres, set the compiler compliance level to 1.6, changed it in my project too for good measure, and changed the default app engine sdk to 1.6.6.
Now I'm getting the error, "Java compiler level does not match the version of the installed java project facet." I googled the problem and everyone says to right click the project and change the facet, but I can't seem to find that option. I also have no idea if I'm going about this the right way. I'd much rather use the most recent versions of everything if possible. I also don't understand why app engine worked the first time with no RPC, but broke with the RPC.
Any help would be greatly appreciated!!! THANK YOU!!!
GAE does not currently support java 1.7, only 1.5 and 1.6 are supported. See the java docs for more information.
The relevant paragraph is the following:
App Engine runs Java applications using the Java 6 virtual machine (JVM). The App Engine SDK supports Java 5 and later, and the Java 6 JVM can use classes compiled with any version of the Java compiler up to Java 6.
The version of the GAE sdk you downloaded (1.7) isn't related in any way with the java version.
GAE is a sandbox environment. Currently it supports only Java 6. But to solve your problem, if you can downgrade your compile version to Java 6, you should be able to take advantage of GAE.
But if you want a standalone server environment without any restrictions, check other cloud platforms like heroku or cloudbee
Possibilities are
you don't have right JDK or
GAE you using that does not support 1.7
Open below file under .settings (use Navigator window) and change java project facet to 1.6
org.eclipse.wst.common.project.facet.core.xml
After change you must close and restart the eclipse.
Currently ,... java 7 already supported
Warning: In a future release, support for Java 6 will be removed, so it is a good idea to start migrating to Java 7 now. If you've been using Java 6 and are interested in learning about possible issues migrating to Java 7, this white paper may be helpful.
from : https://developers.google.com/appengine/docs/java/overview

How to deploy solr4 in jboss6

What is the best way to deploy solr 4.x in a running jboss 6.x application server instance?
Well, JBoss features an embedded Tomcat, so I'd start by reading the docs about Solr and Tomcat. There's also some specific docs for JBoss, and of course there's the wiki page for general installation instructions.

Resources