[jboss-as7-dev] JMS subsystem, clarification needed

[Brian Stansberry]

Clebert has taken it over and is reworking things. So I'm sure your 
feedback to him is very helpful.

On 5/4/11 4:48 AM, Heiko Braun wrote:
>
> IMO, the whole representation is awkward to read.
> It should not require a user manual to understand a trivial resource representation like this.
>
> who is maintaining this piece?
>
> Ike
>
> On May 4, 2011, at 10:35 AM, Kabir Khan wrote:
>
>> I'll hazard a few guesses
>> On 4 May 2011, at 09:10, Heiko Braun wrote:
>>
>>>
>>>
>>> [domain at localhost:9999 /] /profile=default/subsystem=jms:read-resource(recursive=true)
>>> {
>>>    "outcome" =>  "success",
>>>    "result" =>  {
>>>        "connection-factory" =>  {
>>>            "InVmConnectionFactory" =>  {
>>>                "connector" =>  {"in-vm" =>  {"backup-connector-name" =>  "netty"}},
>>>                "entries" =>  ["java:/ConnectionFactory"]
>>>            },
>>>            "RemoteConnectionFactory" =>  {
>>>                "connector" =>  {"netty" =>  {"backup-connector-name" =>  "in-vm"}},
>>>                "entries" =>  ["RemoteConnectionFactory"]
>>>            }
>>>        },
>>>        "queue" =>  {"testQueue" =>  {"entries" =>  ["queue/test"]}},
>>>        "topic" =>  {"testTopic" =>  {"entries" =>  ["topic/test"]}}
>>>    },
>>>    "compensating-operation" =>  undefined
>>> }
>>>
>>>
>>>
>>> Can someone explain JMS resource to me?
>> InVmConnectionFactory uses the 'in-vm' connector, and if that is not available it uses the 'netty' connector.
>> RemoteCOnnectionFactory uses the 'netty' connector, and if that is not available it uses the 'in-vm' connector (not sure if it makes sense to have that one as a fallback now that you mention is :-) ).
>> I am not sure what is meant by 'not available' :-)
>>
>>> What are the "entries" attributes in both cases?
>> InVmConnectionFactory is put into JNDI under java:/ConnectionFactory and RemoteConnectionFactory under RemoteConnectionFactory.
>>>
>>>
>>> Assuming these are JNDI names, why are they mapped to list types?
>> Probably because HornetQ allows these to be bound into JNDI under several names. Not sure if that makes sense in AS, or if it complicates things for users
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat