Also, I just managed to grab the 3.2.0 release (congrats!)

I noticed that wadl2java has this option now: -namePassword <namePassword>
though in your commits, it looks like this was later renamed to
"authorization"

I tried both via the bat file, and "authorization" is an unknown option

there are no complaints when I supply the namePassword though, like this:
\apache-cxf-3.2.0\bin>wadl2java -namePassword apiuser:apiuser
https://whatever:8000/api/rest/somemodel?_wadl

I still get:  Server returned HTTP response code: 401

Looks like the auth pair didn't seem to affect the connection?




On Mon, Sep 11, 2017 at 3:39 PM, Shan Syed <[email protected]> wrote:

> Hi, I I tried this on 3.0.15 just now, and it doesn't seem like the
> "authorization" is available as an option for me. In my POM:
>
> <wadlOption>
> <wadl>https://whatever8000/api/rest/somemodel?_wadl</wadl>
> <impl>true</impl>
> <authorization>apiuser:apiuser</authorization>
> <packagename>com.whatever</packagename>
> </wadlOption>
>
> "Cannot find 'authorization' in class org.apache.cxf.maven_plugin.wa
> dlto.WadlOption"
>
> Does the option go somewhere else? Thanks!
>
>
>
>
>
> On Fri, Sep 8, 2017 at 12:23 PM, Shan Syed <[email protected]> wrote:
>
>> Great, I will try it when it's available!
>>
>> On Wed, Sep 6, 2017 at 11:39 AM, Sergey Beryozkin <[email protected]>
>> wrote:
>>
>>> Np. hope that code I added will work from the 1st attempt :-), I did not
>>> want to introduce a strong dep on the CXF JAX-RS client code, so resorted
>>> to writing some HttpUrlConnection code which is tricky to do right...
>>>
>>> Cheers, Sergey
>>>
>>> On 06/09/17 16:32, Shan Syed wrote:
>>>
>>>> amazing, thank you
>>>>
>>>> On Friday, September 1, 2017, Sergey Beryozkin <[email protected]>
>>>> wrote:
>>>>
>>>> I've created this issue:
>>>>>
>>>>> https://issues.apache.org/jira/browse/CXF-7492
>>>>>
>>>>> but will likely have no time to complete it early next week,
>>>>>
>>>>> but at least it will be tracked
>>>>>
>>>>> Cheers, Sergey
>>>>> On 25/08/17 15:14, Sergey Beryozkin wrote:
>>>>>
>>>>> I see, makes sense to add a new switch
>>>>>>
>>>>>> Sergey
>>>>>> On 25/08/17 14:52, Shan Syed wrote:
>>>>>>
>>>>>> I don't have explicit access to the header via the command line
>>>>>>> wadl2java,
>>>>>>> nor the maven plugin
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Aug 25, 2017 at 6:24 AM, Sergey Beryozkin <
>>>>>>> [email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>>>
>>>>>>>> Why can't they be sent as the header ? Otherwise I guess one needs
>>>>>>>> to
>>>>>>>> configure the HTTP container somehow for the name and password be
>>>>>>>> extracted
>>>>>>>> out of URI and matched against the BasicAuth module...
>>>>>>>>
>>>>>>>> Sergey
>>>>>>>>
>>>>>>>> On 25/08/17 01:10, Shan Syed wrote:
>>>>>>>>
>>>>>>>> Hey there,
>>>>>>>>
>>>>>>>>>
>>>>>>>>> I need to generate client code for a WADL, hosted on a remote
>>>>>>>>> server I
>>>>>>>>> don't control.
>>>>>>>>> The WADL has very deep includes, that reference other xml files
>>>>>>>>> hosted
>>>>>>>>> on
>>>>>>>>> the same server.
>>>>>>>>> Downloading them all isn't practical, because it's a very deep
>>>>>>>>> hierarchy.
>>>>>>>>>
>>>>>>>>> The WADL is also served off of a webserver that asserts basic auth.
>>>>>>>>>
>>>>>>>>> I'm trying both the cxf wadl2java download, and the maven plugin;
>>>>>>>>> neither
>>>>>>>>> seem to work when I provide basic auth details like this:
>>>>>>>>>
>>>>>>>>> https://whateverusernamer:[email protected]?wadl
>>>>>>>>>
>>>>>>>>> A 401 error is returned, and the basic auth parameters aren't sent
>>>>>>>>> to
>>>>>>>>> the
>>>>>>>>> server this way.
>>>>>>>>>
>>>>>>>>> Is there a way to specify user/password for basic auth on a remote
>>>>>>>>> WADL?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>> --
>>>>> Sergey Beryozkin
>>>>>
>>>>> Talend Community Coders
>>>>> http://coders.talend.com/
>>>>>
>>>>>
>>>>
>>
>

Reply via email to