[PJUG Javamail] error running JAX-WS client under NetBeans 6.5 Glassfixh v3

[Michael Phoenix]

I am getting a very ambiguous build error when trying to build a JAX-WS
client.

The error messages on my console are as follows:
*C:\lingosys\LNtestWS\nbproject\jaxws-build.xml:31: The following error
occurred while executing this line:
C:\lingosys\LNtestWS\nbproject\build-impl.xml:212:
org.netbeans.modules.java.source.ant.UserCancel*

jaxws-build.ws starting at line 30:
*    <target name="wsimport-client-compile" depends="-pre-pre-compile">
        <webproject2:javac srcdir="${build.generated.dir}/wsimport/client"
classpath="${j2ee.platform.wsimport.classpath}:${javac.classpath}"
destdir="${build.classes.dir}"/>
        <copy todir="${build.classes.dir}">
            <fileset dir="${build.generated.dir}/wsimport/binaries"
includes="**/*.xml"/>
        </copy>
    </target>
</project>
*

build-impl.xml starting at line 212
*                <javac debug="@{debug}" deprecation="${javac.deprecation}"
destdir="@{destdir}" encoding="${source.encoding}" excludes="@{excludes}"
includeantruntime="false" includes="@{includes}" source="${javac.source}"
srcdir="@{srcdir}" target="${javac.target}">
                    <classpath>
                        <path path="@{classpath}"/>
                    </classpath>
                    <compilerarg line="${javac.compilerargs}
${javac.compilerargs.jaxws}"/>
                    <customize/>
                </javac>*

I don't know if this may be part of the problem, but the service it's
pointing to is JAX-RPC. My understanding is that the client shouldn't be
concerned if you have valid WSDL. I searched but couldn't find a definite
yes or no answer to the question can a JAX-WS client consume a JAX-RPC
service. Any help here would be appreciated.

Another note. I just checked out the glassfish v3 server log messages. It
included the following:
WARNING: JNDI provider for JNDI URLs that look like rmi://host:port/name is
not working. The JMX RMI connector will not be accessible to clients, even
if it appears to load correctly.  See issues #6025, 5637
Have no idea how to find those issues it refers to.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pjug.org/pipermail/javamail/attachments/20080923/7e59c32c/attachment.html