Personally, I would love it if this was fixed! But I don't think turning
off WSA is enough. I set the
org.apache.axis2.Constants.Configuration.DISABLE_ADDRESSING_FOR_OUT_MESSAGES
message property for outgoing messages, and it did not help. It seems
certain clients (dotNET and AXIS2) need the x
An option to specify the soapAction of an operation in the services.xml
---
Key: AXIS2-480
URL: http://issues.apache.org/jira/browse/AXIS2-480
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Com
H...Too bad...
It seems the content-types generated by the two implementations are not interoperable.. Did you try using SUN Mail in both the client and server sides.
>The relevant Content-Type header valueis;>multipart/related;>boundary=MIMEBoundaryurn:uuid:F02ECC18873CFB73E21141271292
Thanks. It seems that AxisServiceBuilder can do the
job.
Raymond
- Original Message -
From:
[EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Wednesday, March 01, 2006 7:58
PM
Subject: Re: [AXIS2] Can AxisService be
constructed from WSDL4J objects (Definitionor
Hi Folks,
I encountered a somewhat critical situation, where if we use Sun's
JavaMail API implementation, instead of Geronimo's JavaMail API
implementation, parsing of MIME Encoded messages fails. The initial
failure occurs in the javax.mail.internet.ContentType class, where we
pass in the Content-
Hi
You may refer to sample applications
provided by Axis for dynamic invocation of webservices.
Regards
Gaurav Bansal
Tata Consultancy Services Limited
India
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com
"Raymond Feng"
<[EMAIL PROTECTED]>
03/02/2006 07:09 AM
Please respond to
ax
If AttachmentUtil is based on WOM and ServiceBuilder has nothing to do
with WOM, that means AttachmentUtil logic is replicated in
ServiceBuilder .. we should have AttachmentUtil marked for refactoring
Srinath
On 3/1/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> On Wed, 2006-03-01 at 16:06 -
On Wed, 2006-03-01 at 10:57 -0800, Simon Fell wrote:
> So your basic message is interop doesn't matter ? Doesn't seem right to
> me.
Not at all Simon .. come on ;-).
But +1 to fixing it now; its a trivial fix too.
Sanjiva.
On Wed, 2006-03-01 at 16:10 -0500, Srinath Perera wrote:
> > The logic is already there in the stubs which we generate given a WSDL
> > with policy attachment. We need to move that to ServiceClient.
> Can you point me to the code that implement the logic? (That is the Q
> I want answer for when I
On Wed, 2006-03-01 at 16:06 -0500, Srinath Perera wrote:
> > > then there is PolicyAttachmentUtil which is related
> > Its already used by AxisServiceBuilder isn't it??
> No, it is based on WOM, and used by code generation modules
>
> In my mail *it* means PolicyAttachmentUtil not AxisServiceBuild
[ http://issues.apache.org/jira/browse/AXIS2-475?page=all ]
Eran Chinthaka resolved AXIS2-475:
--
Resolution: Duplicate
Duplicates Axis2-476
> Remove unused HostConfiguration element from axis2.xml
> -
[
http://issues.apache.org/jira/browse/AXIS-2147?page=comments#action_12368430 ]
Dies Koper commented on AXIS-2147:
--
Axis 1.3
> Axis does not recognize IP v7 format of "0:0:0:0:0:0:0:1" as localhost
> causing deploy problem.
>
Hi,
I have the WSDLs loaded by WSDL4J. Is there any way
to construct/populate the "org.apache.axis2.description.AxisService" using the
WSDL4J objects so that we can drive the client invocation dynamically?
Thanks,
Raymond
Hi Sanka;
> > I think what you need to do is write some logic in ServiceClient
> > (ConfigContext, AxisService) to engage the right stuff based on policies
> > in the AxisService.
> +1
>
> The logic is already there in the stubs which we generate given a WSDL
> with policy attachment. We need to m
> > then there is PolicyAttachmentUtil which is related
> Its already used by AxisServiceBuilder isn't it??
No, it is based on WOM, and used by code generation modules
In my mail *it* means PolicyAttachmentUtil not AxisServiceBuilder.
Will talk ti Sanka :)
Srinath
On 2/28/06, Deepal Jayasingh
Hi Justin,
> On the topic, I have managed to trace the root cause of the problem. It
> seems to
> be as simple as switching from WSA off - using an inline filter to remove WSA
> headers and change types to xsi: works perfectly with .NET clients. Is there
> any
> way to turn off WSA in axis2?
[
http://issues.apache.org/jira/browse/AXIS2-455?page=comments#action_12368337 ]
Davanum Srinivas commented on AXIS2-455:
I think we need to fix this issue for the next release.
> Axis2 dotNET interoperability problem with abstract types.
>
So your basic message is interop doesn't matter ? Doesn't seem right to
me.
Cheers
Simon
-Original Message-
From: Deepal Jayasinghe (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 01, 2006 12:23 AM
To: axis-dev@ws.apache.org
Subject: [jira] Commented: (AXIS2-455) Axis2 dotNET in
Hey a happy user :).
Ajith, I also hate the fact that we generate RemoteException .. I don't
see the point! So I'd be +1 for removing them for sure - when someone
asks for JAX-WS stubs then we can but we don't need to do them for the
normal stuff.
Sanjiva.
--- Begin Message ---
I took a shot at i
[
http://issues.apache.org/jira/browse/AXIS-2150?page=comments#action_12368300 ]
Nils Hammar commented on AXIS-2150:
---
I have found out a workaround and that is to have a class load the Axis
functionality in a separate jar-file that resides in common/endor
You need to map the Axis servlet as defined
in your web.xml to the location you want the endpoints to appear.
In your case “/gns-jaxrpc”.
You should also set the wsdlServicePort to be “gns”.
I believe that will give you the endpoint
you are looking for.
Tom Jordahl
Adobe Server
[ http://issues.apache.org/jira/browse/AXIS2-478?page=all ]
Deepal Jayasinghe resolved AXIS2-478:
-
Fix Version: 0.95
Resolution: Fixed
removed all the default chain stuff
> Remove setting of default chains and message receivers in default
[
http://issues.apache.org/jira/browse/AXIS-2150?page=comments#action_12368255 ]
Bernier commented on AXIS-2150:
---
Hi,
I'm working on a Portal project with some webservices integrations on Sun One
Web servers and App servers and I also face this issue.
I confi
[
http://issues.apache.org/jira/browse/AXIS2-455?page=comments#action_12368248 ]
Justin Schoeman commented on AXIS2-455:
---
Well, I don't know if it is blocker, or not, but interoperability _is_ fairly
important for a webservices platform...
On the top
Axis2 does not deserialise abstract types correctly when receiving WSA messages
---
Key: AXIS2-479
URL: http://issues.apache.org/jira/browse/AXIS2-479
Project: Apache Axis 2.0 (Axis2)
Type: B
[ http://issues.apache.org/jira/browse/AXIS2-186?page=all ]
Deepal Jayasinghe resolved AXIS2-186:
-
Resolution: Fixed
Fixed by introduction of ServiceClient and OperationClie
> Faults are not handled correctly in NonBlocking two channel scenerio
[ http://issues.apache.org/jira/browse/AXIS2-286?page=all ]
Deepal Jayasinghe reassigned AXIS2-286:
---
Assign To: Afkham Azeez
Can you please reduce the priority , this is not a blocker for next relase
> getOwnerDocument of SOAPHeader returns null
[
http://issues.apache.org/jira/browse/AXIS2-427?page=comments#action_12368239 ]
Deepal Jayasinghe commented on AXIS2-427:
-
This is not a blocker for next release :) , and I can not understand the
requirement of ServiceFactory, because creating a Ax
[ http://issues.apache.org/jira/browse/AXIS2-449?page=all ]
Deepal Jayasinghe resolved AXIS2-449:
-
Fix Version: 0.95
Resolution: Fixed
I tested in different ways and I couldn't able to re-generate the problem. I am
sure that meta-inf file
Change the SkeletonTemplate to throw UnsupportedMethodException
Key: AXIS2-474
URL: http://issues.apache.org/jira/browse/AXIS2-474
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Deepal Jayasi
[
http://issues.apache.org/jira/browse/AXIS2-455?page=comments#action_12368233 ]
Deepal Jayasinghe commented on AXIS2-455:
-
I don't think this is a blocker for next release , I know that fact that we
have to fix the issue but I don wont this to be t
Remove setting of default chains and message receivers in default constructor
of AxisConfiguration
--
Key: AXIS2-478
URL: http://issues.apache.org/jira/browse/AXIS2-478
Project:
Remove ServiceContext.setImplementationObject and just use a property for that
--
Key: AXIS2-477
URL: http://issues.apache.org/jira/browse/AXIS2-477
Project: Apache Axis 2.0 (Axis2)
Type: Wis
[ http://issues.apache.org/jira/browse/AXIS2-466?page=all ]
Deepal Jayasinghe updated AXIS2-466:
Summary: Split the core code into secured classes to make it so that users
can't see all the internal stuff (was: Split the core code into secured
clas
Remove unused hostConfiguration from axis2.xml
--
Key: AXIS2-476
URL: http://issues.apache.org/jira/browse/AXIS2-476
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Reporter: Deepal Jayasinghe
There is an element c
Remove unused HostConfiguration element from axis2.xml
--
Key: AXIS2-475
URL: http://issues.apache.org/jira/browse/AXIS2-475
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Reporter: Deepal Jayasinghe
Fi
36 matches
Mail list logo
