[Design the new POJO MicroContainer] - Re: 2.0.0.Beta6 release
by adrian@jboss.org
When I analyze the dependencies for vfs-beta6 it's telling me it's actually
compiling over jboss-common-core:2.0.4 instead of the requested 2.2.1
| [ejort@warjort vfs-beta6]$ mvn dependency:analyze
| [INFO] Scanning for projects...
| [INFO] Searching repository for plugin with prefix: 'dependency'.
| [INFO] ----------------------------------------------------------------------------
| [INFO] Building JBoss VFS
| [INFO] task-segment: [dependency:analyze]
| [INFO] ----------------------------------------------------------------------------
| [INFO] Preparing dependency:analyze
| [INFO] [resources:resources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] [compiler:compile]
| [INFO] Nothing to compile - all classes are up to date
| [INFO] [resources:testResources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] [compiler:testCompile]
| [INFO] Nothing to compile - all classes are up to date
| [INFO] [dependency:analyze]
| [INFO] Used declared dependencies:
| [INFO] org.jboss:jboss-test:jar:1.0.4.GA:test
| [INFO] junit:junit:jar:3.8.1:test
| [INFO] Used undeclared dependencies:
| [WARNING] jboss:jboss-common-core:jar:2.0.4.GA:test
| [WARNING] jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile
| [INFO] Unused declared dependencies:
| [INFO] org.jboss:jboss-common-core:jar:2.2.1.GA:compile
| [WARNING] Potential problems discovered.
| [INFO] Found Resolved Dependency / DependencyManagement mismatches:
| [INFO] Nothing in DepMgt.
|
Did you follow this checklist?
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseProcess
Whatever is referencing 2.0.4.GA needs suppressing as a transient dependency.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102903#4102903
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102903
18 years, 5 months
[Design of JBoss Web Services] - Using the namespace in @WebFault
by veskok
It seems that even the latest version of 2.0.1 I downloaded from SVN still is not using the namespace information in the WebFault annotation to define the namespace of the XmlType that is put into the schema part of the WSDL for a fault. The service namespace is used instead. By looking at the code it seems this is not a bug but rather is done on purpose. However, there are cases when one will need to explicitly define the namespace through an annotation. The solution would be:
1. To change the current behavior. This is easy, I did it by just adding a line of code in org.jboss.metadata.builder.jaxws.JAXWSMetaDataBuilder. However, I can't be sure this will not break some use cases I don't see at the moment.
2. Start using the namespace in @XmlType which is totally ignored currently. This would be again one or two lines of code in the same place.
I can submit the code I changed to the email of the person that can take care of the problem if you think I'm right.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102893#4102893
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102893
18 years, 5 months