[Maksym Gryevtsov]

Once I install the latest CI 15 patch, I’m losing ability to define EAP 6.3 connector (JBoss AS v7.X). The wizard simply tells that selected EAP server folder contains invalid server. It works fine with CI 14.

Thanks,
Maksym

Win7 x64

[support-swapna]

Maksym,

We never had direct support for JBoss EAP in MyEclipse. The JBoss connector validation was made more strict in CI 15 so now it validates only against JBoss AS and not 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.

I have filed a report with the dev team about JBoss EAP support and they are looking into it.

Let us know how it works for you.

–Swapna
MyEclipse Support

[Maksym Gryevtsov]

That helped,

Thanks

[Lofi]

EAP support without workarounds would be great!

[support-swapna]

Lofi,

The team is looking into a better fix without the need for workaround.
Sorry for inconvenience caused.

–Swapna
MyEclipse Support

[support-swapna]

Maksym/Lofi,

The fix for the JBoss EAP validation issue is out with our latest CI release, CI 16.
Instead of an error message, you will now see a warning message and you can still configure the server.

Let us know if you see any issues.

–Swapna
MyEclipse Support

[Author]

Posts