NetBeans Version for WSIT in GlassFish

Guest Author
The NetBeans 5.5 IDE is tested with Sun
Java System Application Server PE 9.0 Update Release 1
or GlassFish
. It also used to work with GlassFish
but stopped doing so after b26
because of issue
in NetBeans. A patch
has been applied to NetBeans 5.5.1 which can be downloaded from here
(select 5.5.1 from the "NetBeans Version" list box).

I downloaded NetBeans
5.5.1 dev build
, installed NetBeans
WSIT plug-in
available from the Update Center, and registered GlassFish
instance following first
of the Flash demo. Then I built a Reliable Web Service and invoked it
using the second part
of the demo. Note that to install the WSIT plug-in from NetBeans Update Center,
"NetBeans Update Center Beta" checkbox has to be explicitly selected
as it is not the default option.

Look for the window title in the screen shots below which indicates NetBeans
5.5.1 dev build dated Jan 11th. And the GlassFish v2 b31 was promoted this
morning as well.

Fig 1: WSIT Plug-in installed in NetBeans 5.5.1 dev build

Fig 2: GlassFish
v2 b31
configured in NetBeans 5.5.1 dev build

Fig 3: Reliable Endpoint Deployed in NetBeans 5.5.1 dev build

Fig 4: Reliable Client invoked from NetBeans 5.5.1 dev build

Look at the last TerminateSequence SOAP message in
the output log window terminating the reliable sequence.

In short, if you want to use build a .NET 3.0 interoperable reliable secure
Web service, use NetBeans
5.5.1 dev build
, GlassFish
v2 b31
and NetBeans WSIT plug-in
(from Update Center) and follow the two part (part
and part 2)
interactive demo .

Technorati: NetBeans GlassFish

Join the discussion

Comments ( 7 )
  • Bukkake Queen Friday, January 12, 2007
    1st Prize for the most Convoluted Hello World program :-)
  • Arun Friday, January 12, 2007
    But imagine the power that can be harnessed using this simple "Hello World". A fully .NET 3.0 interoperable secure reliable transactional Web service can be built in minutes.
  • TR Saturday, January 13, 2007
    I just downloaded the nightly build of NetBeans 5.5.1, 200701120600, and it still fails to work with Glassfish V2 Build 31. Is there any particular configuration that need be done besides having these new builds?
  • TR Saturday, January 13, 2007
    Here is the exception:
    Starting Sun Java System Application Server 9.1 (build b31) ...
    CORE5098: AS Socket Service Initialization has been completed.
    CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_07] from [Sun Microsystems Inc.]
    SEC1002: Security Manager is OFF.
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
    Caused by: java.lang.ClassFormatError: Invalid index 2 in LocalVariableTable in class file com/sun/enterprise/resource/ResourceManagerImpl
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at com.sun.appserv.server.util.ASURLClassLoader.loadClass(ASURLClassLoader.java:100)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
    at com.sun.enterprise.resource.PoolManagerImpl.<init>(PoolManagerImpl.java:88)
    at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.initialize(ConnectorConnectionPoolAdminServiceImpl.java:1535)
    at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.<init>(ConnectorConnectionPoolAdminServiceImpl.java:77)
    at com.sun.enterprise.connectors.ConnectorAdminServicesFactory.getService(ConnectorAdminServicesFactory.java:49)
    at com.sun.enterprise.connectors.ConnectorRuntime.createServices(ConnectorRuntime.java:130)
    at com.sun.enterprise.connectors.ConnectorRuntime.getRuntime(ConnectorRuntime.java:90)
    at com.sun.jdo.spi.persistence.support.sqlstore.ejb.SunTransactionHelper.<clinit>(SunTransactionHelper.java:96)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:242)
    at com.sun.jdo.spi.persistence.support.sqlstore.ejb.PersistenceManagerServiceImpl.forceInit(PersistenceManagerServiceImpl.java:71)
    at com.sun.jdo.spi.persistence.support.sqlstore.ejb.PersistenceManagerServiceImpl.<clinit>(PersistenceManagerServiceImpl.java:54)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:164)
    at com.sun.enterprise.server.ondemand.OnDemandServer.instantiateRuntimeServices(OnDemandServer.java:158)
    at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
    at com.sun.enterprise.server.ondemand.OnDemandServer.onInitialization(OnDemandServer.java:93)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:316)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
    ... 5 more
  • Arun Saturday, January 13, 2007
    TR, This is also reported on dev@glassfish alias. Please follow the thread at:


    For some, this problem has disappeared after using an updated version of JDK (i.e. JDK 1.5.0_10).

  • Tim Saturday, January 13, 2007
    Ah, thanks for the tip; I upgraded from 1.5.0_07 to 1.6.0 and this issue goes away.
  • Arun Sunday, January 14, 2007
    Glad you got it working.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.