I may missing one last thing. It may sound dull, but I've been asking myself
and couldn't find any cleaner solution than the one I'm finally using.
So here it is :
When I was using the default ExpressionAssignmentHandler, I used to pass it an
Expression. (Well nothing stunning until now). This e
Hi Ronald,
In the meantime, I gave my (yours in fact) idea a try and did exactly as I
described in the previous post. Guess what ? It's working ! (of course it's
working might you think ... :) ).
Thanks again.
Jerome
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewt
Yeah ... my last post wasn't that readable ... new try.
___
Hi There,
I've been following this very interesting thread from the start and I'm really
glad someone helps as much as you do.
I'm in a similar situation as Sherry's and if I understand well your post
above, by
"kukeltje" wrote : Ok, here is another quick reply ;-)
|
| Well, you are kind of there, but not completely. I have to admit, the area
of extending/overriding the identitycomponent and/or the
ExpressionAssignmentHandler is/was kind of not really flexible and certainly
not realy documented
Hi there,
I'm probably exhuming a pretty old post now, but I just wanted to make things
clearer for me.
I've been reading a lot this week-end on JBossWS, WStools and a lot of
surrounding topics and suffs.
>From what I understand, you suggest giving up using WSTools in the profit of
>annotations
It may sounds a bit late now, but that was really usefull mate !
Thanks for posting your solution.
J
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138471#4138471
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138471
