[JBossWS] - Re: Not getting instance of Service object from a WSDL file.
by ajayks
Thanks Peter for the taking time to reply.
1.What is strange in my JBOSS 4.2..2 installation is that I have not finding following jars in my $JBOSS_HOME/client/ path :-
jbossws-native-jaxws.jar
jbossws-native-core.jar
client/jbossws-native-jaxws-ext.jar
client/jbossws-native-jaxrpc.jar
jbossws-native-saaj.jar
In fact these jars are not available in any path of my JBOSS installation.
Is the normal JBOSS 4.2.2 installation does not include all these jars .
do I need to insatll JBOSS JAX-WS integartion layer in order to make
JBOSS JAXWS compliant.
2.I made the client stub with wsconsume and I checked the all the names used in the both stub and "stepts to call to make web service using WSDL location".
The all the names used both in the stub and in the "stepts to call to make web service using WSDL location" are same.
In Fact, I am not able to call deployed web service either with stub created by wsconsume or by using WSDL location primitive.
Could please let me know what could be the reason of my problem and what is its soution.
with best rehards,
Ajay Kumar,
ST Microelectronics Ltd.,
Noida, India.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179744#4179744
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179744
17 years, 6 months
[Clustering/JBoss] - Custom implementation of FirstAvailable Load Balancing Polic
by putifer
Hi,
I'm trying to create a simple Jboss cluster with 2 nodes running JBoss 3.2.4 with the farming service activated, but I have a lot of legacy restrictions.
The load balancing policy I need to use is the FirstAvailable, but I need some enhancements.
The FirstAvilable documentation says:
anonymous wrote : One of the available target nodes is elected as the main target and is used for every call: this elected member is randomly chosen from the list of members in the cluster. When the list of target nodes changes (because a node starts or dies), the policy will re-elect a target node unless the currently elected node is still available. Each client-side interceptor or load balancer elects its own target node independently of the other proxies.
This behaviour is perfect for my cluster except for one thing. I need some of this enhancements:
Option 1) When the list of target nodes changes, the policy re-elect ALWAYS a target node
Option 2)The policy re-elect a target node every X timeout
Does anyboy know how could I do this?
I tried storing a session time in my custom policy re-implementing the writeExternal and readExternal methods from LoadBalancePolicyEx unsuccessfully.
Best Regards,
Daniel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179732#4179732
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179732
17 years, 6 months