OK - the trunk should now be building again - I have put a patch in place on the construction of the installers for components, note that they now reference servicemix-soap as a shared library, this is to stop the repackaging of servicemix libs for each component. There still seems to be an issue in the filtering of dependencies ( https://issues.apache.org/activemq/browse/SM-480), we are looking into this.
Thanks Philip On 7/3/06, Philip Dodds <[EMAIL PROTECTED]> wrote:
Yeah :( Unfortuately we are working on both issues now and we should be back in business very soon P On 7/3/06, Renaud Bruyeron < [EMAIL PROTECTED]> wrote: > > > That's not the only problem - I had a look inside the servicemix-http > installer that was generated, and it definitely does not look right to > me (it's missing a lot of stuff like servicemix-common, servicemix-soap, > etc). I think someone else brought this up in another thread already. > > I guess trunk is hosed because of the plugin change you are referring > to. > > - Renaud > > Philip Dodds wrote: > > There is a problem with the sample after some changes in the Maven > > plugin to > > support generating the packages, it should be fixed shortly though > you can > > skip the samples if you want. > > > > P > > > > On 7/3/06, Renaud Bruyeron < [EMAIL PROTECTED]> wrote: > >> > >> > >> ok I've hacked up something, but I can't test it because I can't > build > >> trunk. Any idea ? (why is it so friggin' hard to build this thing > btw?) > >> > >> Missing: > >> ---------- > >> 1) > >> > >> > org.apache.servicemix.samples.wsdl-first:http-su:jar:3.0-incubating-SNAPSHOT > >> > >> > >> Try downloading the file manually from the project website. > >> > >> Then, install it using the command: > >> mvn install:install-file > >> -DgroupId=org.apache.servicemix.samples.wsdl-first-DartifactId=http-su \ > >> -Dversion= 3.0-incubating-SNAPSHOT -Dpackaging=jar > >> -Dfile=/path/to/file > >> > >> Path to dependency: > >> 1) > >> > >> > org.apache.servicemix.samples.wsdl-first:sa:jbi-service-assembly:3.0-incubating-SNAPSHOT > >> > >> 2) > >> > >> > org.apache.servicemix.samples.wsdl-first:http-su:jar:3.0-incubating-SNAPSHOT > >> > >> > >> 2) > >> > >> > org.apache.servicemix.samples.wsdl-first:jsr181-su:jar:3.0-incubating-SNAPSHOT > >> > >> > >> Try downloading the file manually from the project website. > >> > >> Then, install it using the command: > >> mvn install:install-file > >> -DgroupId= org.apache.servicemix.samples.wsdl-first-DartifactId=jsr181-su > >> \ > >> -Dversion=3.0-incubating-SNAPSHOT -Dpackaging=jar > >> -Dfile=/path/to/file > >> > >> Path to dependency: > >> 1) > >> > >> > org.apache.servicemix.samples.wsdl-first:sa:jbi-service-assembly:3.0-incubating-SNAPSHOT > >> > >> 2) > >> > >> > org.apache.servicemix.samples.wsdl-first:jsr181-su:jar:3.0-incubating-SNAPSHOT > >> > >> > >> ---------- > >> 2 required artifacts are missing. > >> > >> for artifact: > >> > >> > >> > org.apache.servicemix.samples.wsdl-first:sa:jbi-service-assembly:3.0-incubating-SNAPSHOT > >> > >> > >> from the specified remote repositories: > >> central (http://ibiblio.org/maven2/), > >> servicemix-m2-repo ( http://servicemix.org/m2-repo), > >> codehaus (http://repository.codehaus.org), > >> apache.snapshots (http://people.apache.org/maven-snapshot-repository > ), > >> codehaus.m1 (http://dist.codehaus.org), > >> activemq-tmp-repo > >> ( http://people.apache.org/~chirino/incubator-activemq-4.0/maven2<http://people.apache.org/%7Echirino/incubator-activemq-4.0/maven2> > ) > >> > >> Guillaume Nodet wrote: > >> > I do not really know which http code should be returned. > >> > I would have thought a 204 (NO_CONTENT) would be fine. > >> > Everything is handled in the > >> o.a.s.http.processors.ConsumerProcessorclass. > >> > I guess that just returning the 202 when there is no out message in > the > >> jbi > >> > exchange > >> > line 210 (either in-only, robust-in-only, or in-optional-out > without > >> > response). > >> > > >> > Cheers, > >> > Guillaume Nodet > >> > > >> > On 6/30/06, Renaud Bruyeron < [EMAIL PROTECTED]> wrote: > >> >> > >> >> > >> >> I could try to fix it, but I am not sure on the best way to do > this... > >> >> I am not even sure on the semantics here: in which case should we > >> return > >> >> a 202 ? Is it when the MEP is in-only, or when the WSDL says > 'oneway', > >> >> or both? > >> >> > >> >> I am willing to look into this, but I am not too sure on the > "correct" > >> >> fix. If you have any pointers/ideas, let me know. In the mean > time, > >> I'll > >> >> create a jira for this. > >> >> > >> >> - Renaud > >> >> > >> >> Guillaume Nodet wrote: > >> >> > I think you are right. A 202 code should be returned. > >> >> > Could you raise a JIRA for that please ? > >> >> > If you can provide a patch, that would be cool :) > >> >> > > >> >> > Cheers, > >> >> > Guillaume Nodet > >> >> > > >> >> > On 6/30/06, Renaud Bruyeron < [EMAIL PROTECTED]> wrote: > >> >> >> > >> >> >> > >> >> >> I am trying to send a oneway message into a http endpoint, but > I am > >> >> >> having trouble doing this. Here's the endpoint declaration: > >> >> >> > >> >> >> <http:endpoint service="mmx:mms-service" > >> >> >> endpoint="mms-service" > >> >> >> role="consumer" > >> >> >> soap="true" > >> >> >> locationURI="http://localhost/mm7"; > >> >> >> > >> >> defaultMep="http://www.w3.org/2004/08/wsdl/in-only"; > >> >> >> wsdlResource="classpath:wsdl/gwxms.wsdl"/> > >> >> >> > >> >> >> > >> >> >> Notice the MEP is in-only. > >> >> >> > >> >> >> The proxied endpoint is actually a JMS queue: > >> >> >> > >> >> >> <jms:endpoint service="mmx:mms-service" > >> >> >> endpoint="mms-service" > >> >> >> role="provider" > >> >> >> destinationStyle="queue" > >> >> >> soap="true" > >> >> >> jmsProviderDestinationName=" queue.mms" > >> >> > >> >> >> > >> >> jndiConnectionFactoryName="java:comp/env/jms/ConnectionFactory"/> > >> >> >> > >> >> >> I am using a Axis 1.4 client to send the message in (I must use > >> Axis > >> >> >> because I need proper SAAJ support). Because it is a oneway > >> message, > >> >> the > >> >> >> client expects a HTTP 202 response. However servicemix-http > only > >> >> replies > >> >> >> with HTTP 200, which means "synchronous" in HTTP/SOAP. > >> >> >> The exchange is working ok (I see the mime message on the JMS > >> queue), > >> >> >> the trouble is with the http endpoint. > >> >> >> > >> >> >> Am I correct in setting up the MEP as in-only on the > http:endpoint? > >> >> Any > >> >> >> idea on what the problem could be? (I suspect that > http:endpoint > >> >> should > >> >> >> figure out from the WSDL that the message is oneway and return > HTTP > >> >> 202 > >> >> >> accordingly, but I could be wrong). > >> >> >> > >> >> >> - Renaud > >> >> >> > >> >> >> > >> >> > > >> >> > >> >> > >> > > >> > >> > > > >
