hmm is this a good place to point out errors in tutorials ?

yeah, it's fine, or just send a mail to the user mailing list

just as new "items" for each one I find ? (I have been granted time to do some research so might as well look for small mistakes)

sure, whatever, any contribution is welcome -- proof-reading the tutorials is very much appreciated for that matter ;)

ok will do ;)

Ok here is the first one: At the subscribe for the mailing list page there is like no information about what to put in the mail body / subject to get subscribed

cvdstap: not sure you need to put something in there actually

cvdstap: btw, if you file an iCLA, we can also grant you edit rights on the wiki -- so you can fix things yourself

that also true for things like: http://servicemix.apache.org/what-is-a-jbi-sa-and-how-do-i-create-one.html

first let me get this mail list thing ~_~. which one to send to is kinda puzzling atm

just send to: users@servicemix.apache.org ?

ok that was fast ;)

gertv: Did you get my 2 mails with patches from yesterday?

gaginn: looks like I didn't

ok, I send it again

gertv: I send it on your another mail, which I have.

gaginn: could you do an svn up first and recreate the patch then?

gaginn: the one for servicemix-audit-jcr

ok

gaginn: are you perhaps using tabs for indentation?

gaginn: if so, could you try to use spaces instead?

indentation? where?

indentation in your code

if you are using Eclipse, you can configure it to use spaces instead of tabs when formatting code

servicemix-sling-console has been patched

thx for the patch once again

yes I used Eclipse, but I never have problem with it, even I use Linux. Why is it problem?

I will reconfigure my Eclipse.

gertv: I create new profile for Eclipse, which use only spaces instead tabs, ok?

Now I must reformating my code.

ok, I'm getting promoted to babysitter-in-chief in a few moments

but I'll apply the new patch this afternoon

ok

Is it possible for one exchange to bounce between components more than once before a done status is set ?

gaginn: just applied your second patch, thx once again

cvdstap: depends on what you mean by 'bounce'

a single exchange can go through the nmr multiple times

it depends on the MEP used -- have a look at https://open-esb.dev.java.net/public/pdf/JBI-Components-Theory.pdf for a diagram/explanation on the 4 JBI MEPs

gertv, i did, but that specifies "make an exchange" -> send it of -> do something -> send it back -> done (or variants there of). My bounce is more like "create" -> (send to provider -> do something with exhcange on provider -> send back to consumer -> do something with exchange on consumer)* -> done

cvdstap: if you look at the diagram for InOut MEP, it's the consumer that receives the reponse in an ACTIVE exchange and sends back the DONE to the producer

cvdstap: in the diagram, you could implement the (do something with exchange on consumer) between steps 4 and 5, no?

gertv, looks like there is only one request / response possible for each exchange ?

yes, there is

you can't have something like one request sending back multiple responses if that's what you mean

ok then i understand.

you can aggregate multiple (EIP Aggregator or Camel) reponses into a single one though and send that back

gnodet: Hi Guillaume. Can u give me a hint here: http://rafb.net/p/jexeUr95.html

lhein: gertv has been moving some classes around, so things may be a bit messy right now (for 3.3 and components)

ah, just wondered

interesting... does servicemix need org/apache/commons/lang/StringUtils on the classpath to run the archetypes ? or did i miss a step in installing servicemix ?

ok according to jira this is something with velocity ~_~

maven dependencies seem to be broken

Anyone arounds that can shed some light on where the xbean 3.3-SNAPSHOT is needed ? In servicemix 3.2.2 pom file it says that the version should be 3.4.3. At the moment i am puzzled

gertv, do you know why i have a dependency to xbean 3.3-SNAPSHOT while in the servicemix pom the xbean version is set to 3.4.3 ?

servicemix version is 3.2.2

cvdstap: try running mvn dependency:tree -Dverbose=true to check it out

but I'm guessing Maven is losing track in the xbean version because we have a wrong dependency in the 3.2.2 release

it has been excluded for 3.2.3 - so it's fixed there, once it gets released

that seems to fit the other nabble / forum posts i have found

and 3.2.3-SNAPSHOT that i culd try ?

any*

could*

those are available from http://people.apache.org/repo/m2-snapshot-repository/org/apache/servicemix/.../

but if you have 2', I'll try to fix up the metadata -- I have an idea where things might go wrong now

cvdstap: could you try to remove the org/apache/xbean directory from local maven repository and re-running the build?

will try

thx

So far its running

but since i deleted my entire repo just before you returned, it is taking a while :)

yeah, I know the feeling, Maven is downloading the entire internet now...

[WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for org/apache/xbean/xbean-kernel/3.3-SNAPSHOT/xbean-kernel-3.3-SNAPSHOT.pom - IGNORING

same for -spring and -classloader

that's ok -- we have frozen a SNAPSHOT in our own Maven repo

but there are no checksum files there, it's just a workaround to keep people's build running until 3.2.3 gets out

i see

maven is the best and worst at the same time. Its a nice way to manage lots of things, but "Ohoh" when something goes wrong in the external dependencies / repositories

+1 on that -- Maven's a great tool 99% of the time, but you'd throw it out of the window for the remaining 1%

also most time spent seems to be in that 1% :)

gertv, it passed the build now

cvdstap: thx

gmm seems that for some reason port 1099 is in use ~_~

ok 1099 is in use with some ati utility :/

you can always change the port smx uses by editing conf/servicemix.properties

\o/ got the filepoller example working

gertv, is it worth to mention the problem with geronimo in the tutorials or will that sort itself ?

i mean velocity ~_~

cvdstap: what problem with velocity is this?

the one that it has a wrong dependency and a wrong group id ?

sorry - I'm still in the dark here

need to get myself another coffee

gnodet: ping

gertv: pong

gnodet: trying to get the new servicemix-utils into smx4

gnodet: but now I all of a sudden need servicemix-core from smx3 container when deploying the bridge-sa sample

gertv, this is about the velocity problem http://jira.codehaus.org/browse/ARCHETYPE-181

gertv: wrong osgi imports ?

well, the strange thing is : the jar was never there to begin with

and it doesn't have any osgi metadata yet either

so I guess it hasn't been necessary before -- I just failed to see why

can you start servicemix-utils bundle in smx4 ?

SAs don't really use OSGi classloaders as the classloaders are built by the JBI layer using components and shared libraries

sure, that one works fine

what is the error exactly ?

java.lang.NoClassDefFoundError: org/apache/servicemix/jbi/FaultException

did you remove servicemix-core from servicemix-shared SL ?

that would be the reason

servicemix-jms-provider-service-unit archetype is broken? maven bables about not being able to find the release version

gnodet: looks like something went wrong the servicemix-shared build -- the JAR file empty (only manifest and the maven files there)

gnodet: isn't the SL installed with a feature now?

oh, you're right, we don't use the JBI packaging anymore for that one

which means servicemix-core won't be available (which is somewhat what we want to achieve)

yeah, that one shouldn't be in SMX4 anyway

gnodet: so I just continue moving shared classes to servicemix-utils then to get -core out of SMX4?

yeah, i suppose so. do you know where the FaultException is referenced ?

looks to be the eip-su

checking now...

yep, it's in Pipeline

fail(exchange, new FaultException(fault, null, null));

and BeanSupport has it too

cvdstap: are you sure you haven't made a typo in a name somewhere

gertv, i couldhave ...

copy pasted again, same problem

could you post the error message to the user list?

http://pastebin.com/d31308241

ah i could do that as well yes

can you try specifying the version?

-DarchetypeVersion=3.2.2

that seems to fix it yes

not sure why -- file in public repo does have the correct version specified (http://repo1.maven.org/maven2/org/apache/servicemix/.../maven-metadata.xml)

could be that my environment hits the wrong repo ?

who knows -- it might be the 1% scenario ;)

to true

but dang this one harsh tutorial to get through

gnodet: is it worth even trying to move things about to avoid split-packaging in OSGi bundles?

gertv: you mean using a subpackage instead of org.apache.servicemix ?

gnodet: yeah, just to avoid having an OSGi export for org.apache.servicemix everywhere

but I guess I need to keep the class in its old package too for backward compatibility in SMX 3

yes

e.g. if I move the FaultException to org.apache.servicemix.jbi.exception I can avoid the split package

but I need to keep the FaultException in servicemix-core as well then (just mark it deprecated)

cvdstap: you seem to be running into a lot of issues indeed

gertv: sounds good

cvdstap: most of them maven and/or dependency related stuff, but still, this is not the kind of first-time experience we want to offer ;)

gnodet: and what about the MessageExchangeListener I mentioned in SM-1455?

gnodet: that one needs to be moved out too to get rid of servicemix-core

who uses the MessageExchangeListener ?

servicemix-bean uses it

and lightweight components mostly

gertv, indeed, have not encountered anything wrong with servicemix yet, mostly maven and deps and some typos on my end ^^;

gnodet: that's about it, I guess

gertv: can't we move the FaultException to servicemix-common and use that one instead ?

and for the MessageExchangeListener, we can define our own interface inside servicemix-bean

