This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 234452 - Support for JB Wildfly 8
Summary: Support for JB Wildfly 8
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: JBoss (show other bugs)
Version: 7.4
Hardware: All All
: P2 normal with 31 votes (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-15 13:39 UTC by Petr Jiricka
Modified: 2015-11-13 08:57 UTC (History)
10 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2013-08-15 13:39:08 UTC
The open source edition of the JBoss server has been renamed to Wildfly, and version 8 will be the next release, which will support Java EE 7. Currently, the Alpha 4 build of Wildfly 8 is available. This build can not be registered in the IDE:

1. Download and unzip Wildfly 8 Alpha 4
2. In Services window -> Servers, choose Add Server... in the popup menu
3. Choose JBoss and press Next
4. Specify the Wildfly build location and press Next

=> Domain combo box is empty, so I can not choose a domain. Finish button is disabled.

Besides implementing this aspect, additional changes should be:
- Wildfly 8 needs to declare Java EE 7 compatibility
- We should present the Wildfly name in the UI, either as a separate item in the server type list, or by renaming the JBoss item to "JBoss/Wildfly"
Comment 1 Petr Hejl 2013-08-20 13:51:42 UTC
This will need some more work as jsr88 has been dropped completely.
Comment 2 arungupta 2013-10-21 20:59:37 UTC
Would like this support in order to demonstrate #JavaEE7 in WildFly. This is not working even for NetBeans 7.4.
Comment 3 Petr Jiricka 2013-10-22 08:34:38 UTC
Unfortunately, Wildfly continues the JBoss tradition of significantly overhauling the server internals in every major release, which makes IDE integration very difficult :-( So as Petr H writes above, this is not easy. 

As for support in NetBeans 7.4 - at the time of NetBeans 7.4 code freeze, Wildfly 8 was still in Alpha, i.e. too early to expect it would be supported in a final release of NetBeans.
Comment 4 ehsavoie 2013-10-22 14:37:37 UTC
I proposed my help on the netcat nbjee mailing lists.
Maybe we ould take advantage of what JBoss / RedHat is doing in Eclipse, since the use cases are quite the same, thus we would have only to concentrate on the GUI.
What do you think ?
Comment 5 cdavis 2013-10-28 20:06:32 UTC
The issue of available servers is so important that the lack of servers in NB has driven me to look at Eclipse.  Eclipse appears to accommodate ALL the major servers which leads me to ask why it is so difficult in NB?  Maybe NB needs to change how servers are integrated so that we can just point it to any server and the server can be used??  I obviously have no idea how much work would be required to accomplish this feat!  But I think the limited availability of servers is a huge draw-back for NB.

1)  Tomcat is only for browsers and I do Java Swing/JavaFX clients;
2)  Glassfish apparently cannot create and serve up a DataSource for either DB2 or postgresql even though it appears to have awesome websockets that work;
3)  WebLogic (free version 12.1.2) cannot create a wlfullclient.jar so fails to provide a usable EJB environment;
4)  JBoss 7.1.1 Final is the only server that works for EJB accessing a database and it has had problems I seem to have overcome by some accident.

This short list is a huge limitation.

I want to use Wildfly (which is now in beta stage) and I want to use TomEE+ as soon as it is integrated into Tomcat 8 which will have the Java API websockets implementation.  To be frank, I'd like to use openEJB as it is as a stand-alone EJB server!  I DO NOT WANT to have to use Eclipse to have a choice of servers!!!!

So here's another vote for this issue and to expand the choices for NB.
Comment 6 puce 2013-11-05 13:30:58 UTC
+1 Now that Oracle stopped its commercial support for GlassFish, WildFly is getting even more important, I guess.

https://blogs.oracle.com/theaquarium/entry/java_ee_and_glassfish_server
Comment 7 jdbenitez 2013-11-12 11:31:02 UTC
I want switch to jboss because Oracle has plans for abandone comercial support of glassfish
Comment 8 grafviktor 2014-01-12 19:12:03 UTC
Hi. Here is a recipe, from a famous and former Oracle member, for those who struggling to get WildFly working on NetBeans 7.4:
http://blog.arungupta.me/2013/12/netbeans8-and-wildfly8-techtip-6/

Regards.
Comment 9 puce 2014-04-15 12:24:40 UTC
The plugin mentioned in that article doesn't seem to be available for NetBeans 8...
Comment 10 puce 2014-04-15 14:48:02 UTC
Another user mentioned the plugin is still available in the nightly version:

http://stackoverflow.com/questions/23081092/add-plugin-for-wildfly-application-server-to-netbeans?noredirect=1#comment35285357_23081092

Could you add it to the final version as well?
Comment 11 negora 2015-11-13 08:53:22 UTC
I believe that this report could be closed, Right? There's already built-in support for Wildfly in NetBeans IDE 8.1.
Comment 12 Petr Hejl 2015-11-13 08:57:08 UTC
Yep.