[
https://issues.apache.org/jira/browse/AXIS2C-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dushshantha Chandradasa resolved AXIS2C-687.
Resolution: Fixed
Provide correct configure options for samples in
[
https://issues.apache.org/jira/browse/AXIS2C-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-678.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Samisa Abeysinghe
I
[
https://issues.apache.org/jira/browse/AXIS2C-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-522.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Samisa Abeysinghe
I
[
https://issues.apache.org/jira/browse/AXIS2C-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-685.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Samisa Abeysinghe
[
https://issues.apache.org/jira/browse/AXIS2C-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-664.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Samisa Abeysinghe
[
https://issues.apache.org/jira/browse/AXIS2C-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-154.
--
Resolution: Won't Fix
We have retired Woden code. So it is unlikely that this feature
[
https://issues.apache.org/jira/browse/AXIS2C-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-519.
--
Resolution: Won't Fix
We have retired Woden code. Hence it is unlikely that we would
[
https://issues.apache.org/jira/browse/AXIS2C-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-232.
--
Resolution: Won't Fix
We have retired woden code. Hence this would not be fixed in the
[
https://issues.apache.org/jira/browse/AXIS2C-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-228.
--
Resolution: Won't Fix
Assignee: (was: Dushshantha Chandradasa)
We have
[
https://issues.apache.org/jira/browse/AXIS2C-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-210.
--
Resolution: Won't Fix
Assignee: (was: Sanjaya Ratnaweera)
We have retired
[
https://issues.apache.org/jira/browse/AXIS2C-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-211.
--
Resolution: Won't Fix
We have retired XML/Schema implementation. Hence would not fox
[
https://issues.apache.org/jira/browse/AXIS2C-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524701
]
Clifford Audinet commented on AXIS2C-519:
-
Well that is certainly disappointing. Thanks for letting me
[
https://issues.apache.org/jira/browse/AXIS2C-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-201.
--
Resolution: Won't Fix
We have retired Woden and XML Schema implementations. Hence this
[
https://issues.apache.org/jira/browse/AXIS2C-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-295.
--
Resolution: Won't Fix
We have retired Woden and XML Schema implementations. Hence this
[
https://issues.apache.org/jira/browse/AXIS2C-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-677.
--
Resolution: Won't Fix
We have discussed on the mailing list on how to live without
[
https://issues.apache.org/jira/browse/AXIS2C-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-669.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Damitha has fixed this issue
In
[
https://issues.apache.org/jira/browse/AXIS2C-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-660.
--
Resolution: Fixed
Manjula have provided insight as to what libs and files are
[
https://issues.apache.org/jira/browse/AXIS2C-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-600.
--
Resolution: Fixed
Fix Version/s: 1.1.0
The latest code have fixed many of the
[
https://issues.apache.org/jira/browse/AXIS2C-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-540.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Accrding to test results by Evanthinka,
[
https://issues.apache.org/jira/browse/AXIS2C-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524972
]
Samisa Abeysinghe commented on AXIS2C-420:
--
Have anybody done anything to support more data types?
No
hello there,
I have uploaded the Mail Transport sender part which I developed at
Google.It is here[1].
I will continue my work to implement the Mail Transport Receiver as well.
[1] -
http://google-summer-of-code-2007-asf.googlecode.com/files/Rajika_Kumarasiri.tar.gz
Thanks
Rajika
[
https://issues.apache.org/jira/browse/AXIS2C-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-483.
--
Resolution: Won't Fix
We have retired Woden and XML Schema implementations. Hence this
[
https://issues.apache.org/jira/browse/AXIS2C-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-428.
--
Resolution: Cannot Reproduce
:( Cannot fix it without being able to re-produce
[
https://issues.apache.org/jira/browse/AXIS2C-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-462.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Looks like the samples have been updated
[
https://issues.apache.org/jira/browse/AXIS2C-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-477.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Samisa Abeysinghe
[
https://issues.apache.org/jira/browse/AXIS2C-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandika Jayawardana resolved AXIS2C-633.
Resolution: Fixed
util.c is now added to the vc project and it builds fine.
we
Rajika
The normal way of donating code to a project is to create a JIRA and
then attach the code to the JIRA. At the time you do this, you must
tick the box which says that you grant a license to Apache.
Thanks
Paul
On 9/5/07, Rajika Kumarasiri [EMAIL PROTECTED] wrote:
hello there,
I have
[
https://issues.apache.org/jira/browse/AXIS2-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524670
]
Deepal Jayasinghe commented on AXIS2-2996:
--
Thx for the patch I will apply that today , once Amila fix the
Hello Amila,
Sorry, but this still doesn't work. I get the same error as before, as
shown below. I think there may be an
extra slash before the drive letter, F: in this case, that probably
shouldn't be there.
Running org.apache.axis2.xmlbeans.WSDL2Java1Test
Retrieving schema at 'wsat.xsd',
Hi
Here is the SOAP-trace:
HTTP/1.1 200 OK Content-Type: text/xml;charset=utf-8 Date: Tue, 04 Sep 2007
11:10:43 GMT Server: Apache-Coyote/1.1 Connection: close
soapenv:Body
GMDSRESPCT xmlns=
CONTENT xsi:type=xsd:byte xmlns=37/CONTENT
CONTENT xsi:type=xsd:byte xmlns=80/CONTENT
Hello
I am trying the example from this link :
http://www.ibm.com/developerworks/webservices/library/ws-castor/
And I get the following error :
org.xml.sax.SAXException:
Unable to marshall between XML and Castor Objects :unable to find
FieldDescriptor for 'DOC_ID' in ClassDescriptor of
[
https://issues.apache.org/jira/browse/AXIS2-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524705
]
Nikolaus Krismer commented on AXIS2-3164:
-
same problem here
...i run the wsdl2java operation using ANT:
[
https://issues.apache.org/jira/browse/AXIS2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524713
]
Patrik Nordwall commented on AXIS2-1820:
setAllowedRetry doesn't work for me with basic auth and xmlbeans.
Thanks, it's fixed now.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
Deepal jayasinghe [EMAIL PROTECTED] wrote on
Maciej,
Currently there are a few problems with doing this. Lets identify the issues
a) We create a new connection for each invocation (sending messages)
b) Hence we create a new session for each invocation.
c) When creating a session for receiving as well as sending transacted is
set to true -
Hi
Generally, only standard xml-schema-data types are
being provided out of the box. The easy way to do it
is to break it up into standard data types. Else I'm
sure IBM is selling some serializing support for its
special data types.
Cheers
--- Thomas Beaujard [EMAIL PROTECTED] wrote:
Hello
I
Good Day,
This is regarding a doubt we have about the coexistence of the older
version of Axis and the Axis2 in the Weblogic server
Some application which are deployed in Weblogic server are using old
version of Axis like axis1_4, now we are doing an enhancement which
needs to use only
Yes, they should work together. Please use the newer version of wsdl4j
jar in axis2 instead of the one on Axis1.
thanks,
dims
On 9/4/07, Rajesh, Peter (CLAIMS, WIP) [EMAIL PROTECTED] wrote:
Good Day,
This is regarding a doubt we have about the coexistence of the older version
of Axis and
Rajith,
Your take appears to be based on the assumption that AXIS is communicating
with the JMS provider directly (that is outside of a managed environment).
In a managed environment the connection/session creation would not be an
issue since these would be pooled objects, with automatic
Thanks. But for example the YearMonth class package is
org.apache.axis.types in Axis 1 the package in Axis2 is
org.apache.axis2.databinding.types
We have used the YearMonth in Axis1 in our source file, so if we copy
the axis jar file from Axis2 will it not create ambiguity?
Thanks Regards,
On 9/4/07, Maciej Szefler [EMAIL PROTECTED] wrote:
Rajith,
Your take appears to be based on the assumption that AXIS is communicating
with the JMS provider directly (that is outside of a managed environment).
In a managed environment the connection/session creation would not be an
issue
-- Forwarded message --
From: Sushil Dodake [EMAIL PROTECTED]
Date: Sep 4, 2007 6:49 PM
Subject: AXIS2 : Help required : getting a zip file using AXIS2 + AXIOM
To: axis-dev@ws.apache.org
-- Forwarded message --
From: Sushil Dodake [EMAIL PROTECTED]
Date: Sep 4,
-- Forwarded message --
From: Sushil Dodake [EMAIL PROTECTED]
Date: Sep 4, 2007 6:47 PM
Subject: Re: Help required : getting a zip file using AXIS2 + AXIOM
To: Thilina Gunarathne [EMAIL PROTECTED]
Hi,
Thanks you very much for a very prompt reply..
I have also sent this mail to the
Axis2, GSoap, and Character Sets
Key: AXIS2-3167
URL: https://issues.apache.org/jira/browse/AXIS2-3167
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: transports
Affects Versions: 1.3
On 9/5/07, Rajesh, Peter (CLAIMS, WIP) [EMAIL PROTECTED] wrote:
Thanks. But for example the YearMonth class package is
org.apache.axis.types in Axis 1 the package in Axis2 is
org.apache.axis2.databinding.types
We have used the YearMonth in Axis1 in our source file, so if we copy
the axis
[
https://issues.apache.org/jira/browse/AXIS2-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524980
]
Amila Chinthaka Suriarachchi commented on AXIS2-3164:
-
can you generate the code with -u option
46 matches
Mail list logo