Is it a typo?
Hi. I met a puzzle when I read 'Now, we should be able to launch maven and have a the SA generated in the bridge-sa/target/ directory' in the page of http://incubator.apache.org/servicemix/creating-a-protocol-bridge.html http://incubator.apache.org/servicemix/creating-a-protocol-bridge.html .I guess if it is an error? Thanks a lot. -- View this message in context: http://www.nabble.com/Is-it-a-typo--tf3844618s12049.html#a10887637 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: Here is the tutorails in English.
faint 2007/5/31, xujingguo <[EMAIL PROTECTED]>: Hello,everyone. I have finished tranferring the web-style tutorails to file-style one.I am not sure if it is serviceable. and then I will finish the chinese version. http://www.nabble.com/file/p10886644/Tutorials-EN.CHM Tutorials-EN.CHM . -- View this message in context: http://www.nabble.com/Here-is-the-tutorails-in-English.-tf3844244s12049.html#a10886644 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Here is the tutorails in English.
Hello,everyone. I have finished tranferring the web-style tutorails to file-style one.I am not sure if it is serviceable. and then I will finish the chinese version. http://www.nabble.com/file/p10886644/Tutorials-EN.CHM Tutorials-EN.CHM . -- View this message in context: http://www.nabble.com/Here-is-the-tutorails-in-English.-tf3844244s12049.html#a10886644 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Commented: (SM-960) JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE )
[ https://issues.apache.org/activemq/browse/SM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39196 ] Sangwoo Han commented on SM-960: Just follow the jsr181 orchestration sample then it should generate the same error. > JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, > END_ELEMENT or ENTITY_REFERENCE ) > > > Key: SM-960 > URL: https://issues.apache.org/activemq/browse/SM-960 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-jsr181 >Reporter: Sangwoo Han >Priority: Minor > > The jsr181 orchestration sample doesn't work. > In the sample of jsr181 orchestration's CityTimeImpl.java class file > [...] > public GetCityTimeResponse getCityTime(GetCityTimeRequest > GetCityTimeRequest) { > > GetInfoByCity GetInfoByCity = new GetInfoByCity(); > GetInfoByCity.setUSCity(GetCityTimeRequest.getCity()); > > GetInfoByCityResponse r = usZip.getInfoByCity(GetInfoByCity); > Element e = (Element) > r.getGetInfoByCityResult().getContent().get(0); > e = (Element) e.getElementsByTagName("Table").item(0); > e = (Element) e.getElementsByTagName("ZIP").item(0); > String ZipCode = e.getTextContent(); > > //String lt = localTime.localTimeByZipCode(ZipCode); // at this > part it errored > GetCityTimeResponse rep = new GetCityTimeResponse(); > rep.getString().add("23:23"); > //rep.setTime(lt); // wsgen didn't generate "setTime" function > return rep; > } > [...] > and the error output is below: > > [...] > DEBUG - header - << "Content-Length: 426[\r][\n]" > DEBUG - content- << " encoding="utf-8"?>http://schemas.xmlso > ap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> dy> xmlns="http://ripedev.com/xsd/ZipCodeResults.xsd";>5/30/2007 > 8:51:44 PM ocalTimeByZipCodeResult>" > > DEBUG - Client - Received message to > urn:xfire:transport:jbi:11805763005154-996237611 > DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to > phase pre-dispatch > DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to > phase dispatch > DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to > phase dispatch > DEBUG - HandlerPipeline- Invoking phase transport > DEBUG - HandlerPipeline- Invoking phase parse > DEBUG - HandlerPipeline- Invoking phase pre-dispatch > DEBUG - HandlerPipeline- Invoking handler > org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch > DEBUG - Client - Correlating context with ID > 118057630051551778993400 > DEBUG - Client - Found correlated context with ID > 118057630051551778993400 > DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to > phase service > DEBUG - HandlerPipeline- Invoking phase dispatch > DEBUG - HandlerPipeline- Invoking handler > org.codehaus.xfire.handler.LocateBindingHandler in phase dispatch > DEBUG - HandlerPipeline- Invoking handler > org.codehaus.xfire.soap.handler.SoapBodyHandler in phase dispatch > DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to > phase user > DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to > phase pre-dispatch > DEBUG - HandlerPipeline- Invoking phase transport > DEBUG - HandlerPipeline- Invoking phase parse > DEBUG - HandlerPipeline- Invoking phase pre-dispatch > DEBUG - HandlerPipeline- Invoking handler > org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch > DEBUG - Client - Correlating context with ID > 118057630051551778993400 > DEBUG - Client - Found correlated context with ID > 118057630051551778993400 > DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to > phase service > DEBUG - HandlerPipeline- Invoking phase dispatch > DEBUG - HandlerPipeline- Invoking phase policy > DEBUG - HandlerPipeline- Invoking phase user > DEBUG - HandlerPipeline- Invoking handler > org.codehaus.xfire.client.ClientFaultConverter in phase user > DEBUG - HandlerPipeline- Invoking phase pre-invoke > DEBUG - HandlerPipeline- Invok
[jira] Created: (SM-960) JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE )
JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE ) Key: SM-960 URL: https://issues.apache.org/activemq/browse/SM-960 Project: ServiceMix Issue Type: Bug Components: servicemix-jsr181 Reporter: Sangwoo Han Priority: Minor The jsr181 orchestration sample doesn't work. In the sample of jsr181 orchestration's CityTimeImpl.java class file [...] public GetCityTimeResponse getCityTime(GetCityTimeRequest GetCityTimeRequest) { GetInfoByCity GetInfoByCity = new GetInfoByCity(); GetInfoByCity.setUSCity(GetCityTimeRequest.getCity()); GetInfoByCityResponse r = usZip.getInfoByCity(GetInfoByCity); Element e = (Element) r.getGetInfoByCityResult().getContent().get(0); e = (Element) e.getElementsByTagName("Table").item(0); e = (Element) e.getElementsByTagName("ZIP").item(0); String ZipCode = e.getTextContent(); //String lt = localTime.localTimeByZipCode(ZipCode); // at this part it errored GetCityTimeResponse rep = new GetCityTimeResponse(); rep.getString().add("23:23"); //rep.setTime(lt); // wsgen didn't generate "setTime" function return rep; } [...] and the error output is below: [...] DEBUG - header - << "Content-Length: 426[\r][\n]" DEBUG - content- << "http://schemas.xmlso ap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";>http://ripedev.com/xsd/ZipCodeResults.xsd";>5/30/2007 8:51:44 PM" DEBUG - Client - Received message to urn:xfire:transport:jbi:11805763005154-996237611 DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to phase pre-dispatch DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to phase dispatch DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to phase dispatch DEBUG - HandlerPipeline- Invoking phase transport DEBUG - HandlerPipeline- Invoking phase parse DEBUG - HandlerPipeline- Invoking phase pre-dispatch DEBUG - HandlerPipeline- Invoking handler org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch DEBUG - Client - Correlating context with ID 118057630051551778993400 DEBUG - Client - Found correlated context with ID 118057630051551778993400 DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to phase service DEBUG - HandlerPipeline- Invoking phase dispatch DEBUG - HandlerPipeline- Invoking handler org.codehaus.xfire.handler.LocateBindingHandler in phase dispatch DEBUG - HandlerPipeline- Invoking handler org.codehaus.xfire.soap.handler.SoapBodyHandler in phase dispatch DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to phase user DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to phase pre-dispatch DEBUG - HandlerPipeline- Invoking phase transport DEBUG - HandlerPipeline- Invoking phase parse DEBUG - HandlerPipeline- Invoking phase pre-dispatch DEBUG - HandlerPipeline- Invoking handler org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch DEBUG - Client - Correlating context with ID 118057630051551778993400 DEBUG - Client - Found correlated context with ID 118057630051551778993400 DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to phase service DEBUG - HandlerPipeline- Invoking phase dispatch DEBUG - HandlerPipeline- Invoking phase policy DEBUG - HandlerPipeline- Invoking phase user DEBUG - HandlerPipeline- Invoking handler org.codehaus.xfire.client.ClientFaultConverter in phase user DEBUG - HandlerPipeline- Invoking phase pre-invoke DEBUG - HandlerPipeline- Invoking phase service DEBUG - HandlerPipeline- Invoking handler org.codehaus.xfire.client.ClientReceiveHandler in phase service ERROR - DefaultFaultHandler- Fault occurred! org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: The current event is not START_ELEMENT but 7 org.codehaus.xfire.fault.XFireFault: The current event is not START_ELEMENT but 7 at org.codehaus.xfire.fault.XFireFault.createFault(XF
Re: servicemix-bean, ServiceUnitAnalyzer
any news? On 5/24/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote: > > JIRA for the custom serviceUnitAnalyzer in jbi-maven-plugin: > > https://issues.apache.org/activemq/browse/SM-956 > > JIRA for the BeanServiceUnitAnalyzer for the servicemix-bean component: > > https://issues.apache.org/activemq/browse/SM-957 Thanks ! I'll take a look at these asap. Regarding the BeanServiceUnitAnalyzer, I only implemented it for endpoints > of type (I just thought this would be the most common > case). > I generated the consumes by looking at the fields with @ExchangeTarget > using > reflection. Yeah, I guess this is the most common use cases. Please take a look. > > > Eduardo Burgos > > > On 5/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > > On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote: > > > > > > No, I'm not thinking about removing the other way, it's just to have > > this > > > as > > > an option. > > > About the custom service analyzer, for example, lets say we have a > > > component > > > that is not supported by this team and we have no possibility to > access > > > it's > > > source code and I still need to build a service unit for it, currently > > > there > > > is no possibility for the jbi-maven-plugin to guess an analyzer for > it, > > so > > > I > > > thought that if we had the option to define the analyzer class at > > service > > > unit level it should do. > > > > > > Yeah, I was thinking about that too. > > > > Another example is what I need right now, I'm looking to develop a > > > servicemix-bean SU and I couldn't find a ServiceUnitAnalyzer for that > > > component. I couldn't have solved my problem in a standard way if I > > don't > > > have access to this mailing list :) > > > > > > Agreed > > > > I have it set in my servicemix source and its ready for a diff and JIRA. > > > Working on the BeanSUAnalyzer as we speak :) > > > > > > Cool, thx ! > > > > Eduardo Burgos > > > > > > On 5/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > > > > > > Sure, sounds good ! > > > > What kind of custom service analyser are thinking about ? > > > > Or is that for non servicemix components ? > > > > > > > > But I don't think we should remove the other way, which work > > > > well for servicemix components. > > > > > > > > Btw, such discussions about enhancing ServiceMix should really > > > > take place on the dev list, so please answer to the dev list > > > > if possible. > > > > > > > > On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote: > > > > > > > > > > There is something else I would like to suggest. > > > > > > > > > > Let's say I have a service-unit artifact and my target component > > does > > > > not > > > > > have a serviceUnitAnalyzer, I've seen the logic on the > > > jbi-maven-plugin > > > > > and > > > > > how it uses the serviceUnitAnalyzer and I noticed that it either > > uses > > > > that > > > > > jbi-services.xml file or looks up the target component for a > > > > > serviceUnitAnalyzer class name. > > > > > What if we also have a > > > > > > > > > > declared in that service-unit artifact (not the component) where I > > can > > > > > specify my desired serviceUnitAnalyzer for that SU. Example: > > > > > > > > > > > > > > myproject > > > > > jbi-service-unit > > > > > > > > > > > > > > > > > > > > org.apache.servicemix.tooling > > > > > jbi-maven-plugin > > > > > ${servicemix-version} > > > > > > > > > > > org.test.jbi.bean.BeanServiceUnitAnalyzer > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Notice that the is in the SU's > > > configuration > > > > > and > > > > > not the component, this way the desired serviceUnitAnalyzer is not > > > tied > > > > to > > > > > the component but to the plugin's configuration (And also keeping > > the > > > > > current approach). > > > > > > > > > > > > > > > Then in the > > > > > > > > > > > > > > > > > > > > org.apache.servicemix.maven.plugin.jbi.GenerateServiceUnitDescriptorMojoclass > > > > > add a String field called 'serviceUnitAnalyzerClass' and insert > this > > > > > where it finds the serviceUnitAnalyzer class: > > > > > > > > > > if (useServiceUnitAnalyzer.booleanValue()) { > > > > > +if (serviceUnitAnalyzerClass!= null) > > > > > +return serviceUnitAnalyzerClass; > > > > > MavenProject project = > > getComponentProject(); > > > > > > > > > > > > > > > Does this makes sense? > > > > > > > > > > > > > > > > > > > > Eduardo Burgos > > > > > > > > > > > > > > > On 5/22/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > Yeah, it's missing. > > > > > > Feel free to attach one to a JIRA :-) > > > > > > > > > > > > On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > Is there a ServiceUnitAnalyzer for this component? if not, can
[jira] Updated: (SM-952) ClassLoaderXmlPreprocessor not able to load shared libraries from xbean.xml
[ https://issues.apache.org/activemq/browse/SM-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ahornbeck updated SM-952: - Attachment: ClassLoaderXmlPreprocessor.java.patch It looks like Honi provieded the fix in his original post. Here is a patch using his file. The fix is 'libraryElement.getFirstChild())...' instead of 'locationElement.getFirstChild())...'. > ClassLoaderXmlPreprocessor not able to load shared libraries from xbean.xml > --- > > Key: SM-952 > URL: https://issues.apache.org/activemq/browse/SM-952 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-common >Affects Versions: 3.2 >Reporter: Honi Jain >Priority: Critical > Fix For: 3.2 > > Attachments: ClassLoaderXmlPreprocessor.java, > ClassLoaderXmlPreprocessor.java.patch > > > If we dont specify location child node but specify library child node of > parent node classpath in xbean.xml we are getting Null Pointer Exception when > we deploy our service assembly in servicemix. > getClassLoader method of ClassLoaderXmlPreprocessor parses the xbean.xml for > the tag 'classpath'. For loading shared-libraries it searches for the child > nodes with tag name 'library'. After it found all the child library nodes it > adds to the arraylist for the shared library using the child node list of > 'location'. This will give null pointer exception if no location node is > there. Even if location node is present when the code will try to look for > shared library it will give an error. > I am attaching the patch file ClassLoaderXmlPreprocessor .java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Possible bug in SU shared library loading
It looks like there's a bug in the block of code that loads the shared library tags in the ClassLoaderXmlPreprocessor class. The block of code I'm looking at starts on line 172 and appears to reference the collection for locations and not libraries: // Add shared libraries List sls = new ArrayList(); NodeList libraries = classpathElement.getElementsByTagName("library"); for (int i = 0; i < libraries.getLength(); i++) { Element locationElement = (Element) locations.item(i); String library = ((Text) locationElement.getFirstChild()).getData().trim(); sls.add(library); } if (sls.size() > 0 && container == null) { throw new IllegalStateException("Can not reference shared libraries if the component is not deployed in ServiceMix"); } -jeff -- View this message in context: http://www.nabble.com/Possible-bug-in-SU-shared-library-loading-tf3841041s12049.html#a10875885 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: Getting started guide
Eduardo, I have started working on it today, feel free to help out whenever/wherever you can... I have added it as Tutorial (in progress) on http://cwiki.apache.org/confluence/display/SM/Sandbox A lot of the information is already in the wiki, I just want to create a step-by-step tutorial to get people started off the right way. Instead of doing copy-paste, I would suggest to 'refactor' the pages and use {include} where appropriate (e.g. starting ServiceMix) Gert Eduardo de Vera wrote: Bravo! I was waiting for something like this to happen sooner or later. I would love to contribute on my spare time. 2007/5/29, Gert Vanthienen <[EMAIL PROTECTED]>: L.S., After having followed the user mailing list for a while, it seems that it's quite a steep learning curve to get started with ServiceMix. I would like to add a tutorial or getting started guide to the website, just guiding a new user through the existing documentation and trying to explain some key concepts on the way. Something like... # starting the container and connect to it using JMX # installing some components and deploying e.g. the wsdl-first example [to explain e.g. components, service assembly, service unit] # building a simple SA, e.g. re-using the 'File binding' page [to explain about the maven archetypes] # building e.g. the protocol bridge example to explain about message exchange patterns, routing, ... Would this be a worthwhile addition or are there other areas in the documentation that need work more urgently? Are there any other topics to include in this guided tour? Regards, Gert
I am puzzled
Hello,everyone. When I followed the step in the page of http://incubator.apache.org/servicemix/hello-world-se.html http://incubator.apache.org/servicemix/hello-world-se.html "End-to-End Testing 1,Save http://svn.apache.org/viewvc/incubator/servicemix/trunk/samples/bridge/client.html to your local desktop and then open it in your browser. 2,Set Target to http://localhost:8192/Service/ 3,Click Send " but I have not find the "Send" ,why? and the http://localhost:8192/Service/ got "HTTP ERROR: 404 Unable to find requested resource RequestURI=/Service/ Powered by Jetty:// " Anyone can help me ?Thanks and best regards. Jingguo -- View this message in context: http://www.nabble.com/I-am-puzzled-tf3838971s12049.html#a10869553 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: when will it finish?
On 5/30/07, xujingguo <[EMAIL PROTECTED]> wrote: Hello,Bruce. Thanks for your reply,I think I have got it. And I wonder if this is a typo in the bold? "Now that we have created the SU and SA projects, a top level pom.xml must be manually created and made aware of each subproject. This will allow all the projects to be built automatically without having to build each project in order manually. Maven will discover all the projects and build them in the proper order. In the hello-world-se directory, create a file named pom.xml containing the following content:..." in the web page of http://incubator.apache.org/servicemix/hello-world-se.html http://incubator.apache.org/servicemix/hello-world-se.html .I think it should be "hello-world-smx",right? Yes, that is correct. Thanks for pointing that out. I've made this fix to the website, too. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.apache.org/ Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Castor - http://castor.org/
Re: when will it finish?
Hello,Bruce. Thanks for your reply,I think I have got it. And I wonder if this is a typo in the bold? "Now that we have created the SU and SA projects, a top level pom.xml must be manually created and made aware of each subproject. This will allow all the projects to be built automatically without having to build each project in order manually. Maven will discover all the projects and build them in the proper order. In the hello-world-se directory, create a file named pom.xml containing the following content:..." in the web page of http://incubator.apache.org/servicemix/hello-world-se.html http://incubator.apache.org/servicemix/hello-world-se.html .I think it should be "hello-world-smx",right? Jingguo bsnyder wrote: > > On 5/28/07, xujingguo <[EMAIL PROTECTED]> wrote: >> >> Bruce. >> I have followed the steps in the tutorial.and the results are all >> right.But >> now how can I deploy the component in servicemix?Thank you a lot. > > This is the one section I haven't had the time to detail yet. You will > need to create a SU that depends upon (and is deployed to) the BC that > you created. You can do this by using the servicemix-service-unit > archetype and then customizing the xbean.xml to contain parameters for > your BC. This SU will then need to be wrapped in a SA and then > deployed to ServiceMix by dropping it into the deploy directory. > > Bruce > -- > perl -e 'print > unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E );' > > Apache Geronimo - http://geronimo.apache.org/ > Apache ActiveMQ - http://activemq.org/ > Apache ServiceMix - http://servicemix.org/ > Castor - http://castor.org/ > > -- View this message in context: http://www.nabble.com/when-will-it-finish--tf3827070s12049.html#a10868588 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.