Isn't Anyone Migrating from JAX-RPC to JAX-WS?

Sun is recommending that web services that are based on JAX-RPC in the Java
Web Services Development Pack (JWSDP) be migrated to the new JAX-WS web
services API currently under development in the GlassFish project. JAX-RPC
will be deprecated. I posted the following query on this group and received
zero responses:
----------------------------------------------------------------------
I am having difficulty migrating a JAX-RPC application to JAX-WS.

The JAX-RPC web service uses custom parameters and return data carrier
classes. The data carrier classes look something like this:

    public class WsProperty {
        public String key;
        public String value;
    }

The JAX-RPC web methods look something like this:

    public WsProperty[] getProperties() throws RemoteException;

    public void setProperties(WsProperty[] properties) throws
RemoteException;

The resulting WSDL contains descriptors for the params and return types
along with the method itself.

My JAX-WS web methods look something like this:

    @WebMethod()
    @WebResult(name = "WsPropertyArray")
    public WsProperty[] getProperties() throws RemoteException {
        ...
    }

    @WebMethod()
    public void setProperties(@WebParam(name = "WsPropertyArray")
WsProperty[] properties) throws RemoteException {
        ...
    }

The problem is, I do not see any description of the custom data type in the
WSDL. Although the NetBeans tools seem to generate generic objects with
similar names, they do not implement anything beyond the base Object
methods. I could use reflection to get the data, but that seems wrong. Any
suggestions?
----------------------------------------------------------------------
I am probably missing something obvious.