You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kandula-dev@ws.apache.org by Dasarath Weeratunge <dw...@purdue.edu> on 2009/05/18 03:39:02 UTC
Re: kandula1
Quoting Mehmet Kuzu <e1...@metu.edu.tr>:
I don't recall having tested Kandula 1 on java 1.5. The last I tried
I believe was 1.4.2. Also, make sure the you build and deploy
Kandula on the same Axis version. You can check this by looking at
the version of axis jar's downloaded by maven against your axis container.
You can set maven to build Kandula on a particular axis version by
modifying the dependencies in project.xml file.
You can also try Kandula 2 which works on Axis2, a better soap
engine than Axis 1.
-- dasarath
> Hi Dear Dasarath,
>
> I am M.S atudent at computer engineering department at Middle East
> Technical University. I am working on semantic web services and service
> composition, transaction support is very essential in my work and during my
> search I have encountered Kandula.
> I tried to use Kandula1, perform the actions that are stated in
> Kandula1 web page but I have some problems. During my search on the
> web I have seen your answers to my problems but they have not solved
> it, I thought you may give some guide, I have 2 problems
>
> I am using axis 1.4, tomcat 5.5, java 1.5 (I have also tried 1.4)
>
> 1- When listing services I get the below exception
>
> java.lang.Exception: Method 'process' does not match any of the valid
> signatures
> for message-style service methods
> at
> org.apache.axis.InternalException.<init>(InternalException.java:71)
> at
> org.apache.axis.description.JavaServiceDesc.checkMessageMethod(JavaSe
> rviceDesc.java:835)
>
> I have checked signature, it is void process(SOAPEnvelope,
> SOAPEnvelope) and it
> is valid message type signature, I did not understand the problem
>
> 2- When viewing wsdl files I get the below exception
>
> org.apache.commons.discovery.DiscoveryException: Class
> > org.apache.axis.components.uuid.FastUUIDGen does not implement
> > org.apache.axis.components.uuid.UUIDGen
> > at
> >
> org.apache.commons.discovery.tools.ClassUtils.verifyAncestory(ClassUtils.java:180)
> > at org.apache.axis.AxisProperties$1.run(AxisProperties.java:182)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at org.apache.axis.AxisProperties.newInstance(AxisProperties.java:166)
> > at org.apache.axis.AxisProperties.newInstance(AxisProperties.java:160)
> > at
> >
> org.apache.axis.components.uuid.UUIDGenFactory.getUUIDGen(UUIDGenFactory.java:52)
>
> I am sure that FastUUIDGen implements UUIDGen, what may be the problem
>
>
>
> Thanks very much,
>
> Best regards,
>
> Mehmet Kuzu
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: kandula1 CallbackRegistery
Posted by Hannes Erven <ha...@erven.at>.
Hi folks,
> Quoting Mehmet Kuzu <e1...@metu.edu.tr>:
>
>> Thanks, I will post my questions to th kandula-dev afterwards, but
>> lastly I should mention that this time out is used in WS-BA too, I
>> have examined the holiday example and I could make it run after
>> increasing time out duration
You are refering to
// FIXME _ALL_ Make default callback timeout configurable
public static final int DEFAULT_TIMEOUT_MILLIS = 20 * 1000;
in CallbackRegistry, right?
This is a default value that is only used when there is no specific
timeout value present when creating the context.
I've taken a look at the sources (it's been long since the last time...)
at it seems that there is no way to actually provide that parameter from
any client, AT or BA.
As Dasarath said, with AT clients a transaction is anyways expected to
last less that 20 seconds, but for BA transactions the time limit may be
inapproriate. The unit tests should run fine, however, since they run
faster than that.
It is absolutely safe to adjust that limit to your needs.
Best regards,
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: kandula1 CallbackRegistery
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Mehmet Kuzu <e1...@metu.edu.tr>:
> Thanks, I will post my questions to th kandula-dev afterwards, but
> lastly I should mention that this time out is used in WS-BA too, I
> have examined the holiday example and I could make it run after
> increasing time out duration
I didn't implement the BA part. You need to ask this question from
Hannes. Please post to the list with WS-BA somewhere in the subject
and he will answer.
Thanks,
-- dasarath
>
> Best regards,
>
> Quoting Dasarath Weeratunge <dw...@purdue.edu>:
>
> > Quoting Mehmet Kuzu <e1...@metu.edu.tr>:
> >
> > It is to handle failures. If the client or the coordinator becomes
> > unresponsive, how do you handle that? 20s is just a rough number.
> > Particularly,
> > WS-AT doesn't handle long lived activities like WS-BA.
> >
> > Please post to kandula-dev@ws.apache.org next time.
> >
> > Thanks,
> > -- dasarath
> >
> >
> >> Hi Dear Dasarath,
> >>
> >> If you dont mind I have one more question about Kandula1, while
> >> examining source
> >> code I have seen some code related with timeout in CallbackRegistery
> >> class, I think this is used for CoordinationContext availability time,
> >> am I right (if I am wrong what it is used for), if this is the case
> >> why did you set this time out period to 20 seconds, is there a
> >> particular reason
> >>
> >> Thanks very much,
> >>
> >> Best regards,
> >>
> >> Mehmet
> >>
> >>
> >>
> >>
> >
> >
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: kandula1 CallbackRegistery
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Mehmet Kuzu <e1...@metu.edu.tr>:
It is to handle failures. If the client or the coordinator becomes
unresponsive, how do you handle that? 20s is just a rough number. Particularly,
WS-AT doesn't handle long lived activities like WS-BA.
Please post to kandula-dev@ws.apache.org next time.
Thanks,
-- dasarath
> Hi Dear Dasarath,
>
> If you dont mind I have one more question about Kandula1, while
> examining source
> code I have seen some code related with timeout in CallbackRegistery
> class, I think this is used for CoordinationContext availability time,
> am I right (if I am wrong what it is used for), if this is the case
> why did you set this time out period to 20 seconds, is there a
> particular reason
>
> Thanks very much,
>
> Best regards,
>
> Mehmet
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org