Hi Dan,
Daniel Kulp wrote:
On Tue July 21 2009 11:25:56 am Alessio Soldano wrote:
The ServiceImpl gets the configurer from the bus after having created
the jaxws proxy factory bean.
Then my custom configurer sets the props in the JaxWSProxyFactoryBean
which in turns copies them to the reques
On Tue July 21 2009 11:25:56 am Alessio Soldano wrote:
> I'm taking this from Richard as he's busy with other things. I've just
> taken a look deep in details and I think CXF already provides us a mean
> of setting properties in the port (actually in the request context upon
> port creation).
> I'v
Hi Dan,
I'm taking this from Richard as he's busy with other things. I've just
taken a look deep in details and I think CXF already provides us a mean
of setting properties in the port (actually in the request context upon
port creation).
I've just tried leveraging the bus extensions in Service
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 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 wrote:
> > Hi CXF Folks,
> >
> > see in lined comments belo
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/override of
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/override of an implementation via a
property...
This is quite common (see the XML parser, JACC, etc) and sounds like
it could lend itself very
Hi Daniel,
all the options mentioned below sound reasonable to me.
Richard
Daniel Kulp wrote:
Richard,
Modifying the generated code is not a doable solution. That would tie them
to CXF which would then violate the JAX-WS spec and TCK and such. Thus,
that's not an option.
However, yo
OSGI, Shmo-sgi! ;-)
Anyways, I am thinking more of a tiered approach to this.
I think the listener is fine, but its nice to be able to have the fall
back property. This gives you the best of both worlds. This is kind
of how we did in the JACC implementation in Geronimo IIRC. - then
again
On Wed June 3 2009 3:18:36 pm Jeff Genender wrote:
> I actually prefer the injection/override of an implementation via a
> property...
>
> This is quite common (see the XML parser, JACC, etc) and sounds like
> it could lend itself very well to what is trying to be done here.
Just because its "quit
I actually prefer the injection/override of an implementation via a
property...
This is quite common (see the XML parser, JACC, etc) and sounds like
it could lend itself very well to what is trying to be done here.
Jeff
On Jun 3, 2009, at 1:13 PM, Daniel Kulp wrote:
Richard,
Modifyin
Richard,
Modifying the generated code is not a doable solution. That would tie them
to CXF which would then violate the JAX-WS spec and TCK and such. Thus,
that's not an option.
However, you could be on the right track. In our ServiceImpl, all the
"getPort" calls forward into the protec
Hi Dan and Richard,
Richard Opalka wrote:
Hi Daniel,
Yes, I know about solution 1) you suggested. However I don't like it.
It's hacky and could cause a lot of troubles to our customers.
Thus I'd like to go the way to modify CXF code base.
I would not say it's hacky, as providing a custom
jav
Hi Daniel,
Yes, I know about solution 1) you suggested. However I don't like it.
It's hacky and could cause a lot of troubles to our customers.
Thus I'd like to go the way to modify CXF code base.
Before I'll write my suggestion let me clarify that we don't need to
wrap your ServiceDelegate.
Well, couple things spring to mind:
Option 1: requires no changes to CXF, but requires some classloader magic on
your side
Write your own javax.xml.ws.spi.Provider that probably subclasses ours and
overrides the method:
@Override
public ServiceDelegate createServiceDelegate(URL url, QNa
Hi CXF Team,
We've spent some time with CXF source code analysis but without success.
Related issue is: https://jira.jboss.org/jira/browse/JBWS-2521
We would like to remove one very ugly JBossWS CXF JAX-WS client proxy
integration hack related to service references (method
hackServiceDelegate
16 matches
Mail list logo
