Well currently we are looking for custom-server.xml,
custom-schema-server.xml, custom-client.xml and custom-schema-client.xml.
Let me know if this does not address your needs.
I will update the document with this info
Regards,
Bhakti
Rama Pulavarthi wrote:
> So you mean, I can place any number of customization files ( jaxws or
> jaxb) in the right place where you look for, the name does not need to
> follow any conventions like custom-server.xml etc.
> Sounds nice, just the docs need to be updated with this info.
>
> thanks,
> Rama Pulavarthi
>
> Bhakti Mehta wrote:
>
>> Rama,
>> Currently if you add the customization file for the server in the
>> server basedir folder and the client customization file in the test
>> basedir where the test.bsh resides the harness will pick it up and
>> use those when invoking wsimport.
>> So you are not restricted to put the user customization files if you
>> need to specify other customizations, only package level
>> customization is already handled by the harness.
>>
>> Regards,
>> Bhakti
>>
>> Rama Pulavarthi wrote:
>>
>>> -p option won't solve all the problems.
>>> I think there should be a way to specify these customization files
>>> which provides tons of options to customize.
>>> thanks,
>>> Rama Pulavarthi
>>>
>>> Bhakti Mehta wrote:
>>>
>>>> Rama,
>>>> We are using the -p option on wsimport to customize the package
>>>> for client and server side customization as well as for schema
>>>> customization. Previously we were generating the customization
>>>> files in the harness but the -p option is does the same work so we
>>>> used that.
>>>> Maybe we should just mention in the docs about users not needing
>>>> to add customization files and that the harness will take care of it.
>>>>
>>>> Regards,
>>>> Bhakti
>>>> Rama Pulavarthi wrote:
>>>>
>>>>> I see in the documentation there is support for jax-ws server
>>>>> customization via custom-server.xml.
>>>>> Does it support client-side jax-ws customization as well.
>>>>> What about schema customization? Is it supported?
>>>>>
>>>>> Also Section 2.1 in User Guide should be updated with conventions
>>>>> for these customization files.
>>>>> Also this structure in 2.1 should convey what is optional and
>>>>> what is not.
>>>>>
>>>>> thanks,
>>>>> Rama Pulavarthi
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
>>>>> For additional commands, e-mail:
>>>>> dev-help_at_ws-test-harness.dev.java.net
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
>>> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
>> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>