7:18 p.m.
I'm working on getting the helloworld-jms quickstart from
https://github.com/jbossas/quickstart.git running against an as7.1.0.Final instance, and
one change I had to make was to add the jboss-marshalling-river dependency shown below.
Without this I'm getting a "Could not find a marshaller factory for river
marshalling strategy" failure. This seems like quite a low level dependency for a
user to have to figure out. Shouldn't this be coming from either the jboss-as-naming
or the jboss-as-messaging, which ever one is needing this for the protocol?
<dependencies>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-naming</artifactId>
<version>7.1.0.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.jms</groupId>
<artifactId>jboss-jms-api_1.1_spec</artifactId>
<version>1.0.0.Final</version>
<!--scope>provided</scope-->
</dependency>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-messaging</artifactId>
<version>7.1.0.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.marshalling</groupId>
<artifactId>jboss-marshalling-river</artifactId>
<version>1.3.9.GA</version>
</dependency>
</dependencies>
7:33 p.m.
New subject: Why should a remote jndi client have to depend on jboss-marshalling-river?
You should just need org.jboss: jboss-remote-naming and hornetq
Sent from my iPhone
On Mar 22, 2012, at 7:21 PM, Scott Stark <sstark(a)redhat.com> wrote:
I'm working on getting the helloworld-jms quickstart from
https://github.com/jbossas/quickstart.git running against an as7.1.0.Final instance, and
one change I had to make was to add the jboss-marshalling-river dependency shown below.
Without this I'm getting a "Could not find a marshaller factory for river
marshalling strategy" failure. This seems like quite a low level dependency for a
user to have to figure out. Shouldn't this be coming from either the jboss-as-naming
or the jboss-as-messaging, which ever one is needing this for the protocol?
<dependencies>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-naming</artifactId>
<version>7.1.0.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.jms</groupId>
<artifactId>jboss-jms-api_1.1_spec</artifactId>
<version>1.0.0.Final</version>
<!--scope>provided</scope-->
</dependency>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-messaging</artifactId>
<version>7.1.0.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.marshalling</groupId>
<artifactId>jboss-marshalling-river</artifactId>
<version>1.3.9.GA</version>
</dependency>
</dependencies>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
7:47 p.m.
New subject: Why should a remote jndi client have to depend on jboss-marshalling-river?
I tried each of the following individually in order, and then even all together, but I
still fail to pickup the jboss-marshalling-river dependency.
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-jms-client</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-jms</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-core-client</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-core</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
----- Original Message -----
From: "Jason Greene" <jgreene(a)redhat.com>
To: "Scott Stark" <sstark(a)redhat.com>
Cc: "jboss-as7-dev(a)lists.jboss.org Development"
<jboss-as7-dev(a)lists.jboss.org>
Sent: Thursday, March 22, 2012 5:33:05 PM
Subject: Re: [jboss-as7-dev] Why should a remote jndi client have to depend
on jboss-marshalling-river?
You should just need org.jboss: jboss-remote-naming and hornetq
Sent from my iPhone
On Mar 22, 2012, at 7:21 PM, Scott Stark <sstark(a)redhat.com> wrote:
I'm working on getting the helloworld-jms quickstart from
https://github.com/jbossas/quickstart.git running against an as7.1.0.Final instance, and
one change I had to make was to add the jboss-marshalling-river dependency shown below.
Without this I'm getting a "Could not find a marshaller factory for river
marshalling strategy" failure. This seems like quite a low level dependency for a
user to have to figure out. Shouldn't this be coming from either the jboss-as-naming
or the jboss-as-messaging, which ever one is needing this for the protocol?
<dependencies>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-naming</artifactId>
<version>7.1.0.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.jms</groupId>
<artifactId>jboss-jms-api_1.1_spec</artifactId>
<version>1.0.0.Final</version>
<!--scope>provided</scope-->
</dependency>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-messaging</artifactId>
<version>7.1.0.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.marshalling</groupId>
<artifactId>jboss-marshalling-river</artifactId>
<version>1.3.9.GA</version>
</dependency>
</dependencies>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
7:49 p.m.
New subject: Why should a remote jndi client have to depend on jboss-marshalling-river?
It looks like the scope was set to provided. I will change this for the
next release.
Stuart
On Thu, 2012-03-22 at 20:47 -0400, Scott Stark wrote:
I tried each of the following individually in order, and then even
all together, but I still fail to pickup the jboss-marshalling-river dependency.
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-jms-client</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-jms</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-core-client</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-core</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
----- Original Message -----
From: "Jason Greene" <jgreene(a)redhat.com>
To: "Scott Stark" <sstark(a)redhat.com>
Cc: "jboss-as7-dev(a)lists.jboss.org Development"
<jboss-as7-dev(a)lists.jboss.org>
Sent: Thursday, March 22, 2012 5:33:05 PM
Subject: Re: [jboss-as7-dev] Why should a remote jndi client have to depend
on jboss-marshalling-river?
You should just need org.jboss: jboss-remote-naming and hornetq
Sent from my iPhone
On Mar 22, 2012, at 7:21 PM, Scott Stark <sstark(a)redhat.com> wrote:
> I'm working on getting the helloworld-jms quickstart from
https://github.com/jbossas/quickstart.git running against an as7.1.0.Final instance, and
one change I had to make was to add the jboss-marshalling-river dependency shown below.
Without this I'm getting a "Could not find a marshaller factory for river
marshalling strategy" failure. This seems like quite a low level dependency for a
user to have to figure out. Shouldn't this be coming from either the jboss-as-naming
or the jboss-as-messaging, which ever one is needing this for the protocol?
>
> <dependencies>
> <dependency>
> <groupId>org.jboss.as</groupId>
> <artifactId>jboss-as-naming</artifactId>
> <version>7.1.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.jms</groupId>
> <artifactId>jboss-jms-api_1.1_spec</artifactId>
> <version>1.0.0.Final</version>
> <!--scope>provided</scope-->
> </dependency>
> <dependency>
> <groupId>org.jboss.as</groupId>
> <artifactId>jboss-as-messaging</artifactId>
> <version>7.1.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.marshalling</groupId>
> <artifactId>jboss-marshalling-river</artifactId>
> <version>1.3.9.GA</version>
> </dependency>
> </dependencies>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
7:51 p.m.
New subject: Why should a remote jndi client have to depend on jboss-marshalling-river?
jboss-sasl is also listed as provided, however I think that is should
also just have compile scope, as it is not really possible to talk to a
secured server without it.
Stuart
On Thu, 2012-03-22 at 20:47 -0400, Scott Stark wrote:
I tried each of the following individually in order, and then even
all together, but I still fail to pickup the jboss-marshalling-river dependency.
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-jms-client</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-jms</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-core-client</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
<dependency>
<groupId>org.hornetq</groupId>
<artifactId>hornetq-core</artifactId>
<version>${version.org.hornetq}</version>
</dependency>
----- Original Message -----
From: "Jason Greene" <jgreene(a)redhat.com>
To: "Scott Stark" <sstark(a)redhat.com>
Cc: "jboss-as7-dev(a)lists.jboss.org Development"
<jboss-as7-dev(a)lists.jboss.org>
Sent: Thursday, March 22, 2012 5:33:05 PM
Subject: Re: [jboss-as7-dev] Why should a remote jndi client have to depend
on jboss-marshalling-river?
You should just need org.jboss: jboss-remote-naming and hornetq
Sent from my iPhone
On Mar 22, 2012, at 7:21 PM, Scott Stark <sstark(a)redhat.com> wrote:
> I'm working on getting the helloworld-jms quickstart from
https://github.com/jbossas/quickstart.git running against an as7.1.0.Final instance, and
one change I had to make was to add the jboss-marshalling-river dependency shown below.
Without this I'm getting a "Could not find a marshaller factory for river
marshalling strategy" failure. This seems like quite a low level dependency for a
user to have to figure out. Shouldn't this be coming from either the jboss-as-naming
or the jboss-as-messaging, which ever one is needing this for the protocol?
>
> <dependencies>
> <dependency>
> <groupId>org.jboss.as</groupId>
> <artifactId>jboss-as-naming</artifactId>
> <version>7.1.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.jms</groupId>
> <artifactId>jboss-jms-api_1.1_spec</artifactId>
> <version>1.0.0.Final</version>
> <!--scope>provided</scope-->
> </dependency>
> <dependency>
> <groupId>org.jboss.as</groupId>
> <artifactId>jboss-as-messaging</artifactId>
> <version>7.1.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.marshalling</groupId>
> <artifactId>jboss-marshalling-river</artifactId>
> <version>1.3.9.GA</version>
> </dependency>
> </dependencies>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
6:31 a.m.
New subject: Why should a remote jndi client have to depend on jboss-marshalling-river?
Actually that dependency is not 100% required although to avoid
confusion we probably should include it.
Without it the JVM supplied Plain and Digest implementations should
still be available and interoperable with our server side
implementations - without it the client would loose our Anonymous and
JBoss Local User implementations but in this context that is probably
not a great loss.
Regards,
Darran Lofthouse.
On 03/23/2012 12:51 AM, Stuart Douglas wrote:
jboss-sasl is also listed as provided, however I think that is
should
also just have compile scope, as it is not really possible to talk to a
secured server without it.
Stuart
On Thu, 2012-03-22 at 20:47 -0400, Scott Stark wrote:
> I tried each of the following individually in order, and then even all together, but
I still fail to pickup the jboss-marshalling-river dependency.
>
> <dependency>
> <groupId>org.hornetq</groupId>
> <artifactId>hornetq-jms-client</artifactId>
> <version>${version.org.hornetq}</version>
> </dependency>
>
> <dependency>
> <groupId>org.hornetq</groupId>
> <artifactId>hornetq-jms</artifactId>
> <version>${version.org.hornetq}</version>
> </dependency>
>
> <dependency>
> <groupId>org.hornetq</groupId>
> <artifactId>hornetq-core-client</artifactId>
> <version>${version.org.hornetq}</version>
> </dependency>
>
> <dependency>
> <groupId>org.hornetq</groupId>
> <artifactId>hornetq-core</artifactId>
> <version>${version.org.hornetq}</version>
> </dependency>
>
>
> ----- Original Message -----
> From: "Jason Greene"<jgreene(a)redhat.com>
> To: "Scott Stark"<sstark(a)redhat.com>
> Cc: "jboss-as7-dev(a)lists.jboss.org
Development"<jboss-as7-dev(a)lists.jboss.org>
> Sent: Thursday, March 22, 2012 5:33:05 PM
> Subject: Re: [jboss-as7-dev] Why should a remote jndi client have to depend
on jboss-marshalling-river?
>
> You should just need org.jboss: jboss-remote-naming and hornetq
>
> Sent from my iPhone
>
> On Mar 22, 2012, at 7:21 PM, Scott Stark<sstark(a)redhat.com> wrote:
>
>> I'm working on getting the helloworld-jms quickstart from
https://github.com/jbossas/quickstart.git running against an as7.1.0.Final instance, and
one change I had to make was to add the jboss-marshalling-river dependency shown below.
Without this I'm getting a "Could not find a marshaller factory for river
marshalling strategy" failure. This seems like quite a low level dependency for a
user to have to figure out. Shouldn't this be coming from either the jboss-as-naming
or the jboss-as-messaging, which ever one is needing this for the protocol?
>>
>> <dependencies>
>> <dependency>
>> <groupId>org.jboss.as</groupId>
>> <artifactId>jboss-as-naming</artifactId>
>> <version>7.1.0.Final</version>
>> </dependency>
>> <dependency>
>> <groupId>org.jboss.spec.javax.jms</groupId>
>> <artifactId>jboss-jms-api_1.1_spec</artifactId>
>> <version>1.0.0.Final</version>
>> <!--scope>provided</scope-->
>> </dependency>
>> <dependency>
>> <groupId>org.jboss.as</groupId>
>> <artifactId>jboss-as-messaging</artifactId>
>> <version>7.1.0.Final</version>
>> </dependency>
>> <dependency>
>> <groupId>org.jboss.marshalling</groupId>
>> <artifactId>jboss-marshalling-river</artifactId>
>> <version>1.3.9.GA</version>
>> </dependency>
>> </dependencies>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5147
days inactive
5147
days old
5 comments
4 participants
participants (4)
-
Darran Lofthouse -
Jason Greene -
Scott Stark -
Stuart Douglas