The folllowing code is taken from EndpointMetaData#eagerInitializeTypes:
| [...]
| String javaTypeName = tmMetaData.getJavaTypeName();
| QName xmlType = tmMetaData.getXmlType();
| if (xmlType != null)
| {
| List<Class> types = typeMapping.getJavaTypes(xmlType);
|
| boolean registered = false;
| for (Class current : types)
| {
| if (current.getName().equals(javaTypeName))
| {
| registered = true;
| break;
| }
| }
|
| if (registered == false)
| {
| // register type follows here
| [...]
|
In which cases is type already known (registered = true;) and doesnt need to be registered?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025133#4025133
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025133
"scott.stark(a)jboss.org" wrote : Either a custom jar plugin that supports spi/impl notions, or the use of ant to build the jars would be needed otherwise.
|
I think that pretty much sums up our options
1 - Break into separate projects
2 - Create maven plugin to generate artifacts
3 - use ant to build the jars
The first option is obviously the easiest for me, but I think it is the best choice.
The second option will bring up some other issues if we start changing the names of artifacts. For example how will the artifacts be structured in the repository? If we just have two separate jars, it will be more complicated for projects that might depend on just the spi.
The third option will create a mix of ant and maven which is not ideal.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025123#4025123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025123