[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-19 Thread appendix
Thank you Shane, you've been really helpful! The getter is not an immediate issue for me. I just wanted to point that out, that some other guy later on won't need to worry, why the provider cannot be set in components.xml :) Again, I'd like to thank you for your great help! Kurt View the

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-18 Thread appendix
Hi, that finally did the trick! Thank you again for your help. By the way, I'm using JBossMessaging instead of JBossMQ and therefore needed to set the connection provider in the subscriptionRegistry. Is there a reason why the property connectionProvider in

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-18 Thread sbryzak2
appendix wrote : | Is there a reason why the property connectionProvider in org.jboss.seam.remoting.messaging.SubscriptionRegistry lacks a getter method and hence cannot be set by a parameter in seam.properties, components.xml or web.xml? I'll add the getter method for you today. View

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-17 Thread appendix
Thanks Shane, overriding the subscriptionCallback definitely did the trick. I never wanted to use the setTimeout() version in a production environment. So finally I got the token in an input field and this is passed along the request until the page is rerenderd. I followed your suggestion,

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-17 Thread sbryzak2
Hmm, I'm not sure why you'd be getting that specific Javascript error in relation to messaging. The only place I can see it possibly happening is in the Seam.Remoting.hideLoadingMessage() method - just to be safe I've updated this method in CVS to check that Seam.Remoting.loadingMsgDiv is not

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-16 Thread appendix
Hi, thanks for helping me on this topic! But I'm not sure, if your suggestion would realy help me out, because the channelMessageCallback() method is not always called _before_ the page is refreshed. Actually in my scenario it is never called before the first refresh. Imagine this timeline: 1)

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-16 Thread sbryzak2
Seam.Remoting.subscribe() sends an asynchronous request to the server, which means you're not guaranteed to have a token in the subscription registry by the time your page gets to the script at the bottom of the page. I suggested putting the code to set the token inside your callback method,

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-13 Thread appendix
Hi, thanks for your reply! I've tried to follow your hint, but somehow it seems that I cannot access the token after subscription to be able to write it to an input field. The xhtml page is defined as following: | script type=text/javascript | //![CDATA[ | Seam.Remoting.setDebug(true);

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-13 Thread sbryzak2
The token is passed back in the response to the subscribe request, and added to the subscription registry in Seam.Remoting.subscriptionCallback(). You should put the code for setting the token in your channelMessageCallback() method (only setting it if it hasn't already been set). View the

[jboss-user] [JBoss Seam] - Re: Seam Remoting und JMS Topic subscription questions.

2006-10-11 Thread sbryzak2
The code for dealing with stale subscriptions is a little messy at the moment. However to deal with your immediate issue, if you can somehow pass your subscription token to the next page (with a hidden field or something) then you can manually insert your subscription into the registry like