The http component will not generate any wsdl by itself, as it does
not have any informations.  It will only retrieve the wsdl for the
target service / endpoint and add http / soap binding to it.
Not all components support wsdl, but in your case, you use the
servicemix-jsr181 which generates a wsdl for the POJO you use.  You
can check that using a JMX console and looking for the mbean created
for the endpoint (there is an operation to retrieve the wsdl).
You should also check if one is available (from the jmx console) for
the external endpoint that is created by the http component.

Cheers,
Guillaume Nodet

On 5/8/06, mqaiserm <[EMAIL PROTECTED]> wrote:

I did'nt get what you wana say. I have no WSDL , I am assuimg that it will be
automaticall generated, the following is my servicemix.xml code is :

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:sm="http://servicemix.apache.org/config/1.0";
       xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0";
       xmlns:http="http://servicemix.apache.org/http/1.0";
       xmlns:demo="http://servicemix.apache.org/demo/";
       xmlns:my="http://servicemix.apache.org/demo/";>

  <!-- the JBI container -->
  <sm:container id="jbi"
                useMBeanServer="true"
                createMBeanServer="true"
                dumpStats="true"
            rmiPort="2222"
                statsInterval="10"
                transactionManager="#transactionManager">

        <sm:activationSpecs>

        <!-- Subscribe to a JMS destination -->
                <sm:activationSpec componentName="inputReceiver"
                                                   service="my:inputReceiver"
                                                   
destinationService="my:outputSender">
                  <sm:component>
                    <bean
class="org.apache.servicemix.components.jms.JmsInUsingJCABinding">
        <property name="jcaContainer" ref="jencks"/>
        <property name="activationSpec">
          <bean class="org.apache.activemq.ra.ActiveMQActivationSpec">
            <property name="destination"
value="demo.org.servicemix.source"/>
            <property name="destinationType" value="javax.jms.Topic"/>
          </bean>
        </property>
                    </bean>
                  </sm:component>
                </sm:activationSpec>

      <!-- Publish the result to a JMS destination -->
                <sm:activationSpec componentName="outputSender"
                                                   service="my:outputSender">
                  <sm:component>
                    <bean
class="org.apache.servicemix.components.jms.JmsSenderComponent">
        <property name="template">
          <bean class="org.springframework.jms.core.JmsTemplate">
            <property name="connectionFactory">
              <ref local="jmsFactory"/>
            </property>
            <property name="defaultDestinationName"
value="demo.org.servicemix.result"/>
            <property name="pubSubDomain" value="true"/>
          </bean>
        </property>
                    </bean>
                  </sm:component>
                </sm:activationSpec>


      <sm:activationSpec>
       <sm:component>
         <jsr181:component>
           <jsr181:endpoints>
             <jsr181:endpoint
pojoClass="com.rhg.infrastructure.webservices.HelloService"
annotations="none" service="demo:Hello" endpoint="helloService"/>
           </jsr181:endpoints>
         </jsr181:component>
       </sm:component>
       </sm:activationSpec>


       <sm:activationSpec>
       <sm:component>
        <http:component>
        <http:endpoints>
            <http:endpoint service="demo:Hello"
                                         endpoint="helloService"
                       role="consumer"
                     defaultOperation="pingHello"
                       locationURI="http://localhost:8194/Service/";
                       defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
                 soap="true" />
         </http:endpoints>
         </http:component>

        </sm:component>
       </sm:activationSpec>



        </sm:activationSpecs>
  </sm:container>


  <!-- the JCA container -->
  <bean id="jencks" class="org.jencks.JCAContainer" singleton="true">

    <!-- lets use the default configuration of work manager and transaction
manager-->
    <property name="bootstrapContext">
      <bean class="org.jencks.factory.BootstrapContextFactoryBean">
        <property name="threadPoolSize" value="25"/>
      </bean>
    </property>

    <!-- the JCA Resource Adapter -->
    <property name="resourceAdapter">
      <bean id="activeMQResourceAdapter"
class="org.apache.activemq.ra.ActiveMQResourceAdapter" singleton="true">
        <property name="serverUrl" value="tcp://localhost:61616"/>
      </bean>
    </property>
  </bean>

  <!-- message broker -->
  <bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
     <property name="config" value="classpath:activemq.xml"/>
   </bean>

        <bean id="transactionContextManager"
class="org.jencks.factory.TransactionContextManagerFactoryBean"/>
        <bean id="transactionManager"
class="org.jencks.factory.GeronimoTransactionManagerFactoryBean" />

  <bean id="jmsFactory"
class="org.apache.activemq.pool.PooledConnectionFactory">
    <property name="connectionFactory">
      <bean class="org.apache.activemq.ActiveMQConnectionFactory">
        <property name="brokerURL">
          <value>tcp://localhost:61616</value>
        </property>
      </bean>
    </property>
  </bean>

</beans>

--
View this message in context: 
http://www.nabble.com/no-wsdl-available-for-end-point-t1577004.html#a4286624
Sent from the ServiceMix - User forum at Nabble.com.


Reply via email to