Hi slevy,
I've already solved this a while ago, but in any case - you're right.
the configuration of RMI over HTTP can be done in the client side by setting the following properties:
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.factory.initial=org.jboss.naming.HttpNamingContextFactory
java.naming.provider.url=http://localhost:8080/invoker/JNDIFactory
there's no need to configure any ports in the /http-invoker.sar/META-INF/jboss-service.xml (unlike some tutorials state).
hope this helps others that have the same problem.
Elad
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037350#4037350
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037350
dj - thanks for your help and writing the code you posted very early in this discussion. I finally got it to work.
The trick is that the component that is the target for the binding element on the <tr:inputText binding="#{dialogManager.input}".../> can not be a Conversation Scoped Component. Once I took off the @Stateful annotation and just had @Name, everything started to fall into place.
And a big thanks to cbauer. I finally figured this out by reading a comment he put on the example wiki UIBinding component about bindings not working with @In or conversation scoped components.
Thanks,
Chris....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037346#4037346
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037346
