Forwarding with the Axis2 prefix. I nearly missed it :)
BTW I guess these changes are done by Dims and Thilina for MTOM
compatibility so I guess they are the best people to test what went
wrong here :)
On 9/6/06, Chuck Williams <[EMAIL PROTECTED]> wrote:
Hi Dims and Ajith,
I believe you guys ad
[ http://issues.apache.org/jira/browse/AXIS2-1115?page=all ]
Nikhil Thaker updated AXIS2-1115:
-
Attachment: JIRA_1115_DescriptionChanges.txt
This is the fix for the JIRA issue.
> Error while creating multiple instance of same service on same thread.
>
[
http://issues.apache.org/jira/browse/AXIS2-1116?page=comments#action_12433011 ]
Davanum Srinivas commented on AXIS2-1116:
-
#1 is already fixed. please try a nightly.
> WSDL2Java with Xmlbeans binding is not generating classes for all s
Hi all,
what plans does the Axis2 community have regarding XmlSchema and Axiom
releases for the next release of Axis2 proposed for later this month?
At the weekly Woden chat we discussed doing a milestone release of
Woden in time for the next Axis2 release, but as Woden depends on
XmlSchema and Ax
Fernando,
Thank you for sharing with the example.
Actually, I am looking for more than just adding permission to the policy file. I would like AXIS2 to have doPrivilege when a call stack (applet) needs a permission.
Sincerely,
Ming Cheung
WebSphere Web Services Developer
Address: IBM, Inc. 1
WSDL2Java with Xmlbeans binding is not generating classes for all schema
Key: AXIS2-1116
URL: http://issues.apache.org/jira/browse/AXIS2-1116
Project: Apache Axis 2.0 (Axis2)
[ http://issues.apache.org/jira/browse/AXIS2-1089?page=all ]
Davanum Srinivas resolved AXIS2-1089.
-
Resolution: Fixed
Fixed in latest SVN. got your wsdl working as is in the files.zip that you
uploaded.
thanks,
dims
> WSDL2Java is generating inval
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12432945 ]
Derek Foster commented on AXIS2-919:
For closing this bug (and getting Axis 1.1 out the door), I don't care if
Iterator-related interface changes are made. I th
Error while creating multiple instance of same service on same thread.
--
Key: AXIS2-1115
URL: http://issues.apache.org/jira/browse/AXIS2-1115
Project: Apache Axis 2.0 (Axis2)
Thanks so much!!!
Looking at the combination of the Installation and User's Guide for Axis 1.2,
the dependencies seem to be:
commons-discovery
commons-logging
jaxrpc
saaj
log4j-1.2.8
wsdl4j
xml-apis
xercesImpl
What has changed for 1.3? What are the minimum versions?
-Katie
-Original Messa
[ http://issues.apache.org/jira/browse/AXIS2-1114?page=all ]
Nikhil Thaker updated AXIS2-1114:
-
Attachment: JIRA_1114_Proxy_support_for_NULL.txt
Heres the patch for the JIRA.
> Adding support to handle NULL object in Proxy
>
Adding support to handle NULL object in Proxy
-
Key: AXIS2-1114
URL: http://issues.apache.org/jira/browse/AXIS2-1114
Project: Apache Axis 2.0 (Axis2)
Issue Type: New Feature
Components: j
> Can Axis 1.3 be used with JDK 1.3?
Yes.
➢ Additionally, what versions of Axis dependencies are needed?
Can you clarify the question?
Tom Jordahl
[
http://issues.apache.org/jira/browse/AXIS2-?page=comments#action_12432878 ]
Eran Chinthaka commented on AXIS2-:
---
Hi Jochen,
I didn't want to make the life difficult for whoever implement something. Sorry
if my comment made you
[ http://issues.apache.org/jira/browse/AXIS2-1089?page=all ]
Davanum Srinivas updated AXIS2-1089:
Priority: Blocker (was: Major)
> WSDL2Java is generating invalid inner class, method with XmlBeans binding
> --
[ http://issues.apache.org/jira/browse/AXIS2-1082?page=all ]
Davanum Srinivas updated AXIS2-1082:
Priority: Blocker (was: Major)
> digest authentication is not working
>
>
> Key: AXIS2-1082
>
[ http://issues.apache.org/jira/browse/AXIS2-1081?page=all ]
Davanum Srinivas updated AXIS2-1081:
Priority: Blocker (was: Major)
> Basic Authentication should not be tried before NTLM authentication
>
[ http://issues.apache.org/jira/browse/AXIS2-1096?page=all ]
Afkham Azeez closed AXIS2-1096.
---
Fixed. Added this method to org.apache.axis2.saaj.SOAPElementImpl
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
> --
[ http://issues.apache.org/jira/browse/AXIS2-1096?page=all ]
Afkham Azeez resolved AXIS2-1096.
-
Resolution: Fixed
Fixed. Added this method to org.apache.axis2.saaj.SOAPElementImpl
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
>
[ http://issues.apache.org/jira/browse/AXIS2-1096?page=all ]
Afkham Azeez updated AXIS2-1096:
Assignee: Afkham Azeez
Fixed. add this method to org.apache.axis2.saaj.SOAPElementImpl
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
> ---
[
http://issues.apache.org/jira/browse/AXIS2-548?page=comments#action_12432836 ]
Rajith Attapattu commented on AXIS2-548:
Deepal,
Better to close this as we are taking a different approach now.
So the documentation is going to change
Re
Hi Deepal,The best practice is to put the wsdl file into service archive file .
100% correct. Wouldn't it be cool to generate ?wsdl/?xsd if MR is *RPCMessageReceiver, when the service object supplier is "ServiceObjectSupplier"
>> Current Axis-spring module has SpringAppContextAwareObjectSupplier an
[
http://issues.apache.org/jira/browse/AXIS2-?page=comments#action_12432816 ]
Jochen Wiedmann commented on AXIS2-:
I believe, that modules inside modules are fine in this particular case:
Obviously, it makes sense to use a specia
[
http://issues.apache.org/jira/browse/AXIS2-1113?page=comments#action_12432799 ]
Deepal Jayasinghe commented on AXIS2-1113:
--
In Axis2 we do not have method call invokeOneWay in service client ?
I think this is an Axis 1.x bug ?
> If ca
[ http://issues.apache.org/jira/browse/AXIS2-1112?page=all ]
Deepal Jayasinghe resolved AXIS2-1112.
--
Resolution: Fixed
fixed in the current SVN
> Ant Task generates reference to Skeleton Class instead of SkeletonInterface
> for InOnly binding
> --
[
http://issues.apache.org/jira/browse/AXIS2-?page=comments#action_12432796 ]
Eran Chinthaka commented on AXIS2-:
---
Jochen, this contains modules inside this. So once we add this to Axis2 it will
becomes modules inside modules.
Do y
Saminda Abeyruwan wrote:
> Hi Robert,
>
> Earlier, when "ServiceObjectSupplier" is given {even if Spring} you
> have to expose the available operations via . If not at
> the deployment time when creating the AxisService, it will not pick up
> the operations for that service.
Well specifying the
[jira] Created: (AXIS2-1102) schema generation for .aar when ServiceObjectSupplier given with *RPCMessagaReceiverThank youSaminda On 9/6/06,
Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
Hi Robert,Earlier, when "ServiceObjectSupplier" is given {even if Spring} you have to expose the available oper
Hi Robert,Earlier, when "ServiceObjectSupplier" is given {even if Spring} you have to expose the available operations via . If not at the deployment time when creating the AxisService, it will not pick up the operations for that service.
Now assume [thinking only in Spring] you have 20 public meth
[
http://issues.apache.org/jira/browse/AXIS2-?page=comments#action_12432778 ]
Jochen Wiedmann commented on AXIS2-:
> I hope Axis2 project itself will move to maven2 as its build system.
Gimme time. :-) As a first step, you could
If callObjec.invokeOneWay() is being used for a huge data transfer, client side
system is encountering Socket create exception
--
Key: AXIS2-1113
31 matches
Mail list logo