Kuddi: Enhydra.org old server stopped

Hi,

This mail is to inform you that the old Enhydra.org server is going to
be removed as previously announced (see
http://www.objectweb.org/wws/arc/enhydra/2004-05/msg00000.html). As a
consequence, this mailing list will be closed. The server will be
now used only as ObjectWeb download mirror site.

The following Web sites have been migrated into an ObjectWeb Web
server for archive purpose - CVS, mailing lists and search engine will
be no more available.

- aleutia.enhydra.org
- brock.enhydra.org
- khttp.enhydra.org
- ksoap.enhydra.org
- ksync.enhydra.org
- kuddi.enhydra.org
- kxml.enhydra.org
- kxmlrpc.enhydra.org
- locumi.enhydra.org
- mail4me.enhydra.org
- mapper.enhydra.org
- me.enhydra.org

I recall you also that most other Enhydra projects (Enhydra server,
Enhydra XMLC, BarracudaMVC, ...) are now hosted on
ObjectWeb (see forge.objectweb.org).

On behalf of the ObjectWeb executive committee, I would like to thank

RE: kSync v2

KSync and CVS

kSync

(no subject)

Synchronysing contacts and appointments in mobile phone

Hi all,

I am working on a project where we need to synch the "address book" (phone
numbers) and appointments between a mobile phone and a remote server-based
database. We know we can do it for phones featuring SyncML, in which case we
only need to sort out the server side of the application. However, we also
want to support phones without embedded SyncML functionality. We came across
to your kSync project and thought this can be an option to provide SyncML
capabilities to any Java phone. Then, our question is:
 - Can we synchronise the phone's contact and appointment details using
kSync? In other words, can kSync access the phone's common address book and
calendar?
 - If yes, can we even access the contact data stored in the SIM card, or
just the data stored in the phone's memory?

Look forward to your answers.
Thanks in advance for your help, and congratulations for your work.

-
Luis Alcántara García
RIGEL (Grupo Calidad y Tecnología)
lalcantara <at> rigelmsp.com
Tel.: +34 91 233 97 54
-

client can't work

dear all,

i think this is my first msg to this list.
i've a problem... i've installed enhydra3.1 and run the ksync on port 9009
and then i try to sync (ksync client) using the j2me toolkit 2.0 beta 
2... and then the 'phone' hangs
in the console... they showed until this sentence:
......bla bla ...
            <Item>
                <Target>
                    <LocURI>
                        Test1.xml
                    </LocURI>
                </Target>
            </Item>
        </Alert>
        <Final/>
    </SyncBody>
</SyncML>
004.656    Connect tohttp://localhost:9009/ksync ...

is this the correct way? or is the ksync can ONLY work on j2metoolkit1.02 ??
TQ

needing help

Ksync: Is it popssible to get a copy of kSync 2.0???

Hi ,

Is it popssible to get a copy of kSync 2.0?

Best regards

Paul Sorati

Ksync: Two way sync problem

Hi all,

I found in this list archives a message that corresponds exactly to my
problem,
But unfortunately nobody has reply.

I past the question :

"The following use case seems to NOT work properly.  I started the
server and the client.  I made a modification to an attribute and synced
with the server.  This works ok.  When I make a modification to the data
on the server (modifying the test1.xml file) and then tell the client to
sync again I don't get the updates made on the server sent to the
client.  I thought this might have been because the test1.xml file was
not re-read from the filesystem, so I tried restarting the server and
then it works, but it doesn't send the changes, it only ever does a
"508" (Slow sync necessary) response to the client which means it sends
the entire database contents (in this case the contents of the test1.xml
file) from the server to the client.  This doesn't seem like the correct
operation because this replaces any modifications currently in the
client with what the server sent.  Am I doing something wrong or am I
misunderstanding something?"

Any idea ?
Thank you for your time.

Stéphane

Ksync: Current status of KSync? It seems pretty inactive

Hi,

Is anyone out there?

The last message I see in the archives is June 3, 2002.  I've read about a
version 2.0 being available, but surprised that I can't find it on the site.

I'm in the evaluation stage and am looking at this and Sync4J.  KSync
appears to have released one, but the inactivity leads me to believe that
KSync doesn't work well.  Any comments would be helpful.

Brent Hale
Eventronix Inc

Ksync: Sync Problems

Hi,

 We are trying to sync the ksync client with server but are having the
following problem.
"org.xml.sax.SAXParseException: The markup in the document preceding the
root element must be well-formed." which is given below.

We can not see anything wrong with the document - has anyone come across
this problem in the past?

Any help  would be very much appreciated.

Thanks for your time

Best regards

Paul Sorati

000.010    CommServlet.init(CommServlet.log)
000.010    CommServlet.root=C:/usr/local/enhydra3.1/ksync/xml/
026.187    doService:POST
026.187    getAuthType:null
026.187    getCharacterEncoding:null
026.187    getContentType:application/vnd.syncml-xml
026.187    getProtocol:HTTP/1.1
026.187    getScheme:http
026.187    Header:content-type:application/vnd.syncml-xml
026.187    Header:Transfer-Encoding:chunked
026.187    Header:Host:203.213.47.250:80
026.187    SYNC: <-:248
<SyncML>
	<SyncHdr>
		<VerDTD>
			1.0
		</VerDTD>
		<VerProto>
			SyncML/1.0
		</VerProto>
		<SessionID>
			2
		</SessionID>
		<MsgID>
			1
		</MsgID>
		<Target>
			<LocURI>
				http:/localhost/ksync
			</LocURI>
		</Target>
		<Source>
			<LocURI>
				ksync_client
			</LocURI>
		</Source>
		<NoResp/>
	</SyncHdr>
	<SyncBody>
		<Alert>
			<CmdID>
				1
			</CmdID>
			<Data>
				205
			</Data>
			<Item>
				<Target>
					<LocURI>
						Test1.xml
					</LocURI>
				</Target>
			</Item>
		</Alert>
		<Final/>
	</SyncBody>
</SyncML>

026.658    7
org.xml.sax.SAXParseException: The markup in the document preceding the root
element must be well-formed.
	at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
	at
org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocume
ntScanner.java:625)
	at
