Thursday Jun 07, 2012

AntClassLoader bug exposed by forgetful NetBeans

Many users have run into ClassNotFoundExceptions and NoClassDefFoundErrors after working with web services that target GlassFish while developing their projects in NetBeans.

The issue usually appears as a dialog similar to this

This can be pretty debilitating.

The bug appears to be in the AntClassLoader, which is tickled by the wsimport ant task that ships with GlassFish 3.1.2. The fix is pretty simple: Upgrade the Metro bits that ship in 3.1.2 with bits that have had a patch applied.

There are detailed instruction about installing the updated Metro bits onto GlassFish. This upgrade is probably useful for any install of GlassFish 3.1, but it is critically important for folks that develop web services from inside NetBeans and deploy them onto GlassFish 3.1.2.

Monday Jul 25, 2011

Prototype of cluster and instance support available for evaluation

I recently checked in an initial implementation of cluster and stand-alone instance support into the NetBeans trunk and would like to get feedback on the utility of the feature from folks.

  • Users can register a cluster or stand-alone instance as a deployment target for ant and maven based Java EE projects.
  • Users can undeploy applications from a cluster or stand-alone instance
  • Users can start and stop cluster or stand-alone instances that are controlled by a local or remote domain. Note: The remote domain must be started/stopped on the remote host, outside of the IDE, to be able to manipulate the state of its clusters and instances.

There are not a lot of user visible changes.

The biggest change is on the last page of the registration wizard.

The new 'Target' field is used to specify a value which is used to identify a cluster and/or stand-alone instance. This name is often used as the value of the --target option, associated with a number of asadmin subcommands. If you leave the field blank, all commands will be applied to the DAS instance (as they have in the past).

I have not extended the NB/GF integration to help you create clusters or stand-alone instances at this point, so you must use asadmin to do those kinds of things.

I plan on producing a screencast that demonstrates the cluster/instance support capabilities in the next couple days. If you would be willing to wade in and provide feedback before that screencast is ready, please feel free and add your comments onto this blog entry.

Thursday Mar 10, 2011

GlassFish Server 3.1 fully integrated in dev builds of 7.0

After the FCS bits for GlassFish Server 3.1 became available, I had to make a change in the GlassFish integration plugin sources and the web to get it integrated into the dev builds.

The folks that build the installer also needed to make some changes and it looks like they are done, too.

Thursday Dec 16, 2010

Fewer Wizards, More Magic

summary of recent changes in the registration wizard for GlassFish Server 3.0.x and GlassFish Server 3.1[Read More]

Friday Sep 10, 2010

Web Service Nodes of a GlassFish Server 3.1 instance

NetBeans has supported web service development for quite a while but... I always hit an issue when I develop web services clients that bothered me... I never knew the wsdl url for services that I had deployed. So, if I was creating a client for a web service, I would need to have the service's implementation project available OR I would need to fire up the admin gui to find out what the wsdl url is to complete either of these two dialogs:

The Add Web Service dialog

The Create Web Service Client dialog

I got tired of feeling stupid and opening the admin gui to lookup the wsdl url (or to run the 'tester'), so I started to look for a solution for folks that do web service development against GlassFish Server 3.1.... and here it is in a single screenshot:

Web services on a registered server exposed with
an action to test the service and
an action to copy the wsdl url to the clipboard

A special shoutout to Ludovic Champenois and Jitendra Kotamraju for exposing the data that I needed, restfully.

NOTE: To see these new nodes you will need to get a recent nightly build of NetBeans 6.10 that includes GlassFish Server 3.1 build 20 or higher (or a post September 9, 2010 nightly build of GlassFish Server 3.1)

Sunday Aug 22, 2010

Create domains that use the default ports

Some will call this a new feature. Some will call this a bug fix.

I call it a chance to slap my forehead, really hard, again.

A couple years ago, we made it really hardIMPOSSIBLE to use NetBeans to create a domain that uses the 'default ports'. The strategy we decided to employ was one that would let users create multiple domains that could run at the same time.

That has changed, today.

If you want to create a domain that can run while another domain is running, you will need to uncheck the 'Use default ports' control. If there is some process active on the default ports (like 4848 or 8080), the dialog opens with 'Use default ports' unselected AND disabled. If you hover over the disabled control, the tool tip will provide more details about the 'problem'.

Monday Aug 02, 2010

Supporting glassfish-resources.xml

In my initial blog post about GlassFish Server 3.1 support in NetBeans dev builds, I mentioned that projects that target 3.1 will get glassfish-\*.xml deployment descriptors instead of sun-\*.xml deployment descriptors. There are a number of other files that are getting name and content changes in 3.1. One of the files that is getting changed is the resource definition file, previously known as sun-resources.xml.

If you create a project that targets GlassFish Server 3.1 and that project needs to define resources, the definitions will be persisted in a file named glassfish-resources.xml.

WebApp431 (web app for three one) targets GlassFish Server 3.1

The content of an automatically generated glassfish-resources.xml file.

Vince Kraemer writes the entries in this blog.


« June 2016

No bookmarks in folder