Right , Dan. No need to add this interceptor in the client side.
Thanks for the review and committed the optimized code in revision 1049415.
On Wed, Dec 15, 2010 at 8:18 AM, Daniel Kulp wrote:
>
> Jim,
>
>
> On Tuesday 14 December 2010 7:07:47 pm e...@apache.org wrote:
>> MustUnderstandEndingInte
Jim,
On Tuesday 14 December 2010 7:07:47 pm e...@apache.org wrote:
> MustUnderstandEndingInterceptor(); +
> public MustUnderstandInterceptor() {
> super(Phase.PRE_PROTOCOL);
> }
> @@ -80,12 +83,18 @@ public class MustUnderstandInterceptor e
> checkUnderstand(mustUnder
You don't NEED to move to java 7. There are two options:
1) Endorse the jars in the lib/endorsed directory. That upgrades the apis
that are picked up to 2.2 level. The wsdl2java script does that so they are
picked up. When found, the tool generates 2.2 compiant code and thus would
need t
Hello,
I am new to Apache CXF. I tried it few months ago with Apache CXF 2.3.0,
with a contract first approach.
Now that the version 2.3.1 is released, I used again the wsdl2java tools to
check for differences.
I encounter a compilation error on the generated Service class.
This come from the ne
I think if you go to "File -> Import -> General -> Preferences", you can
import those preferences directly into the workspace.
Dan
On Tuesday 14 December 2010 9:16:32 am David Valeri wrote:
> I can confirm success over here too. I imported the security module using
> M2Eclipse and the import
I can confirm success over here too. I imported the security module using
M2Eclipse and the import completed successfully.
I noticed that you added eclipse.prefs to SVN. I updated your instructions
in the wiki last week since eclipse.prefs wasn't in source control. If
using it reduces the numbe
