Hi,
About the namespaces:
2005/10 does not exist
even though the specs have been updated
last month, it seems that the latest schemas are at 2004/10
these at 2003/09 exist but are not accessible – i.e. “You are not authorized to view this page”
any suggestion?
>Also using http://schemas.xmlsoap.org/ws/2003/09/wsat
(/coor) refering
>to no more valid specification make me worried. Valid schema can be found
>here http://schemas.xmlsoap.org/ws/2004/10/wsat
(/coor).
The newest specs were out on last month, making the namespaces .../2005/10/..
We kept the earlier namespace cause Kandula1 supports those specs...We are planing
to support the latest set of specs + async in Kandula2, which is under
development.
Ivan
Djordjevic, PhD
Research Professional, Security Research
Centre
BT Group Chief Technology Office
___________________________
pp21
Rigel House
Adastral Park
Martlesham Heath
Ipswich
Suffolk IP5 3RE
United Kingdom
Office:
Mobile:
07786 394334
Fax :
01473 649546
Email:
[EMAIL PROTECTED]
British
Telecommunications plc
Registered office: 81 Newgate Street London
EC1A 7AJ
Registered in England
no. 1800000
This
electronic message contains information from British Telecommunications plc
which may be privileged or confidential. The information is intended to be for
the use of the individual(s) or entity named above. If you are not the intended
recipient be aware that any disclosure, copying, distribution or use of the
contents of this information is prohibited. If you have received this
electronic message in error, please notify us by telephone or email (to the
numbers or address above) immediately.
Activity
and use of the British Telecommunications plc email system is monitored to
secure its effective operation and for other lawful business purposes.
Communications using this system will also be monitored and may be recorded to
secure effective operation and for other lawful business purposes.
-----Original
Message-----
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: 07 September 2005 07:46
To: Burian,M,Michal,CXR7A
C; [email protected]
Subject: Re: Kandula - deployment
correcting some typos....
>Also using http://schemas.xmlsoap.org/ws/2003/09/wsat
(/coor) refering
>to no more valid specification make me worried. Valid schema can be found
>here http://schemas.xmlsoap.org/ws/2004/10/wsat
(/coor).
The newest specs were out on last month, making the namespaces .../2005/10/..
We kept the earlier namespace cause Kandula1 supports those specs...We are
planing to support the latest set of specs + async in Kandula2, which is
under development.
On 9/7/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
Hi,
I'm also bit confused seen this.... :-(
Have you tried replacing all the kandula related jars like JOTM,
J2EE.... in tomcat.
>Also using http://schemas.xmlsoap.org/ws/2003/09/wsat
(/coor) refering
to no more valid specification make me worried. Valid schema can be
found >here http://schemas.xmlsoap.org/ws/2004/10/wsat
(/coor).
The newest specs were out on last month, making the namespaces
.../2005/10/..
We kept the earlier namespace cause Kandula1 supports tohse specs...
We are supporting the latest set of specs in Kandula2, which is under
development.
Thanks,
~Thilina
Note : You will be able to get much more fruitfull answers if you submit
ur porbs to the mailing list. :-)
[EMAIL PROTECTED] wrote:
> Hi,
>
> I have tried to reinstall Kandula (now available in Apache SVN). While
> deploying handlers I'm getting following exception:
>
> Processing file server-config.wsdd
>
> Exception in thread "main"
java.lang.UnsupportedClassVersionError:
> org/apache/ws
>
> /transaction/participant/standalone/handler/TransactionHandler
> (Unsupported major.minor version 49.0)
>
> at java.lang.ClassLoader.defineClass0(Native Method)
>
> at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
>
> at java.security.SecureClassLoader.defineClass
(SecureClassLoader.java:123)
>
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
>
> at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
>
> at java.net.URLClassLoader$1.run (URLClassLoader.java:194)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
>
> at java.lang.ClassLoader.loadClass (ClassLoader.java:289)
>
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
>
> at java.lang.ClassLoader.loadClassInternal (ClassLoader.java:302)
>
> at java.lang.Class.forName0(Native Method)
>
> at java.lang.Class.forName(Class.java:219)
>
> at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:176)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
>
> at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java :100)
>
> at
>
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableItem.java:353)
>
> at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java
:295)
>
> at
>
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
>
> at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java
:260)
>
> at
>
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
>
> at
>
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java
:274)
>
> at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
>
> at
>
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.java
:473)
>
> at
> org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269)
>
> at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
>
> at org.apache.axis.client.AxisClient.invoke (AxisClient.java:126)
>
> at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
>
> at org.apache.axis.client.Call.invoke(Call.java:2748)
>
> at org.apache.axis.client.Call.invoke (Call.java:1784)
>
> at org.apache.axis.client.AdminClient.process(AdminClient.java:439)
>
> at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
>
> at org.apache.axis.client.AdminClient.process (AdminClient.java:410)
>
> at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
>
> at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
>
> I am little bit confused by UnsupportedClassVersionError because my
> environment hasn't changed and I deployed Kandula successfully before.
>
> JAVA_HOME = c:\j2sdk1.4.2_08
>
> Tomcat 5.0.28
>
> Axis 1.2.1
>
> I tried to build Kandula using provided build file ( axis1.2-RC2.jar
> etc. dependency) as well as using newer libraries.
>
> Also using http://schemas.xmlsoap.org/ws/2003/09/wsat
(/coor) refering
> to no more valid specification make me worried. Valid schema can be
> found here http://schemas.xmlsoap.org/ws/2004/10/wsat
(/coor).
>
> Regards,
>
> Michal Burian
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
"May the SourcE be with u"
http://www.bloglines.com/blog/thilina http://webservices.apache.org/~thilina/
