[wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

[wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Arun Gupta
Hello there ..

Trying to deploy a simple JMS sample that uses classic and simplified
API. The sample is available at:

https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive-simple

But the deployment is failing with:

07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
rolled back with the following failure message:
{"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]"
]}


Any suggestions ?

Arun
--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Nick Mpallas
Arun,
you have to create the queues + the name of the exposed ConnectionFactory depends if you are connecting from an in-vm factory or you want a remote connection factory.


On Wed, Oct 30, 2013 at 3:05 PM, Arun Gupta <[hidden email]> wrote:
Hello there ..

Trying to deploy a simple JMS sample that uses classic and simplified
API. The sample is available at:

https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive-simple

But the deployment is failing with:

07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
rolled back with the following failure message:
{"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]",
"jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
is missing [jboss.naming.context.java.global.jms.myQueue2]"
]}


Any suggestions ?

Arun
--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
\n\m
"camel is a horse made up in a laboratory"

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Jeff Mesnil
In reply to this post by Arun Gupta

On 30 Oct 2013, at 15:05, Arun Gupta <[hidden email]> wrote:

> Hello there ..
>
> Trying to deploy a simple JMS sample that uses classic and simplified
> API. The sample is available at:
>
> https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive-simple
>
> But the deployment is failing with:
>
> 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
> 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
> rolled back with the following failure message:
> {"JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
> is missing [jboss.naming.context.java.global.jms.myQueue2]",
> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
> is missing [jboss.naming.context.java.global.jms.myQueue2]",
> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
> is missing [jboss.naming.context.java.global.jms.myQueue2]",
> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
> is missing [jboss.naming.context.java.global.jms.myQueue2]"
> ]}
>
>
> Any suggestions ?

which standalone configuration are your using?

JMS is part of standalone-full.xml and not in standalone.xml.

jeff

--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Arun Gupta
In reply to this post by Nick Mpallas
Both of these should not be required for Java EE 7.

The sample has:

@JMSDestinationDefinitions({@JMSDestinationDefinition(name =
"java:global/jms/myQueue2",
interfaceName = "javax.jms.Queue")
})

so the destination should be created as part of deployment.

And JMSContext relies upon default JMS Connection Factory.

Arun

On Wed, Oct 30, 2013 at 7:08 AM, Nick Mpallas <[hidden email]> wrote:

