[
http://issues.apache.org/jira/browse/AXIS-2132?page=comments#action_12316443 ]
xiao-fei song commented on AXIS-2132:
-
just tried ont 1.2.1 on tomcat 5.5, exactly the same excetion thrown.
> WSDL document object generated by AxisServer can not be read
Hi Deepal!
Thanks for the reply. But looks like Srinath already fixed that one.
Bye
Jaya
On 7/22/05, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> can up please build a war file and check , I mean rather than replacing 0.9
> jar.
>
> Thanks,
> Deepal
>
can up please build a war file and check , I mean rather than replacing 0.9
jar.
Thanks,
Deepal
~Future is Open~
- Original Message -
From: "Jayachandra Sekhara Rao Sunkara (JIRA)" <[EMAIL PROTECTED]>
To:
Sent: Thurs
Hi everyone,
As you recall, I'm working on a Google project to develop an XML
binary serializer for Axis2.
I've just started looking at the Axis2 code, and attempting to deploy
a basic web service with it. However, I've started on some basic XML
parsing and serializing, and would like to play ar
Hi Thomasz,
Thanks for the info :)
Jaliya
Tomasz Pik wrote:
On 20/07/05, Jaliya Ekanayake <[EMAIL PROTECTED]> wrote:
Hi Tomasz,
I tired to get the souce code of commons-id, but could not find the svn
repositiory for the above.
The viewcvs is down and no way to get the code.
Here y
Hi Dims,
Yes, let's use the axis 1.X's UUID Generator. In ws-addressing, we have
the jug's uuid generator. That is why I wanted to clarify which one to use.
Thanks,
Jaliya
Davanum Srinivas wrote:
jaliya,
is there a problem in using the uuidgen in axis 1.X? LGPL is a strict no.
-- dims
not a known problem. please dive in.
-- dims
On 7/21/05, Steve Green <[EMAIL PROTECTED]> wrote:
> Developers,
>
> I've just run across another problem with the head of CVS as it pertains
> to W2j. The following xsd snippet is cut down from
> http://www.w3.org/2000/09/xmldsig#
>
>
>
Commiters,
Can someone please have a look at my last comment on AXIS-1753. I know
this is a problem with respect to xsd:groups but I can't say for sure
about other choice members.
~S
Developers,
I've added a feature to SymbolTable and W2j such that it will cache
downloaded imports (and includes) to a directory specified on the
command line (-C ). Subsequent regens will find the cached files
and not have to download them again. This is useful for us since we
sometimes have to
Developers,
I've just run across another problem with the head of CVS as it pertains
to W2j. The following xsd snippet is cut down from
http://www.w3.org/2000/09/xmldsig#
Once upon a time, the bean metadata for the Diges
[
http://issues.apache.org/jira/browse/AXIS-2084?page=comments#action_12316420 ]
Davanum Srinivas commented on AXIS-2084:
Brian,
Applied.
Tom,
Could you please verify latest CVS?
thanks,
dims
> Dime attachements: Type_Length of the final record c
[ http://issues.apache.org/jira/browse/AXIS-2084?page=all ]
Brian Husted updated AXIS-2084:
---
Attachment: DimeBodyPartDiff_2.txt
DimeBodyPart_2.java
dims/Tom,
I ran into this problem as well. I have attached a patch that resolves this
pro
[
http://issues.apache.org/jira/browse/AXIS-2086?page=comments#action_12316413 ]
Lars Olson commented on AXIS-2086:
--
This looks like the same bug as AXIS-1993.
> WSDL2Java and xmldsig
> -
>
> Key: AXIS-2086
> URL: http
[ http://issues.apache.org/jira/browse/AXIS-2135?page=all ]
SPSS updated AXIS-2135:
---
Attachment: castor_serializer_diffs.zip
I have attached diffs as you requested.
Thanks,
Dmitry
> CastorSerializer 1.2/1.2.1 does not handle arrays correctly
> --
[
http://issues.apache.org/jira/browse/AXIS-2135?page=comments#action_12316406 ]
Davanum Srinivas commented on AXIS-2135:
can you please submit a diff against latest CVS? easier to review the changes.
(New files i can get from the zip, that's ok)
t
[ http://issues.apache.org/jira/browse/AXIS-2135?page=all ]
SPSS updated AXIS-2135:
---
Attachment: castor_serializer.zip
Added castor_serializer.zip with updated
org.apache.axis.encoding.ser.castor.CastorSerializer file
The ZIP also includes updated Castor*Factory
CastorSerializer 1.2/1.2.1 does not handle arrays correctly
---
Key: AXIS-2135
URL: http://issues.apache.org/jira/browse/AXIS-2135
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
[ http://issues.apache.org/jira/browse/AXIS-2111?page=all ]
Davanum Srinivas resolved AXIS-2111:
Resolution: Incomplete
closing this bug as Christian has opened other actionable bugs.
thanks,
dims
> Naming Conventions and Code Generation
> ---
[ http://issues.apache.org/jira/browse/AXIS-2112?page=all ]
Davanum Srinivas reassigned AXIS-2112:
--
Assign To: Venkat Reddy
> Problem with Method Implementation of generated Amazon WSDL's
> ---
[ http://issues.apache.org/jira/browse/AXIS-2113?page=all ]
Davanum Srinivas reassigned AXIS-2113:
--
Assign To: Venkat Reddy
> WSDL Generation Does Not Work With Paypal
> -
>
> Key: AXIS-2113
>
[
http://issues.apache.org/jira/browse/AXIS-2119?page=comments#action_12316374 ]
Davanum Srinivas commented on AXIS-2119:
can u try?
http://localhost:8080/RLIproject/services/ResourceListManagementServiceSyncSoap?wsdl
> ?wsdl returns http 500 error
[ http://issues.apache.org/jira/browse/AXIS-2122?page=all ]
Davanum Srinivas resolved AXIS-2122:
Resolution: Fixed
fixed. thx.
-- dims
> WSDL2Java - i18n - JavaWriter.java
> --
>
> Key: AXIS-2122
>
[ http://issues.apache.org/jira/browse/AXIS2-89?page=all ]
Srinath Perera resolved AXIS2-89:
-
Resolution: Fixed
I revert the code .. Sorry my mistake .. forget that I change it among other
commits
> NPE in AxisServlet
> --
>
>
[ http://issues.apache.org/jira/browse/AXIS2-76?page=all ]
Srinath Perera resolved AXIS2-76:
-
Resolution: Fixed
set to MessageContext agiest the property MessageContext .TRANSPORT_HEADERS
> Need for HTTP HEADER information
> ---
[
http://issues.apache.org/jira/browse/AXIS-2121?page=comments#action_12316364 ]
Thilo Frotscher commented on AXIS-2121:
---
I investigated further on this issue and found out the following. In my case,
the real trouble occurs in class SOAPFaultBuilder.
ManagedMemoryDataSource does not correctly handle large attachments
---
Key: AXIS-2134
URL: http://issues.apache.org/jira/browse/AXIS-2134
Project: Apache Axis
Type: Bug
Components: Serialization/Deser
[
http://issues.apache.org/jira/browse/AXIS-2133?page=comments#action_12316362 ]
Jihong Jin commented on AXIS-2133:
--
As mentioned in the bug report, it is for AXIS 1.2RC3.
The NPE is originated in BeanPropertyDescriptor line 127 as I listed before,
when B
[ http://issues.apache.org/jira/browse/AXIS2-37?page=all ]
Srinath Perera resolved AXIS2-37:
-
Resolution: Fixed
Fixed, if I have miss some strings pls replace them .. and in the futrue
preserve i18n with the code chaneges
> Internationalization Su
[
http://issues.apache.org/jira/browse/AXIS-2132?page=comments#action_12316359 ]
Davanum Srinivas commented on AXIS-2132:
did you try Axis 1.2.1 which is the latest?
-- dims
> WSDL document object generated by AxisServer can not be read successfull
[
http://issues.apache.org/jira/browse/AXIS-2133?page=comments#action_12316358 ]
Davanum Srinivas commented on AXIS-2133:
can you please post the whole stack trace? AND are u using Axis 1.2.1? it's
probably fixed by now.
-- dims
> NullPointerExcep
NullPointerException on Java Bean serialization when Java Bean is null
--
Key: AXIS-2133
URL: http://issues.apache.org/jira/browse/AXIS-2133
Project: Apache Axis
Type: Bug
Components: Serialization
Hello,
I'm quite pleased that I can now use end-end XSD/POJOs with Axis 1.3 via
XmlBeans!
However, the manual method of specifying your [de]serializers imposed by
Axis makes this power virtually impossible to wield. Just think of a
large collection of quickly evolving XSD documents and havin
Mark,
the code is based on the code in beehive. can u please check if they
have any updates that will help us?
http://svn.apache.org/repos/asf/incubator/beehive/trunk/wsm/src/axis/org/apache/beehive/wsm/axis/util/encoding/
thanks,
dims
On 7/21/05, Mark Swanson <[EMAIL PROTECTED]> wrote:
> There
There were two problems:
XmlBeans.typeForClass(javaType) creates a SchemaType with a QName of
null for Anonymous types. This is fine. However, the QName is required
to get the XmlObject. So I just parsed the anonymous type to get its
QName and that works fine.
Because the QName may be null o
establishing one public repository for sharing Axis2 Modules
Key: AXIS2-90
URL: http://issues.apache.org/jira/browse/AXIS2-90
Project: Apache Axis 2.0 (Axis2)
Type: Wish
Environment: n/a
Reporter: Joer
[ http://issues.apache.org/jira/browse/AXIS-1764?page=all ]
Mark Swanson updated AXIS-1764:
---
Attachment: XmlBeanSerializer.java
The previous version didn't handle anonymous types correctly (QName == null).
> Add an XmlBean Serializer and Deserializer to A
[
http://issues.apache.org/jira/browse/AXIS-2078?page=comments#action_12316350 ]
Revanth Thoutireddy commented on AXIS-2078:
---
Hi Dims,
You are right. The xml should not hold null dates. I tried without the dates
and there are no errors being thro
[
http://issues.apache.org/jira/browse/AXIS-2126?page=comments#action_12316349 ]
neal neal commented on AXIS-2126:
-
Ok that is the best answer you could have given me, Srinivas...for that helped
me spot the issue and solve it :)
What I did immediately on
[
http://issues.apache.org/jira/browse/AXIS-2122?page=comments#action_12316347 ]
David Brandow commented on AXIS-2122:
-
I attached a proposed fix, which is based on the implementation of
JavaDeployWriter's getPrintWriter() method.
> WSDL2Java - i18n -
[ http://issues.apache.org/jira/browse/AXIS-2122?page=all ]
David Brandow updated AXIS-2122:
Attachment: JavaWriter.java
Proposed fix (very simple)
> WSDL2Java - i18n - JavaWriter.java
> --
>
> Key: AXIS-2122
>
[
http://issues.apache.org/jira/browse/AXIS2-12?page=comments#action_12316343 ]
Joerg Buchberger commented on AXIS2-12:
---
- Javolution and
- JiBX
both seem to be a lot faster than all the others (see
http://bindmark.dev.java.net/ )
both also share th
[
http://issues.apache.org/jira/browse/AXIS2-77?page=comments#action_12316341 ]
Joerg Buchberger commented on AXIS2-77:
---
Does this help?
http://www.ietf.org/rfc/rfc4122.txt
contains a sample implementation in appendix
> Need a UUID Generator with Axi
[
http://issues.apache.org/jira/browse/AXIS-2084?page=comments#action_12316338 ]
Tom Ziemer commented on AXIS-2084:
--
Hi,
I was using Axis 1.2 Final on our server in cobination with a) an axis client
and b) a .NET (2.0 Beta) client to send attachments. Wi
Gayan,
we should have a full soapbuilders test suite (all tests) using AXIOM.
To guarantee everyone that you can do what you want by dropping down
to the bottom most later.
for data-binding based test suite, yes, we can start with doc/lit
wsdl's for now till we get some code gen support for other
NPE in AxisServlet
--
Key: AXIS2-89
URL: http://issues.apache.org/jira/browse/AXIS2-89
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: core
Environment: Tomcat5.0 servlet container
Reporter: Jayachandra Sekhara Rao Sunkara
Priority
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
Thanks Deepal,
Actually I've requested for a work around to register the custom
message receiver. (I've looked into example version service and that
didn't help me). Since there wasn't any reply I've patched it today
morning, thinking the feature might not be there. I was mistaken. But
now, I'd us
Hi jaya
It is already there no need to re-implement it , as you have said if a
operation tag dose not contains a MessageRecievr then the default one
RowXMLInoutMessageReceiver will be the message receiver for the operation.
We encounter this kind of problem since we are lack of documentation.
Hi Jaya;
It is already there in Axis2 , you can register MessageReceiver per
operation basis and the required xml element for the service.xml will look
like follows;
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
Thanks,
Deepal
..
[ http://issues.apache.org/jira/browse/AXIS2-88?page=all ]
Deepal Jayasinghe resolved AXIS2-88:
Fix Version: 0.9
Resolution: Fixed
It is already there and the way of registering custom messageReceiver as follows
We
[
http://issues.apache.org/jira/browse/AXIS2-88?page=comments#action_12316320 ]
Jayachandra Sekhara Rao Sunkara commented on AXIS2-88:
--
Deepal!
If the above description looks valid, have a look at my tiny patch that does
the job. If tha
[ http://issues.apache.org/jira/browse/AXIS2-88?page=all ]
updated AXIS2-88:
--
Attachment: RegisterMessageReceiver.patch
> Support for registering custom MessageReceiver for an operation
> ---
>
> Key
52 matches
Mail list logo
