[Design the new POJO MicroContainer] - Re: Some Maven related changes
by alesj
"pgier" wrote :
| For microcontainer we wouldn't have anything other than Java. But if we use the standard maven directory names, then I can remove that config from the poms. Yes, it's most useful when you have multi language projects which includes stuff like javacc grammar files (src/main/javacc) like we have in the app server build.
|
| I'll plan on changing all the MC subproject directories also. And eventually the app server will change once it's fully migrated.
OK, you have green light to do it, all proposed changes.
But starting on Thursday, when I'm already on holiday. :-)
What about that release-pom.xml issue we never resolved?
Keep us posted about the changes. ;-)
"adrian(a)jboss.org" wrote :
| I'd suggest doing this while Ales is on holiday to minimize the impact and
| before the branches get created for 2.0.x
|
Yup, good call. ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172561#4172561
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172561
17 years, 7 months
[Design the new POJO MicroContainer] - Re: JBMICROCONT-336; empty string failure
by adrian@jboss.org
"alex.loubyansky(a)jboss.com" wrote : In XB empty string processing is different for simple and complex types. I.e. for the following element
| <e></e>
| the result will be an empty string if e is of a simple type and null if e is of a complex type. It's null for the complex types because otherwise elements of complex types would always get non-null text data which was undesirable.
This is a complex type, but it is also "mixed", i.e. it can take a value.
Maybe there should be some kind of @JBossXmlValue
annotation where we can say we want the empty string even for complex types.
I'd suggest an element on the annotation where you say you don't want
the empty string data if there are child xml elements?
That is the rule for the mc's property element, but there's no way to say
that in an xml schema. ;-)
A workaround would be to create a subclass of AbstractPropertyMetaData
that initialises the value to an empty StringValueMetaData and then specify
that class on @XmlElement of the setProperties()
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172556#4172556
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172556
17 years, 7 months
[Design of Messaging on JBoss (Messaging/JBoss)] - JBM remoting configuration
by timfox
As discussed I would like to make changes to our remoting layer, to generalise the way our transports are configured and to allow a non fixed of transport types.
Currently all our transports are configured via hard coded properties in the Configuration and ConnectionParams classes, which all transports use to get their config.
Instead I propose each acceptor config on the server side can be configured with a typed map of properties that can be used by the specific transport.
On the client side, the ClientSessionFactory will take a String transport identifier, and an optional map of properties.
The mapping between String identifier and ConnectorFactory is specified in jbm-connector-factories.properties, which can be overridden on the classpath.
This means we can get rid of TransportType enum, since the mapping between name and factory is no longer hardcoded - this makes things more flexible.
We can also get rid of Location and ConnectionParams - and remove several attributes from configuration.
Any comments?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172543#4172543
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172543
17 years, 7 months