dear all,
I end up using seam remoting method. The following is an example of what i did.
Cheers.
java -cp . Reverse http://localhost:8080/seam-helloworld/seam/remoting/execute
call component=\helloAction\ method=\sayHello\ id=\0\hjhj
Reverse class:
==
import java.io.*;
import
some text was cut off in the reply. If you need do combine them without any
carriage return. You can also see this similar trace when you run the remoting
seam example.
java -cp . Reverse http://localhost:8080/seam-helloworld/seam/remoting/execute
call component=\helloAction\
i guess the text is still cutoff, if anybody need them, please capture the
trace from running remoting example. Cheers.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3971587#3971587
Reply to the post :
sorry for the multiple posts, the input arg is as follows. please add the \
escape character before the character inside the quotes. Cheers.
java -cp . Reverse http://localhost:8080/seam-helloworld/seam/remoting/execute
hjhj
View the original post :
What I figured. Thanks. Any plans to publish a protocol spec?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3970660#3970660
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970660
CptnKirk wrote : What I figured. Thanks. Any plans to publish a protocol
spec?
I was actually thinking just the other day that it would be a good idea to
document this stuff, so yeah it's on my list of things to do now :)
View the original post :
Thanks Raja for the advice. I'm building a web app using seam + portal +
facelets, so i wanted the C app to interface with the java beans written in
seam.
Sorry, i'm a newbie so some of the terms may be incorrectly used.
Cheers.
View the original post :
Remoting was built for exactly this scenario, and even though we only provide a
Javascript implementation of the remoting client, there is nothing stopping
anyone from building a C (or whatever) client that integrates with the remoting
servlet. It uses a simple XML-based structure for its
Not to knock the work done by the remoting team, but is there a reason a custom
protocol was chosen vs a Seam RemotingEndpoint that would handle remoting via
some version of SOAP?
I would have a thought the benefits of a standard transport protocol would
outweigh the down side. Since
CptnKirk wrote : Not to knock the work done by the remoting team, but is
there a reason a custom protocol was chosen vs a Seam RemotingEndpoint that
would handle remoting via some version of SOAP?
|
| I would have a thought the benefits of a standard transport protocol would
outweigh the
1. Web Services maybe a good way to do this, you dont have to use Seam for
that, but just generally have an endpoint that can receive your WS calls and
act on it. Why do you have to use Seam for this?
2. Use JMX. If you have an JMX enabled bean, you could use the twiddle script
(look up in
11 matches
Mail list logo
