I should be a little bit careful. I work for Tippingpoint and we make network security products. We're using remoting for communication between nodes in a distributed policy system, the remote nodes control firewalls and things like that and then the central node (now becoming a cluster) makes the policy decisions.
There was a bit of a learning curve, especially since I like to read docs after exhausting other resources, but it's been rock solid once we figured it all out.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202212#4202212
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202212
I have a requirement to migrate our application to a better configuration server. For this, I need to copy JBOSS from the present server to the new server. So, should the log folder under $JBOSS_HOME/server/default also be copied or will it get created on the new system as the system is used. So, my query here is whether the log folder needs to be copied or not?
I hope, my question is clear.
Please, help in solving the doubt.
regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202205#4202205
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202205
I'm attempting to port the Web Beans EJB integration to the EJB3.1 embedded container. I've identified two potential issues:
1) Do the org.jboss.ejb3.EjbReferenceResolver and the PersistenceUnitDependencyResolver beans exist in embedded EJB3.1?
2) How can I get hold of the deployment unit and MC kernel in this embedded environment. In AS, Ales wrote some code to push these into the servlet context for later use, but that isn't relevant here I think.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202199#4202199
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202199
Hi there!
Iôve got a bit of a problem with Webservice-Responses. A Client sends in MTOM-Format and needs an answer in MTOM-Format. Iôve tried to change the BindingType to SOAP12HTTP_MTOM_BINDING. This changes the Webservice-Response to Soap 1.2, so this kind of works. But it still isnôt in MTOM-Format. I think this is the result of the absence of an Base64-coded element in the webservice-response.
Is there a way to force MTOM on a response?
Thanks and best regards,
M. Fueser
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202192#4202192
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202192