Feel free to let me know when this is scheduled and I will try and
attend.
Terry
Interesting.
We need to have a very serious chat about application lifecycles and
governance...
Terry
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
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
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
I've been going over the servicemix-bean docs and as they are written at the
moment, they seem to imply that most of the clever functionality can only be
used in a static configuration. Is this actually the case or just an artifact of
the way the documentation is structured?
--
Terry
I'm going to write some tests to see how well things interoperate within the
types of deployment scenarios I would expect to deal with on a large project. I
think there is scope for some streamlining in the way projects can be developed
and deployed quickly.
--
Terry Cox
Meta-Concepts Ltd
about changing the code, nor the jar, just to do a
bit more advertising
on the the web site about it ...
--
Terry Cox
Meta-Concepts Ltd
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.
--
Terry
Hi,
Can someone fix the continuum reporting config as well as the build,
please? It seems to be spitting out multiple copies of the error mails
and flooding the list.
--
Terry Cox
Meta-Concepts Ltd
change,
so it is still using the original copy. You may have to stop continuum
and manually clean its build folder first to see if the problem is there
or in svn.
Cheers,
--
Terry Cox
Meta-Concepts Ltd
0788 1920512
The problem seems due to a failure in the merge/switch. The error
message is a bit obtuse, but seems to relate to switching to/from a
folder which doesn't exist.
It might be worth trying to back out those changes and apply them
individually to see which breaks?
--
Terry Cox
Meta-Concepts Ltd
Any ideas on how to do that ?
You need more than one way to get to information as people will use
different strategies to find out about a new technology. I personally
like to know at a glance the scope of a project, so I preferred the
original approach (and the one taken on the ActiveMQ
Well, I'm not sure how to solve the problem in the xbean build.
Just a question, but does XBean need to evolve with backward
compatability to multiple Spring versions in the trunk, or should it
fork to a new release path that is maintained in parallel with the
associated Spring release?
--
Good idea, I think we should do a 3.0 of xbean and
throwing away the spring 1.x support
Let me know if you need a hand with anything.
--
Terry
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
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 contains
This little error is causing me some fun:
org.springframework.core.ConstantException: Field 'ISOLATION_' not found
in class [org.springframework.transaction.TransactionDefinition]
To explain, I am trying to use a POJO in a lightweight container and that
POJO requires some injected dependencies
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]
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
'd like to start a thread about where JBI components that
are contributed by users should be hosted.
I think that, like most other applications that have plugins, we should
cover all three bases. Components maintained by the core team should be
hosted locally. An open repository should exist
To operate effectively at an enterprise level, ServiceMix needs robust,
predictable resilience and redundancy facilities. ServiceMix relies upon
ActiveMQ to deliver this, however it is becoming clear from the number
of outstanding JIRA issues on ActiveMQ 4.0.2 that it is not able to
deliver on
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
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
Oh i don't care about my suggestion really, just trying to get us to
think outside the box.
Well, here are a few that spring to mind to get the creative process
rolling:
InTheMix
MixCentral
MixDepot
MixCore
BeyondServiceMix
MixBase
Terry
Take it from me, most big corporate clients spend much more effort
worrying about whether they like the name of the project than on
evaluating the quality of the technology it contains.
If they can't pronounce it or spell it, they won't use it. :)
Terry
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
However it seems to make for more brittle builds since the builds
are depending on external resources being available and downlaoded.
Using your own site repository helps in this respect, as does working
against release versions of libraries rather than snapshots.
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
I have just built ServiceMix from HEAD
I had just synchronised with HEAD. I've checked that I am up to date and
have done another clean build of ServiceMix, but I still get the same
error when I run jbi:servicemix.
Terry
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)
Do you have an example, I'm not sure to understand.
Are you talking about a SU that depends on another SU ?
Well, elements in a SU can have dependencies on both component libraries
and normal java libraries. SAs may contain SUs that have dependencies
upon different versions of these
+1 for going away from lw-container when possible.
I think both archetypes and ready to run examples are necessary.
Agreed. You need to understand the patterns before you can choose an
archetype to apply.
Terry
I would recommend more worked examples in the documentation and
strictly, the worked examples should be used as QA tests for snapshots
so that the examples are provably in sync with the releases.
If you look at the forum, nobody could build consistently until a web
page was put up documenting
When parsing schemas for flattening a WSDL definition, the schemas
are loaded with the baseUri set to null.
This same problem occurs when using the Validation component to validate
against a schema with imports. Hopefully this can be fixed in the same way?
Terry
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
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]
38 matches
Mail list logo
