Comments on: Using Maven Repository as Web Services Registry

By: Alexander Ananiev

Alexander Ananiev — Tue, 08 Apr 2008 02:42:49 +0000

Patrice,
No, I have not - the problem I’ve run into is that Maven is just not very widely used in corporate environments, I’m guessing, because it’s not very easy to customize.

By: Patrice Matignon

Patrice Matignon — Fri, 04 Apr 2008 20:49:13 +0000

Andi, Alexander,

I like the idea as well : have you gotten a chance to try this out, or have you found a better approach ?

Thanks in advance.

By: andi

andi — Thu, 19 Jul 2007 10:17:55 +0000

You’re right. The implementation will in most cases not be published.
My point is separation of concerns, though. Having the wsdl at hand is tempting. I’d rather have the ones who change the implementation (as you said this will happen more often than a wsdl change) depend on a frozen state of it for validation.

My quick-and-dirty-approach:
The wsdl dependency is deployed with type wsdl.
In the dependency of the service implementation you must use pom for a type.
And then the maven-dependency-plugin copies the artifact. Luckily, you can use type wsdl again here.
No other work necessary.

By: Alexander Ananiev

Alexander Ananiev — Wed, 18 Jul 2007 12:16:50 +0000

Andi,
No, I haven’t implemented it yet but I’m planning to work on it in the near future. I’m not sure about your point about service contract versioning. While the contract won’t change as often as the implementation would, in general it still follows the lifecycle of the implementation, i.e., implementation always changes when the contract changes.

The contract would still be independent from the implementation from the repository standpoint since there is no need to put implementation into the repository; “deploying” in Maven should only upload WSDL to the repository and not the code.

By: andi

andi — Wed, 18 Jul 2007 09:22:32 +0000

I like that idea.
I’m currently trying to figure out the best architecture for such an approach.
I don’t want to keep the wsdl within the service implementation project, because I see it as a contract the developer has to fulfill.
Also it should be versioned independently from the service implementation versioning.

I would then like to have the wsdl file included as a dependency, so the generated wsdl during jboss deployment can be validated against the “contract”.
However I have no idea yet on how to fetch the wsdl from the repository during the build process.

Did you already manage to work this out?