[jboss-jira] [JBoss JIRA] (WFLY-7864) Missing dependency in wildfly-jms-client-bom

[Jeff Mesnil (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13347705#comment-13347705 ] 

Jeff Mesnil commented on WFLY-7864:
-----------------------------------

Note also that a standalone Java app requires the presence of wildfly-config.xml to negotiate auth with WildFly.

I have updated the helloworld-jms and ejb-remote quickstarts as an example of such configuration (https://github.com/wildfly/quickstart/pull/122)

> Missing dependency in wildfly-jms-client-bom
> --------------------------------------------
>
>                 Key: WFLY-7864
>                 URL: https://issues.jboss.org/browse/WFLY-7864
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>
> I am unable to do JNDI lookup if I use only wildfly-jms-client-bom. I see the following exception
> {code}
> java.lang.reflect.InvocationTargetException
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoadException
> 	at org.jboss.remoting3.EndpointBuilder.build(EndpointBuilder.java:117)
> 	at org.jboss.remoting3.ConfigurationEndpointSupplier.lambda$static$0(ConfigurationEndpointSupplier.java:68)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at org.jboss.remoting3.ConfigurationEndpointSupplier.<clinit>(ConfigurationEndpointSupplier.java:48)
> 	at org.wildfly.common.context.ContextManager.setGlobalDefaultSupplierIfNotSet(ContextManager.java:108)
> 	at org.jboss.remoting3.Endpoint.lambda$static$0(Endpoint.java:58)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at org.jboss.remoting3.Endpoint.<clinit>(Endpoint.java:56)
> 	at org.wildfly.naming.client.remote.RemoteNamingProviderFactory.supportsUriScheme(RemoteNamingProviderFactory.java:70)
> 	at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:318)
> 	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:123)
> 	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:113)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:417)
> 	at org.jboss.as.quickstarts.jms.HelloWorldJMSClient.main(HelloWorldJMSClient.java:62)
> 	... 6 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.modules.ModuleLoadException
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 	... 20 more
> {code}
> This issue was marked as Blocker because there shouldn't be needed any additional dependencies if wildfly-jms-client-bom is used.
> *Customer impact:* Standalone clients doesn't work out of the box and programmer has to append additional dependency. This is serious user experience issue. Quickstarts do not work as well.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)