October 2009 - jboss-dev-forums - Jboss List Archives

[JBoss XML Binding Development] - Re: How to retrieve the value of a

by epbernard

"alex.loubyansky(a)jboss.com" wrote : Use controls presence. If use="required" the attribute must appear in the XML. | Fixed is a value constraint. If the attribute is present and different from the fixed value the parsing will fail. | You sure? My schema parsing is failing when I add unexpected elements (blah) but they pass if I don't set version. Even worse, if I set version, then it fails Caused by: org.xml.sax.SAXException: cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'persistence-unit' anonymous wrote : | All this stuff is handled by the underlying xml parser, which is xerces SAX in our case. Xerces will include fixed and default attributes into org.xml.sax.Attributes only if schema validation is enabled. | | In XB you can do that by unmarshaller.setSchemaValidation(true); It's for JBoss Metadata's JPA parsing. Do you know the piece of code that set the unmarshaller? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261878#4261878 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261878

16 years, 2 months

1
0
0 / 0

[JBoss XML Binding Development] - Re: How to retrieve the value of a

by alex.loubyansky＠jboss.com

We could create an annotation for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261876#4261876 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261876

16 years, 2 months

1
0
0 / 0

[JBoss XML Binding Development] - Re: How to retrieve the value of a

by david.lloyd＠jboss.com

I guess Alexey nailed it. Anyway it's unlikely we'd ever turn on validation due to perf. reasons. My analysis of handing this kind of situation (two very similar but not identical namespaces with JBossXB or JAXB in general) came to the conclusion that you can't really do it cleanly without having completely separate object models, which of course is a ton of redundancy. Maybe there's some way you can hack it into telling you what namespace was parsed? Setting it as a property on your root element or something? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261874#4261874 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261874

16 years, 2 months

1
0
0 / 0

[JBoss XML Binding Development] - Re: How to retrieve the value of a

by epbernard

"david.lloyd(a)jboss.com" wrote : So the default value of the field depends on the JPA spec in force? How is that differentiated? Through the namespace? Different version of the xsd, there is also a version attribute on the schema (unrelated though in theory) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261873#4261873 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261873

16 years, 2 months

1
0
0 / 0

[JBoss XML Binding Development] - Re: How to retrieve the value of a

by alex.loubyansky＠jboss.com

Use controls presence. If use="required" the attribute must appear in the XML. Fixed is a value constraint. If the attribute is present and different from the fixed value the parsing will fail. All this stuff is handled by the underlying xml parser, which is xerces SAX in our case. Xerces will include fixed and default attributes into org.xml.sax.Attributes only if schema validation is enabled. In XB you can do that by unmarshaller.setSchemaValidation(true); View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261866#4261866 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261866

16 years, 2 months

1
0
0 / 0

[JBoss XML Binding Development] - Re: How to retrieve the value of a

by david.lloyd＠jboss.com

So the default value of the field depends on the JPA spec in force? How is that differentiated? Through the namespace? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261864#4261864 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261864

16 years, 2 months

1
0
0 / 0

[JBoss AS Development Deployment Framework] - Re: Incorrect Undeployment Order

by alesj

Yup, this is a bug: - https://jira.jboss.org/jira/browse/JBDEPLOY-218 But the "real" problem is that your app is missing explicit dependency on RA. e.g. if there was one and RA was undeployed first, MC Controller would apply/recognize that dependency and undeploy app before it fully undeploys RA Once we fully enforce classloading dependencies among JBossAS components, this will fall out of the box, till then you should use either: * jboss-dependency.xml * jboss-classloading.xml mechanism: http://www.jboss.org/community/docs/DOC-13178 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261858#4261858 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261858

16 years, 2 months

1
0
0 / 0

[JBoss XML Binding Development] - How to retrieve the value of a "fixed" attribute

by epbernard

JPA 2 has added a new attribute to the persistence-unit element. It is required but is fixed at the same time so the user doesn't have to set it explicitly. I can't seem to find a way to let JBoss XB to populate my mapped attribute with he fixed value. I always end up with null. How can I do that? PS: I can't hard code the value as the binding model is supposed to bind both JPA1 and JPA2 so null != 2.0 Here is the attribute declaration <xsd:attribute name="version" type="persistence:versionType" | fixed="2.0" use="required"/> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261856#4261856 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261856

16 years, 2 months

1
0
0 / 0

[Management Development] - Re: management domain model

by emuckenhuber

Another item which might be important to mention is the differences in building managedObjects. Whereas most spec deployment descriptor (ejbs, wars) mostly represent the desired management view already (excl. metrics). This is different for jboss-beans.xml and -service.xml which are more assembly descriptors than something directly usable for management. In AS5 we are already applying some changes based on the managedObject view to the actual deployment descriptor which is quite tricky, as the actual injected value might differ from the deployment descriptor - especially for more complex values - like we had for the ServiceBindingManager. Also those changes would need to get applied earlier not after classloading to support something like offline-edits. I'll start with some changes in jboss-man, which we should do regardless of the additional requirements for the domain model. Basically starting with separating the population with the building of ManagedObjects. This should be a separate step, maybe even built on a different managedObject metadata/structure. This description represents a model for the managedObject itself and should be reusable for the same type of components - only that the values are going to be different. The deployers integration could also be improved, to something a bit more explicit where we don't process the same meta data several times. I also want to move some Component processing (currently done in the ManagementView) more in this model building. Maybe the only thing the ManagementView should do is to create some composite ManagedObjects - containing more managedObjects which cannot be grouped during this building process. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261854#4261854 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261854

16 years, 2 months

1
0
0 / 0

[JBoss ESB Development] - Re: duplicate key value violates unique constraint

by tomeicher

True... Thx/Tom. http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261831#4261831 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261832#4261832 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261832

16 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2009