[george-tang]

Hi

I installed jboss eap 6.4 to “c:\DevTools\EAP-6.4.0”, and try to configure JBoss AS as server runtime. I selected “JBoss 7.0 Runtime” and select “c:\DevTools\EAP-6.4.0” as installation directory. I got the message “c:\DevTools\EAP-6.4.0” is not a valid JBoss 7.0 Runtime installation directory.

My installation of myeclipse is

MyEclipse Enterprise Workbench

Version: 2015 CI 15
Build id: 13.0.0-20150930

Is there something wrong? I think it should support JBoss AS.

Attachments:

You must be logged in to view attached files.

[support-swapna]

George,

The JBoss connector validation was made more strict in CI 15 so now it validates only against JBoss AS and not JBoss EAP.We never had direct support for JBoss EAP.

You can work around the validation issue by creating a dummy jar file with name jboss-as-web-7.1.1.Final.jar in this path : {$jboss.home}/modules/org/jboss/as/web/main. If the folder structure is not present in the JBoss EAP installation, please create the folders accordingly. The JBoss AS 7.x connector will now support JBoss EAP 6.x.

The fix for the validation issue will be out with our next CI release due very soon. I will keep you posted about the CI release.

–Swapna
MyEclipse Support

[support-swapna]

George,

The fix for the JBoss EAP validation issue is out with our latest CI release, CI 16. Please go to Help > Check for Updates to update to CI 16.

Let us know if you see any issues.

–Swapna
MyEclipse Support

[Author]

Posts