# xml Published articles for xml. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Failed XML-Based DSL Design Using a Large Regular Expression DevFeed: [A Failed XML-Based DSL Design Using a Large Regular Expression]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-07T06:30:00Z Content type: opinion Language: en Sources: [The Daily WTF]() Topics: [XML](), [Structured-data](), [bug](), [Code]() Tags: [best-of](), [bug](), [code](), [documentation](), [domain-specific-languages](), [dsls](), [regex](), [xml]() ### AI overview The article revisits a failed attempt to build a domain-specific language with XML schemas and a 1,310-character regular expression. It describes a bug in the expression and criticizes the resulting design as an unsuccessful effort to save labor. ### Source excerpt It's a holiday here in the US, a celebration of labor, so we're reaching back through the archives for a story about an attempt to be labor saving that was not successful. Original. --Remy I've had to write a few domain-specific-languages in the past. As per Remy's Law of Requirements Gathering, it's been mostly because the users needed an Excel-like formula language. The danger of DSLs, of course, is that they're often YAGNI in the extreme, or at least a sign that you don't really understand your problem. XML, coupled with schemas, is a tool for building data-focused DSLs. If you have some complex structure, you can convert each of its features into an XML attribute. For example, if you had a grammar that looked something like this: The Source specification obeys the following syntax source = ( Feature1+Feature2+... ":" ) ? steps Feature1 = "local" | "global" Feature2 ="real" | "virtual" | "ComponentType.all" Feature3 ="self" | "ancestors" | "descendants" | "Hierarchy.all" Feature4 = "first" | "last" | "DayAllocation.all" If features are specified, the order of features as given above has strictly to be followed. steps = oneOrMoreNameSteps | zeroOrMoreNameSteps | componentSteps oneOrMoreNameSteps = nameStep ( "." nameStep ) * zeroOrMoreNameSteps = ( nameStep "." ) * nameStep = "#" name name is a string of characters from "A"-"Z", "a"-"z", "0"-"9", "-" and "_". No umlauts allowed, one character is minimum. componentSteps is a list of valid values, see below. Valid 'componentSteps' are: - GlobalValue - Product - Product.Brand - Product.Accommodation - Product.Accommodation.SellingAccom - Product.Accommodation.SellingAccom.Board - Product.Accommodation.SellingAccom.Unit - Product.Accommodation.SellingAccom.Unit.SellingUnit - Product.OnewayFlight - Product.OnewayFlight.BookingClass - Product.ReturnFlight - Product.ReturnFlight.BookingClass - Product.ReturnFlight.Inbound - Product.ReturnFlight.Outbound - Product.Addon - Product.Addon.Service - Product.Addon.ServiceFeatu ## DocLang: a markup language for LLMs DevFeed: [DocLang: a markup language for LLMs]() Original publisher: [Read original article]() Author: Kim Martineau Published: 2026-08-12T12:00:00Z Content type: article Language: en Sources: [IBM Research]() Topics: [XML](), [Parser](), [Parsing](), [Large Language Model](), [Generative AI](), [HTML]() Tags: [ai](), [algorithms](), [generative-ai](), [llms](), [news](), [parsing](), [xml]() ### AI overview IBM researchers introduce DocLang, a constrained XML sub-language designed to help large language models interpret document structure. The article explains how it represents semantics, layout, bounding boxes, and reading order, and how it may reduce token use, latency, and inference costs in AI pipelines. ### Source excerpt The lead researcher behind IBM's popular document parser, Docling, explains why generative AI needs its own document standard. ## kPointer Replaces cw-json with Support for JSON, YAML, HTML, and XML DevFeed: [kPointer Replaces cw-json with Support for JSON, YAML, HTML, and XML]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-22T12:27:15Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [data](), [JSON](), [YAML](), [HTML](), [XML](), [Command-line interface](), [test]() Tags: [blog](), [cli](), [data](), [html](), [json](), [sdk](), [test](), [testing](), [xml](), [yaml]() ### AI overview kPointer replaces cw-json as a library for extracting values from structured data. It supports JSON, YAML, HTML, and XML through adapter-style abstractions, adds JavaScript access path notation, and includes conformance testing and a CLI. ### Source excerpt The cw-json project has been replaced by kPointer -- learn what kPointer offers! ## Rich Text And Code Editing: RichTextArea And A Syntax-Highlighting CodeEditor DevFeed: [Rich Text And Code Editing: RichTextArea And A Syntax-Highlighting CodeEditor]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-28T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Syntax Highlighting](), [Code](), [cross-platform](), [Web](), [JavaScript](), [Kotlin](), [Python](), [CSS](), [JSON](), [XML]() Tags: [code](), [code-completion](), [cross-platform](), [css](), [javascript](), [kotlin](), [python](), [syntax](), [web](), [xml]() ### AI overview The article describes RichTextArea and CodeEditor, two Codename One visual editors built on a shared semantic abstraction. A bundled cross-platform web-view engine is the default backend, while ports can provide optional native peers. The CodeEditor supports syntax highlighting for eight languages, themes, automatic bracket and quote closing, and asynchronous code completion. ### Source excerpt RichTextArea and a syntax-highlighting CodeEditor, both built on a shared editor abstraction with a cross-platform web-view engine and an optional native peer. ## Sliding Doors: ten years of RSS-Parser DevFeed: [Sliding Doors: ten years of RSS-Parser]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2026-06-17T00:00:00Z Content type: opinion Language: en Sources: [Posts on Marco Gomiero]() Topics: [RSS Feed](), [RSS](), [Mobile](), [Kotlin](), [Coroutines](), [Java](), [Android](), [iOS](), [macOS]() Tags: [android](), [coroutines](), [ios](), [java](), [kotlin](), [macos](), [mobile](), [rss](), [xml]() ### AI overview The author reflects on ten years of RSS-Parser, a library that began as part of an RSS-reading app and was later published for other developers. The article describes how the project contributed to the author's learning and career, including its move from Java to Kotlin and Coroutines, and its continued use in developing a new RSS app. ### Source excerpt Today marks ten years since the first commit of RSS-Parser. TEN YEARS. I want to use this opportunity to reflect on the journey of this library, the sliding doors moments along the way, and the chain of events that made RSS-Parser an important part of my career. The bare bones of the library started earlier, though; it was 2015 when I wrote my first app that I've published to the Play Store. This app was for reading the articles of the tech blog that I was collaborating with (for a while I was reviewing apps, phones, consumer tech - that's when I fell in love with mobile). The blog was built (of course) with the good old WordPress, and at the time I discovered that you can have the published articles formatted in XML - yes, I discovered the existence of RSS. ## Extract Text from Your PDF and Image Files with Apache Tika DevFeed: [Extract Text from Your PDF and Image Files with Apache Tika]() Original publisher: [Read original article]() Author: Nic Raboy Published: 2026-06-13T00:45:07Z Content type: tutorial Language: en Sources: [Nic Raboy]() Topics: [Docker Compose](), [Docker](), [container](), [AI search]() Tags: [ai](), [browser](), [command-line](), [container](), [docker](), [how-to](), [image](), [pdf](), [rag](), [services](), [xml]() ### AI overview This tutorial explains how to deploy Apache Tika with Docker or Docker Compose and use it to extract text from PDF, image, and other document formats. The extracted text can provide plaintext context for local AI tools and RAG workflows. ### Source excerpt With AI becoming increasingly popular in everything, and retrieval-augmented generation (RAG) becoming a requirement in everyone's organization, how you're providing context to the AI tools becomes im... The post Extract Text from Your PDF and Image Files with Apache Tika appeared first on The Polyglot Developer. ## OpenAPI, ORM, SVG and Lottie DevFeed: [OpenAPI, ORM, SVG and Lottie]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-01T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [OpenAPI Specification](), [Code generation](), [SQLite](), [Object-relational mapping](), [JSON](), [XML](), [SVG](), [ASP.NET Core](), [FastAPI](), [Nest]() Tags: [build](), [fastapi](), [http](), [java](), [json](), [lottie](), [maven-plugin](), [net](), [openapi](), [orm](), [rest](), [spring](), [svg](), [xml]() ### AI overview A Codename One release follow-up describes a shared build-time code generation pipeline for OpenAPI client generation, a SQLite ORM, JSON and XML mappers, SVG and Lottie transcoders, and a declarative router. The pipeline emits typed Java from annotations or declarative source files without reflection. ### Source excerpt An OpenAPI client generator, a JPA-shaped SQLite ORM, JAXB-shaped JSON / XML mappers, build-time SVG / Lottie transcoders, and a declarative router with deep links. All on the same build-time codegen pipeline. ## From RSS to Atom DevFeed: [From RSS to Atom]() Original publisher: [Read original article]() Published: 2026-05-04T00:00:00Z Content type: opinion Language: en Sources: [Susam Pal]() Topics: [Atom Feed](), [RSS Feed](), [Lisp](), [Git](), [XML]() Tags: [2026](), [git](), [git-commit](), [lisp](), [rss](), [xml]() ### AI overview The author describes switching a personal website from RSS feeds to Atom feeds in 2026. The change was implemented in Common Lisp, took about an hour, and included replacing RSS item identifiers with UUID-based Atom entry identifiers and updating feed templates. ### Source excerpt Yesterday, I switched my website from RSS feeds to Atom feeds. In case you are wondering whether you have somehow landed on an ancient post from 2010, no, you have not. Yes, this is the year 2026, and I have finally switched from RSS feeds to Atom feeds. Yes, I am fifteen, or perhaps twenty, years too late. Contents Impulse Coding Atom Entries Temporary Workaround Does It Matter? References Impulse Coding I have always wanted to do this but could never make the time for it. Finally, it happened while I was giving my brain some rest from my ongoing algebraic graph theory studies. That's when I felt like spending a little time on my website and doing a little Lisp to change the feeds from RSS to Atom. I suppose this was impulse coding, a bit like impulse buying, except that I ended up with an Atom feed instead of a new book. I find it quite surprising that when I have plenty of time, it usually does not occur to me to do these things, but when I am too busy and really short of time, these little ideas possess me during the short breaks I take. My personal website is one of my passion projects. Common Lisp is one of my favourite programming languages. So any time spent on this passion project using my favourite programming language is a very relaxing experience for me. It serves as an ideal break between intense study sessions. It took about an hour to implement the changes needed to make the switch from RSS to Atom. In the end, I could go back to my studies reinvigorated. In case you are curious, here is the Git commit where I implemented the change from RSS to Atom: 596e1dd. As you might notice, a large portion of the change consists of replacing the key attribute in each post with the uuid attribute. The key attribute value was used as the value of the element in the RSS feeds. While an arbitrary short string could serve as the element for the items in an RSS feed, the element of the entries in an Atom feed needs to be a URI. It turns out UUID URN ## Managing Sensitive Data in jOOQ 3.21+ Logs DevFeed: [Managing Sensitive Data in jOOQ 3.21+ Logs]() Original publisher: [Read original article]() Author: lukaseder Published: 2026-03-27T12:45:19Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Logging](), [sensitive data](), [Security](), [configuration](), [Code]() Tags: [configuration](), [csv](), [debug-logging](), [jooq](), [jooq-in-use](), [json](), [logging](), [logs](), [maven](), [redacted-columns](), [security](), [sensitive-data](), [xml]() ### AI overview This article explains how jOOQ debug logging can expose query bind values and fetched records in application logs, creating security concerns in production. It describes a code-generation configuration available in commercial jOOQ distributions to mask exported data, including text, HTML, and optionally CSV, JSON, or XML output. ### Source excerpt One of jOOQ's most popular feature is the out-of-the-box debug logging experience. jOOQ developers find this feature very useful when developing their applications. Assuming you run a jOOQ query and configure your logger to print DEBUG log output: When this query is executed, your log output might contain something like this: Executing query : select ... Continue reading Managing Sensitive Data in jOOQ 3.21+ Logs -> ## Text formats are everywhere. Why? DevFeed: [Text formats are everywhere. Why?]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-03-05T14:40:58Z Content type: opinion Language: en Sources: [Daniel Lemire]() Topics: [Internet](), [data](), [Web](), [JSON](), [HTML](), [JavaScript](), [Code](), [GeoJSON](), [SVG](), [Assembly]() Tags: [assembly](), [code](), [data](), [html](), [internet](), [javascript](), [json](), [maps](), [parsing](), [web](), [xml]() ### AI overview This commentary explains why text formats remain dominant across Internet technologies and data exchange. It argues that text is often efficient in practice, easier to transform, search, quote, version, and inspect, while noting that binary formats can be preferable in some performance-sensitive cases. It also emphasizes parsing and validating data received from remote sources. ### Source excerpt The Internet relies on text formats. Thus, we spend a lot of time producing and consuming data encoded in text. Your web pages are HTML. The code running in them is JavaScript, sent as text (JavaScript source), not as already-parsed code. Your emails, including their attachments, are sent as text (your binary files are sent ... Continue reading Text formats are everywhere. Why? ## You can use newline characters in URLs DevFeed: [You can use newline characters in URLs]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-02-28T19:21:39Z Content type: tutorial Language: en Sources: [Daniel Lemire]() Topics: [Web](), [browsers](), [HTML](), [SVG](), [Parsing](), [data]() Tags: [ascii](), [browsers](), [code](), [graphics](), [html](), [parsing](), [svg](), [web](), [xml]() ### AI overview This article explains that HTML URLs can contain newline and tab characters in practice because the URL parser reports a validation error but removes those characters and continues. It also describes how ASCII whitespace is handled in data URLs, including base64-encoded PNG and SVG images. ### Source excerpt We locate web content using special addresses called URLs. We are all familiar with addresses like https://google.com. Sometimes, URLs can get long and they can become difficult to read. Thus, we might be tempted to format them like so in HTML using newline and tab characters, like so: my blog post It will ... Continue reading You can use newline characters in URLs ## Moved my blog to \[blog.wagemakers.be\](https://blog.wagemakers.be) DevFeed: [Moved my blog to \[blog.wagemakers.be\](https://blog.wagemakers.be)]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2026-01-26T17:26:00Z Content type: tutorial Language: en Sources: [stafwag Blog]() Topics: [migration](), [hosting](), [GitHub](), [Security](), [RSS Feed](), [Hugo](), [Atom](), [XML]() Tags: [atom](), [blog](), [disquss](), [github](), [hosting](), [html](), [https](), [hugo](), [jekell](), [migration](), [rss](), [security](), [security-privacy](), [xml]() ### AI overview The author moved the blog from GitHub to self-hosted hosting and documents the migration issues encountered. The article covers HTML redirects, updating hardcoded links, Disqus comment reindexing, and difficulties redirecting RSS feeds when moving from Octopress to Jekyll. ### Source excerpt If you follow my blog posts with an RSS reader, update the rss feed to: https://blog.wagemakers.be/atom.xml ...If you want to continue to follow me off-course ;-) I moved my blog from GitHub to my own hosting ( powered by Procolix ). Procolix sponsored my hosting for 20 years, till I decided to start my company Mask27.dev. One reason is that Microsoft seems to like to put "copilot everywhere", including on repositories hosted on github. While I don't dislike AI ( artificial intelligence ), LLM ( Large Language Models ) are a nice piece of technology. The security, privacy, and other issues are overlooked or even just ignored. The migration was a bit more complicated as usual, as nothing "is easy" ;-) You'll find the pitfalls of moving my blog below as they might be useful for somebody else ( including the future me ). ## \[Pentesting\] ONVIF (CCTV cameras) auth DevFeed: [\[Pentesting\] ONVIF (CCTV cameras) auth]() Original publisher: [Read original article]() Published: 2025-11-27T23:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [passwords](), [XML](), [Python]() Tags: [auth](), [camera](), [cameras](), [password](), [python](), [tcp](), [xml]() ### AI overview This article examines ONVIF authentication for CCTV cameras over TCP. It explains the username, password digest, nonce, and date fields, gives the digest calculation, and describes using Hashcat to crack a known password digest. ### Source excerpt [Pentesting] ONVIF (CCTV cameras) auth ## XML Modelling in OpenAPI 3.2: A Quiet but Important Upgrade for Enterprise Teams DevFeed: [XML Modelling in OpenAPI 3.2: A Quiet but Important Upgrade for Enterprise Teams]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2025-11-14T14:54:07Z Content type: tutorial Language: en Sources: [DeveloperHub.io]() Topics: [OpenAPI Specification](), [XML](), [upgrade](), [API]() Tags: [api-design](), [engineering](), [enterprise](), [openapi](), [upgrade](), [xml]() ### AI overview OpenAPI 3.2 expands XML modelling with clearer support for namespaces, attributes, mixed content, and precisely named nested wrappers. The article explains how these capabilities address limitations in OpenAPI 3.1 and reduce reliance on parallel XSDs, proprietary extensions, and prose documentation. ### Source excerpt OpenAPI 3.2 modernises XML support with richer modelling, proper attribute handling, and nested structures. It removes old workarounds and gives enterprise teams clearer, more accurate ways to define their XML based APIs. ## Changes in ipSpace.net RSS Feeds DevFeed: [Changes in ipSpace.net RSS Feeds]() Original publisher: [Read original article]() Published: 2025-10-08T04:40:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [RSS Feed](), [Atom](), [Atom Feed](), [Hugo](), [XML](), [HTML]() Tags: [hugo](), [rss](), [update](), [web](), [xml]() ### AI overview The author describes replacing the ipSpace.net RSS and Atom feed generation system with static Hugo-generated feeds, adding redirects for older URLs, and discontinuing the free-content feed. The changes followed a Feedburner failure that prevented Apple Podcasts from discovering a new episode. The article also discusses feed formatting issues involving iTunes tags, whitespace trimming, HTML escaping, content truncation, and conversion of HTML to plain text. ### Source excerpt TL&DR: You shouldn't see any immediate impact of this change, but I'll eventually clean up old stuff, so you might want to check the URLs if you use RSS/Atom feeds to get the list of ipSpace.net blog posts or podcast episodes. The (hopefully) final URLs are listed on this page. Executive Summary: I cleaned up the whole ipSpace.net RSS/Atom feeds system. The script that generated the content for various feeds has been replaced with static Hugo-generated RSS/Atom feeds. I added redirects for all the old stuff I could find (including ioshints.blogspot.com), but I could have missed something. The only defunct feed is the free content feed (which hasn't changed in a while, anyway), as it required scanning the documents database. You can use this page to find the (ever-increasing) free content. And now for the real story ;) Read more ... ## Compose Unstyled v1.40: Android XML themes DevFeed: [Compose Unstyled v1.40: Android XML themes]() Original publisher: [Read original article]() Author: Alex Styl Published: 2025-08-14T00:00:00Z Content type: release Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [Compose](), [Jetpack Compose](), [migration](), [Android](), [XML](), [material-components]() Tags: [adapter](), [android](), [api](), [compose](), [jetpack](), [jetpack-compose](), [material-components](), [migration](), [performance](), [v1](), [xml]() ### AI overview Compose Unstyled v1.40.0 introduces the resolveTheme API, which lets Jetpack Compose resolve selected values from existing Android XML themes during a gradual migration from Views. The approach avoids maintaining duplicate theme sources, but each resolution has a measurable performance cost and is intended to be temporary. ### Source excerpt v1.40.0 introduces a new resolveThemeX() API to make the migration to Jetpack Compose simpler. ## Where Are the NETCONF/YANG Tools? DevFeed: [Where Are the NETCONF/YANG Tools?]() Original publisher: [Read original article]() Published: 2025-06-04T05:38:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [NETCONF](), [Tooling](), [Network](), [Automation](), [XML]() Tags: [netconf](), [network](), [network-automation](), [tooling](), [xml]() ### AI overview The article examines difficulties finding reliable, current tooling for NETCONF/YANG network-device configuration and model inspection. It discusses ncclient's incomplete documentation, abandoned or outdated YANG tools, installation problems on modern Python versions, and the challenges of using Docker-based tooling. It mentions pyang as a possible tool and asks readers to recommend maintained alternatives. ### Source excerpt Jo attempted to follow the vendor Kool-Aid recommendations and use NETCONF/YANG to configure network devices. Here's what he found (slightly edited): IMHO, the whole NETCONF ecosystem primarily suffers from a tooling problem. Or I haven't found the right tools yet. ncclient is (as you mentioned somewhere else) an underdocumented mess. And that undocumented part is not even up to date. The commit hash at the bottom of the docs page is from 2020... I am amazed how so many people got it working well enough to depend on it in their applications. Read more ... ## Repost: On the Advantages of XML DevFeed: [Repost: On the Advantages of XML]() Original publisher: [Read original article]() Published: 2025-05-26T06:07:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [XML](), [JSON](), [NETCONF](), [Artificial Intelligence](), [Python](), [ChatGPT]() Tags: [ai](), [automation](), [chatgpt](), [json](), [netconf](), [python](), [xml]() ### AI overview This reposted discussion examines XML and JSON for network automation. It argues that XML's semantic structure can support reliable, maintainable automation despite XML's size and complexity, while describing mixed results from ChatGPT-generated XPath and Python code, including failures in a fuller ncclient solution. ### Source excerpt Continuing the discussion started by my Breaking APIs or Data Models Is a Cardinal Sin and Screen Scraping in 2025 blog posts, Dr. Tony Przygienda left another thoughtful comment worth reposting as a publicly visible blog post: Having read your newest rant around my rant ;-} I can attest that you hit the nail on the very head in basically all you say: XML output big? yeah. JSON squishy syntax? yeah. SSH prioritization? You didn't live it until you had a customer where a runaway python script generated 800+ XML netconf sessions pumping data ;-) Read more ... ## Screen Scraping in 2025 DevFeed: [Screen Scraping in 2025]() Original publisher: [Read original article]() Published: 2025-05-07T09:32:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Structured-data](), [JSON](), [XML](), [Parsing](), [Python]() Tags: [automation](), [blog-post](), [code](), [data](), [json](), [parsing](), [python](), [xml]() ### AI overview The article examines why screen scraping remains necessary for network devices that lack reliable JSON or XML output. It compares screen-scraped text with structured data, noting that JSON and XML can be larger and that manually generated or legacy structured output may be invalid or unavailable. It also argues that XML is generally harder to process than JSON, especially for large objects and data involving namespaces. ### Source excerpt Dr. Tony Przygienda left a very valid (off-topic) comment to my Breaking APIs or Data Models Is a Cardinal Sin blog post: If, on the other hand, the customers would not camp for literally tens of years on regex scripts scraping screens, lots of stuff could progress much faster. He's right, particularly from Juniper's perspective; they were the first vendor to use a data-driven approach to show commands. Unfortunately, we're still not living in a perfect world: Read more ... ## Inner Loop Agents DevFeed: [Inner Loop Agents]() Original publisher: [Read original article]() Published: 2025-04-19T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Large Language Model](), [Tool](), [Parsing](), [Ollama](), [vllm](), [JSON](), [Reinforcement learning](), [XML]() Tags: [agents](), [anthropic](), [api](), [json](), [llm](), [ollama](), [openai](), [parsing](), [reinforcement-learning](), [tools](), [vllm](), [xml]() ### AI overview This article explains "inner loop agents," a design in which an LLM can parse and execute tool calls within the model-serving loop instead of returning control to a client. It discusses how software such as Ollama and vLLM handles model-specific tool-call formats and suggests that concurrent tool use during generation is a key motivation. ### Source excerpt What if an LLM could use tools directly? In this post I discuss a potentially divergent view of agents, where agents are less like systems and more like LLMs specially trained to solve problems with a specific set of tools. ## SAML roulette: the hacker always wins DevFeed: [SAML roulette: the hacker always wins]() Original publisher: [Read original article]() Author: Gareth Heyes Published: 2025-03-18T14:55:43Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [GitLab](), [Vulnerabilities](), [Security](), [XML](), [Exploit](), [Authentication](), [Authorization](), [Ruby](), [Library]() Tags: [attacks](), [authentication](), [authorization](), [exploit](), [github](), [gitlab](), [library](), [research](), [ruby](), [saml](), [security](), [testing](), [vulnerabilities](), [vulnerability](), [xml]() ### AI overview This security research post explains how round-trip attacks and namespace confusion in the ruby-saml library can be chained to bypass signature verification and obtain unauthenticated administrative access to GitLab Enterprise. It describes parser inconsistencies involving REXML and Nokogiri, XML mutations using comments and CDATA, and a testbed for evaluating SAML libraries. The supplied article text ends during the discussion of DOCTYPE analysis. ### Source excerpt Introduction In this post, we'll show precisely how to chain round-trip attacks and namespace confusion to achieve unauthenticated admin access on GitLab Enterprise by exploiting the ruby-saml library ## Using Compose Previews to Preview XML-Based Android Views DevFeed: [Using Compose Previews to Preview XML-Based Android Views]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2024-12-17T20:09:09Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [Jetpack Compose](), [XML](), [Android](), [ui](), [Code]() Tags: [android](), [android-app-development](), [android-studio](), [compose](), [jetpack-compose](), [layout](), [recyclerview](), [testing](), [ui](), [ui-testing](), [xml]() ### AI overview This tutorial explains how Jetpack Compose Previews can be used to preview XML-based Android Views, including ViewHolder UI logic and dynamic behavior that static XML previews cannot represent. ### Source excerpt Jetpack Compose has transformed Android UI development with its declarative approach, making UI code simpler to write. One of its standout features is Compose Previews, which allows developers to instantly view how Composable functions will look on a... ## Demystifying Maestro's UI Testing Implementation DevFeed: [Demystifying Maestro's UI Testing Implementation]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2024-11-18T13:59:04Z Content type: article Language: en Sources: [Handstand Sam]() Topics: [Testing](), [ui-testing](), [Android](), [Code](), [Git]() Tags: [adb](), [android](), [android-testing](), [code](), [format](), [git](), [library](), [maestro](), [on-device](), [open-source](), [server](), [testing](), [ui](), [ui-testing](), [uiautomator](), [updates](), [xml]() ### AI overview This technical post examines how Maestro implements UI testing. It describes its YAML-based test commands, CLI-installed APKs, an on-device Netty gRPC server, UiAutomator view-hierarchy access, XML serialization, and UI interactions. ### Source excerpt I first heard about Maestro when it was released in 2022, but I haven't played with it until now. I'm doing some work with Espresso and UiAutomator for Android testing and was curious how Maestro worked under the hood, so I cloned their git repo and dove into the code. This quick post shares what [...] ## Essential Annotations Every Spring Developer Should Know DevFeed: [Essential Annotations Every Spring Developer Should Know]() Original publisher: [Read original article]() Author: Nelson Djalo Published: 2024-10-08T16:03:11Z Content type: tutorial Language: en Sources: [Amigoscode Newsletter]() Topics: [Spring Boot](), [Java](), [Application Development](), [configuration](), [Spring MVC](), [HTTP](), [JSON](), [XML]() Tags: [application-development](), [developer](), [http](), [java](), [json](), [mvc](), [spring](), [spring-boot](), [xml]() ### AI overview A tutorial explaining commonly used Spring Boot annotations for configuring applications, managing dependencies, enabling auto-configuration, scanning components, defining MVC controllers, handling HTTP responses, and binding URL and request parameters. ### Source excerpt Understanding Key Annotations for Simplified Development [Next page]()