[JBossWS] - wstools is working properly?
by asarubbi
running wstools generates invalid datatypes when an array was specified in WSDL
/*
| * JBossWS WS-Tools Generated Source
| *
| * Generation Date: Fri Jul 14 12:29:50 ADT 2006
| * This generated source code represents a derivative work of the
| * input to
| * the generator that produced it. Consult the input for the copyright and
| * terms of use that apply to this source code.
| */
|
| package gov.py.set.services.rucas;
|
|
| public class ClientSystem
| {
|
| protected java.lang.Integer id;
|
| protected java.lang.String name;
|
| protected [Ljava.lang.Byte; password;
|
should be protected java.lang.Byte[] password;
in some classes, first letter of the method name is not mantained when
using an uppercase identifier:
/*
| * JBossWS WS-Tools Generated Source
| *
| * Generation Date: Fri Jul 14 12:29:50 ADT 2006
| *
| * This generated source code represents a derivative work of the input to
| * the generator that produced it. Consult the input for the copyright and
| * terms of use that apply to this source code.
| */
| package gov.py.set.services.rucas;
| public interface SessionManagement extends java.rmi.Remote
| {
|
| public gov.py.set.services.rucas.RUCASConnectResponse rUCASConnect(gov.py.set.services.rucas.AppInfo appInfo,gov.py.set.services.rucas.LoginMethod loginMethod,gov.py.set.services.rucas.CryptMethod cryptMethod) throws java.rmi.RemoteException;
and finally, jaxrpc-mapping.xml:
<service-endpoint-method-mapping>
| <java-method-name>rUCASConnect</java-method-name>
| <wsdl-operation>RUCASConnect</wsdl-operation>
| <method-param-parts-mapping>
all errors are fixable but after every regeneration, needs plumbing...
don't know if previous messages posted this or resolution status...
(newbie in jboss web services)
thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958158#3958158
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958158
20 years
[Messaging, JMS & JBossMQ] - messages getting cached and not getting distributed among re
by nabeelhamad
Hi,
We are using JBoss 3.2.1 version. We have three nodes (say node1, node2 and node3) and on each node we have 2 MDBs listening to a queue on a single node (say node1). We have limited the MDBs to 2 each to achieve load balancing. The idea was that when there are more than 2 messages coming at the same time, they be processed on different nodes.
The problem we are facing is that when we place 8 messages at the same time, the first 2 gets picked up by the MDBs on a particular node (say node2 - this changes every time we restart the servers) and starts processing immediately. The next four gets cached, and the next two goes to another node (say node1) and gets processed over there. The four that gets cached gets processed only on node2 and not on any other node.
We would require your help to understand this behaviour of messages getting cached and to fix this issue so that the messages are processed first come first basis. Now what is happening is, whenever the number of messages are lesser than or equal to six they always get processed on the same node, two at a time and doesn't get distributed among the nodes.
Thanks in advance.
regards,
nabeel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958149#3958149
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958149
20 years