not sure what the best approach is: either cleaning the code and make components more independant, or put everything in the utils module

well, if we are going to have two copies of the same thing (like with the FaultException), I'd move it to servicemix-utils

and just make the servicemix-core one extend the utils one -- marking it deprecated

yeah

ok, thx for the advice

gnodet: btw, if you have a moment to spare, could you review the async stuff I did for servicemix-drools?

sure

gnodet: the unit tests work, but just to make sure I haven't missed an odd case for some MEP somewhere

gnodet: every component seems to use MessageExchangeListener through the AsyncBaseLifecyle class

gnodet: same solution as for the FaultException?

the MessageExchangeListener is used only from the SyncLifecycleWrapper now

which is create only if the MessageExchangeListener class is available

see DefaultComponent#getLifecycle

so that it works in both smx3 (when the class is available) and other containers

so in short, we could move it to servicemix-utils, but only smx3 would really use it

gnodet: and we are not going to port e.g. servicemix-audit over to SMX4 in its current form?

gnodet: we will be doing something more flashy there -- like the interceptor stuff we've been talking about?

the auditor does not use the MessageExchangeListener afaik

it uses the org.apache.servicemix.jbi.event package

yeah, sorry 'bout that -- my mistake

but we still have the problem for servicemix-bean (which could also be solved by using the ExchangeProcessor interface)

actually, the ExchangeProcessor interface could be trimmed down by removing the start() / stop() method which are not used afaik

well, that's not completely true, the start / stop method are used from the SoapEndpoint

gnodet: sorry, but I have to go now

gnodet: let's look at it tonight or tomorrow

sure

bye

tomorrow there is another day, bye all

Could someone please apply the patch at https://issues.apache.org/activemq/browse/SMX4-89 for me? The features project build is currently failing to generate an assembly.

jstrachan: Mind kicking off the bundles build (here http://projects.open.iona.com/builds)? I need latest wss4j bundle for the features project build.

will do

http://projects.open.iona.com/builds/status

building

jstrachan: thanks!

anyone expert within smx ?

what protocol would be the best to communicate a web application with consumers on the same application server?

what protocol would be the best to communicate a web application with consumers on the same application server?

vm/seda transport is fine or you could use jms/activemq if you want persistence/reliability

I was thinking about VM transport actually

thanks

:)

is there a SE ready for that ?

you could use the camel se and then easily switch from seda <-> activemq if you like

gnodet: ping

gertv: pong

gnodet: do you see any problem if I move JavaSource, JbiConstants and MessageExchangeListener to servicemix-utils but leave them in the same package?

since servicemix-core isn't becoming a bundle anyway, the split package remark doesn't count there

well, JbiConstants has been copied in servicemix-common and JavaSource is not really used anywhere afaik

for JbiConstants, we could remove the duplicate from servicemix-common

and JavaSource is used in MessageHelper, which is referenced from the servicemix-bean component

yeah, but i'm not sure about using the org.apache.servicemix package

i've tried to avoid that

well, I have managed to get servicemix-bean to build without using smx3

but the tests fail if I run them with smx 3.2.1 because I moved the MessageExchangeListener to another package

and the MessageExchangeListener interface is used from within the container itself to do the exchange handling through the listener

yeah, the MessageExchangeListener interface can't really be moved anywhere

not sure how that works for other containers -- is it the syncbaselifecyclewrapper thing you showed me before?

we could replace its use in servicemix-bean though

just toss it out and implement something specific for servicemix-bean

this is an optional interface and it is included in the servicemix-shared SL

to get the same behavior?

yeah

now, with the SyncLifeCycleWrapper, if the interface is not in the classloader, it won't be used

so I shouldn't even be putting it in servicemix-utils or it would be available from the SL

breaking compatibility with other containers

right?

everything else is fairly simple stuff to move about -- helper classes like MessageTransformer and the like

anyway, I'll be calling it a day now -- thx again for the help, I'll get this done on Friday

once this is done, we should start releasing utils and the components to get 3.3 out at apache

are we going to do a 3.2.3 release to ease our users' pain with the maven dependencies?

could be a good idea

it is still a problem with the stuff you did ?

i mean putting the snapshot in smx repo ?

well, i guess users have to add the repo at least ...

the good thing is that it is in the archetypes

so many of them already had it

changed the parent on those poms to 3.3 today (instead of 3.3-SNAPSHOT)

to avoid the SNAPSHOT version to propagate all over the place

seems to have solved most issues

if we have no more complaints about it, we might as well focus on getting 3.3 out (for the split components)

and 4.0 off course

yeah

ok, have a nice evening

see you tomorrow