inputSchema in WSDL processing cant handle space in file
Key: AXIS-2173
URL: http://issues.apache.org/jira/browse/AXIS-2173
Project: Apache Axis
Type: Bug
Versions: 1.2.1
Reporter: Ravi Kumar
In c
Java2WSDL, stopClasses and Interfaces
-
Key: AXIS-2172
URL: http://issues.apache.org/jira/browse/AXIS-2172
Project: Apache Axis
Type: Bug
Components: WSDL processing
Versions: 1.2.1
Environment: all platforms
Repor
Hi all,
I am writing an end to end test case for the code generator. To compile
the generated code I use the Javac task from Ant. However I 've come
across some problems, specially a weird problem where the 'java.home'
appears to be pointing to the Java runtime instead of the JDK home.
Here are the
[
http://issues.apache.org/jira/browse/AXIS2-129?page=comments#action_12318112 ]
Tom Jordahl commented on AXIS2-129:
---
I would hope that you can just take the Axis 1.x i18n package and use it.
> Internationalisation support for OM
> ---
Funniest scene is all these test cases run fine when sending through tcpmonMay be a thread issue..On 8/9/05, Aleksander Slominski <
[EMAIL PROTECTED]> wrote:Thilina Gunarathne wrote:> hi all,> I also had this problem with CharacterEncodingTest test case once in a
> while.> Some of the MTOM
Thilina Gunarathne wrote:
hi all,
I also had this problem with CharacterEncodingTest test case once in a
while.
Some of the MTOM test cases are also failing occationally due to this
connection reset problem. I have noticed through the TCP monitor that
some messages sent by simple axis server
Hi Robert,
We actually talked about it that day also. Glen seems to be doing some
work on a simple data binding framework but I am not really sure how it
will turn out. I mean I am not sure whether it's based on Axis1 or so.
Any thoughts Glen :)On 8/9/05, robert burrell donkin <[EMAIL PROTECTED]>
Hi Glen
see my comments below;
Thanks,
Deepal
~Future is Open~
- Original Message -
From: "Glen Daniels" <[EMAIL PROTECTED]>
To:
Sent: Monday, August 08, 2005 7:05 PM
Subject: [axis2] Exploded directory support
Hey
See my comments below
Thanks,
Deepal
~Future is Open~
- Original Message -
From: "Chathura Ekanayake" <[EMAIL PROTECTED]>
To:
Sent: Monday, August 08, 2005 1:53 PM
Subject: Re: [Axis2] JMX front end to Axis2
Hi,
I d
Hi all,
When you resolve a issue in JIRA, please make sure you select one from "Fix
versions". For example, if you fix something during this week, that would be
0.91.
This will give some more information about the bug and will help in the
release process.
Thanks,
Chinthaka
[ http://issues.apache.org/jira/browse/AXIS2-95?page=all ]
Eran Chinthaka updated AXIS2-95:
Fix Version: 0.91
> SOAP with Attachements sample
> -
>
> Key: AXIS2-95
> URL: http://issues.apache.org/jira/browse/
[ http://issues.apache.org/jira/browse/AXIS2-100?page=all ]
Eran Chinthaka updated AXIS2-100:
-
Fix Version: 0.91
> Separating sample and test cases form Sample module
> ---
>
> Key: AXIS2-100
>
[ http://issues.apache.org/jira/browse/AXIS2-103?page=all ]
Eran Chinthaka updated AXIS2-103:
-
Fix Version: 0.91
> Remove code duplication
> ---
>
> Key: AXIS2-103
> URL: http://issues.apache.org/jira/browse/AXIS2-10
[ http://issues.apache.org/jira/browse/AXIS2-112?page=all ]
Eran Chinthaka updated AXIS2-112:
-
Fix Version: 0.91
> Doclitparams Interoperability Test failed
> -
>
> Key: AXIS2-112
> URL: http://is
[
http://issues.apache.org/jira/browse/AXIS2-112?page=comments#action_12318099 ]
Eran Chinthaka commented on AXIS2-112:
--
For me, it seems that this is a problem in interop endpoint and needs ideas
from Axis2 side as to how to tackle this.
I'd like to
[ http://issues.apache.org/jira/browse/AXIS2-116?page=all ]
Eran Chinthaka updated AXIS2-116:
-
Fix Version: 0.91
> element namespaces mistaken in the generated artifacts.
> ---
>
> Key: AXIS2-1
[
http://issues.apache.org/jira/browse/AXIS2-128?page=comments#action_12318097 ]
Davanum Srinivas commented on AXIS2-128:
Please see http://issues.apache.org/jira/browse/AXIS2-121#action_12318096
> CharacterEncodingTest and EchoRawXMLChunkedTest Fai
[ http://issues.apache.org/jira/browse/AXIS2-84?page=all ]
Eran Chinthaka updated AXIS2-84:
Component: Integration
> Addressing interop testing (Pre-W3C)
>
>
> Key: AXIS2-84
> URL: http://issues.apac
[ http://issues.apache.org/jira/browse/AXIS2-120?page=all ]
Eran Chinthaka updated AXIS2-120:
-
Component: databinding
> Testing XMLBeans databinding with real life example
> ---
>
> Key: AXIS2-120
[
http://issues.apache.org/jira/browse/AXIS2-121?page=comments#action_12318096 ]
Davanum Srinivas commented on AXIS2-121:
After reviewing our code in org.apache.axis2.transport.http.SimpleHTTPServer
and reviewing Jetty and AXIS-2082. Here's what i t
[
http://issues.apache.org/jira/browse/AXIS2-132?page=comments#action_12318095 ]
Eran Chinthaka commented on AXIS2-132:
--
I looked at the code in WS-FX WS-Addressing stuff before I wrote the current
impl in Axis2. If I can remember correct it was writte
[ http://issues.apache.org/jira/browse/AXIS2-126?page=all ]
Eran Chinthaka updated AXIS2-126:
-
Component: om
Assign To: Thilina Gunarathne
> Enable AXIOM to work even when activation/javamail jars are absent.
> ---
[ http://issues.apache.org/jira/browse/AXIS2-74?page=all ]
Eran Chinthaka updated AXIS2-74:
Component: om
> Full Infoset support in AXIOM
> -
>
> Key: AXIS2-74
> URL: http://issues.apache.org/jira/browse/AXIS
[ http://issues.apache.org/jira/browse/AXIS2-66?page=all ]
Eran Chinthaka updated AXIS2-66:
Component: om
> Binary Serialization support for SOAP Message
> -
>
> Key: AXIS2-66
> URL: http://is
[ http://issues.apache.org/jira/browse/AXIS2-92?page=all ]
Eran Chinthaka updated AXIS2-92:
Component: core
> Axis2 Addressing does not check for the legal URI values at right places
> -
[ http://issues.apache.org/jira/browse/AXIS2-107?page=all ]
Eran Chinthaka updated AXIS2-107:
-
Component: Tools
> WSDL Wizard for Eclipse
> ---
>
> Key: AXIS2-107
> URL: http://issues.apache.org/jira/browse/AXIS2-107
[
http://issues.apache.org/jira/browse/AXIS2-126?page=comments#action_12318092 ]
Eran Chinthaka commented on AXIS2-126:
--
+1 from me too.
Like to see AXIOM not depending on anything other than StAX.
> Enable AXIOM to work even when activation/javamai
[
http://issues.apache.org/jira/browse/AXIS2-128?page=comments#action_12318091 ]
Eran Chinthaka commented on AXIS2-128:
--
The reason for this seems a connection reset error. This is random and happens
in Linux only. 'm using win xp but I never got this
[ http://issues.apache.org/jira/browse/AXIS2-75?page=all ]
Davanum Srinivas reassigned AXIS2-75:
-
Assign To: (was: Davanum Srinivas)
> Enter wsdl file in eclipse platform
> ---
>
> Key: AXIS2-75
>
[ http://issues.apache.org/jira/browse/AXIS2-75?page=all ]
Davanum Srinivas reassigned AXIS2-75:
-
Assign To: Davanum Srinivas (was: Ajith Harshana Ranabahu)
> Enter wsdl file in eclipse platform
> ---
>
> Key
[
http://issues.apache.org/jira/browse/AXIS2-129?page=comments#action_12318090 ]
Eran Chinthaka commented on AXIS2-129:
--
Currently all the messages in AXIOM are in English. So I'd prefer to have them
I18N supported.
> Internationalisation support for
IIRC at ApacheCon (good talk BTW Ajith) a question were raised (from
the audience) about compatibility with the older axis 1 databinding. i
believe that the reply was that the plan would be to create a new
simple binding framework.
i was wondering whether this has already been created and if the
i
Done. Issue id AXIS-2171.
Thanks Srinivas.
On 8/8/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Pramod,
>
> Please create a enhancement issue - http://issues.apache.org/jira/browse/AXIS
>
> thanks,
> dims
>
> On 8/8/05, Pramod Immaneni <[EMAIL PROTECTED]> wrote:
> > Hi folks,
> >
> > I am
Pramod,
Please create a enhancement issue - http://issues.apache.org/jira/browse/AXIS
thanks,
dims
On 8/8/05, Pramod Immaneni <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I am new to this list and do not know the right process to submit a
> patch for consideration. Please let me know if there is
Hi folks,
I am new to this list and do not know the right process to submit a
patch for consideration. Please let me know if there is any specific
process I should follow. This is against version 1.2.1.
I was using axis and I needed to register a custom serializer for a
java type with the followi
Folks
It seems to me that creating a WSIF provider for Axis2 is really a WSIF
issue not an Axis2 issue. All the other providers were created by the
WSIF team.
PaulOn 8/8/05, Davanum Srinivas (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://issues.apache.org/jira/browse/AXIS2-123?page=comments#actio
Hi Saminda ,
The Service.xml is calling the generated message receiver as shown below :
edu.sjsu.wsrm.wsdlskel.SequenceAbsractPortTypeSkeleton
Here are the details of the code in the CreateSequence() method :
//Create the Response Document
CreateSequenceResponseDocument response = Cre
Done!
Richard
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Monday, August 08, 2005 11:15 AM
To: axis-dev@ws.apache.org
Subject: Re: Problem with referenced elements in wsdl2java
Could you please open a bug report?
thanks,
dims
On 8/8/05, Richard Persche <[E
Could you please open a bug report?
thanks,
dims
On 8/8/05, Richard Persche <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi,
>
>
>
> I am not an Axis developer but I think I found a problem with Axis 1.2.1
> (same behavior with Axis 1.3 observed by Joe Nall) which I want to share
> with you.
>
Hi,
I am not an Axis developer but I think I found a problem
with Axis 1.2.1 (same behavior with Axis 1.3 observed by Joe Nall) which I want to share with
you.
When a wsdl contains elements that are defined by
ref=”xzy”
[…]
+1 in general, and +1 specifically for eliminating the service name from
service.xml .. DRY.
Sanjiva.
On Mon, 2005-08-08 at 09:05 -0400, Glen Daniels wrote:
> Hey folks:
>
> I notice that we don't seem to support exploded directories yet. Is
> anyone working on this? We should be able to jus
[ http://issues.apache.org/jira/browse/AXIS-2169?page=all ]
Jesper Zedlitz updated AXIS-2169:
-
Attachment: AxisContentHandler.java
> CastorSerializer: wrong namespace on accessor element when using RPC/literal
> --
CastorSerializer: wrong namespace on accessor element when using RPC/literal
Key: AXIS-2169
URL: http://issues.apache.org/jira/browse/AXIS-2169
Project: Apache Axis
Type: Bug
Components: S
Hello everybody,
this is a tiny (and my first) contribution to a oss project.
Hope that's the right way in this form via developer mailinglist.
Please give me a feedback if there is something wrong or missing.
Since I am was testing different Axis versions it was trying
to see directly (via HTML
Thanks dims.
On 8/8/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Yes, it's ok to use ALLOW_FORM_OPTIMIZATION (It's a ugly hack we need
> under some conditions. I hate it, but no way around it currently.)
>
> thanks,
> -- dims
>
> On 8/8/05, mtim <[EMAIL PROTECTED]> wrote:
> > Hello dims,
Support for Exploded directories
Key: AXIS2-131
URL: http://issues.apache.org/jira/browse/AXIS2-131
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Reporter: Davanum Srinivas
>From Glen Daniels:
I notice that we don't seem
Glen,
Added issue for exploded support
(http://issues.apache.org/jira/browse/AXIS2-131).
Should we make service name optional? and if it is absent pick up the
directory/file? (worried about uppercase/lower case issues,
self-contained dynamic deployments over network etc.)
-- dims
On 8/8/05, Gl
Hey folks:
I notice that we don't seem to support exploded directories yet. Is
anyone working on this? We should be able to just drop a directory
structure like
echo/
META-INF/service.xml
classes/echo.class
lib/support.jar
modules/
underneath $AXIS/services/, and have the
Chatura,
As long as everything works when jmx jars are absent. it should be ok.
Where is the code? (could you post it as an attachment in jira?)
thanks,
dims
On 8/8/05, Chathura Ekanayake <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I developed the Axis2 JMX front using commons.modeler package. And I
>
Yes, it's ok to use ALLOW_FORM_OPTIMIZATION (It's a ugly hack we need
under some conditions. I hate it, but no way around it currently.)
thanks,
-- dims
On 8/8/05, mtim <[EMAIL PROTECTED]> wrote:
> Hello dims,
>
> We have web service that is running perfectly under Axis 1.1 and
> fails under 1.
Wrong handling of in faults in WSDL2Java
--
Key: AXIS-2168
URL: http://issues.apache.org/jira/browse/AXIS-2168
Project: Apache Axis
Type: Bug
Components: WSDL processing
Reporter: Donal Fellows
When processin
[
http://issues.apache.org/jira/browse/AXIS2-123?page=comments#action_12317980 ]
Davanum Srinivas commented on AXIS2-123:
Deepal, Ruchith,
i am not exactly sure about details. we need to dig it up. I know WSIF
supports Apache SOAP and Apache Axis to
Hello dims,
We have web service that is running perfectly under Axis 1.1 and
fails under 1.2 because of the change that was introduced in Axis 1.2
I checked CVS and found that you made a change in
org.apache.axis.SOAPPart.setCurrentForm(Object, int) method which now
executes only if ALLOW_FOR
Deepal, Ruchith,
i am not exactly sure about details. we need to dig it up. I know WSIF
supports Apache SOAP and Apache Axis to make soap calls. we need to be
able to plugin in Axis2 as well. This URL has a bit more info (i
remember the class name)
http://www.google.com/search?q=WSIFDynamicProvid
Jaya,
Is this available in JDK1.3? :)
-- dims
On 8 Aug 2005 10:28:34 -, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> jayachandra2005/08/08 03:28:34
>
> Modified:java/src/org/apache/axis/transport/http
> CommonsHTTPSender.java
> Log:
> Removing the har
Sure Thilina. Just make sure there is a JIRA issue and we track it
appropriately so that it does not get forgotten.
thanks,
dims
On 8/8/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> Hi,
> In the current impl we have two Part implementations called MemoryPart and
> FilePart, which takes car
[
http://issues.apache.org/jira/browse/AXIS2-129?page=comments#action_12317978 ]
Davanum Srinivas commented on AXIS2-129:
What is expected from AXIOM here? What do we need to do i mean?
> Internationalisation support for OM
> ---
[
http://issues.apache.org/jira/browse/AXIS2-128?page=comments#action_12317977 ]
Davanum Srinivas commented on AXIS2-128:
Which is why we i created this issue
(http://issues.apache.org/jira/browse/AXIS2-121) :)
-- dims
> CharacterEncodingTest and
[
http://issues.apache.org/jira/browse/AXIS2-126?page=comments#action_12317976 ]
Davanum Srinivas commented on AXIS2-126:
+1 from me
> Enable AXIOM to work even when activation/javamail jars are absent.
>
Hi,
In the current impl we have two Part implementations called MemoryPart
and FilePart, which takes care of in memory buffering and file
caching
When it comes to in memory impl we use Java Mail to parse the
Mime parts ( we just feed the boundary delimited stream to MimePart in
JavaMail and it
[
http://issues.apache.org/jira/browse/AXIS2-126?page=comments#action_12317972 ]
Thilina Gunarathne commented on AXIS2-126:
--
I think we should be able to get them running without Activation & Mail.. But
we would need those jars at the compile tie f
[
http://issues.apache.org/jira/browse/AXIS-2139?page=comments#action_12317973 ]
Venkat Reddy commented on AXIS-2139:
I agree with Steve - need to fix the bug which is setting the envelope as dirty
after deser. I think it makes sense to be able to repla
Hi,
I've an AXIS C++ client that consumes IIS .net
web services with WS-Security.
I managed to handle the ws-security but the
client failed to work in some cases.
I've found .net
client doesn't serialize xsi:nil (object or values) and Axis client
does.
Is there a way to avoid xsi:nil bee
thanks.. I filed a Jira...On 8/8/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
It is valid WSDL.On 8/8/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:> Hi all,> I have a WSDL which uses the same message in two operations. In one
> operation it used it as a Input Message (Async One way operati
It is valid WSDL.
On 8/8/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> Hi all,
> I have a WSDL which uses the same message in two operations. In one
> operation it used it as a Input Message (Async One way operation) and in the
> other it is used it as a Output message (sync request resp
Two operations refering to same message
---
Key: AXIS2-130
URL: http://issues.apache.org/jira/browse/AXIS2-130
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: databinding
Reporter: Thilina Gunarathne
Assigned to: Aj
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project ws-axis-xerces-HEAD has an issue affecting its community integration.
This issue
Kevin,
There is an option you can set in your
server-config.wsdd/client-config.wsdd:
…
…
By the way - Axis 1.1 always sent
multirefs by default also for rpc/encoded services.
Tom Jordahl
Macromedia
Server Development
From: Kevin McLoughlin
[mailto:[EMAIL
Ok compiling with jdk1.5
with axis requires you to upgrade to axis 1.2rc2 or later. This has the
disadvantage that the sent message uses "href ="" and a multiref
tag to hold the values. Although this is valid soap the server is running the
ms soap toolkit which is expecting the actual val
On 8 Aug 2005, at 04:41, Eran Chinthaka wrote:
Hi all,
(This is not IDEA marketing ;))
I installed IDEA version 5 and it seems it has very good integrated
support
for SVN. You can do update, commit and most of the other stuff within
IDEA
itself without using Tortoise SVN or anything.
The c
[ http://issues.apache.org/jira/browse/AXIS2-51?page=all ]
Eran Chinthaka updated AXIS2-51:
Fix Version: 0.91
> blocking access to some OMElement methods within SOAPElements
> -
>
> Key
[ http://issues.apache.org/jira/browse/AXIS2-55?page=all ]
Eran Chinthaka updated AXIS2-55:
Fix Version: 0.91
Attaching bug to version
> Children order in SOAPElements
> --
>
> Key: AXIS2-55
> URL: http://is
[
http://issues.apache.org/jira/browse/AXIS2-128?page=comments#action_12317952 ]
Thilina Gunarathne commented on AXIS2-128:
--
The mail I sent to the group ...
I also had this problem with CharacterEncodingTest test case once in a whi
Hi all,
I have a WSDL which uses the same message in two operations. In one
operation it used it as a Input Message (Async One way operation) and
in the other it is used it as a Output message (sync request response
operation).. Is this a valid WSDL..If so pls go ahead and read
the rest;-)
I trie
Hi all,
I have a WSDL which uses the same message in two operations. In one
operation it used it as a Input Message (Async One way operation) and
in the other it is used it as a Output message (sync request response
operation).. Is this a valid WSDL..If so pls go ahead and read
the rest;-)
I trie
Hi,
I developed the Axis2 JMX front using commons.modeler package. And I
have used runtime class loading to load modeler classes as done in
Axis1.2.
I have also added functionality to publish the MBeanServer using a RMI
connector so that it can be accessed by remote machines through RMI.
But this
Internationalisation support for OM
---
Key: AXIS2-129
URL: http://issues.apache.org/jira/browse/AXIS2-129
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Reporter: Eran Chinthaka
Assigned to: Eran Chinthaka
Priority: Mino
CharacterEncodingTest and EchoRawXMLChunkedTest Fail
Key: AXIS2-128
URL: http://issues.apache.org/jira/browse/AXIS2-128
Project: Apache Axis 2.0 (Axis2)
Type: Test
Versions: 0.91
Environment: Linux(Ubuntu)
78 matches
Mail list logo
