We are considering to upgrade an existing system which used FUSE ESB 4.4.1 to latest JBOSS FUSE.
From what I understand, JBOSS FUSE is the much newer version of FUSE ESB. But I have no idea how much have it changed and does the code we have already implemented in FUSE ESB possible to run on latest JBOSS FUSE without extensive changes?
You should be able to migrate. Only if you use JBI components then they are deprecated and no longer supported in the upcoming JBoss Fuse 6.2 release. But for OSGi applications you may have developed for the old Fuse ESB, then it should be possible to recompile and deploy as-is, or there is some minor migration effort. Its primary the upgrades to Camel / CXF that may drive migration changes upon you. Or if you are unlucky then OSGi itself may cause a bit of pain to upgrade, as its errors sometimes can be hard to understand and figure out how to resolve.
There is some migration guides at JBoss Fuse documentation, you can find here
http://www.jboss.org/products/fuse/resources/
Related
In this https://help.mulesoft.com/s/article/Runtime-Security-Update-February-22-2021 page a Data-weave plugin patch of Mule Runtime Version 3.9.0 is enlisted as a fixation of "Server Side Request Forgery affecting Mule runtimes in certain use cases". But the patch jar is not available in given link https://help.mulesoft.com/sfc/servlet.shepherd/version/download/0682T000008XHSw. Can anyone help to get the workable link to download the mentioned patch jar?
No. MuleSoft only distributes patches for the Enterprise Edition (ie the commercial version). The reason you can not use the link is that you need to be a customer of the Enterprise Edition. Even if you could access it, trying to use a patch for a different version or edition may cause unexpected failures.
Have a few projects that need to run at the same time so have one run/debug configuration. Not all projects have the same mule runtime (EE) and I want all of them under the same runtime version. One is 3.8.4, another – 3.9.0 and the rest – 3.9.2. What are the main implications that I should be aware of?
I've just installed JBoss EAP 6.4.3 and now I'm checking on Arquillian updates. According to http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/eap/jboss-eap-bom-parent/6.4.3.GA/jboss-eap-bom-parent-6.4.3.GA.pom I'm stuck with version 1.1.0.
Is this version the one that JBoss uses when developing JBoss EAP?
Should I stick to this to be as compatible as possible or can I use the latest, greatest Arquillian version?
What is the strategy of updates regarding Arquillian and JBoss EAP?
It would be great if someone from JBoss (e.g. Aslak Knutsen) could give me some hints.
You should be fine using the latest, but I doubt you'd get support for it if something didn't work right because it wasn't tested with that version of EAP.
I am using Grails 2.5.1 and trying to use Authentication Plugin 2.0.1.
However, I have an error due to ConfigurationHolder not being found (this happens INSIDE authentication 2.0.1).
It seems that authentication 2.0.1 does not work with Grails 2.5.1 - it is not compatible with how grails structure changed in 2.4.x version.
What good authentication plugin version could I use? Or... How could I fix it? Or... what good authentication plugin alternative could I use?
Firstly, that plugin is no longer under development. The source code is on github, but no one has touched it in years. See this.
Alternatives
I don't know of a drop-in replacement. The closest one I know of is Grails Spring Security.
Fixing it
With some keyboard grease you can upgrade the plugin. If the holder error is the one I'm thinking of, it's easy to fix. Here's a general guideline:
With the source code in hand, check which version of Grails the p!ugin was written in.
Upgrade the plugin to the next minor version. Avoid skipping around.
Using the upgrading from grails section of the Grails documentation make the necessary changes.
Test, then rinse and repeat.
Change the plugin version and do a plugin local install.
Change the version of the plugin in your app so that it uses the new version.
Consider publishing your changes on github.
I want to configure Jboss 7.1.1 final in Netbeans 7.0.1. But I am getting an error "Provide a JBoss application server 6,5,4 Location". How can I add the latest JBoss AS?
Please help me. Thanks in advance.
Unfortunately, NetBeans doesn't support JBoss AS 7 at least as of NetBeans 7.2. A patch adding support has existed for some time, but was unfortunately not merged for the 7.2 release. There seems to be relatively little interest in AS7 in the NetBeans community.
I eventually gave up on NetBeans supporting AS 7 and moved to JBoss Developer Studio - basically a roll-up of Eclipse and JBoss Tools with preinstalled AS7 support, some bug fixes and polish.
There are a few NetBeans features I miss and it took a little learning, but overall I'm happy and there's enough really good stuff that I'm not going to bother going back.
I was stuck with JBoss 6.1 until I coded my own solution to deploy my projects.
Check the ant script here:
https://stackoverflow.com/a/13372389/980442