On Jun 18, 2006, at 1:55 PM, Gianny Damour wrote:
Hi,
Is there a way to do this substitution of JACC implementation by
providing a substitutionGroup attribute to the security element?
giant snip
I think this is the best solution, although there are some problems.
It appears that
Hi,
Is there a way to do this substitution of JACC implementation by
providing a substitutionGroup attribute to the security element?
This may be not be correct; yet, this could look like this:
xs:complexType name=security
xs:sequence
xs:element ref=security:security
I'll have to investigate this more. I'm not very
familiar with substitution groups. If we can make
this work, I think it would take care of at least some
of Aarons concerns about anys, although for a generic
build structure we might end up with something similar
to anys. I don't like anys
The noupa approach seems to be working, although
it's going to require changes to either or both of the
m1 and m2 xmlbeans plugins... still investigating.
thanks
david jencks
--- David Jencks [EMAIL PROTECTED] wrote:
For the pluggable jacc implementation
(GERONIMO-1563)
I've been working on
I don't really like listing any elements in the middle of our
schema. Then there's no way to tell what is valid or intended. Is
there any other possible way to make this work?
If not, I'd at least like to have a security-provider element that
holds the any so it's clear what the any is
For the pluggable jacc implementation (GERONIMO-1563)
I've been working on making a basic namespace-driven
builder framework. The code is simple and looks like
it will work fine but. there's a problem with the
schema unique particle attribute rule, which basically
says that in order for a
