Re: [wildfly-dev] wildfly 8 client library now requires Java 7 ?
On 09/13/2013 11:48 PM, David M. Lloyd wrote:
I've been building things with 1.7 and targeting them to 1.6 via
seven2six. So the following should all be 1.6 compatible (if they
aren't then please let me know because it's a bug):
* org.jboss.marshalling:jboss-marshalling:jar:1.4.0.Final
* org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta1
* org.jboss.sasl:jboss-sasl:jar:1.0.3.Final
* org.jboss.xnio:xnio-api:jar:3.1.0.CR7
* org.jboss.xnio:xnio-nio:jar:3.1.0.CR7
I'm noticing an issue currently. It seems something in xnio requires a
class only available in java7. I'll be re-opening the wfly bug for you
to investigate.
java.lang.NoClassDefFoundError: java/lang/ReflectiveOperationException
at org.xnio.ssl.JsseXnioSsl.<init>(JsseXnioSsl.java:81)
at org.xnio.Xnio.getSslProvider(Xnio.java:221)
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:188)
at
org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at
org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
Usecase is running eclipse with java6, then launching wildfly with
java7, but using the features in jbosstools to communicate with the
running server over management API. The jars we're using are:
<jbossdmr.version>1.2.0.Beta2</jbossdmr.version>
<jboss.logging.version>3.1.3.GA</jboss.logging.version>
<jboss.marshalling.version>1.4.1.Final</jboss.marshalling.version>
<jboss.marshalling.river.version>1.4.1.Final</jboss.marshalling.river.version>
<jboss.remoting.version>4.0.0.Beta1</jboss.remoting.version>
<jboss.sasl.version>1.0.3.Final</jboss.sasl.version>
<jboss.threads.version>2.1.1.Final</jboss.threads.version>
<wildfly.controller.version>8.0.0.Beta1</wildfly.controller.version>
<wildfly.protocol.version>8.0.0.Beta1</wildfly.protocol.version>
<xnio.api.version>3.1.0.CR7</xnio.api.version>
<xnio.nio.version>3.1.0.CR7</xnio.nio.version>