I tried deploying bridge (sorry , i told it wrong in the last post). I took out the service assembly zip file and put it inside deploy folder of service mix.
Starting Apache ServiceMix ESB: 3.1-incubating Loading Apache ServiceMix from servicemix.xml on the CLASSPATH INFO - ConnectorServerFactoryBean - JMX connector available at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi INFO - JBIContainer - ServiceMix 3.1-incubating JBI Container (ServiceMix) is starting INFO - JBIContainer - For help or more informations please see: http://incubator.apache.org/servicemix/ INFO - ComponentMBeanImpl - Initializing component: #SubscriptionManager# INFO - DeploymentService - Restoring service assemblies INFO - ServiceAssemblyLifeCycle - Starting service assembly: IQSummary-SA INFO - ServiceAssemblyLifeCycle - Starting service assembly: MyLW-SA INFO - JBIContainer - ServiceMix JBI Container (ServiceMix) started INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-eip-3.1-incubating-instal ler.zip ... WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicemix-ei p installation is suspended and will be resumed once the listed shared libraries are installed INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-eip-3.1-incubating -installer.zip INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-jms-3.1-incubating-instal ler.zip ... INFO - JDBCAdapterFactory - Database driver recognized: [apache_derby_embedded_jdbc_driver] INFO - LogTask - log4j system reconfigured WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicemix-jm s installation is suspended and will be resumed once the listed shared libraries are installed INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-jms-3.1-incubating -installer.zip INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-saxon-3.1-incubating-inst aller.zip ... WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicemix-sa xon installation is suspended and will be resumed once the listed shared libraries are installed INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-saxon-3.1-incubati ng-installer.zip INFO - AutoDeploymentService - Directory: deploy: Archive changed: processing bridge-sa-3.1-incubating.zip ... WARN - AutoDeploymentService - Components servicemix-http, servicemix-jms, servicemix-saxon, servicemix-eip are not installed yet: the service assembly bridge-sa deployment is suspended and will be resumed once the listed components are ins talled INFO - AutoDeploymentService - Directory: deploy: Finished installation of archive: bridge-sa-3.1-incubating.zip The last line says it got deployed properly, but the client.html retrieves the message "Status: 12029". Gert Vanthienen wrote: > > Varun, > > Which of the examples have you deployed (wsdl-first, bridge, ...)? Is > there a stacktrace on the console that you can post? > > Gert > > > unni_varun wrote: >> >> Hi, >> >> We tried deploying the build example provided by service mix. Deployment >> happened fine, but then when we tried to use client.html file it was >> returning the message "Status 12029". >> >> does have any idea on this ? >> >> Thanks in anticipation. >> Varun >> > > -- View this message in context: http://www.nabble.com/Status-12029-tf3940060s12049.html#a11176047 Sent from the ServiceMix - User mailing list archive at Nabble.com.
