I want to know how a wsdl can be active and made deployed in a container.

I created a new project from scratch.

In src i added a wsdl. In pom.xml i specified a cxf wsdl2java codegen plugin
. Then i bundled it and deployed to servicemix successfully. but i was not
able to point the wsdl file through browser. Is there anything else i need
to do for making the wsdl active ?.

BYW i created a camel-context file which will do a simple file transfer.
Which is working fine. When the above issue is solved i can add cxf to the
camel context.

Please help out in this. I have added the pom.xml of the project i created.

  <groupId>org.*****.coe.fuseprojects</groupId>
  <artifactId>camelblueprint</artifactId>
  <version>0.0.1-SNAPSHOT</version>
  <packaging>jar</packaging>
  <name>CAMEL CXF BLUEPRINT TEST PROJECT - CoE</name>
  <description>Camel project with cxf and blueprint</description>
 
  <dependencies>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <scope>test</scope>
    </dependency>
  </dependencies>
 
  <build>
        <plugins>
           
                        <plugin>
                                <groupId>org.apache.felix</groupId>
                                <artifactId>maven-bundle-plugin</artifactId>
                                 <version>2.3.4</version>
                               
                                <configuration>
                                       
<manifestLocation>target/META-INF</manifestLocation>
                                        <instructions>
                                               
<Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>
                                               
<Export-Package>org.*****.coe.fuseprojects.camelblueprint*</Export-Package>
                                                <Import-Package>
                                                    *,
                                                       
org.apache.camel.osgi,
                                                        META-INF.cxf,
                                                        META-INF.cxf.osgi,
                                                        org.apache.cxf,
                                                       
org.apache.cxf.binding,
                                                       
org.apache.cxf.binding.corba,
                                                       
org.apache.cxf.binding.soap,
                                                       
org.apache.cxf.binding.soap.spring,
                                                        org.apache.cxf.bus,
                                                       
org.apache.cxf.bus.resource,
                                                       
org.apache.cxf.bus.spring,
                                                       
org.apache.cxf.buslifecycle,
                                                       
org.apache.cxf.catalog,
                                                       
org.apache.cxf.configuration,
                                                       
org.apache.cxf.configuration.spring,
                                                       
org.apache.cxf.endpoint,
                                                       
org.apache.cxf.headers,
                                                       
org.apache.cxf.management,
                                                       
org.apache.cxf.management.jmx,
                                                       
org.apache.cxf.phase,
                                                       
org.apache.cxf.resource,
                                                       
org.apache.cxf.service.factory,
                                                       
org.apache.cxf.transport,
                                                       
org.apache.cxf.transport.http,
                                                       
org.apache.cxf.transport.http.policy,
                                                       
org.apache.cxf.transport.http_jetty,
                                                       
org.apache.cxf.transport.jms,
                                                       
org.apache.cxf.transports.http,
                                                       
org.apache.cxf.workqueue,
                                                        org.apache.cxf.wsdl,
                                                       
org.apache.cxf.wsdl11,
                                                       
org.apache.ws.security.action,
                                                       
org.apache.ws.security.processor,
                                                       
org.springframework.beans.factory.config,
                                                       
org.springframework.mail.javamail,
                                                        *
                                            </Import-Package>
                                        </instructions>
                                </configuration>
                        </plugin>

                       
      <plugin>
        <groupId>org.apache.cxf</groupId>
        <artifactId>cxf-codegen-plugin</artifactId>
        <version>2.4.1</version>
        <executions>
          <execution>
            <id>generate-sources</id>
            <phase>generate-sources</phase>
            <configuration>
             
<sourceRoot>${basedir}/target/generated/src/main/java</sourceRoot>
              <wsdlOptions>
                <wsdlOption>
                 
<wsdl>${basedir}/src/main/resources/META-INF/wsdl/report_incident.wsdl</wsdl>
                </wsdlOption>
              </wsdlOptions>
            </configuration>
            <goals>
              <goal>wsdl2java</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

    </plugins>
    </build>
</project>

Regards
Guru 

--
View this message in context: 
http://camel.465427.n5.nabble.com/How-a-wsdl-is-published-tp4996722p4996722.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to