Geertjan's Blog

  • September 3, 2011

"More Complex" NetBeans Platform Samples... (Part 2)

Geertjan Wielenga
Product Manager

In response to "More Complex" NetBeans Platform Samples... (Part 1), Toni Epple has put together instructions for connecting to EJBs deployed to GlassFish from the NetBeans Platform:


The above was published today on NetBeans Zone. The instructions worked perfectly for me. I tweaked the article very slightly, so any errors in it are likely my fault rather than Toni's.

This is how the Projects window looks after having followed all the instructions in the article:

Looking forward to hearing what developers such as Sergio Bello (who has been eagerly awaiting a solution on this topic), as well as Antonio Vieiro, who has been working on this area too, make of the above!

Join the discussion

Comments ( 2 )
  • Toni Monday, September 5, 2011

    Hi Geertjan,

    thanks for editing the article. I probably should expand it to also cover deploying such an application to a different client, since you need to carry a lot of stuff with you (see my comment on the article in reply to Geoff).

    As far as I recall, Antonio Viero had submitted a patch to fix the problem with ClassLoaders in Glassfishs gf-client.jar, but it was rejected due to a lack of understanding/interest. I worked around this issue as described in the Troubleshooting section. In the meantime the issue seems to be fixed in glassfish 3.1. I didn't check the sources, but otherwise I'd get a ClassNotFoundException. So that's why no classloader hacks are required anymore.


  • guest Tuesday, September 6, 2011

    Here I am...

    If I include Glassfish dependencies in a library wrapper module, I still need to temporarily change the classloader when I lookup an EJB.

    I suppose that putting dependencies on the classpath with run.args.extra or in a script (as per Toni example) avoids the problem.

    Still investigating, anyway (oh, and I'm on GF 3.1.1).



Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.