> Arun,
> you have to create the queues + the name of the exposed ConnectionFactory
> depends if you are connecting from an in-vm factory or you want a remote
> connection factory.
>
>
> On Wed, Oct 30, 2013 at 3:05 PM, Arun Gupta <[hidden email]> wrote:
>>
>> Hello there ..
>>
>> Trying to deploy a simple JMS sample that uses classic and simplified
>> API. The sample is available at:
>>
>>
>> https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive-simple
>>
>> But the deployment is failing with:
>>
>> 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
>> 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
>> rolled back with the following failure message:
>> {"JBAS014771: Services with missing/unavailable dependencies" => [
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
>> is missing
>> [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
>> is missing
>> [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]"
>> ]}
>>
>>
>> Any suggestions ?
>>
>> Arun
>> --
>> Blog: http://blog.arungupta.me
>> Twitter: http://twitter.com/arungupta
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
>
> --
> \n\m
> "camel is a horse made up in a laboratory"



--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Nick Mpallas
Jeff has a  strong point because if you are using the standalone.xml and not the full one..the JMS isn't loaded.


On Wed, Oct 30, 2013 at 3:10 PM, Arun Gupta <[hidden email]> wrote:
Both of these should not be required for Java EE 7.

The sample has:

@JMSDestinationDefinitions({@JMSDestinationDefinition(name =
"java:global/jms/myQueue2",
interfaceName = "javax.jms.Queue")
})

so the destination should be created as part of deployment.

And JMSContext relies upon default JMS Connection Factory.

Arun

On Wed, Oct 30, 2013 at 7:08 AM, Nick Mpallas <[hidden email]> wrote:
> Arun,
> you have to create the queues + the name of the exposed ConnectionFactory
> depends if you are connecting from an in-vm factory or you want a remote
> connection factory.
>
>
> On Wed, Oct 30, 2013 at 3:05 PM, Arun Gupta <[hidden email]> wrote:
>>
>> Hello there ..
>>
>> Trying to deploy a simple JMS sample that uses classic and simplified
>> API. The sample is available at:
>>
>>
>> https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive-simple
>>
>> But the deployment is failing with:
>>
>> 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
>> 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
>> rolled back with the following failure message:
>> {"JBAS014771: Services with missing/unavailable dependencies" => [
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
>> is missing
>> [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
>> is missing
>> [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]"
>> ]}
>>
>>
>> Any suggestions ?
>>
>> Arun
>> --
>> Blog: http://blog.arungupta.me
>> Twitter: http://twitter.com/arungupta
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
>
> --
> \n\m
> "camel is a horse made up in a laboratory"



--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta



--
\n\m
"camel is a horse made up in a laboratory"

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Arun Gupta
In reply to this post by Jeff Mesnil
Ah, that might be it.

Noob question then ...

How do you tell standalone.sh to use standalone-full.xml ?

Arun


On Wed, Oct 30, 2013 at 7:10 AM, Jeff Mesnil <[hidden email]> wrote:

>
> On 30 Oct 2013, at 15:05, Arun Gupta <[hidden email]> wrote:
>
>> Hello there ..
>>
>> Trying to deploy a simple JMS sample that uses classic and simplified
>> API. The sample is available at:
>>
>> https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive-simple
>>
>> But the deployment is failing with:
>>
>> 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
>> 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
>> rolled back with the following failure message:
>> {"JBAS014771: Services with missing/unavailable dependencies" => [
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
>> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
>> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]"
>> ]}
>>
>>
>> Any suggestions ?
>
> which standalone configuration are your using?
>
> JMS is part of standalone-full.xml and not in standalone.xml.
>
> jeff
>
> --
> Jeff Mesnil
> JBoss, a division of Red Hat
> http://jmesnil.net/
>



--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Stuart Douglas
./standalone.sh -c standalone-full.xml


On Wed, Oct 30, 2013 at 3:12 PM, Arun Gupta <[hidden email]> wrote:
Ah, that might be it.

Noob question then ...

How do you tell standalone.sh to use standalone-full.xml ?

Arun


On Wed, Oct 30, 2013 at 7:10 AM, Jeff Mesnil <[hidden email]> wrote:
>
> On 30 Oct 2013, at 15:05, Arun Gupta <[hidden email]> wrote:
>
>> Hello there ..
>>
>> Trying to deploy a simple JMS sample that uses classic and simplified
>> API. The sample is available at:
>>
>> https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive-simple
>>
>> But the deployment is failing with:
>>
>> 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
>> 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
>> rolled back with the following failure message:
>> {"JBAS014771: Services with missing/unavailable dependencies" => [
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
>> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
>> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
>> is missing [jboss.naming.context.java.global.jms.myQueue2]"
>> ]}
>>
>>
>> Any suggestions ?
>
> which standalone configuration are your using?
>
> JMS is part of standalone-full.xml and not in standalone.xml.
>
> jeff
>
> --
> Jeff Mesnil
> JBoss, a division of Red Hat
> http://jmesnil.net/
>



_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Pete Muir
In reply to this post by Arun Gupta
http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/#run_the_quickstarts

On 30 Oct 2013, at 14:12, Arun Gupta <[hidden email]> wrote:

> Ah, that might be it.
>
> Noob question then ...
>
> How do you tell standalone.sh to use standalone-full.xml ?
>
> Arun
>
>
> On Wed, Oct 30, 2013 at 7:10 AM, Jeff Mesnil <[hidden email]> wrote:
>>
>> On 30 Oct 2013, at 15:05, Arun Gupta <[hidden email]> wrote:
>>
>>> Hello there ..
>>>
>>> Trying to deploy a simple JMS sample that uses classic and simplified
>>> API. The sample is available at:
>>>
>>> https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receive-simple
>>>
>>> But the deployment is failing with:
>>>
>>> 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread -
>>> 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was
>>> rolled back with the following failure message:
>>> {"JBAS014771: Services with missing/unavailable dependencies" => [
>>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory
>>> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory
>>> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]",
>>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue
>>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue
>>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue
>>> is missing [jboss.naming.context.java.global.jms.myQueue2]",
>>> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue
>>> is missing [jboss.naming.context.java.global.jms.myQueue2]"
>>> ]}
>>>
>>>
>>> Any suggestions ?
>>
>> which standalone configuration are your using?
>>
>> JMS is part of standalone-full.xml and not in standalone.xml.
>>
>> jeff
>>
>> --
>> Jeff Mesnil
>> JBoss, a division of Red Hat
>> http://jmesnil.net/
>>
>
>
>
> --
> Blog: http://blog.arungupta.me
> Twitter: http://twitter.com/arungupta
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Jeff Mesnil
In reply to this post by Arun Gupta

