Fils de type TEXT au lieu d'ELEMENT
Bonjour,
Voici mon problème une API que j utilise navigue de noeud en noeud pour creer des objets en recuperant les infos. Or une fois arrivée au noeud Sender elle recupère le premier fils avec un getFirstChild(). Le noeud obtenu est de type TEXT_NODE ! Mon problème est là ca cela devrait être une ELEMENT puisque le XML (SOAP) d'entrée est le suivant :
Code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
| POST /vasp/servlet/messagerouter HTTP/1.0
Content-Type: multipart/related; type="text/xml"; start="<9492CA26D0CCEC78BF572496FED42869>"; boundary="----=_Part_29_4523229.1152001559483"
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.1beta
Host: 192.168.200.9:8081
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 2402
Connection: close
Authorization: Basic YmFzaWN0ZXN0OmJhc2ljdGVzdA==
------=_Part_29_4523229.1152001559483
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-Id: <9492CA26D0CCEC78BF572496FED42869>
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<ns1:TransactionID soapenv:actor="" soapenv:mustUnderstand="1" xsi:type="xsd:string" xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">mmsc1/192.168.200.208:1ff7a1e:10c373028e8:-4fe7</ns1:TransactionID>
</soapenv:Header>
<soapenv:Body>
<DeliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
<MM7Version>5.3.0</MM7Version>
<LinkedID>RKokk8CoyNAAAAr8AAAADgAAAAEAAAAA</LinkedID>
<Sender>
<Number displayOnly="false">20231</Number>
</Sender>
<Recipients>
<To>
<Number displayOnly="false">20805</Number>
</To>
</Recipients>
<TimeStamp>2006-07-04T08:19:31.000Z</TimeStamp>
<Priority>Normal</Priority>
<Subject>Enter the subject here</Subject>
<Content allowAdaptations="false" href="cid:3ECBF624017175D3CF18654AB82DB979"/>
</DeliverReq>
</soapenv:Body>
</soapenv:Envelope>
------=_Part_29_4523229.1152001559483
Content-Type: multipart/mixed; boundary="Nokia-mm-messageHandler-BoUnDaRy-=_-1875013426"
Content-Transfer-Encoding: binary
Content-Id: <3ECBF624017175D3CF18654AB82DB979>
--Nokia-mm-messageHandler-BoUnDaRy-=_-1875013426
Content-Type: text/plain; Charset=UTF-8
Content-ID: <1-bonjour.txt>
Content-Location: 1-bonjour.txt
Content-Transfer-Encoding: BASE64
Ym9uam91ci==
--Nokia-mm-messageHandler-BoUnDaRy-=_-1875013426
Content-Type: application/smil
Content-ID: <MMS.smil>
Content-Location: MMS.smil
Content-Transfer-Encoding: BASE64
PHNtaWw+PGhlYWQ+PGxheW91dD48cm9vdC1sYXlvdXQgd2lkdGg9IjE3NiIgaGVpZ2h0PSIyMDgi
Lz48cmVnaW9uIGlkPSJSZWdpb25JbWFnZSIgd2lkdGg9IjE3NiIgaGVpZ2h0PSIxNzgiIHRvcD0i
MCIgbGVmdD0iMCIgLz48cmVnaW9uIGlkPSJSZWdpb25UZXh0IiB3aWR0aD0iMTc2IiBoZWlnaHQ9
IjMwIiB0b3A9IjE3OCIgbGVmdD0iMCIgLz48L2xheW91dD48L2hlYWQ+PGJvZHk+PHBhciBkdXI9
IjJzIj48dGV4dCBzcmM9IjEtYm9uam91ci50eHQiIHJlZ2lvbj0iUmVnaW9uVGV4dCIgLz48L3Bh
cj48L2JvZHk+PC9zbWlsPg==
--Nokia-mm-messageHandler-BoUnDaRy-=_-1875013426--
------=_Part_29_4523229.1152001559483-- |
L'API utilise DOM. Je me demande d'où vient se comportement ... Avez vous une idée ? Merci
Julie.
