steve8858 Absent Member.
Absent Member.
1542 views

use archive.wsdl through axis1.4 generated running 500 error

I use the file that you have provided archive.wsdl, through the AXIS generated WebService server-side code, but running in Tomcat container reported http 500 error.

What is the reason? Is not your provided archive.wsdl non-standard? Are there any other better way to generated code?
Labels (1)
Tags (2)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: use archive.wsdl through axis1.4 generated running 500 error

On 3/9/2010 7:06 PM, steve8858 wrote:
>
> I use the file that you have provided archive.wsdl, through the AXIS
> generated WebService server-side code, but running in Tomcat container
> reported http 500 error.
>
> What is the reason? Is not your provided archive.wsdl non-standard?
> Are there any other better way to generated code?
>
>

WE had no trouble with doing this with Metro. So maybe your Axis is
nonstandard 🙂

0 Likes
steve8858 Absent Member.
Absent Member.

Re: use archive.wsdl through axis1.4 generated running 500 e

mikebell90;1944582 wrote:
On 3/9/2010 7:06 PM, steve8858 wrote:
>
> I use the file that you have provided archive.wsdl, through the AXIS
> generated WebService server-side code, but running in Tomcat container
> reported http 500 error.
>
> What is the reason? Is not your provided archive.wsdl non-standard?
> Are there any other better way to generated code?
>
>

WE had no trouble with doing this with Metro. So maybe your Axis is
nonstandard 🙂



archive.wsdl generated WebService server-side code is very little information on programming in your web site.
Can you give me java version of the demo available code for stub?

Thank you very much!
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: use archive.wsdl through axis1.4 generated running 500 error

On 3/10/2010 12:36 AM, steve8858 wrote:
>
> mikebell90;1944582 Wrote:
>> On 3/9/2010 7:06 PM, steve8858 wrote:
>>>
>>> I use the file that you have provided archive.wsdl, through the AXIS
>>> generated WebService server-side code, but running in Tomcat

>> container
>>> reported http 500 error.
>>>
>>> What is the reason? Is not your provided archive.wsdl non-standard?
>>> Are there any other better way to generated code?
>>>
>>>

>> WE had no trouble with doing this with Metro. So maybe your Axis is
>> nonstandard 🙂

>
>
> archive.wsdl generated WebService server-side code is very little
> information on programming in your web site.
> Can you give me java version of the demo available code for stub?
>
> Thank you very much!
>
>

I'm sorry, internal politics prevent me from sharing it 😞
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: use archive.wsdl through axis1.4 generated running 500 error

Am 11.03.2010 00:47, schrieb Michael Bell:
> On 3/10/2010 12:36 AM, steve8858 wrote:
>>
>> mikebell90;1944582 Wrote:
>>> On 3/9/2010 7:06 PM, steve8858 wrote:
>>>>
>>>> I use the file that you have provided archive.wsdl, through the AXIS
>>>> generated WebService server-side code, but running in Tomcat
>>> container
>>>> reported http 500 error.
>>>>
>>>> What is the reason? Is not your provided archive.wsdl non-standard?
>>>> Are there any other better way to generated code?
>>>>
>>>>
>>> WE had no trouble with doing this with Metro. So maybe your Axis is
>>> nonstandard 🙂

>>
>>
>> archive.wsdl generated WebService server-side code is very little
>> information on programming in your web site.
>> Can you give me java version of the demo available code for stub?
>>
>> Thank you very much!
>>
>>

> I'm sorry, internal politics prevent me from sharing it 😞


If you have the need for stubbing,
I strongly suggest you don't reinvent the wheel ( and pain )
and go to a vendor like gwava.com/retain or tma who have this ready.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.