org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
LDocumentScanner.java:804)
	at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:380)
	at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
	at com.reaxion.tequila.server.util.XmlUtils.readElementFromStream(Unknown
Source)
	at com.reaxion.tequila.syncml.xml.node.XmlIO.readXmlNodeFromStream(Unknown
Source)
	at com.reaxion.tequila.syncml.xml.node.XmlIO.readXmlNodeFromBytes(Unknown
Source)
	at com.reaxion.tequila.syncml.SyncMLReader.readBytes(Unknown Source)
	at
com.reaxion.tequila.server.syncml.comm.CommSyncmlServer.performRequest(Unkno
wn Source)
	at com.reaxion.tequila.server.syncml.comm.CommServlet.service(Unknown
Source)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
	at
org.apache.tomcat.core.ServiceInvocationHandler.method(ServletWrapper.java:6
41)
	at
org.apache.tomcat.core.ServletWrapper.handleInvocation(ServletWrapper.java:5
49)
	at
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:392)
	at org.apache.tomcat.core.Context.handleRequest(Context.java:732)
	at
org.enhydra.servlet.servletManager.ServletManager.service(ServletManager.jav
a:1096)
	at
org.enhydra.servlet.connectionMethods.http.HttpHandler.doARequest(HttpHandle
r.java:241)
	at
org.enhydra.servlet.connectionMethods.http.HttpHandler.processRequests(HttpH
andler.java:258)
	at
org.enhydra.servlet.connectionMethods.http.HttpHandler.run(HttpHandler.java:
96)
	at java.lang.Thread.run(Thread.java:536)
026.658    6
com.reaxion.tequila.syncml.util.CommException: The markup in the document
preceding the root element must be well-formed.
	at
com.reaxion.tequila.server.syncml.comm.CommSyncmlServer.performRequest(Unkno
wn Source)
	at com.reaxion.tequila.server.syncml.comm.CommServlet.service(Unknown
Source)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
	at
org.apache.tomcat.core.ServiceInvocationHandler.method(ServletWrapper.java:6
41)
	at
org.apache.tomcat.core.ServletWrapper.handleInvocation(ServletWrapper.java:5
49)
	at
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:392)
	at org.apache.tomcat.core.Context.handleRequest(Context.java:732)
	at
org.enhydra.servlet.servletManager.ServletManager.service(ServletManager.jav
a:1096)
	at
org.enhydra.servlet.connectionMethods.http.HttpHandler.doARequest(HttpHandle
r.java:241)
	at
org.enhydra.servlet.connectionMethods.http.HttpHandler.processRequests(HttpH
andler.java:258)
	at
org.enhydra.servlet.connectionMethods.http.HttpHandler.run(HttpHandler.java:
96)
	at java.lang.Thread.run(Thread.java:536)