Skip to content

Conversation

@rmoquin
Copy link

@rmoquin rmoquin commented Jan 20, 2013

Details will be submitted in a jira referencing this pull request. Ignore the two commits that aren't mine in this, I am not sure what I did to cause them to be part of this pull request, but only my commit is meant to be here.

djencks and others added 30 commits October 24, 2008 18:59
…, Thanks for the patch, Jack Cai !

git-svn-id: https://svn.apache.org/repos/asf/geronimo/xbean/trunk@759067 13f79535-47bb-0310-9956-ffa450edef68
… tests for it and immutable context

git-svn-id: https://svn.apache.org/repos/asf/geronimo/xbean/trunk@761803 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/geronimo/xbean/trunk@764554 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/geronimo/xbean/trunk@766039 13f79535-47bb-0310-9956-ffa450edef68
…dle pathnames with containing spaces, thanks Ingo Bormann for the patch

git-svn-id: https://svn.apache.org/repos/asf/geronimo/xbean/trunk@776705 13f79535-47bb-0310-9956-ffa450edef68
…s org.apache.xbean.asm + some less important stuff

git-svn-id: https://svn.apache.org/repos/asf/geronimo/xbean/trunk@777524 13f79535-47bb-0310-9956-ffa450edef68
…ceable. Introduce some flags to configure behavior (although they are constants now)

git-svn-id: https://svn.apache.org/repos/asf/geronimo/xbean/trunk@777634 13f79535-47bb-0310-9956-ffa450edef68
Ming Xia and others added 29 commits June 7, 2012 14:26
…always expects to validate the xml. Otherwise, if you try to use an element from a different custom namespace where the any element is specified in the xsd of a different namespace, then you'll get a validation error. This also applies if you try to use any blueprint elements where the any element is in the schema for a custom namespace. The reason the validation fails is because apparently the processContents="strict" (I think it is), will only allow root elements to be placed there. This isn't caught in xbean-blueprint because the validation is turned off in the tests, but it is always on in osgi blueprint. Tests will fail if you turn on validation (I had to hack the test code to return the schema for the xml being tested and it was ugly, I'm sure someone will know a better way to turn it on).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants