wsdl - Maven for building SOA services and clients? -
i changed title generalize question isn't specific axis2. gave on axis2 altogether , switched metro/jax-ws considering giving on both , switching opensaml. real question i'm struggling answered here is, how build complex standards-based soa services work.
the original phrasing was: paste in working example of maven pom invoke axis2 java2wsdl defaults can live with? here's command line incantation behaves sort of ok.
-o target/generated-sources/java2wsdl \ -l "http://localhost:9763/services/policyservice" \ -tn urn:sesgg:sc:security:1.0.spec.policyservice \ -tp ps \ -stn urn:oasis:names:tc:saml:2.0:protocol \ -stp samlp \ -of policyservice.wsdl \ -sn policyservice \ -cp "../../schema/target/schema-1.0-snapshot.jar target/policyservice-1.0-snapshot.jar" \ -cn com.technica.pbac.ps.policyservice \
everything winds squirrely results; e.g. weird reversed namespaces (http://xmldsig._09._2000.w3.org/xsd example). explain why , how stop it?
there seems lot java2wsdl's out there expect entirely different arguments, little consistency between command line , maven pom.
no responses i'll post current results of own experiments others similar problems. can't guarantee correct until testing finished @ least i'm getting results can bear looking @ in eclipse:
<build> <plugins> <plugin> <groupid>org.apache.maven.plugins</groupid> <artifactid>maven-compiler-plugin</artifactid> <version>2.3.2</version> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> <plugin> <groupid>org.jvnet.jaxb2.maven2</groupid> <artifactid>maven-jaxb2-plugin</artifactid> <version>0.7.5</version> <configuration> <schemaexcludes> <exclude>*saml*.xsd</exclude> </schemaexcludes> <strict>true</strict> <extension>true</extension> </configuration> <executions> <execution> <goals> <goal>generate</goal> </goals> </execution> </executions> </plugin> <plugin> <groupid>org.apache.axis2</groupid> <artifactid>axis2-java2wsdl-maven-plugin</artifactid> <version>1.5.4</version> <executions> <execution> <goals> <goal>java2wsdl</goal> </goals> </execution> </executions> <configuration> <id>generate wsdl based on policyservice interface</id> <servicename>policyservice</servicename> <classname>com.technica.pbac.ps.policyserviceimpl</classname> <targetnamespace>http://sesgg/sc/security/1.0/spec/policyservice</targetnamespace> <targetnamespaceprefix>sesgg</targetnamespaceprefix> <schematargetnamespace>http://sesgg/sc/security/1.0/spec/policyservice</schematargetnamespace> <schematargetnamespaceprefix>sesgg</schematargetnamespaceprefix> <elementformdefault>qualified</elementformdefault> <extension>false</extension> <package2namespace> <property> <name>urn:sesgg:sc:security:1.0:spec:policyservice</name> <value>http://sesgg/sc/security/1.0/spec/policyservice</value> </property> <property> <name>com.technica.pbac.ps</name> <value>http://com.technica.pbac.ps</value> </property> <property> <name>oasis.names.tc.saml._2_0.protocol.xsd</name> <value>http://oasis/names/tc/saml/2.0/protocol</value> </property> <property> <name>oasis.names.tc.saml._2_0.protocol</name> <value>http://oasis/names/tc/saml/2.0/protocol</value> </property> </package2namespace> <episodes> <episode> <groupid>technica-pbac</groupid> <artifactid>schema-1.0-snapshot.jar</artifactid> </episode> </episodes> <outputfilename>target/generated-sources/java2wsdl/policyservice.wsdl</outputfilename> <filename>target/generated-sources/java2wsdl/services.xml</filename> <locationuri>http://localhost:9763/services/policyservice</locationuri> </configuration> </plugin> <plugin> <groupid>org.apache.axis2</groupid> <artifactid>axis2-wsdl2code-maven-plugin</artifactid> <version>1.5.4</version> <executions> <execution> <goals> <goal>wsdl2code</goal> </goals> <configuration> <wsdlfile>target/generated-sources/java2wsdl/policyservice.wsdl</wsdlfile> <packagename>com.technica.pbac.ps</packagename> <outputdirectory>target/generated-sources/wsdl2java</outputdirectory> <unwrap>true</unwrap> <allports>true</allports> <databindingname>adb</databindingname> <generateserverside>true</generateserverside> <generateallclasses>true</generateallclasses> <generateservicesxml>true</generateservicesxml> <generatetestcase>true</generatetestcase> <overwrite>true</overwrite> <servicename>policyservice</servicename> <syncmode>sync</syncmode> <backwardcompatible>false</backwardcompatible> </configuration> </execution> </executions> </plugin> </plugins> <pluginmanagement> <plugins> <plugin> <groupid>org.apache.axis2</groupid> <artifactid>axis2-java2wsdl-maven-plugin</artifactid> <version>1.5.4</version> </plugin> <plugin> <groupid>org.apache.axis2</groupid> <artifactid>axis2-wsdl2code-maven-plugin</artifactid> <version>1.5.4</version> </plugin> </plugins> </pluginmanagement> </build>
one caution: doubt right running jaxb, java2wsdl, wsdl2java , compile phases in single pom. java2wsdl runs after wsdl2java way obvously isn't right. pom doubly suspicious since java2wsdl needs compiled jar run, , seems using 1 left on previous runs. bear working again after mvn clean. i'll wind splitting several poms , adjust answer when do.
Comments
Post a Comment