I believe that it is pretty similar to aar files - a jar with a
well-known descriptor in it see [1].
Also, the rahas mar file includes some dependant jars in a /lib
directory within the mar.
Does anyone else know if I've missed anything?
David
[1] http://ws.apache.org/axis2/1_1/Axis2Architectur
FWIW, i prefer "1.2-SNAPSHOT" (not just "SNAPSHOT")
-- dims
On 11/22/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
Chamikara Jayalath wrote:
> Could u please explain a bit more. What do u think the version of the 'trunk'
should be ?
> (until we move to maven 2)
What's wrong with "1.2-SNAPSH
Eran,
Is this same as this?
http://issues.apache.org/jira/browse/WSCOMMONS-94
Toshiro TAKASE
IBM Research, Tokyo Research Laboratory, Internet Technology
notes ID: Toshiro Takase/Japan/[EMAIL PROTECTED], e-mail: [EMAIL PROTECTED]
"Sameera Madushan" <[EMAIL PROTECTED]> wrote on 2006/11/22
15:02:1
Forgot to reply to axis-dev as well.
-- Forwarded message --
From: Jochen Wiedmann <[EMAIL PROTECTED]>
Date: Nov 22, 2006 7:23 AM
Subject: Re: [Axis2] Maven2 plugin for mar building?
To: David Illsley <[EMAIL PROTECTED]>
Cc: axis-dev@ws.apache.org
Hi, David,
On 11/22/06, David
Chamikara Jayalath wrote:
Could u please explain a bit more. What do u think the version of the 'trunk'
should be ?
(until we move to maven 2)
What's wrong with "1.2-SNAPSHOT" (Maven convention) or "1.2-dev",
which Jakarta used to have? I believe we agree, that subsequent 1.1.x
versions won't
Sanjiva Weerawarana wrote:
Is it completely done? I remember we had problems with docs etc. - those
need to be fully fixed to be able to move to m2.
It is definitely *not* completely done. There aren't even yet POM
files for all modules, as the rare time I have for Axis 2 is spent for
playing
Hi, David,
On 11/22/06, David Illsley <[EMAIL PROTECTED]> wrote:
I'm looking forward to moving to Maven2 for builds but my
understanding is that we need to define a packaging type for the
modules which build mar files (addressing, rahas, soapmonitor, savan)
rather than the custom scripting we u
[
http://issues.apache.org/jira/browse/AXIS2-1751?page=comments#action_12451309 ]
Asankha C. Perera commented on AXIS2-1751:
--
Oleg
I opened an issue here.. http://issues.apache.org/jira/browse/HTTPCORE-15
Basically Axis2 needs to know
It seems that theare is no way to remove a declared namespace.
Thanks
Sameera.
On 11/21/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Sameera Madushan wrote:
> Hi all,
>
> As far as I know , an OMNamespace can be declared using the
> OMElement.declareNamespace() method.
>
> Is there a way to r
Hi All,
I am re-posting my query as I don't get any response from my previous post.
My problem is I am required to create a SOAP Request with X509 security
token but can not use certificate from any persistent store like keystore
that is used by axis2 framework.
Actually, I get certificate at
[
http://issues.apache.org/jira/browse/AXIS2-1754?page=comments#action_12451422 ]
Davanum Srinivas commented on AXIS2-1754:
-
Can u please upload your sample service as well?
thanks,
dims
> Exceptions thrown by service methods are not pr
Exceptions thrown by service methods are not propogated to clients properly.
Key: AXIS2-1754
URL: http://issues.apache.org/jira/browse/AXIS2-1754
Project: Apache Axis 2.0 (Ax
Hello,
I am trying to connect a axis client to a web service created using Oracle
WS. All the methods receive as parameter a org.w3c.dom.Element and return a
org.w3c.dom.Element. Using the WSDL defined by Jdeveloper 10g i am getting
the following error:
WSDLException (at /definitions/types/ns0:sc
[ http://issues.apache.org/jira/browse/AXIS2-1733?page=all ]
Saminda Wishwajith Abeyruwan resolved AXIS2-1733.
-
Resolution: Fixed
Assignee: Saminda Wishwajith Abeyruwan (was: Davanum Srinivas)
Applied to bothe 1.1 branch and trunk.
hi,i am getting following axis fault
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.NoService
faultSubcode:
faultString: The AXIS engine could not find a target service to invoke!
targetService is CVSIntegrator
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org
[ http://issues.apache.org/jira/browse/AXIS2-1748?page=all ]
Erland Isaksson updated AXIS2-1748:
---
Attachment: DeveloperService.wsdl
The wsdl file used
> It don't work to provide a wsdl inside the aar when deploying the war
> unexploded in WebLogic
>
[ http://issues.apache.org/jira/browse/AXIS2-1732?page=all ]
Saminda Wishwajith Abeyruwan resolved AXIS2-1732.
-
Resolution: Fixed
Applied to both 1.1 branch and trunk
Thank you
Saminda
> AxisFault throwing problems
> -
[
http://issues.apache.org/jira/browse/AXIS2-841?page=comments#action_12451581 ]
Vijay Phadke commented on AXIS2-841:
Somehow my earlier post did not make it here!
Yes, org.apache.axis2.wsdl.WSDL2Java compiles the wsdl
(${axis2-1.0.home}/sa
Jochen,
Please hold on to the VOTE. Let's take this week to see if anything
else pops up. We may as well do a quick 1.1.1 next week. ok? if not,
we can do the pom/jars as you mentioned.
thanks,
dims
On 11/21/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
Hi,
I am sorry to say, but I have foun
[ http://issues.apache.org/jira/browse/AXIS2-1753?page=all ]
Jeff Barrett closed AXIS2-1753.
---
> Add SPI to allow naviation to ServiceDelegate and associated
> EndpointDescription from BindingProvider
> -
Hi all,
In trying to complete AXIS2-1457 I've been looking at the dispatchers
we have and trying to work out the cleanest way of dealing with them.
I think that the best approach will be to move them out of the
o.a.a.engine package into an o.a.a.dispatchers package (and move the
AddressingBasedDi
[ http://issues.apache.org/jira/browse/AXIS2-1753?page=all ]
Jeff Barrett reassigned AXIS2-1753:
---
Assignee: Jeff Barrett
> Add SPI to allow naviation to ServiceDelegate and associated
> EndpointDescription from BindingProvider
> --
[
http://issues.apache.org/jira/browse/AXIS2-1752?page=comments#action_12451694 ]
Asankha C. Perera commented on AXIS2-1752:
--
Dims
This applies only for *plain text* messages arriving over JMS, and I think
Synapse would be using or sup
Hi,I am getting following error .
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (404)/axis/services/CVSIntegrator
faultActor:
faultNode:
faultDetail:
{}:return code: 404
Apache Tomcat/5.5.17 - Error
report