Parameters are not searched in description hierarchy
Key: AXIS2C-218
URL: http://issues.apache.org/jira/browse/AXIS2C-218
Project: Axis2-C
Issue Type: Bug
Reporter: Damitha
[ http://issues.apache.org/jira/browse/AXIS2C-218?page=all ]
Damitha Kumarage reassigned AXIS2C-218:
---
Assignee: Damitha Kumarage
Parameters are not searched in description hierarchy
Remove the old wom dependant code from decription hierarchy.
Key: AXIS2C-219
URL: http://issues.apache.org/jira/browse/AXIS2C-219
Project: Axis2-C
Issue Type: Improvement
[ http://issues.apache.org/jira/browse/AXIS2C-219?page=all ]
Damitha Kumarage reassigned AXIS2C-219:
---
Assignee: Damitha Kumarage
Remove the old wom dependant code from decription hierarchy.
No namespace validation
Key: AXISCPP-988
URL: http://issues.apache.org/jira/browse/AXISCPP-988
Project: Axis-C++
Issue Type: Bug
Reporter: kamlesh
Axis-C++ does not verify that the elements in the
[ http://issues.apache.org/jira/browse/AXIS2C-197?page=all ]
Malinda Kaushalye Kapuruge updated AXIS2C-197:
--
Attachment: cryptoengine.tar
PLease include these files to rampart.
Cheers,
Kaushalye
OMXmlSec - The XML Security library for
[ http://issues.apache.org/jira/browse/AXIS2C-197?page=all ]
Malinda Kaushalye Kapuruge updated AXIS2C-197:
--
Attachment: patch_rampart
Please apply this patch.
Cheers,
Kaushalye
OMXmlSec - The XML Security library for AXIOM [Phase1 :
Hi Guys,
Sorry for the mix up, I've mistaken the *init* method to the
*setOperationContext* method.
The setOperationContext indeed gets called before every business
invocation and I've corrected the comment in the FAQ as well.
However I've got a small issue here. It obviously becomes very unsafe
What exactly you want to do here? Do you want to send a SOAP request
with WS-Addressing enabled?
If yes, the easiest way is to use the ServiceClient api with addressing
enabled (refer the user guide for this)
-- Chinthaka
Shyam Shukla wrote:
Hello All,
I am just started working
[
http://issues.apache.org/jira/browse/AXIS2-758?page=comments#action_12424487 ]
Ajith Harshana Ranabahu commented on AXIS2-758:
---
is this for the latest nightly ?
Generated xmlbeans code is not handling elementFormDefault
When I try to return back a array of objects from my method, I get back an
exception on the server stating
12:24:09,670 ERROR [AxisServlet] java.lang.NoSuchMethodError:
org.apache.axis2.databinding.utils.BeanUtil.getOMElement(Ljavax/xml/namespac
Thanks Chinthaka for your reply.
I've enabled WS-Addressing and have associated in my SOAP Request.
My problem is I want to modify the SOAP Envelop part in the request, by
default axis2 1.0 is referring to
xmlns:wsa=http://www.w3.org/2005/08/addressing; namespace as I have
mentioned in my email
No wait, you don't need to change the source code to do that.
just do the following.
options.setProperty(
org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION,
org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE);
Hope you know how to set the options.
[ http://issues.apache.org/jira/browse/AXIS2-929?page=all ]
Deepal Jayasinghe reassigned AXIS2-929:
---
Assignee: Eran Chinthaka
need to Update the Axiom tutorial to reflect Axiom-1.0.jar (need to made the
examples compile , need to fix the
[ http://issues.apache.org/jira/browse/AXIS2-928?page=all ]
Deepal Jayasinghe reassigned AXIS2-928:
---
Assignee: Eran Chinthaka
Not all added header elements are included in outgoing SOAP header unless run
under debugger - bug in OMElement
[ http://issues.apache.org/jira/browse/AXIS2-919?page=all ]
Deepal Jayasinghe reassigned AXIS2-919:
---
Assignee: Eran Chinthaka
Unable to print out entire SOAP message: bug in OMElement.serialize()
[
http://issues.apache.org/jira/browse/AXIS2-942?page=comments#action_12424491 ]
Deepal Jayasinghe commented on AXIS2-942:
-
I like the idea , but we need to change Handler interface to solve the issue.
Are we in a position to change
[ http://issues.apache.org/jira/browse/AXIS2-943?page=all ]
Deepal Jayasinghe reassigned AXIS2-943:
---
Assignee: Deepal Jayasinghe
Add support for disengagement of modules to administration web frontend
[ http://issues.apache.org/jira/browse/AXIS2-945?page=all ]
Deepal Jayasinghe reassigned AXIS2-945:
---
Assignee: Deepal Jayasinghe
Property clientData in generated CallbackHandler is unaccessible
[ http://issues.apache.org/jira/browse/AXIS2-788?page=all ]
David Illsley closed AXIS2-788.
---
Resolution: Fixed
Confirmed using SVN - seems to have gone away :-)
Outbound MAP EPRs overwritten with values from the response message
[ http://issues.apache.org/jira/browse/AXIS2-741?page=all ]
David Illsley reassigned AXIS2-741:
---
Assignee: David Illsley
Transport error 500 for EchoBlockingDualClient echoF
[
http://issues.apache.org/jira/browse/AXIS2-741?page=comments#action_12424494 ]
David Illsley commented on AXIS2-741:
-
I noticed this the other day doing some addressing interop work and know how it
should work so I've assigned it to me.
[ http://issues.apache.org/jira/browse/AXIS2-939?page=all ]
Deepal Jayasinghe resolved AXIS2-939.
-
Resolution: Fixed
fixed in current SVN
Client API does not remove OperationContext instances from configuration
context after MEP completes
Eran, unfortunately Shyam is looking for the 2004/03 namespace which
the current addressing handlers do not support and if you sets the
WS_ADDRESSING_VERSION property to
http://schemas.xmlsoap.org/ws/2004/03/addressing;, the submission
version is used.
Shyam, if you can move up to a newer
David you got my point I was just going to reply Eran about this point.
Actually, in my current project web services which I have to invoke support
mentioned WSA namespace in this email
i.e.http://schemas.xmlsoap.org/ws/2004/03/addressing; only and I am
required to write a client program to
The AddressingOutHandler shipped with Axis2 (in the addressing module)
which adds the soap headers can be found at [1].
David
[1]
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/addressing/src/org/apache/axis2/handlers/addressing/AddressingOutHandler.java?view=markup
On
[ http://issues.apache.org/jira/browse/AXIS2-917?page=all ]
Deepal Jayasinghe reassigned AXIS2-917:
---
Assignee: Eran Chinthaka
User guide should give explanation and examples of fault handling
[
http://issues.apache.org/jira/browse/AXIS2-850?page=comments#action_12424508 ]
Deepal Jayasinghe commented on AXIS2-850:
-
I fixed this issue few days ago , can you please check whether error is still
there
NullPointerException in
[
http://issues.apache.org/jira/browse/AXIS2-850?page=comments#action_12424511 ]
Michele Mazzucco commented on AXIS2-850:
Deepal, I've tried to download the latest nightly build (July 31st), but maybe
it has some problems since I get a
[ http://issues.apache.org/jira/browse/AXIS2-848?page=all ]
Ruchith Udayanga Fernando resolved AXIS2-848.
-
Resolution: Fixed
Fixed in svn revision : 427078
axiom-dom.jar is not included in the war distribution
I will deploy my service in application scope because I want to have only one
instance of my service running.
The idea of load on startup is the same principle used by a servlet. You set
an option so that when the container starts your application is also started.
Otherwise, your application
Tony,
I am with you on this. There should be a way to do this.
-- dims
On 7/31/06, Tony Dean [EMAIL PROTECTED] wrote:
I will deploy my service in application scope because I want to have only one
instance of my service running.
The idea of load on startup is the same principle used by a
+1 from me Eran
-- dims
On 7/31/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
David Illsley wrote:
Fabien,
If you want access to the SOAPHeader, you can get it through the
MessageContext. You can get this by adding the following method to
your skeleton (I think this works for all
[
http://issues.apache.org/jira/browse/AXIS2-939?page=comments#action_12424541 ]
Thomas Eckoldt commented on AXIS2-939:
--
Fix in OutInAxisOperation works fine, but in AddressingBasedDispatcher the
problem is not resolved.
I think the
Adding Simple Content Extension Support to ADB
--
Key: AXIS2-946
URL: http://issues.apache.org/jira/browse/AXIS2-946
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Reporter:
[ http://issues.apache.org/jira/browse/AXIS2-946?page=all ]
Maryam Moazeni updated AXIS2-946:
-
Attachment: patchfile.txt
SchemaCompiler.java
Attached the svn diff and the modified source code.
Adding Simple Content Extension Support to
Duplicate shema elements in WSDL generated at runtime.
--
Key: AXIS-2534
URL: http://issues.apache.org/jira/browse/AXIS-2534
Project: Apache Axis
Issue Type: Bug
Components:
[ http://issues.apache.org/jira/browse/AXIS2-946?page=all ]
Maryam Moazeni updated AXIS2-946:
-
Attachment: Test5.xsd
Attached the simple XSD that I used.
Adding Simple Content Extension Support to ADB
--
[ http://issues.apache.org/jira/browse/AXIS2-906?page=all ]
Maryam Moazeni updated AXIS2-906:
-
Attachment: ModifiedSrc.zip
Attached the modified source codes.
Adding Complex Content Restriction Support to ADB
Chinthaka
Sounds like a great idea.
Paul
On 7/31/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
David Illsley wrote:
Fabien,
If you want access to the SOAPHeader, you can get it through the
MessageContext. You can get this by adding the following method to
your skeleton (I think this works
Initial scaffolding for Metadata factory, renamed from MDQ
--
Key: AXIS2-947
URL: http://issues.apache.org/jira/browse/AXIS2-947
Project: Apache Axis 2.0 (Axis2)
Issue Type: New
[ http://issues.apache.org/jira/browse/AXIS2-947?page=all ]
Jeff Barrett updated AXIS2-947:
---
Attachment: patch.txt
This patch contains the refactoring of the Description package to use a factory
and removal of the MDQ package, which is replaced the the
Extract and support wsaw:Anonymous values
-
Key: AXIS2-948
URL: http://issues.apache.org/jira/browse/AXIS2-948
Project: Apache Axis 2.0 (Axis2)
Issue Type: Sub-task
Reporter: David Illsley
Adding OneWay and Asynchronous Callback functionality for Dynamic Proxy
Key: AXIS2-949
URL: http://issues.apache.org/jira/browse/AXIS2-949
Project: Apache Axis 2.0 (Axis2)
[ http://issues.apache.org/jira/browse/AXIS2-949?page=all ]
Nikhil Thaker updated AXIS2-949:
Attachment: jaxws_patch_src_7312006.txt
JAXWS Source changes in the attachment.
Adding OneWay and Asynchronous Callback functionality for Dynamic Proxy
[ http://issues.apache.org/jira/browse/AXIS2-949?page=all ]
Nikhil Thaker updated AXIS2-949:
Attachment: jaxws_patch_test_7312006.txt
JAXWS Test Cases for Proxy Async functionality.
Adding OneWay and Asynchronous Callback functionality for Dynamic
[ http://issues.apache.org/jira/browse/AXIS2-885?page=all ]
Brian DePradine updated AXIS2-885:
--
Attachment: newestpatch.txt
In this latest patch I have now removed the code to set the default for the
wsa:To header. I also merged in the latest changes
[
http://issues.apache.org/jira/browse/AXIS-2210?page=comments#action_12424584 ]
Peter Conrey commented on AXIS-2210:
Just add a flag or option to WSDL2Java to allow the CORRECT behavior: reversal
of http:// style namespaces, and as-is use
Thanks Anne,
Now, I think I have the WSDL in the correct way:
xsd:element name=enqueue-image
xsd:complexType
xsd:sequence
xsd:element name=meta-info type=xsd:string/
xsd:element name=image-attachment
xsd:complexType
[
http://issues.apache.org/jira/browse/AXIS2-938?page=comments#action_12424587 ]
Bill Nagy commented on AXIS2-938:
-
(Sorry that I'm a little late to the discussion; I just switched machines and
apparently my mail filtering is screwed up.)
The
[ http://issues.apache.org/jira/browse/AXIS2-885?page=all ]
David Illsley closed AXIS2-885.
---
Resolution: Fixed
Assignee: David Illsley
Resolved with patch applied. r427178
Enhance support for the WS-Addressing anonymous and none URIs
On Mon, 2006-07-31 at 10:41 -0700, Bill Nagy (JIRA) wrote:
(Sorry that I'm a little late to the discussion; I just switched
machines and apparently my mail filtering is screwed up.)
The plugpoint was indeed meant to be PM-agnostic, and I know for a fact
that when Tuscany integrates with
Bill,
If we decide to mode the whole thing into modules/core, then i will
have no problem keeping the methods for migrators and make it similar
to modules, transports, phases etc.
Here's my problem, the Patch does not reflect the intention. If you
check it in as-is right now. Anyone using the
Is there any documentation or tutorials that explains how to use MTOM
with Axis2?
-- Forwarded message --
From: Francisco Fernandez Velasco [EMAIL PROTECTED]
Date: Jul 31, 2006 1:14 PM
Subject: RE: SwA Axis2 implementation swaRef document literal
To: axis-dev@ws.apache.org
Francisco,
Can you please open a JIRA bug report and then upload your complete WSDL?
thanks,
dims
On 7/31/06, Francisco Fernandez Velasco [EMAIL PROTECTED] wrote:
Thanks Anne,
Now, I think I have the WSDL in the correct way:
xsd:element name=enqueue-image
xsd:complexType
Hi Anne, I'm on vacation and lurking. There is a tutorial from axis2
1.0 under the main docs page, but I recently updated it to include a
databinding / wsdl example. That would be in the axis2 svn from about
a week ago and later under xdocs/latest. If you could look at it and
had anything to add
JAXWS: Make server side code use new Message Model APIs
---
Key: AXIS2-950
URL: http://issues.apache.org/jira/browse/AXIS2-950
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
[ http://issues.apache.org/jira/browse/AXIS2-950?page=all ]
Nick Gallardo updated AXIS2-950:
Attachment: 950-patch.txt
A patch containing the fixes/changes mentioned.
JAXWS: Make server side code use new Message Model APIs
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/latest/mtom-guide.html
On 7/31/06, robert lazarski [EMAIL PROTECTED] wrote:
Hi Anne, I'm on vacation and lurking. There is a tutorial from axis2
1.0 under the main docs page, but I recently updated it to include a
databinding /
Dims suggests you have a look at this:
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/latest/mtom-guide.html
On 7/31/06, Francisco Fernandez Velasco [EMAIL PROTECTED] wrote:
Thanks Anne,
Now, I think I have the WSDL in the correct way:
xsd:element name=enqueue-image
Hi dims,
If all you are asking me for is to add calls into the other
MessageReceiver's and the ServiceClient, I'd be happy to do it; I just
didn't have a use case that required that, so didn't want to clutter the
code.
Alternatively I can make it more explicit in the comments that it is up
to
[ http://issues.apache.org/jira/browse/AXIS2-400?page=all ]
Davanum Srinivas reopened AXIS2-400:
Assignee: Davanum Srinivas
I know this is marked as won't fix..i am gonna reopen it to see if there's a
way to set the TCL and keep
Hi Sanjiva,
Unless I'm not explaining it well, the only piece that is different from
what I had described earlier
(http://marc.theaimsgroup.com/?l=axis-devm=115270290506219w=2) is the
interface; there are now two extra methods to make it more clear to
someone who is writing a migrator (or reading
This is a feature I too would use. Another important reason is that in
many services, this initialization is based on configuration paramters.
It'd be nice to see the initialization occur at service startup, so that any
errors are discovered at that point, versus a failed client request.
-Dave
I am officially confused...But let's start with:
- explicit comments as mentioned in your email.
- Please move the methods in AxisConfiguration to ConfigurationContext
as AxisConfiguration is only till deployment.
- Ok to leave the explicit methods, would prefer get/set property till
we get this
[ http://issues.apache.org/jira/browse/AXIS2-947?page=all ]
Rich Scheuerle reassigned AXIS2-947:
Assignee: Rich Scheuerle
Initial scaffolding for Metadata factory, renamed from MDQ
--
[ http://issues.apache.org/jira/browse/AXIS2-950?page=all ]
Rich Scheuerle reassigned AXIS2-950:
Assignee: Rich Scheuerle
JAXWS: Make server side code use new Message Model APIs
---
[ http://issues.apache.org/jira/browse/AXIS2-949?page=all ]
Rich Scheuerle reassigned AXIS2-949:
Assignee: Rich Scheuerle
Adding OneWay and Asynchronous Callback functionality for Dynamic Proxy
JAXWS: Need to remove the calls that are being made to the AxisController
--
Key: AXIS2-951
URL: http://issues.apache.org/jira/browse/AXIS2-951
Project: Apache Axis 2.0 (Axis2)
[ http://issues.apache.org/jira/browse/AXIS2-947?page=all ]
Rich Scheuerle resolved AXIS2-947.
--
Resolution: Fixed
Fixed in latest SVN.
Initial scaffolding for Metadata factory, renamed from MDQ
[ http://issues.apache.org/jira/browse/AXIS2-949?page=all ]
Rich Scheuerle resolved AXIS2-949.
--
Resolution: Fixed
Fixed in latest SVN
Adding OneWay and Asynchronous Callback functionality for Dynamic Proxy
71 matches
Mail list logo
