-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sanjiva Weerawarana wrote:
> On Tue, 2006-06-27 at 09:00 +0100, Brian Hulse wrote:
>> I understand what you're saying, but there's a processing
>> overhead here. In your model, each module will winnow out the
>> alternatives it cannot support and pass
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everyone,
Let me explain bit more on the suggested model for policy processing.
The central point of control in AxisDescription. This is how it works.
When you call axisDescription.applyPolicy(Policy) first it will get a
registry of namespaces t
On Tue, 2006-06-27 at 09:00 +0100, Brian Hulse wrote:
> I understand what you're saying, but there's a processing overhead
> here. In your model, each module will winnow out the alternatives it
> cannot support and pass on the result to the next. The problem with
> this is that each will have to d
In mercury QTP - web serice wizard - unable to load axis toolkit error
--
Key: AXIS-2514
URL: http://issues.apache.org/jira/browse/AXIS-2514
Project: Apache Axis
Type: Test
Reporter: becky
C:\
Looks great, but I seen a minor problem I think (A little late here) ...
Parameter implInfoParam = service.getParameter(SERVICE_CLASS);
if (implInfoParam != null) {
Class implClass = Class.forName(((String)
implInfoParam.getValue()).trim(), true,
c
[
http://issues.apache.org/jira/browse/AXIS2-853?page=comments#action_12418102 ]
James Bender commented on AXIS2-853:
The java.lang.IllegalStateException is thrown in the method
getOMDocumentElement() on the OMDocumentImpl class.
public OMElement getOM
Administrator create server error
-
Key: AXIS2-857
URL: http://issues.apache.org/jira/browse/AXIS2-857
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: deployment
Versions: 1.0
Environment: JRE 1.5.0_6-b05, Tomcat 5
[
http://issues.apache.org/jira/browse/AXIS2-844?page=comments#action_12418075 ]
Derek Foster commented on AXIS2-844:
Yes. I have already tested this. When the namespace of the schema is the same
as the targetNamespace of the WSDL document, the problem
WSDL generation should not be attempted for non RPC receivers
-
Key: AXIS2-856
URL: http://issues.apache.org/jira/browse/AXIS2-856
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Environment: Windows
Report
Sorry -- was not complete in my last answer. If you change it to rpc style, then you must also add namespace attributes to the definitions, e.g.,:http://www.fabiorosolino.com/Servizio.xsd1"/>AnneOn 6/27/06,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Anne,I modified Servizio.wsdl as you suggeste
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, June 28, at:
5AM SF, 8AM Boston, 1PM London, 5:30PM Colombo, 10PM Melbourne
The chat takes place on the freenode IRC network, (use server
irc.freenode.net), on channel #apache-axis, and is sc
Anne,
I modified Servizio.wsdl as you suggested but the question is,
1) why it work fine (style document) with axis 1.2?
2) after the change in rpc style i'm still not able to do a service that
work!!! :(
I use Tomcat 5.5 as container either with axis 1.2 or with axis 2 on windows.
There will be s
[ http://issues.apache.org/jira/browse/AXIS2-830?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-830:
---
Resolution: Invalid
>From the explanation of Mike this seems an invalid issue. Marking it as
>resolved
> WSDL2Java fails with NPE wh
[ http://issues.apache.org/jira/browse/AXIS2-855?page=all ]
Davanum Srinivas resolved AXIS2-855:
Resolution: Fixed
Fixed.
thanks,
dims
> javax.xml.ws.handler.MessageContext constant fields need update
>
[
http://issues.apache.org/jira/browse/AXIS2-844?page=comments#action_12418040 ]
Ajith Harshana Ranabahu commented on AXIS2-844:
---
It is possible for the namespace handling to screw up this point. I will look
into this. In any case is it possib
[ http://issues.apache.org/jira/browse/AXIS2-855?page=all ]
Brent Ulbricht updated AXIS2-855:
-
Attachment: patch.txt
The attached file contains a patch.
> javax.xml.ws.handler.MessageContext constant fields need update
>
javax.xml.ws.handler.MessageContext constant fields need update
---
Key: AXIS2-855
URL: http://issues.apache.org/jira/browse/AXIS2-855
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: jaxws
Envir
[
http://issues.apache.org/jira/browse/AXIS-2487?page=comments#action_12418025 ]
Andreas Goetz commented on AXIS-2487:
-
Would anybody now if this is fixed in a later release?
> Cannot create web service client from WSDL containing %20 characters
> -
Fabio,There are errors in your WSDL. You must fix them before you can get Axis2 to work.You've defined the service as document style, but your message parts reference types rather than elements. (A document style service MUST reference elements; and RPC style service MUST reference types.) Either c
I tried to follow step by step thr migration guide, but i'm not able to develop
correct code for my service with axis 2.0,
This is the skeleton that i developed.
-- Initial Header ---
>From : "robert lazarski" [EMAIL PROTECTED]
To : axis-dev@ws.apache.org
Cc
Hi Fabio,
Why don't you try to do it yourself and get that "Aha" feeling yourself.
I can send it over but the one of the key features of Axis2 is its
usability.
Get the Axis2 1.0 release, find the wsdlcode.bat inside bin folder. Run
it with the following options.
If u r in Windows : WSDL2Code.ba
Have you looked at the migration guide ?
http://ws.apache.org/axis2/1_0/migration.html
HTH,
Robert
http://www.braziloutsource.com/
On 6/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I have a wsdl genereted by SOA Editor.
I'm able to develop a service in Axis 1.2 from this WSDL, but i'm n
I have a wsdl genereted by SOA Editor.
I'm able to develop a service in Axis 1.2 from this WSDL, but i'm not able to
develop a service with Axis 2 v1.0.
Someome can send me send me a service developed using my WSDL in Axis 2.
In attachment the Servizio.wsdl (Servizio means Service in italian ;))
T
[
http://issues.apache.org/jira/browse/AXIS2-850?page=comments#action_12417995 ]
Michele Mazzucco commented on AXIS2-850:
Deepal, I fixed the problem by manually removing the relatesTo element (this is
done by a handler running before the Transport
[ http://issues.apache.org/jira/browse/AXIS2-676?page=all ]
Deepal Jayasinghe resolved AXIS2-676:
-
Resolution: Fixed
Arod send a patch to solve the problem.
> An exception is thrown while getting WSDL for a deployed service
> --
[
http://issues.apache.org/jira/browse/AXIS2-850?page=comments#action_12417992 ]
Deepal Jayasinghe commented on AXIS2-850:
-
How can I regenerate the problem ?
any possibility of attaching test case ?
> NullPointerException in AbstractHTTPSender
> -
[
http://issues.apache.org/jira/browse/AXIS-2260?page=comments#action_12417991 ]
Artur Kraft commented on AXIS-2260:
---
Seems to also affect dotNet communication, as the content of
not-namespace-qualified gets ignored.
> elements in SOAP response document
[
http://issues.apache.org/jira/browse/AXIS2-676?page=comments#action_12417990 ]
Sébastien Arod commented on AXIS2-676:
--
Yes this patch solves my problem
> An exception is thrown while getting WSDL for a deployed service
> -
[
http://issues.apache.org/jira/browse/AXIS2-676?page=comments#action_12417984 ]
Deepal Jayasinghe commented on AXIS2-676:
-
applied
> An exception is thrown while getting WSDL for a deployed service
>
[
http://issues.apache.org/jira/browse/AXIS2-676?page=comments#action_12417980 ]
Deepal Jayasinghe commented on AXIS2-676:
-
Does this patch solve your problem ?
> An exception is thrown while getting WSDL for a deployed service
> --
documentation elements in custom wsdl are lost during "?wsdl"
-
Key: AXIS2-854
URL: http://issues.apache.org/jira/browse/AXIS2-854
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Davanum Srinivas
[ http://issues.apache.org/jira/browse/AXIS2-676?page=all ]
Sébastien Arod updated AXIS2-676:
-
Attachment: AxisService2OM_patch.txt
The code used to generate wsdl from schema assume default encoding is UTF8
(AxisOMService.java line 160) :
XMLStreamReade
I understand what you're saying, but there's a processing overhead here. In your model, each module will winnow out the alternatives it cannot support and pass on the result to the next. The problem with this is that each will have to do an exhaustive search throughout the whole policy tree, includ
33 matches
Mail list logo