On 30 Oct 2013, at 15:12, Arun Gupta <[hidden email]> wrote:

> Ah, that might be it.
>
> Noob question then ...
>
> How do you tell standalone.sh to use standalone-full.xml ?

standalone.sh -c standalone-full.xml

bear in mind that the standalone.xml corresponds to the Web profile (and JMS is not part of it) while standalone-full.xml corresponds to the whole EE7 stack.

jeff

--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Arun Gupta
On Wed, Oct 30, 2013 at 7:14 AM, Jeff Mesnil <[hidden email]> wrote:

>
> On 30 Oct 2013, at 15:12, Arun Gupta <[hidden email]> wrote:
>
>> Ah, that might be it.
>>
>> Noob question then ...
>>
>> How do you tell standalone.sh to use standalone-full.xml ?
>
> standalone.sh -c standalone-full.xml
Instead of copy/pasting the command as is, I tried:

./bin/standalone.sh -c standalone/configuration/standalone-full.xml

And of course that was incorrect :)

What is the idea behind specifying the complete configuration file
name (including extension) instead of just the file name ? I think the
latter  is less verbose.

>
> bear in mind that the standalone.xml corresponds to the Web profile (and JMS is not part of it) while standalone-full.xml corresponds to the whole EE7 stack.

That I know :)

Arun

>
> jeff
>
> --
> Jeff Mesnil
> JBoss, a division of Red Hat
> http://jmesnil.net/
>



--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Alessio Soldano
In reply to this post by Jeff Mesnil
On 30/10/13 15:14, Jeff Mesnil wrote:
> standalone.sh -c standalone-full.xml
>
> bear in mind that the standalone.xml corresponds to the Web profile (and JMS is not part of it) while standalone-full.xml corresponds to the whole EE7 stack.
Not really a problem here :-), but just FYI standalone.xml has more then
the minimum required for Web profile, as it comes with webservices
subsystem (hence JSR 224, JSR 181, JSR 109) enabled.
But still, for the whole EE7 stack, standalone-full.xml is required.

--
Alessio Soldano
Web Service Lead, JBoss

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

jtgreene
Administrator

On Oct 30, 2013, at 9:26 AM, Alessio Soldano <[hidden email]> wrote:

> On 30/10/13 15:14, Jeff Mesnil wrote:
>> standalone.sh -c standalone-full.xml
>>
>> bear in mind that the standalone.xml corresponds to the Web profile (and JMS is not part of it) while standalone-full.xml corresponds to the whole EE7 stack.
> Not really a problem here :-), but just FYI standalone.xml has more then
> the minimum required for Web profile, as it comes with webservices
> subsystem (hence JSR 224, JSR 181, JSR 109) enabled.
> But still, for the whole EE7 stack, standalone-full.xml is required.


And remote ejb. The difference is JMS + Corba are added in full.

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Arun Gupta
Got it, will work on a blog entry for this and share!

On Wed, Oct 30, 2013 at 7:46 AM, Jason Greene <[hidden email]> wrote:

>
> On Oct 30, 2013, at 9:26 AM, Alessio Soldano <[hidden email]> wrote:
>
>> On 30/10/13 15:14, Jeff Mesnil wrote:
>>> standalone.sh -c standalone-full.xml
>>>
>>> bear in mind that the standalone.xml corresponds to the Web profile (and JMS is not part of it) while standalone-full.xml corresponds to the whole EE7 stack.
>> Not really a problem here :-), but just FYI standalone.xml has more then
>> the minimum required for Web profile, as it comes with webservices
>> subsystem (hence JSR 224, JSR 181, JSR 109) enabled.
>> But still, for the whole EE7 stack, standalone-full.xml is required.
>
>
> And remote ejb. The difference is JMS + Corba are added in full.
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Brian Stansberry
In reply to this post by Arun Gupta
On 10/30/13 9:21 AM, Arun Gupta wrote:

> On Wed, Oct 30, 2013 at 7:14 AM, Jeff Mesnil <[hidden email]> wrote:
>>
>> On 30 Oct 2013, at 15:12, Arun Gupta <[hidden email]> wrote:
>>
>>> Ah, that might be it.
>>>
>>> Noob question then ...
>>>
>>> How do you tell standalone.sh to use standalone-full.xml ?
>>
>> standalone.sh -c standalone-full.xml
> Instead of copy/pasting the command as is, I tried:
>
> ./bin/standalone.sh -c standalone/configuration/standalone-full.xml
>
> And of course that was incorrect :)
>
> What is the idea behind specifying the complete configuration file
> name (including extension) instead of just the file name ? I think the
> latter  is less verbose.
>

