tion and remove
aforementioned ugly hack?
JBossWS Team
PS: We're looking forward for your suggestions ;)
--
B.Sc. Richard Opalka
Senior Software Engineer
JBoss, a division of Red Hat
Mobile: +420 731 186 942
Mail: ropa...@redhat.com
you have feedback, questions or would like to get involved in the CXF
project please join the mailing lists and let us know your thoughts.
The Apache CXF Team
http://cxf.apache.org/
--
Richard Opalka
JBoss Software Engineer
Mail: ropa...@redhat.com
Mobile: +420 731 186 942
to any calls.
Or, we could look for a property someplace for the name of the "ServiceImpl"
class to instantiate. If set, use reflection to create the ServiceImpl thing
if set.
Anyway, those are my immediate thoughts.
Dan
On Mon May 25 2009 9:21:35 am Richard Opalka wrote:
CXF and put it into
the JaxWsProxyFactoryBean/ClientProxyFactoryBean.create() call. That way,
if they end up using the spring "jaxws:client" call or use the factories
directly themselves, the listeners would be invoked as well.
Dan
On Wed June 3 2009 2:11:22 am Richard Opalka wrote:
ring "jaxws:client" call or use the
factories
directly themselves, the listeners would be invoked as well.
Dan
On Wed June 3 2009 2:11:22 am Richard Opalka wrote:
Hi Daniel,
Yes, I know about solution 1) you suggested. However I don't like
it.
It's hacky and could caus
Hi CXF Team,
what's the current CXF roadmap from WS-* point of view?
What specs are you going to work on next and what is the schedule for them?
The roadmap as defined here:
http://cxf.apache.org/roadmap.html
just specifies "Other WS-* stuff"
Richard
--
Richard Opalka
Hi Eoghan,
I'm interested mainly in WS-Trust and WS-Management now ;)
Richard
Eoghan Glynn wrote:
One thing I've had at the back of my mind is WS-RM 1.1 support.
Is that something that would be of interest to you?
Cheers,
Eoghan
2009/6/12 Richard Opalka :
Hi CXF Team,
dd, please add it to the list.
Dan
On Fri June 12 2009 9:50:29 am Richard Opalka wrote:
Hi CXF Team,
what's the current CXF roadmap from WS-* point of view?
What specs are you going to work on next and what is the schedule for them?
The roadmap as defined here:
http://cxf.apache.o
ice) ensured in CXF WS-RM implementation?
* Is current CXF WS-RM implementation tightly coupled with Endpoint?
* Is there some API for client side when receiving undelivered
messages? Where I could find it?
* Is there some detailed architecture documentation about CXF WS-RM?
Thanks,
Richard
--
What's the current status of this issue Daniel?
Should I create JIRA issue or is there already one?
Richard
Richard Opalka wrote:
Hi CXF Folks,
see in lined comments below:
Daniel Kulp wrote:
On Wed June 3 2009 3:18:36 pm Jeff Genender wrote:
I actually prefer the injection/overri
OK, will do ;)
Richard
Daniel Kulp wrote:
On Mon June 15 2009 9:39:51 am Richard Opalka wrote:
What's the current status of this issue Daniel?
Should I create JIRA issue or is there already one?
Create a JIRA (and attach a patch ;-) )!
Dan
Richard
Richard Opalka
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
as (including the ones I am thinking of
for J2XB 2.0) to existing frameworks in CFX?
Having never heard of J2XB before, I really have no idea. :-)
--
Richard Opalka
JBoss Software Engineer
Mail: ropa...@redhat.com
Mobile: +420731186942
Forwarding to Daniel for his opinions on this topic.
Rio
Original Message
Subject:Re: [jbossws-dev] CXF-2926
Date: Wed, 04 Aug 2010 11:37:38 +0200
From: Alessio Soldano
To: Richard Opalka
CC: Sergey Beryozkin , jbossws-dev
OK Richard, thanks.
Then you
accept the challenge and modify the TCK, then change
to WARNING so you can proceed. If they do change it, leave as is.
Dan
On Wednesday 04 August 2010 7:33:21 am Richard Opalka wrote:
Forwarding to Daniel for his opinions on this topic.
Rio
Original Message
Subject:
two.
If that is anywhere related to the above issue I have no idea, but
with such circular (SNAPSHOT) dependencies you can of course end up
with using an outdated version of either one of them during the build.
Regards,
Ate
thanks, Sergey
--
Richard Opalka
ropa...@redhat.com
JBoss, by R
Maven version:
Java version (full version string):
32/64 bit:
Value of MAVEN_OPTS env variable:
OS (and version):
I haven't run into this in a while. :-(
Dan
On Thursday 30 September 2010 8:29:23 am Richard Opalka wrote:
I'm facing this issue each time I build CXF trunk.
The trick
ow this kind of error.
I just committed a work around[1] before we decide to change the check
style configuration file.
[1]http://svn.apache.org/viewvc?rev=1341332&view=rev
On Wed Apr 25 02:42:14 2012, dk...@apache.org wrote:
--
Richard Opalka
JBoss, by Red Hat
Cell: +420 731 186 942
e ISE guidelines (is not lenient
like e.g. Jakarta Tomcat).
The last issue that I identified with Servlet3ContinuationProvider is
the isNew flag has incorrect initial value - it should be *true*.
Cheers,
Rio
--
Richard Opalka
Principal Software Engineer
JBoss, by Red Hat
Cell: +420 731 186 942
Hi Sergey,
On 11/26/2012 01:21 PM, Sergey Beryozkin wrote:
> Hi Richard
> On 26/11/12 12:15, Richard Opalka wrote:
>> Dear CXF developers,
>>
>> I'm analyzing our recent CXF continuation related failures in CI
>> and I identified the following pr
Hi Sergey,
On 11/26/2012 01:31 PM, Sergey Beryozkin wrote:
> Hi Richard
> On 26/11/12 12:29, Richard Opalka wrote:
>> Hi Sergey,
>>
>>
>> On 11/26/2012 01:21 PM, Sergey Beryozkin wrote:
>>> Hi Richard
>>> On 26/11/12 12:15, Richard Opalka wro
Hi Sergey,
On 11/26/2012 02:57 PM, Richard Opalka wrote:
> Hi Sergey,
>
> On 11/26/2012 01:31 PM, Sergey Beryozkin wrote:
>> Hi Richard
>> On 26/11/12 12:29, Richard Opalka wrote:
>>> Hi Sergey,
>>>
>>>
>>> On 11/26/2012 01:21 PM, Serge
Hi Sergey,
On 11/26/2012 04:58 PM, Sergey Beryozkin wrote:
> Hi Richard
> On 26/11/12 15:05, Richard Opalka wrote:
>> Hi Sergey,
>>
>> On 11/26/2012 02:57 PM, Richard Opalka wrote:
>>> Hi Sergey,
>>>
>>> On 11/26/2012 01:31 PM, Sergey Bery
ering why CXF isn't using generated 'exception' beans for JAXB
de/serialization & WSDL generation
but instead operate directly on top of exception objects? I know CXF is
passing TCK, but isn't it violating JAXWS spec.?
Most probably TCK tests doesn't cover this iss
ML then the above definition should at least look like:
WDYT?
PS1: Just thinking loud :)
PS2: Attached are generated WSDL sources.
On 11/30/2012 02:53 PM, Richard Opalka wrote:
> Hi CXF folks,
>
> Below is copy/paste from JAXWS 2.2 spec, Section 3.7 - Service Specific
> Excep
Clarification,
was thinking little bit about it during the weekend.
On 11/30/2012 03:20 PM, Richard Opalka wrote:
> Forgot to mention that this is related to CXF-4600 :(
>
> Follow up (thinking CXF way and for a while ignoring previous post):
>
> The sources we're goi
a can of worms in JAXWS spec.
On 12/03/2012 08:36 AM, Richard Opalka wrote:
> Clarification,
>
>was thinking little bit about it during the weekend.
>
> On 11/30/2012 03:20 PM, Richard Opalka wrote:
>> Forgot to mention that this is related to CXF-4600 :(
>>
>>
/2009/07/using-soap-faults-and-exceptions-in-java-jaxws-web-services.html
Cheers,
Rio
PS: I'm closing CXF-4600 as won't fix.
On 12/03/2012 04:15 PM, Richard Opalka wrote:
> Hello CXF folks,
>
>after googling, reading the specs. & blogs whole day
> I have few addit
ite a bit to look a bit less like confluence. This is a
"would be nice anytime, not just for 2.2" type thing.
I'm sure there will be a bunch of other enhancements as well.Stuff
like performance/memory enhancements, etc...
Anyway, thoughts? Other ideas? Comments?
-
ill it rely on Maven to resolve the
Spring dependencies for a particular stable release?
--
B.Sc. Richard Opalka
Senior Software Engineer
JBoss, a division of Red Hat
Mobile: +420 731 186 942
Mail: [EMAIL PROTECTED]
ss.
--oh
--
B.Sc. Richard Opalka
Senior Software Engineer
JBoss, a division of Red Hat
Mobile: +420 731 186 942
Mail: [EMAIL PROTECTED]
31 matches
Mail list logo
