"mark.little(a)jboss.com" wrote : We're talking about EPRs in terms of addresses, not interaction sequences. So the EPR referenced in the link is out-of-date. It'll be more like:
|
| public class EPR
| {
| public void setAddr (URI uri);
| public URI getAddr () throws URISyntaxException;
| public MetaData setters/getters
| }
Grand. That thread I linked there actually talks about both i.e. it breaks what was the old EPR structure into 2 structures (based on the WS-Addressing spec):
1) A new EPR similar to what you outline above and
2) An Interaction/Invocation structure. Guess we need to discuss this on a seperate thread.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970984#3970984
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970984
Hi,
I've problem connecting to jboss version 4.0.3. I've replaced my client libraries to the the ones of 4.3.0 but still I'm having some problems connect to it (with jboss 4.0.2 I've no problem).
the exception I get is :
javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.invocation.InvokerInterceptor; unable to create instance]
The list of libraries I'm using is :
jboss-client.jar
jboss-common-client.jar
jboss-j2ee.jar
jboss-remoting.jar
jbosssx-client.jar
jboss-transaction-client.jar
jmx-client.jar
jmx-invoker-adaptor-client.jar
jnp-client.jar
Is there a new jar that was added to this version that I might need t o use ? Do you have any other idea for this problem ?
Thanks,
Lital
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970948#3970948
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970948
Well, if that is true you will have the some strange effects.
E.g.
Connection conn1 sends message m1
conn1 creates consumer with no local = true.
conn1 sends message m2
consumer closes without receiving anything
conn1 sends message m3
conn1 creates consumer with no local = false
consumer receives m1
consumer receivers m3
(no m2!!)
My opinion is that no local should only apply to the *consumer* of the subscription (the subscriber), not the subscription itself, which is the way it currently is and has been for some time, and passes TCK.
I just to wanted to clarify since the spec is a bit fuzzy about this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970947#3970947
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970947