axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Kidby (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-4485) In an ADB Client how do I set/control an Element's attributes/sub-elements
Date Thu, 03 Sep 2009 13:06:57 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Kidby updated AXIS2-4485:
--------------------------------

    Description: 
First of all I apologise for wasting people's time but I am still very green when it comes
to web services and Axis.

I have been supplied with a WSDL and using WSDL2Java have generated my client stub. Then I've
written my client and all appears OK as I have successfully tested it against the required
remote service.

However, one part of the service calls for an XML construct such as this:
                                          <TAG1 ATTR1="ABC" ATTR2="DEF" ATTR3="XYZ">
                                                <TAG2>VALUE1</TAG2>
                                          </TAG1>

In the past I have only had to deal with elements such as TAG2 and it's value - no problem.

I have never had to cater for the TAG1 situation, i.e. where it has attributes (or are they
sub-elements?).

How and where do I need to define/set  ATTR1, "ABC", ATTR2, "DEF" etc. ?

I have trawled around the internet but cannot seem to find the info I need - probably because
I'm using the wrong terminology.

Any help at all would be greatly appreciated.

Thanks in advance

  was:
First of all I apologise for wasting people's time but I am still very green when it comes
to web services and Axis.

I have been supplied with a WSDL and using WSDL2Java have generated my client stub. Then I've
written my client and all appears OK as I have successfully tested it against the required
remote service.

However, the one part of the serviice calls for an XML construct such as this:
                                          <TAG1 ATTR1="ABC" ATTR2="DEF" ATTR3="XYZ">
                                                <TAG2>VALUE1</TAG2>
                                          </TAG1>

In the past I have only had to deal with elements such as TAG2 and it's value - no problem.

I have never had to cater for the TAG1 situation, i.e. where it has attributes (or are they
sub-elements?).

How and where do I need to define/set  ATTR1, "ABC", ATTR2, "DEF" etc. ?

I have trawled around the internet but cannot seem to find the info I need - probably because
I'm using the wrong terminology.

Any help at all would be greatly appreciated.

Thanks in advance


> In an ADB Client how do I set/control an Element's attributes/sub-elements
> --------------------------------------------------------------------------
>
>                 Key: AXIS2-4485
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4485
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.4
>         Environment: Windows XP / Axis2 1.4.1 / Java 1.4.2
>            Reporter: Martin Kidby
>
> First of all I apologise for wasting people's time but I am still very green when it
comes to web services and Axis.
> I have been supplied with a WSDL and using WSDL2Java have generated my client stub. Then
I've written my client and all appears OK as I have successfully tested it against the required
remote service.
> However, one part of the service calls for an XML construct such as this:
>                                           <TAG1 ATTR1="ABC" ATTR2="DEF" ATTR3="XYZ">
>                                                 <TAG2>VALUE1</TAG2>
>                                           </TAG1>
> In the past I have only had to deal with elements such as TAG2 and it's value - no problem.
> I have never had to cater for the TAG1 situation, i.e. where it has attributes (or are
they sub-elements?).
> How and where do I need to define/set  ATTR1, "ABC", ATTR2, "DEF" etc. ?
> I have trawled around the internet but cannot seem to find the info I need - probably
because I'm using the wrong terminology.
> Any help at all would be greatly appreciated.
> Thanks in advance

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message