[JBoss Seam] - How to build action parameter expression for s:button with v
by lpmon
I need to build a button to pass an argument to an action method. I can hard code the parameter and all is fine. I just cannot figure how to dynamically build it with tags.
Key point: I need to use el to specify the Seam "named" method and I also need to use el to specify its argument. This creates a nesting scenario that I cannot figure out. The track var is the object
<ice:dataTable id="trackList"
var="track"
value="#{trackList.resultList}"
columnClasses="allCols"
rendered="#{not empty trackList.resultList}">
...
...
<ice:column>
<f:facet name="header">Click to Play</f:facet>
<s:button value="Play" id="play" action="#{connectedUser.playMediaId(track.id)}"/>
</ice:column>
Track.id is passed as a null string to the method. I created a different method that takes a track object and tried passing track. I get a null object passed to the method.
I am adapting the standard SeamGen pages for my app. I can get it to work if I use the select in the seamgen'd trackList page which passes the selected track to the track page. Then on that page I use trackHome.instance as the parameter to the method that accepts a track object. This works.
One key difference between the two pages is in the tracklist page (non-working one) the data is provided by the var from ice:dataTable
I want to get this to work in the trackList page inside the dataTable
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072738#4072738
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072738
18Â years, 10Â months
[Remoting] - Re: bisocket usage as a tunneling connection
by ron.sigalï¼ jboss.com
The answer is "yes".
anonymous wrote : so i want the client machine to connect to my server and the connection to be kept open (tunneling) with keep alive pulses.
With the bisocket transport you don't need to worry about a keep-alive problem. You can configure the socket timeout value to be zero, so the sockets will stay open indefinitely. In fact, you don't even need to rely on setting the timeout value to zero. The client will create new sockets as needed.
anonymous wrote : from now on (once connected) i want the server to be able to call the client in a request - response manner, as if the client is a 'server'.
Remoting has a callback mechanism which allows the server to send invocations to the client in an asynchronous manner. See Section "5.6. Callbacks" in the Remoting Guide (http://labs.jboss.com/jbossremoting/docs/guide/index.html).
anonymous wrote : i also want the connection/connections to support a pool of connections, so i can have multiple concurrent requests.
The socket transport, from which bisocket is derived, maintains a connection pool on the client side and a worker thread pool on the server side. The same is true, in reverse, with respect to callbacks going from the server to the client.
anonymous wrote : i also want the connection to use https or ssl on tcp/ip.
There is an sslbisocket version of bisocket.
anonymous wrote : is bisocket the tool for me?
Yes, I believe it could be.
anonymous wrote : if it is - how?
Ah, well, I'd say take a look at the Remoting Guide and the sample code in the distribution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072732#4072732
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072732
18Â years, 10Â months