[jboss-as7-dev] Why should a remote jndi client have to depend on jboss-marshalling-river?

[Scott Stark]

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>