Dear Bert,
It seems that you are registering both services using the same address... I
think you could check the properties that you are using while registering
the services. Each one should have its own address.
Best regards,
Fábio
On Tue, Feb 14, 2012 at 7:35 PM, jbert wrote:
> I have two
Hi,
Does anyone have more information about this?
Thank you very much!
Best regards,
Fábio
On Mon, Nov 28, 2011 at 1:10 PM, David Bosschaert <
david.bosscha...@gmail.com> wrote:
> Hi David,
>
> This is not expected behaviour. It sounds like a plain bug to me.
> Could you please file a JIRA?
>
Just to better explain, that code should be included in interceptors that
you would develop.
cheers,
Fábio
On Thu, Oct 27, 2011 at 12:38 PM, Fabio souza <
fabio.nogueira.so...@gmail.com> wrote:
> Hi Vassilis,
>
> You can put the start time directly in the exchange, li
Hi Vassilis,
You can put the start time directly in the exchange, like in this code:
Exchange ex = message.getExchange();
ex.put("START_TIME", System.nanoTime());
Now you can read the exchange in the out chain:
Exchange ex = message.getExchange();
Long start = ex.get("START_TIME");
Regarding t
r other things you need.
>
> Dan
>
>
>
> On Thursday, June 02, 2011 9:20:20 AM Fabio souza wrote:
> > Hi,
> >
> > I'd like to be able to dynamically monitoring different aspects related
> to
> > web services (e.g. response time, processing time, availa
Hi,
I'd like to be able to dynamically monitoring different aspects related to
web services (e.g. response time, processing time, availability, etc). I
would like that the set of possible monitoring aspects was an open end. I
mean, I would like to be able to start monitoring something that wasn't
String portName =
> message.getExchange().getBinding().getBindingInfo().getService().getInterface().getName().toString();
>...
>}
>..
> }
>
> Regards
> Xilai Dai
>
> -Original Message-
> From: Fabio souza [mailto:fabio.nogueira.so...@gmail.com]
>
Hi,
I am using cxf to build WS solutions and I'd like to log requests and
responses. I saw logging interceptors and I was trying to build something
similar. However, I would like to include the name of the service interface
(java) in the log output. I saw that there are several data that are
inclu
Ok, Willen,
Thank you again for your promptness!
Best regards,
Fabio
On Mon, Feb 14, 2011 at 8:53 AM, Willem Jiang wrote:
> On 2/14/11 11:48 AM, Fabio souza wrote:
>
>> Hi Willen,
>>
>> First of all, thank you very much for your answer! Let me try to be more
>> e
;
>
> On 2/12/11 9:36 PM, Fabio souza wrote:
>
>> Hi,
>>
>> I'm building some monitoring interceptors to evaluate my Web Services, so
>> I'd like to "mark" some messages on the client-side using an Id and
>> recover
>> that Id on the serv
Hi,
I'm building some monitoring interceptors to evaluate my Web Services, so
I'd like to "mark" some messages on the client-side using an Id and recover
that Id on the server-side in order to build a correlation. How can I send
contextual informal (like that Id) from the client to the server side
sumer.intents' is just a proposal, other names would be
> possible too, oh and while it's not part of the standard yet we should
> really prefix is with org.apache.cxf to make that clear...
>
> Just a thought,
>
> David
>
> On 18 October 2010 21:21, Fabio souza
> wrot
Hi Vincent,
Nice hearing that you are interested in this topic.
Well, let's discuss a little bit about intents and configs. First of all, I
think you are right. I mean, as far as I know, intents are, as you said, a
vendor-agnostic way to configure how a service should be exported. The
concept of
Ok, David, I will do that. Thank you very much for the discussion, anyway.
In fact, I am very interested in the idea of intents, so I will try to get
involved in the discussions related to this topic and in implementation if
necessary.
Cheers,
Fábio
On Fri, Oct 29, 2010 at 7:41 AM, David Bosscha
Hi Robert,
Yes, it is correct. In fact there is a front end named Simple. That's the
point. So, this sentence is mentioning the front ends that are supported by
CXF.
Cheers,
Fábio
On Mon, Oct 25, 2010 at 10:10 AM, Robert Liguori wrote:
> I'm a little confused on the terminology and context use
so it
> overrides the default.
>
> Does this answer your question?
>
> Cheers,
>
> David
>
> On 27 October 2010 15:53, Fabio souza
> wrote:
> > Hi everybody,
> >
> > I have a doubt corcerning the mecanism to include intents in CXF/DOSGi
> > i
ualify logging as optional
> by adopting a convention like calling the intent optional:logging
> instead of just logging.
> * another option would be to introduce new properties to hold optional
> intents...
>
> Do you have any other concrete use-cases beyond logging? They might
>
Hi Anne,
I am also very interested in this topic. Just like you, I am
researching this area from an academical point of view. My focus is on
QoS based dynamic service composition. The idea is to propose a
solution that supports some kind of QoS negotiation and partner
selection based on QoS parame
er.intents.extra just like this is done on the
> exporter side.
>
> 'service.consumer.intents' is just a proposal, other names would be
> possible too, oh and while it's not part of the standard yet we should
> really prefix is with org.apache.cxf to make that clear..
oesn't contain any 'exported'
> properties. However you should see some *.imported properties there...
>
> Hope this helps,
>
> David
>
> [1] Table 13.1 in the OSGI 4.2 Enterprise Specification
> http://www.osgi.org/Download/Release4V42
> [2]
> htt
Hi,
Looking at DOSGi's intents implementation I found something that seems
a little bit strange to me... To apply an intent during proxy
creation, the method createProxy in class PojoConfigurationTypeHandler
calls method applyIntents, right? Ok, but, this method calls
getRequestedIntents to recove
> >
>> > We've discussed this issue few months ago and the idea of templated
>> intents
>> > was mentioned.
>> > That said I do believe we should be open to supporting extensions, ex,
>> > supporting existing CXF constructs for configuring stuff lik
Hi Peter,
Are you planning to create a new intent or just use an existing one?
Well, if you just want to use an existing intent, it is as simple as
setting up some service's properties... Here is the intent-map.xml
that comes with DOSGi:
http://www.springframework.org/schema/beans";
xmlns:
> the source code and see if you can come up with an improvement that
> would make it more extensible?
>
> Cheers,
>
> David
>
> On 21 September 2010 22:33, Fabio souza
> wrote:
>> Hi everybody,
>>
>> I created a cxf feature that acts like a timer and
Hi everybody,
I created a cxf feature that acts like a timer and I'd like to use it
while accessing some dosgi services.
The idea was to setup an extra intent (using
"service.exported.intents.extra" property) while registering a new
service. However, as far as I could understand, in order to that
25 matches
Mail list logo