Hi Richard,
Apologies for the delay in replying. Please see my comments in-line.
2009/6/15 Richard Opalka :
> what's the current state of CXF WS-RM?
See below.
> I'm asking because we'd like to integrate probably
> WS-RM in our JBossWS CXF integration.
Great that you're thinking of using CXF
Hi,
I'm seeing problems with the JAXRS AegisElementProvider producing/consuming
complex types like Maps.
I'm nearly done with making a basic end to end JAX-RS demo working n DOSGi, the
immediate problem is that
a client proxy fails to consume the following somewhat complicated
Aegis-produced re
The 'any' in the map means that somehow Aegis is not finding type
information for the map element type. If you set up some sort of test case
and check it in with @Ignore, and make a JIRA, and assign it to me :-) I can
probably fix it.
On Wed, Jun 17, 2009 at 8:19 AM, Sergey Beryozkin wrote:
> Hi,
For the purpose of the demo I introduced a wrapper around the Map and it works nicely, but I'd appreciate
any help in getting to the bottom of the problem I described below.
thanks, Sergey
- Original Message -
From: "Sergey Beryozkin"
To:
Sent: Wednesday, June 17, 2009 1:19 PM
Subje
Like I said. Given my current level of load, if you tee it up, I'll try to
knock it down. But I need something that misbehaves. I'm sorry to have to
ask for that silver platter.
On Wed, Jun 17, 2009 at 8:43 AM, Sergey Beryozkin wrote:
> For the purpose of the demo I introduced a wrapper around th
Hi Benson - I just sent a followup email at the same time you replied :-), I'll
create a JIRA shortly,
thanks, Sergey
- Original Message -
From: "Benson Margulies"
To:
Sent: Wednesday, June 17, 2009 2:10 PM
Subject: Re: JAXRS : issues with AegisProvider
Like I said. Given my curr
I created two JIRAs - please have a look at them whenever you get a chance -
they don't block me at the moment
https://issues.apache.org/jira/browse/CXF-2296
https://issues.apache.org/jira/browse/CXF-2297
thanks, Sergey
- Original Message -
From: "Sergey Beryozkin"
To:
Sent: Wedn
On Mon June 15 2009 10:15:54 pm Pradeep Fernando wrote:
> we are using CXF code engine to generate artifacts. CXF currently supports
> JAX-WS compatibility, one of our main requirements.
> Other than that in databinding perspective it supports ,
>
> JAXB- primary requirement
> XMLBeans
> aegis
On Tue June 16 2009 10:12:54 pm liucong wrote:
> Hi,
> I have added a simple interceptor in the SOAP binding. If the
> transport uri is http://www.w3.org/2008/07/soap/bindings/JMS/, the jms
> interceptor will be added. But I have some question for that:
> 1. I feel a little weird to add a t
Since that error message is coming back in the Fault, that is something on the
server side. Thus, we'd need to see the logs for the server side.
I've never seen that error before either. Bizarre.
Dan
On Tue June 16 2009 5:12:17 pm rajla wrote:
> Hello, I am getting the exception
> "javax.
Log a JIRA with a patch? :-)
Dan
On Tue June 16 2009 1:05:01 pm Jim Hansen wrote:
> I did some debugging and discovered that the RECV_RESULTS are not found in
> the right place. My fix (probably not the best fix) is to override
> getProperty() on the WSS4JOutInterceptor class as follows:
>
>
>
Hey Dan, the problem must be something with Spring 3.0+ and CXF
compatibility. That is all I can think of What sort of server logs?
All the server really does is throw the exception I posted below after it
chokes and pukes. Other than that I don't see anything else in stdout.
Thanks
dku
On Wed June 17 2009 3:21:58 pm rajla wrote:
> Hey Dan, the problem must be something with Spring 3.0+ and CXF
> compatibility.
Interesting. I haven't tried anything with Spring 3.0 yet.
> That is all I can think of What sort of server logs?
> All the server really does is throw the exce
Actually, that error message seems to come from an OLD Axis SAAJ
implementation. Definitely check the server side parts for any leftover Axis
SAAJ things and replace them with a modern implementation. (Sun's SAAJ is what
we test with)
Dan
On Wed June 17 2009 3:21:58 pm rajla wrote:
> Hey D
2009/6/16 Daniel Kulp :
>
> Just a reminder that July 13th (the date when Mid-term evaluations are due) is
> now less than a month away. We definitely should start seeing some visible
> progress sometime soon. More importantly, for mid-terms, we should be seeing
> more interaction with the comm
Sergey,
I have a pretty good idea of the nature of the problem.
When Aegis is run with good-old-soap, various types from the SEI are pushed
into its view to start the process. We're not doing anything like this for
JAX-RS yet, I bet.
--benson
On Wed, Jun 17, 2009 at 9:42 AM, Sergey Beryozkin w
Sergey,
My memory of how all this is supposed to work isn't good enough.
In your failing test case, the problem starts with ...
WARNING: xsi:type="{http://fortest.jaxrs.cxf.apache.org}AegisTestBean"; was
specified, but no corresponding Type was registered; no default.
For this to work, somehow
On Wed June 17 2009 7:20:09 pm Krzysztof Wilkos wrote:
> I've got some busy days at university (exams etc.) but I'm close to
> get session initialization working. I should finish this before the
> end of this week. To initiate a session I have to call service method
> so there is short way from ses
Sorry Dan, sometimes I am a a really loser.you are 100% right, the guilty
party was old AXIS stuff server side. After that, I pushed the SAAJ stuff
into the stupid endorsed directory (who came up with that brilliant idea
anyway it is like the JBoss windows registry ha ha ha).
anyway,
Hi,
Forward this mail to the dev mail list.
liucong wrote:
> Hi,
> I have added a simple interceptor in the SOAP binding. If the
> transport uri is http://www.w3.org/2008/07/soap/bindings/JMS/, the jms
> interceptor will be added. But I have some question for that:
> 1. I feel a little wei
Hi Eoghan,
see in lined comments below:
Richard
Eoghan Glynn wrote:
Hi Richard,
Apologies for the delay in replying.
NP
Please see my comments in-line.
2009/6/15 Richard Opalka :
what's the current state of CXF WS-RM?
See below.
I'm asking because we'd like to integrate
21 matches
Mail list logo
