On Tue, 2006-03-28 at 21:05 -0500, Anne Thomas Manes wrote:
I recently responded to a question from someone using the OTA schema
which does not declare a targetNamespace (bad form on their part, but
such is the case).
Do you recall how they refer to those things from WSDL? (Ref would be
great;
On Mon, 2006-03-27 at 09:19 -0500, Anne Thomas Manes wrote:
I agree with Dennis on this.
WSDL 1.1 doesn't *require* that a schema have a targetNamespace. The
BP does, but that's a best practice, not a spec requirement. WSDL 2.0
requires that schemas have a targetNamespace, but that doesn't
On Mon, 2006-03-27 at 14:59 +1200, Dennis Sosnoski wrote:
The resolution of http://issues.apache.org/jira/browse/AXIS2-67 was
to
add a check that the schema definition within a WSDL defines a
targetNamespace. What is the justification for this? AFAIK it's
The justification is that its
On Mon, 2006-03-27 at 16:54 +1200, Dennis Sosnoski wrote:
The justification is that its required by WSDL. WSDL 1.1 wasn't clear
but it has since been clarified.
So the requirement was added after WSDL 1.1 - is it spelled out
somewhere, or just an informal interpretation? I'm happy
On Mon, 2006-03-27 at 10:31 +0600, Ajith Ranabahu wrote:
Ok I don't want to drag this on but It seems you didn't get the hint
at all :). What I tried to express was the idea that when things
change, people (at least most of them) want to go with the latest tech
thing, even when the old thing
[
http://issues.apache.org/jira/browse/AXIS2-522?page=comments#action_12371937 ]
Sanjiva Weerawarana commented on AXIS2-522:
---
I'd say this is not a 1.0 requirement at all .. agreed?
If so you might as well change this issue to read It's good
[
http://issues.apache.org/jira/browse/AXIS2-515?page=comments#action_12371840 ]
Sanjiva Weerawarana commented on AXIS2-515:
---
Can you please give us a driver for the generated stub (or some stub that works
for you now) so that we can test
I'd rather do this after we do 1.0 ...
Sanjiva.
On Fri, 2006-03-24 at 13:36 +0600, Ajith Ranabahu wrote:
Hi all,
I've been doing some work in the ws commons project and noticed that
they are using maven2. So this flared up a thought whether we should
upgrade to maven2 too. it seems that
On Fri, 2006-03-24 at 09:10 +1000, Shaun Mangelsdorf wrote:
Does Axis2/C (any version) support https on the client side?
Sorry if this is answered somewhere already, I couldn't find it and I
have tried to make it work on the current SVN version with little success.
If not, my question is
On Thu, 2006-03-23 at 18:18 -0500, Srinath Perera wrote:
Hi all;
I implement the toOM(..) method for my work. I add a wrapper name as
we usally we do not know what is the wrapper name for the epr. Shall I
check it in?
+1 from me. Chinthaka? (Since u r the main addressing person!)
Sanjiva.
On Wed, 2006-03-22 at 16:14 +0600, Ajith Ranabahu wrote:
Hi,
I think chathura answered your questions yesterday.
Checkout the archive at
http://marc.theaimsgroup.com/?l=axis-devm=114292862001333w=2
BTW Chathura is still a student. Still opensource mailing lists are
not guranteed to give
On Wed, 2006-03-22 at 16:16 +0530, Soumadeep wrote:
[Soumadeep] An open source community doesn't mean that it's doesn't share
any time lines or responsibilities, I completely disagree with your
statement as above
No matter what your other obligation may be if you take a responsibility
being
On Wed, 2006-03-22 at 11:16 +, Steve Loughran wrote:
Hey, I have that @work too. Proxies, you understand.
I have to put my laptop up on the WLAN as a guest for the day, which
means going to the
appropriate IT page and registering a guest (me) under the supervision
of an employee (me)
application can listen to
events generated by ASIX2 by registering to that Mbean?
Thanks
Soumadeep
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 22, 2006 5:12 PM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Management Interface
On Wed, 2006-03-22 at 07:01 -0500, Srinath Perera wrote:
Hi Eran;
IMHO Stateless does not talk only about across multiple invocations,
just like EJB it simply say user should not be looking at the states
on the Handler anytime.
+1.
On 3/21/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
I
On Tue, 2006-03-21 at 14:33 +0600, Chamil Thanthrimudalige wrote:
Hi,
I think we can make a better decision if we are clear about Apache
policy about maintaining docs for older revisions [Before a 1.0
version and after]. So can some one jump in an enlighten us on what
is the policy
Cool :) +1.
Damn, I was going to enjoy giving boxing gloves to see open source
developers fight about documentation!!!
Sanjiva.
On Tue, 2006-03-21 at 16:25 +0600, Eran Chinthaka wrote:
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
[
http://issues.apache.org/jira/browse/AXIS2-418?page=comments#action_12371239 ]
Sanjiva Weerawarana commented on AXIS2-418:
---
I have no problem with not supporting simpleContent right now, but we MUST
throw an exception saying Unsupported schema
On Tue, 2006-03-21 at 21:55 +, Steve Loughran wrote:
One caveat. Once you get to 1.0, you are making some promise of stability.
I am still trying to get code that worked with 0.93 working on 0.95
snapshot, it looks like the dynamic classloading stuff is using the
wrong classloader.
+1 except for adding axiom-doom.jar :).
Sanjiva.
On Mon, 2006-03-20 at 15:09 +0600, Eran Chinthaka wrote:
Hi all,
I'd like to suggest to have a api jar and an impl jar for axiom. This
will help us to have more than one impl of axiom at the same time.
For the time being we have two
On Mon, 2006-03-20 at 12:42 +, Anthony Elder wrote:
Could a createClientSideAxisService method be added to AxisService that
uses a WSDL Definition object for 0.95?
See:
Most definitely +1! Axis2 is now ready for prime time .. and we need
much wider user feedback to make it move to the next level. We won't get
that until we release 1.0.
I propose we change 0.96 below to the label 1.0RC to signal to everyone
that this is our planned 1.0 release. That will get more
On Mon, 2006-03-20 at 13:57 +0100, Franz Fehringer wrote:
Will the TCP monitor be factored out (- ws-commons) in release 1.0?
This is an excellent idea. However, can someone offer to do the work?
Its not a huge amount but it does require refactoring the code to change
Java package names etc..
On Sun, 2006-03-19 at 09:30 -0500, Davanum Srinivas wrote:
Team,
I've added a short list of show stoppers, Please add your wishes to the list:
http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0
I removed two items and added one .. since there's no easy way to
discuss via the wiki I'll
On Mon, 2006-03-13 at 19:50 -0800, David Blevins wrote:
Dims created an Axis 1.4 final branch in early Dec at:
http://svn.apache.org/repos/asf/webservices/axis/branches/AXIS_1_4_FINAL
There was a vote to release this that went through but the binaries
were never produced. Geronimo,
[
http://issues.apache.org/jira/browse/AXIS2-164?page=comments#action_12370287 ]
Sanjiva Weerawarana commented on AXIS2-164:
---
Doesn't this get done by the servlet container?? Basic auth is always handled
by the servlet container and the servlet
---BeginMessage---
There was a service running at that endpoint (for the
soapbuilders interop testing) it has however been down for quite a while now,
previous attempts to prod people to get the endpoint active again have always
failed.
Perhaps the axis2 folks will put up an interop
Forwarding with proper Axis2 prefix ;-).
---BeginMessage---
Forwarding with axis2 prefix.
-- Forwarded message --
From: Chathura Herath [EMAIL PROTECTED]
Date: Mar 8, 2006 8:04 AM
Subject: Re: Async Service with callback for BPEL process (any hints?)
To: axis-user@ws.apache.org
Is this an XMLBeans bug or a bug in the Axis2 integration of XMLBeans?
Sanjiva.
On Fri, 2006-03-10 at 01:14 +, Ajith Harshana Ranabahu (JIRA) wrote:
XMLBeans truncates dateTime values
--
Key: AXIS2-487
URL:
On Thu, 2006-03-09 at 22:15 +0600, Ruchith Fernando wrote:
IMHO, for example we should be able to create two instances of the
_same_ stub within a method and invoke them independently. Before
modifying those security test cases this is the behaviour that we had.
Can we make sure we have this
Very cool. What's the connection between this and the security policy
work going on in the WSS4J world by Werner and Ruchith??
Sanjiva.
On Wed, 2006-03-08 at 06:28 -0500, Srinath Perera wrote:
Hi All;
Right now, In my local machine I have a security policy client side
working for Security
[
http://issues.apache.org/jira/browse/AXIS2-427?page=comments#action_12369451 ]
Sanjiva Weerawarana commented on AXIS2-427:
---
+1 to closing the issue with no action.
Axis2 has no ServiceFactory
---
Key: AXIS2
On Mon, 2006-03-06 at 11:28 +0600, Deepal Jayasinghe wrote:
yes you have :)
ConfigurationContext createConfigurationContext(AxisConfigurator
axisConfigurator)
Or, of course you can always saw new ConfigurationContext() and fill it
to your heart's content .. :).
Sanjiva.
Hi Glen,
Wow, this is a serious -1 for me. We had this discussion, IIRC, at
least twice (I think even at both F2Fs!), and I thought we'd resolved to
keep things in terms of the WSDL model and have a role switch which
This was done months ago .. way before the ApacheCon F2F even!
[
http://issues.apache.org/jira/browse/AXIS2-482?page=comments#action_12368850 ]
Sanjiva Weerawarana commented on AXIS2-482:
---
Deepal, if we put this code in ClientUtils that makes ClientUtils part of the
public API. I don't think that's a good
On Sat, 2006-03-04 at 07:53 -0500, Srinath Perera wrote:
I think major point is WSDL have a notion that *everything is
explained with respect to the Service Provider* in all times. (I think
both you and glen says a the first F2F this is done to avoid need to
have a client specific WSDL) .
On Fri, 2006-03-03 at 13:04 -0500, Srinath Perera wrote:
Team;
Have we flipped the MEP in the client side? Is it the case that at the
Yes ..
client side normal In-Out is called Out-In? (Which is against notions
of WSDL2.0 AFAIK)
No ..
That means one can not use the Service build from the
On Sat, 2006-03-04 at 05:21 +0600, Sanjiva Weerawarana wrote:
client side normal In-Out is called Out-In? (Which is against notions
of WSDL2.0 AFAIK)
No ..
Sorry; my answer above could be confusing: The answer to your question
above is yes .. what I said no for was your assertion that its
On Thu, 2006-03-02 at 04:01 -0600, Ajith Ranabahu wrote:
Hi all,
I'm surprised to hear that XMLbeans fails to do the right thing! May
be we need to redirect the issue to some of the XMLBeans gurus ?
Ajith, is this in code *generated* by XMLBeans?? If so I agree but
otherwise its our problem
: [Fwd:[Axis2] WSRF Implementation]
Sanjiva Weerawarana wrote:
AFAIK no one has so far signed up to doing a WSRF impl over Axis2. If
you're willing to do it that's very cool!
When you're ready we can create a new maven module for that code or if
its more appropriate you can talk
[
http://issues.apache.org/jira/browse/AXIS2-427?page=comments#action_12368529 ]
Sanjiva Weerawarana commented on AXIS2-427:
---
I'd go one step further than Deepal: If the requirement is to support JAX-RPC
ServiceFactory then its simply
On Thu, 2006-03-02 at 17:11 +0100, Fernando Mato Mira (JIRA) wrote:
[
http://issues.apache.org/jira/browse/AXIS2-427?page=comments#action_12368531
]
Fernando Mato Mira commented on AXIS2-427:
--
In Spring there's a single point of
Definitely +1! I guess Ruchith should reply too though since I don't
know the security stuff .. seems logical however ;-).
Sanjiva.
On Thu, 2006-03-02 at 17:11 -0500, Srinath Perera wrote:
Hi All;
Currently SecuirtyModule engageNotifyMethod() does the following
1) create InFlow/OutFlow
On Thu, 2006-03-02 at 15:14 -0500, Srinath Perera wrote:
When module is engegd as the Operation level engagedNotify(..) is not invoked?
according to eclipse engagedNotify() is invoked only in follwing places
1) AxisService (addOperation(AxisOperation), engageModule(AxisModule,
On Wed, 2006-03-01 at 18:51 +0600, Dimuthu Chathuranga wrote:
Hi,
Sorry for the earlier mail. The files for test client (of
interoperability tests round2 ) are attached with this mail.
Hi Dimuthu,
Thanks for the contrib! However, please create a JIRA issue and attach
the patch there ..
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.
---BeginMessage---
I took a shot at
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 start
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 Mon, 2006-02-27 at 12:42 +0600, Afkham Azeez wrote:
Hi All,
I came across the same problem when I tried to run some of the SAAJ TCK tests.
One reason for the error was in the axis2_default.xml, the following
section had some problems:
transportReceiver name=jms
On Mon, 2006-02-27 at 15:26 -0500, Srinath Perera wrote:
One more thing, I am get a feeling that code o create a AxisService
from WSDL and policy support are scattered
1. AxisServiceBuilder (Based on WSDL4J .. with policy)
2. ClientUtils.creatAxisService(...) (Based on WSDL4J . without
On Sat, 2006-02-25 at 08:27 -0500, Srinath Perera wrote:
Personally I can live without that constructor by creating may own
ServiceClient Class (Even though I do not believe in private code like
that). My concern is normal users, I know for a fact Taverna guys are
trying to migrate to Axis2.
Now that Dan has managed to push out the 1.0 release (or nearly; he's
still trying to get it signed ;-)) let's upgrade to the 1.0 release
instead of the snapshot?
Sanjiva.
On Sat, 2006-02-25 at 20:06 -0600, Deepal Jayasinghe wrote:
Hi Srinath;
What I said was there is a class called AxisServiceBuilder and if you
are given a WSDL which has policy in it then that guy will populate
AxisService for that given policy, the missing part is using that policy
some one
AFAIK no one has so far signed up to doing a WSRF impl over Axis2. If
you're willing to do it that's very cool!
When you're ready we can create a new maven module for that code or if
its more appropriate you can talk to Muse folks and ask them what their
plans are. To be honest, I haven't looked
On Fri, 2006-02-24 at 13:21 +0600, Chathura Ekanayake wrote:
Is there a problem of using singleton objects as I mentioned in the
design? Will it fail if we deploy two Axis2 engines in the same
servlet engine?
Why do you need a singleton? I didn't quite get that ..
Sanjiva.
On Fri, 2006-02-24 at 05:30 -0500, Thushantha De Alwis wrote:
Hi All
When I tried to write a client to invoke axis2 as follows.
There was a packaging error in the 0.94 distro .. if you go to the
download site you'll see instructions on how to fix it.
Sanjiva.
Come on Srinath .. its ONE more line of code:
- create the repo
- create the config context using ConfigurationContextFactory
- now create the ServiceClient
I hardly see that being hard .. and its not a common case anyway. If you
have your own repo then its unlikely its something you use for
On Fri, 2006-02-24 at 16:13 -0500, Srinath Perera wrote:
Hi All;
Do we have a code that given a WSDL file/ WSDL discription create a
policy populated
Context Hierachy/AxisService? If yes .. please name the exact laocation
Context hierarchy? That doesn't make sense.
AxisService - yes .. I
On Fri, 2006-02-24 at 19:15 -0500, Srinath Perera wrote:
If we had constructor
public ServiceClient(ConfigurationContext configContext) throws AxisFault
Note that this idea is generally nonsensical: you want a client for a
service but don't say for what service. However, we do have the
Srinath, it looks like you added a new constructor to ServiceClient:
ServiceClient(ConfigurationContext configContext,
WSDLDescription wsdldesc,
QName wsdlServiceName, String portName)
First of all, when making client API changes please send a note to the
list to
Guys, please use the [axis2] prefix when sending Axis2 related mail.
On Tue, 2006-02-21 at 19:52 -0800, rick rineholt wrote:
I was wondering if there would be any consideration to
refactoring
DeploymentEngine to use just InputStream instead of
Strings for filename
location and repositories
(You forgot the [axis2] prefix Steve ;-))
We need to fix this .. in the recent changes to the ListenerManager
stuff, we ended up with the current model. A few more days and you'll be
back to normal :).
I'm not sure of the answer for the backport issues.
Sanjiva.
On Mon, 2006-02-20 at 15:53
(Forwarding with proper prefix.)
---BeginMessage---
Hi all,
I have recently started using Axis2 (0.94) for a project, and have
encountered a problem when connecting to MS C# clients. I have logged
the bug on JIRA (AXIS2-455).
Basically, the problem is that, with abstract parameter types,
On Fri, 2006-02-17 at 11:45 -0500, Srinath Perera wrote:
Hi All;
Did the xxx(x?,SOAPEnvelope) methods not going to supported in the
Service Client?
Nope. ServiceClient is meant to be the simple API .. supports OM only.
The next level is an operation client you get to play with MCs then.
On Fri, 2006-02-17 at 13:16 -0500, Srinath Perera wrote:
Team;
If we engage a module that does not exists, it returns without a
error, and continue as usual?
Is there a specific reason to do this? (IHMO this is bad, sorry if I
sound gloomy on all these mails, trying to port my code to
On Thu, 2006-02-16 at 17:02 -0600, Hyen V Chung wrote:
The problem is that there is a wss4j-SNAPSHOT.jar in the
axis2.war#WEB-INF/lib/wss4j-SNAPSHOT.jar, for some reason, the classloader
loads the classes from axis2.war#WEB-INF/lib/wss4j-SNAPSHOT.jar and it also
try to load classes from
How about more items:
I was thinking of starting to work on some of the bigger issues/features
Excellent!
How about some more unlisted items:
- I18n of the entire codebase .. a lot of painful work :(
- Make ADB more complete .. pick an unsupported schema construct and
make it work .. hard
On Thu, 2006-02-16 at 23:34 -0500, Srinath Perera wrote:
Hi Deepal;
you have to have ur axis2.xml file inside the conf sub directory inside
the repository
You mean repository/conf/axis2.xml?
No by default AXIS2_HOME/conf/axis2.xml.
My 2 cents, but to me it is step backward?
1) is
On Tue, 2006-02-14 at 09:56 +0200, Steve Loughran wrote:
I see that on SVN_HEAD, the old Client class is no more.
What do I have to do to migrate some code that extended Client to move
to the 0.94 architecture?
Look at org.apache.axis2.client.ServiceClient .. this is the entrypoint
to the
On Tue, 2006-02-14 at 07:42 -0600, R J Scheuerle Jr wrote:
The Iterator returned by getChildElements should traverse the actual
soap.Node objects in the tree. One should be able to use the iterator
to add to the tree. The iterator should also support removal of the
elements. The iterator
On Mon, 2006-02-13 at 10:16 -0500, Doug Davis wrote:
Done - apologies for not explaining this a bit more in the svn
commit... the changes that Dims
is referring to are the couple of lines in the AxisEngines that make
calls out to RM code
and Security code. These do not assume any
On Sun, 2006-02-12 at 15:35 +0600, Kapila Dissanayake wrote:
Hi,
I have started the implementation of MTOM for AXIS2 C.
Great! Welcome aboard!!
We have to have equivalent implementation for
Java.activation.Datahandler and all MIME related classes(e.g
MimeBodyPart).
I would propose to
On Mon, 2006-02-13 at 10:40 +0800, Juanda Zeng wrote:
Hi. I know this has been asked before, but the last time I checked, I
couldn't find the answer. So here it is again...
Our company plans to incorporate Axis2 into one of our products. But
we would be more comfortable in adopting Axis2 if
On Thu, 2006-02-09 at 18:37 -0500, Dan Diephouse wrote:
Passed: 1177/1177 :-)
http://issues.apache.org/jira/browse/WSCOMMONS-4
- Dan
WOW! Cool!!
Sanjiva.
On Fri, 2006-02-10 at 18:09 -0500, Davanum Srinivas wrote:
I added the bug report a few days back:
http://issues.apache.org/jira/browse/AXIS2-438
-- dims
On 2/10/06, Hyen V Chung [EMAIL PROTECTED] wrote:
Using this morning build, got this when starting using tomcat, is
On Fri, 2006-02-10 at 18:10 -0500, Davanum Srinivas wrote:
you need the xml-security jar
Um shouldn't that be in security.mar?
Sanjiva.
On Wed, 2006-02-08 at 09:44 -0600, Hyen V Chung wrote:
I am not using 0.94 source distribution. I did a checkout from svn last
night.
Are you still not able to build?? I removed my entire maven repo and
built it earlier today with no problems ..
Sanjiva.
On Wed, 2006-02-08 at 07:30 -0500, Srinath Perera wrote:
+1
Can we have a WS-commons jar .. as a one build as well for use in
Axis2 purposes, I hate having to increase the number of jars ..
already too many!!
I'm -1 to a ws-commons.jar idea .. each of these components are likely
to have
On Wed, 2006-02-08 at 13:36 -0200, robert wrote:
Sorry for the confusion - it is an unusual case as it was unexpected for me
to
have the privilege.
Accordingly, my new email is [EMAIL PROTECTED] , and that email will be
used for all of my future correspondence to this list. No problem
I'd like to nominate Trebor for committer status in Axis2- he has been
contributing to Axis2 for a while and has now taken on grander and more
glorious tasks on too ;-).
Here's my vote: +1.
Sanjiva.
We currently have the HTTP Tracer (aka tcpmon) in Axis2 and have another
version of it in Axis1.
I suggested this many years ago but was voted down. I'd like to move
this to WS commons because this has NOTHING to do with Axis1 or Axis2
and all it is just a damned useful bit of code.
Can we
On Tue, 2006-02-07 at 19:21 -0500, Davanum Srinivas wrote:
Folks,
it's Robert Lazarski you are voting for :)
Um, I'm very confused. Who's Robert Lazarski in relation to the person
who has been using Trebor Iksrazal as the real name of his email address
all this time??
I can't see a single
On Mon, 2006-02-06 at 11:39 -0500, Lawrence Mandel wrote:
John Kaputin and I have found a few problems in XmlSchema while developing
Woden [1]. We've fixed some but do have some outstanding issues such as
adding a URI resolver framework and clearly defining an XmlSchema API
capable of both
Hi Samuel,
I finally understood the problem yesterday .. when we shipped 0.94, it
depended on a version of policy called 0.94-SNAPSHOT. Snapshots are
dynamically downloaded by maven when you build.
However, we recently refactored the policy stuff out of Axis2 into its
own commons project and
On Tue, 2006-02-07 at 21:31 -0500, Davanum Srinivas wrote:
/me loves Mr Sherlock...follow the trail :) on the footers of the
emails you can see (http://www.braziloutsource.com/;). click on it
and click on profiles (http://www.braziloutsource.com/profiles.html;)
and then see the names there :)
Just committed the fix .. thanks for reporting it.
Sanjiva.
On Tue, 2006-02-07 at 20:48 -0600, Hyen V Chung wrote:
In order to build the war from the latest source, I have to change
axis2/modules/webapp/project.xml:
from
dependency
groupIdws-commons/groupId
Another option to look at might be the JDK 1.5 java.util.concurrent
package's thread pool stuff ..
Sanjiva.
On Mon, 2006-02-06 at 12:57 +0600, Samisa Abeysinghe wrote:
Samisa Abeysinghe wrote:
Sahan Gamage wrote:
Hi,
I am having some design issues with the threading model in Axis2.
I'd like to nominate Chatra for committer status .. she's been
contributing tons of patches for Axis2 docs over the last couple of
months and its time to give her the karma.
Here's my vote: +1.
Sanjiva.
I ran the build a bit ago and it ran just fine. I'm using maven 1.0.2
and here's my OS info:
Linux vishwa 2.6.10-5-386 #1 Mon Oct 10 11:15:41 UTC 2005 i686 GNU/Linux
Sanjiva.
On Mon, 2006-02-06 at 20:36 -0500, Bill Nagy wrote:
Hi,
I'm trying to build from the source tree (I've checked out
On Sun, 2006-02-05 at 10:15 -0500, Dan Diephouse wrote:
Hi all,
Can we do some kind of release of the XmlSchema stuff? 1.0-M1?
1.0-beta-1? We could even call it 1.0 I suppose as its been around a
while...
+1 for doing a 1.0 of XmlSchema. Dan, can we rope you into help bash the
release into
Or better yet .. please submit a patch!
Sanjiva.
On Wed, 2006-02-01 at 06:34 -0500, Srinath Perera wrote:
Hi Yves ;
Yes, please file a bug report
Thanks
Srinath
On 2/1/06, Yves Langisch [EMAIL PROTECTED] wrote:
I just checked the code and it seems that the http version is not
Folks, we currently have a circular dependency between policy and axis2
projects: axis2 depends on policy and policy depends on axiom from
axis2. I think the right solution is to move axiom out of axis2 and to
ws-commons. I think this makes sense anyway (independent of the circular
dep) as axiom
On Mon, 2006-01-30 at 13:50 -0500, Davanum Srinivas wrote:
I've reviewed the code in question, there are exactly 2 files in
policy project that uses axiom namely
- OMPolicyReader : OMPolicyReader is loaded on demand (using a class
loader) from PolicyFactory.java. So moving it to axis2 core
Hi Ed,
This would be a *very* useful update! Please go ahead and patch it ...
BTW this discussion belongs in axis-c-dev and not here.
Thanks,
Sanjiva.
On Thu, 2006-01-26 at 14:27 +, Edward Slattery wrote:
I dont know where to log this one - anyone want to tell me if its a
problem or
Please open a JIRA .. the ID must be a URI; what we're generating is
wrong.
Sanjiva.
On Tue, 2006-01-24 at 19:10 -0500, Tony Dean wrote:
Hi,
I am starting to integrate some attachment processing into my webservices and
found problem with MS [MS client/Axis2 server].
They complain about
Hi Dug,
This sounds like a major re-arch of Axis 1.x. Do you see this being part
of Axis 1.(x+1) or more say Axis1 2.0?
From a project perspective, its perfectly fine and healthy to have
multiple versions of a major project going (proof: HTTPD and Tomcat) but
it does require a serious
On Fri, 2006-01-20 at 11:03 -0500, Rajith Attapattu wrote:
Well, For Axis2 vs Axis2 scenario this is true. However I feel that
we should be thinking of non-Axis2 clients as well in which case they
have to know the specifc id to be sent in the SOAP header.
This is exactly my concern as
On Fri, 2006-01-20 at 20:10 -0500, Rajith Attapattu wrote:
So if a service is deployed in SOAP session scope we do that with
the understanding that any client that uses this service supports
WS-Addressing.
If above assumption is wrong, How about the client that don'
On Fri, 2006-01-20 at 12:24 -0600, Dong Liu wrote:
Hi, folks,
I remembered the WSDL2Java took the first porttype in a wsdl file last
time when I tested it. I want to know the development plan of
WSDL2Java for multi porttypes. Maybe I need to do some work on it.
Do you have thoughts on what
We currently package a default axis.xml in the jar file and have a model
where we create a .axis directory in the user's home dir and do some
copying of stuff. That's a non scalable plan and leads to version issues
too (old modules etc.). A proposal to clean this up follows:
- Use AXIS2_HOME as
501 - 600 of 984 matches
Mail list logo
