Learn how to structure a Quarkus multi-module project with a SOAP server, client, and a clean SEI contract module that works across teams and projects.
Thanks for sharing Markus. While this "Java first" approach presented as "Option 1" is sometimes useful, for rapid prototyping and POCs, the professional practice requires, more often than not, the "Option 2", i.e. a "WSDL-first" approach. As you're explaining, SOAP services are represented, enterprise wide, as WSDL documents, containing XSDs of several hundreds lines, with complicated namespaces, etc. This is why, in my opinion, an "Option 2" implementation, would be more realistic. Especially if it addresses the case of WSDL imports, including shared schemas, etc.
But thank you anyway for popularizing this forgotten technology that only SOA people like me still remember :-)
Thank you for your comment. And you're absolutely right. I'll get to a follow up tutorial soon. I really want to make sure to start with simple basics first.
Thanks for sharing Markus. While this "Java first" approach presented as "Option 1" is sometimes useful, for rapid prototyping and POCs, the professional practice requires, more often than not, the "Option 2", i.e. a "WSDL-first" approach. As you're explaining, SOAP services are represented, enterprise wide, as WSDL documents, containing XSDs of several hundreds lines, with complicated namespaces, etc. This is why, in my opinion, an "Option 2" implementation, would be more realistic. Especially if it addresses the case of WSDL imports, including shared schemas, etc.
But thank you anyway for popularizing this forgotten technology that only SOA people like me still remember :-)
Thank you for your comment. And you're absolutely right. I'll get to a follow up tutorial soon. I really want to make sure to start with simple basics first.
And it's still more common than you think ;-)