davsclaus commented on PR #27612:
URL: https://github.com/apache/camel/pull/27612#issuecomment-6085098875

   Thanks @oscerd. All of these reproduced, and I checked each against the 
DataWeave CLI (`dw` 2.12) before fixing. They're fixed in cc2a6b280fdd, with a 
corpus entry for each, all verified with `dw`:
   
   - **CDATA next to text (blocking):** `textOf` now uses the text the reader 
collates in `$`. In mixed content, adjacent text and CDATA segments are one 
`__text`, as in DataWeave (`<c>t<![CDATA[u]]><d/>v</c>` gives `__text` "tu", 
`d`, `__text` "v"). Corpus XM34.
   - **Two namespaces, same local name:** `.*item` and `..*item` now give the 
elements of every prefix, in document order. `dw` gives `["1","2","3"]`. 
`.item` and `..item` give the first in document order. Corpus XM33.
   - **Empty array through `xmlObject`:** it is now an empty element (`<a/>`), 
as `dw` writes it. Corpus XM36.
   - **Nested lambdas with the same parameter name:** whether a parameter is 
kept as an XML element is now part of its binding in the scope, not a flat name 
set. So an inner lambda can't change the outer one. Converter test, plus corpus 
XM37 with XML output, where the outer `v: o` matters.
   - **Default namespace:** corpus XM35 (`xmlns="…"` with `ns`-qualified 
selectors, also in the wrong namespace).
   - **Prefixes with `-`:** DataWeave rejects `ns my-ns http://…` too (`Invalid 
input 'h', expected directive`), so failing the conversion is consistent. I 
left the pattern as it is.
   - **Nits:** `keyName` now uses `prefix:name`, the name as written in XML, so 
a quoted `"a:b"` and `a#b` count as the same element. `DescendantSelector`'s 
2-arg constructor is public.
   - **Process:** CAMEL-25481 now has fixVersion 4.23.0.
   
   camel-dataweave: 101 tests pass. camel-datasonnet: 450 tests pass, including 
365 corpus entries.
   
   _Claude Code on behalf of davsclaus_
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to