Interesting.
We need to have a very serious chat about application lifecycles and
governance...
Terry
This solution is intended for the provider site not for the consumer
site. So what I mean is to limit the outgoing connections from
servicemix (for example to an external web service) over the provider
endpoint with the thread limit. It doesn't depend on the consumer
site.
Do you know what I mea
So if you let the thread pool define the mnumber of connections you
wouldn't get a hang and would not lose any messages. Am I right?
Not necessarily. What you are doing in that situation is directly
coupling the number of internal threads with the number of external
connections, leaving the ma
So what if we put both limits to a very high number in the default
configuration ? Is there any drawbacks?
The risk there is that you are just increasing the size of the bang when
it goes wrong. The system must degrade gracefully under heavy load in a
production environment. If it has operatin
If we go that way, how could we deal with the examples ?
I guess they would either require the use to download the components,
or be available on a separate distros (and thus have their own
release cycle too).
Ideally needs a Maven-like dependency management system for components
so that you c
I think it would certainly help to drill out some of the general
component lifecycle management issues.
--
Terry
I think it's a good plan to have a continuous build system on the
snapshot versions of each branch, but somebody on the team needs access
to resolve issues like this and we should make sure that the
notification system is configured to generate a smaller volume of
warning messages.
--
> Well evidently XBean 2.8 depends on Spring 1.2.4 which I don't
> understand. I seem to recall that XBean used Spring 2.x so I'm
> rather
> perplexed as to why a dep on Spring 1.2.4 is defined in the POM. I'm
> sure Guillaume can shed some light on it, so let's wait for his
> response.
XBean con
> Terry, what is the $xbean.version is used in the pom.xml?
2.8
My code is built against the 3.1 release of ServiceMix.
As an experiment, I just deleted all the 1.2.x versions of Spring from my
repository and built ServiceMix 3.1 from source. Spring versions 1.2.4
and 1.2.6 both re-appeared in t
> why is there a spring 1.2.4 version in the classpath ?
> You need to remove it somehow.
It appears to be coming in via the maven-xbean-plugin, which seems to
import xbean-spring. I have tried over-riding the dependency on xbean
spring in the plugin reference and excluding Spring, but that doesnt
That fixed it. One day, compiler technology will evolve far enough to
reliably handle dependency management for large projects...
:)
Terry
Just synchronised with HEAD and ran the build, but it is failing at
ServiceMix :: Samples :: WSDL first :: SA
[INFO] Determining component name for service unit wsdl-first-jsr181-su
[INFO]
[ERROR] FATAL ERROR
[INFO]
--
Downloading:
http://www.ibiblio.org/maven2/org/apache/geronimo/specs/geronimo-qname_1.1_spec/1.0.1/geronimo-qname_1.1_spec-1.0.1.test
[WARNING] Unable to get resource from repository central
I can confirm this. Looks like something in the tooling as it is
breaking my application build.
Terry
if we call it servicemix-cxf or servicemix-xfire - that still isn't
very descriptive of what it does :)
I've read the documentation several times and I *still* don't know what
it does. :)
Terry
It seems most of the docs could be moved to the User's Guide,
so maybe the User's Guide is not worth it.
Opinions ?
Perhaps the User's Guide should focus on walking through some end to end
examples in detail with explanations? If it is done correctly, it should
also form a QA document for exa
Interesting. 'sm' words in English often have negative or derogative
connotations:
Smut
Smack
Smug
Small
Smarm
Smash
Smatter
Smear
Smeg
Smell
Smirch
Smit
Smite
Smithereens
Smog
Smother
Smudge
I would advise against 'sm' words for that reason.
Other thoughts:
intermixable.org
overmix.org
mixibl
ServiceMixins
Bit cheesy from a professional 'business technology' point of view.
Terry
Encouraging new developers to work within maven is probably a good thing
as dependency management is a big part of the JBI world. Maven enforces
good practices with respect to that and hopefully the examples will
provide a cleaner path into a workable build environment.
We initially experience
If you put commons-pool as a dependency of your project, the
jbi:embeddedServicemix goal will put it in the classpath.
I tried that, but it didn't make any difference. (against HEAD from
yesterday afternoon)
Terry
When starting a ServiceMix instance, it makes sense to me to put the
ActiveMQ-related config in the top level servicemix.xml and then put JMS
component-related stuff in Service Units that can be deployed in the
container.
Only trouble is, creating a connection pool depends on commons-pool
whi
Just synchronised and performed a step1, step2 build but it seems to be
failing on the bridge samples stuff:
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.servicemix.sampl
I've just seen a problem though.
Far from me to say "I told you so" but...
This is causing us some problems too. It also raises the issue of the
build resolving or flagging dependency issues within SUs, which is
likely to become a problem in the lifecycle of richly featured
applications usi
To add my bit to this idea. I am discovering that in order to develop
components, you end up with lots of dependencies back into the
ServiceMix project, most especially if you wish to be able to run unit
tests that instantiate a container in order to test components. This in
turn means that the
> Refactored the projectDeploy goal so that is can determine whether
> dependencies are already deployed and if so it will stop and undeploy
> them before redeploying
This seems to have broken the jbi:projectDeploy task here. I now get:
[ERROR] BUILD ERROR
[INFO] -
The question here is should the test component installer jbi.xml
files have the bootstrap-class-path element added as an empty
> element () ?
The specification is not that helpful here:
"The JBI implementation MUST create an InstallationContext object,
initialized to provide the following dat
25 matches
Mail list logo