You mean why not just bin/standalone.sh -c standalone-full  ?

No particular reason. It never occurred to me. Thinking back on it, it
partly arose because in AS < 7 the -c value was basically a reference to
a dir name, while in AS7 it's a ref to a file name. The entire structure
of the AS dist is radically different in AS7. Being more explicit about
that difference was more important at the time than it is now.

If bin/standalone.sh -c st<tab complete to
andalone/configuration/standalone-full.xml> would work I'd be real
tempted to support that.

>>
>> bear in mind that the standalone.xml corresponds to the Web profile (and JMS is not part of it) while standalone-full.xml corresponds to the whole EE7 stack.
>
> That I know :)
>
> Arun
>
>>
>> jeff
>>
>> --
>> Jeff Mesnil
>> JBoss, a division of Red Hat
>> http://jmesnil.net/
>>
>
>
>


--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Arun Gupta
>>
>> What is the idea behind specifying the complete configuration file
>> name (including extension) instead of just the file name ? I think the
>> latter  is less verbose.
>>
>
> You mean why not just bin/standalone.sh -c standalone-full  ?
>
> No particular reason. It never occurred to me. Thinking back on it, it
> partly arose because in AS < 7 the -c value was basically a reference to
> a dir name, while in AS7 it's a ref to a file name. The entire structure
> of the AS dist is radically different in AS7. Being more explicit about
> that difference was more important at the time than it is now.
>
> If bin/standalone.sh -c st<tab complete to
> andalone/configuration/standalone-full.xml> would work I'd be real
> tempted to support that.

This would be really nice, simplicity and intuitiveness go a long way
in better developer experience.

Arun

Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Ladislav Thon
>>> What is the idea behind specifying the complete configuration file
>>> name (including extension) instead of just the file name ? I think the
>>> latter  is less verbose.
>>>
>>
>> You mean why not just bin/standalone.sh -c standalone-full  ?
>>
>> No particular reason. It never occurred to me. Thinking back on it, it
>> partly arose because in AS < 7 the -c value was basically a reference to
>> a dir name, while in AS7 it's a ref to a file name. The entire structure
>> of the AS dist is radically different in AS7. Being more explicit about
>> that difference was more important at the time than it is now.
>>
>> If bin/standalone.sh -c st<tab complete to
>> andalone/configuration/standalone-full.xml> would work I'd be real
>> tempted to support that.
>
> This would be really nice, simplicity and intuitiveness go a long way
> in better developer experience.

Wonder how that would work together with -Djboss.server.base.dir and/or
-Djboss.server.config.dir [1]. A great potential for confusion I see.

[1] https://docs.jboss.org/author/display/WFLY8/Command+line+parameters

LT
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] JMS 2 sample in WildFly 8 giving "missing/unavailable dependencies"

Brian Stansberry
On 10/31/13 4:17 AM, Ladislav Thon wrote:

>>>> What is the idea behind specifying the complete configuration file
>>>> name (including extension) instead of just the file name ? I think the
>>>> latter  is less verbose.
>>>>
>>>
>>> You mean why not just bin/standalone.sh -c standalone-full  ?
>>>
>>> No particular reason. It never occurred to me. Thinking back on it, it
>>> partly arose because in AS < 7 the -c value was basically a reference to
>>> a dir name, while in AS7 it's a ref to a file name. The entire structure
>>> of the AS dist is radically different in AS7. Being more explicit about
>>> that difference was more important at the time than it is now.
>>>
>>> If bin/standalone.sh -c st<tab complete to
>>> andalone/configuration/standalone-full.xml> would work I'd be real
>>> tempted to support that.
>>
>> This would be really nice, simplicity and intuitiveness go a long way
>> in better developer experience.
>
> Wonder how that would work together with -Djboss.server.base.dir and/or
> -Djboss.server.config.dir [1]. A great potential for confusion I see.
>

Yes. That's why we don't support it now. If we ever did we'd have to
enforce clear rules about the relationships between these things
(basically the same rules we have now.) It's just not worth it to me to
add that complexity when tab completion doesn't fill in the path anyway.

> [1] https://docs.jboss.org/author/display/WFLY8/Command+line+parameters
>
> LT
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev