Surely 1.4.1 is a point in time (r684402) along the 1_4 branch, and
that will be tagged as 1_4_1 if this vote succeeds.
Jeremy
2008/8/21 Eran Chinthaka [EMAIL PROTECTED]:
SVN Info:
https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_4
(Revision: 684402)
Shouldn't this branch
Hi, I have axis2 installed with one user id and run as a different id.
It works, but we are getting warnings that the user doesn't have
permissions to update the last modified time on mar/jar/aar files
(actually anything on the classpath with a module.xml). This is
because the userid running axis2
Dims, thanks. Sorry wasn't watching closely enough. I'll try that out.
Thanks,
Jeremy
2008/5/12 Davanum Srinivas [EMAIL PROTECTED]:
Wasn't this fixed in http://svn.apache.org/viewvc?rev=649335view=rev ?
thanks,
dims
On Mon, May 12, 2008 at 6:19 AM, Jeremy Hughes [EMAIL PROTECTED
I'd like to get source jars for Axis2 modules out of the mvn build. I've
noticed XmlSchema, neethi and axiom all create source jars in the 'package'
stage of the maven2 lifecycle. But the Axis2 modules don't. Is there a good
reason behind this? If not then I propose we add this to the axis2 parent
Hi
On 28/02/2008, Andreas Veithen [EMAIL PROTECTED] wrote:
[...]
What we did was to use retrotranslator
(http://retrotranslator.sourceforge.net/
) to translate the library as well as its dependencies (including JAXB
2) back to Java 1.4.
retroweaver is another
+1 to moving to Java 5. I think maintenance releases could be key in
keeping those users tied to Java 1.4, interested in Axis2 until
they're ready to move up to Java 5 themselves.
Jeremy
On 27/02/2008, Paul Fremantle [EMAIL PROTECTED] wrote:
Yes I guess that makes sense.
However, its most
Is there any reason why the policy extension elements aren't implemented as
first-class Classes instead of using the non-type safe
UnknownExtensibilityElement? They would be much easier to deal with in that
way.
Cheers,
Jeremy
On 24/01/2008, Sanka Samaranayake [EMAIL PROTECTED] wrote:
Hi
On 14/01/2008, Davanum Srinivas [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did some debugging, looks like javax.wsdl.Service's getPorts() returns a
map. the order of items in the iterator on
that map is non-deterministic. internally com.ibm.wsdl.ServiceImpl
On 07/01/2008, Nicholas L Gallardo [EMAIL PROTECTED] wrote:
Keith,
Have you looked at JSR-311 as an example of a RESTful annotation API.
Granted, the JSR isn't complete, but it's worth taking a look at.
I'm not as familiar with WSDL 2.0 as I should be so I can't speak to whether
or
On 07/01/2008, Jeremy Hughes [EMAIL PROTECTED] wrote:
On 07/01/2008, Nicholas L Gallardo [EMAIL PROTECTED] wrote:
Keith,
Have you looked at JSR-311 as an example of a RESTful annotation API.
Granted, the JSR isn't complete, but it's worth taking a look at.
I'm
Hi, this sounds good - please see comments inline.
On 19/10/2007, David Illsley [EMAIL PROTECTED] wrote:
Hi Andrew,
It's not entirely clear to me what you're trying to do... are you
looking to add client and service samples into the axis2 build which
you can then run against WebSphere? If so,
Hi Deepal,
On 02/08/07, Deepal jayasinghe [EMAIL PROTECTED] wrote:
Davanum Srinivas wrote:
Deepal, Folks,
Suggestion #1: I think we have accumulated a lot of code changes since
last RC and since we have time, let's please cut another RC.
+1 , I will do it today.
Did you manage to do
No, sorry. We should put it up on the m2 incubating repo [1] but
historically it has lived on the one in ws zones [2] which Dims has
kindly maintained. In fact I just noticed he or someone has just
posted it at [2] ... so thanks for that!
[1]
Hi Asankha,
On 08/05/07, Asankha C. Perera [EMAIL PROTECTED] wrote:
Hi Jeremy
I'm a committer on WSDL4J. The project home page which you mention
indicates what the mailing list is in the project summary:
[EMAIL PROTECTED]
Thanks for the quick reply. I think I made a mistake and looked at the
Hi Asankha,
I'm a committer on WSDL4J. The project home page which you mention
indicates what the mailing list is in the project summary:
[EMAIL PROTECTED]
To answer your question, I don't think 1.6.2 has been uploaded to
ibiblio. It's not part of the WSDL4J release process. Sounds like it
Hi Samisa,
This is just what we're looking for. Is there something written down
about this on a wiki or web page? Perhaps we could reuse it :-)
Cheers,
Jeremy
On 01/05/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
Axis2/C team used to vote on the feature list but form 0.96 release
onwards,
[Sorry should have replied to axis-dev ..]
Hi, this is great - congrats! But I didn't see a [VOTE] thread against
a release candidate in the last week. Did one happen and I missed it?
Cheers,
Jeremy
On 27/04/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hi David,
On 30/04/07, David Illsley [EMAIL PROTECTED] wrote:
Jeremy,
From watching a number of WS-Commons and Axis2 releases, it appears
that neither project votes on release binaries in line with the way
the Incubator does things, we seem to simply vote on the principle of
having a release
Hi, sorry, I've been away from the list. Thanks for expanding on this
and yes I guess we don't want to *rely* on non-committers in order
that we can close off JIRAs. Getting their feedback is of course
useful.
I'm +1. I have a comment though:
On 14/04/07, Glen Daniels [EMAIL PROTECTED] wrote:
Just a thought ... could JIRA be used in a way that means we can see
that fixes put into a branch have also gone into the trunk, rather
than assuming it. e.g. for a JIRA that needs to be fixed in 1.2 branch
and trunk, set the 'fix for' field of the JIRA to be both 1.2 and
nightly (which I assume
On 07/03/07, Paul Fremantle [EMAIL PROTECTED] wrote:
Yep I guess. If CPL is really an issue for some people maybe we should
prompt IBM to donate as promised and Woden to build a version of
WSDL4J too.
Although this is draft [1], it indicates CPL is ok to ship in binary
form (with conditions)
Hi guys ...
On 21/02/07, Paul Fremantle [EMAIL PROTECTED] wrote:
David, Sanjiva
Shouldn't we be using the SOAP role model to handle this kind of
situation. It seems to me that what you are describing is a case where
the Axis2 engine is not the ultimateReceiver (see 2.7 Relaying SOAP
Messages
On 08/03/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
Jukka,
There may be a way out...check the JIRA :)
Maybe it hasn't been clear (sorry) ... the code in the JIRA is a
snapshot of WSDL4J 1.4. Axis2 uses WSDL4J 1.6.2 which isn't
contributed. So, the revisions to WSDL4J since 1.4 haven't been
Hi Paul, I seem to remember IBM donating a snap shot, so I don't think
that means any of the revisions between then and the current HEAD of
CVS on sf.net. I'll check up on this though.
Cheers,
Jeremy
On 07/03/07, Paul Fremantle [EMAIL PROTECTED] wrote:
I thought that IBM donated the WSDL4J
On 05/02/07, Jeremy Hughes [EMAIL PROTECTED] wrote:
On 05/02/07, David Illsley [EMAIL PROTECTED] wrote:
I don't think we can drop the old version without doing a release in
which they are deprecated... so I'd move to deprecate the 04/08 before
1.2 and remove them after.
As for the 06/01, do
On 05/02/07, David Illsley [EMAIL PROTECTED] wrote:
I don't think we can drop the old version without doing a release in
which they are deprecated... so I'd move to deprecate the 04/08 before
1.2 and remove them after.
As for the 06/01, do we have any knowledge of the expected PR/REC
namespace
On 03/02/07, Bill Nagy [EMAIL PROTECTED] wrote:
How do I (can I?) get at the test report logs for the continuum build?
I didn't see anything off of the continuum page except for the log that
was in the body of the notification. I assume that, for example, the
logs for JAX-WS are
at
Very cool! It would be great if you could add Woden.
scm:svn:http://svn.apache.org/repos/asf/incubator/woden/trunk/java/
The buildAll target on build.xml is more useful than the default.
Thanks,
Jeremy
On 12/01/07, David Illsley [EMAIL PROTECTED] wrote:
Hi all,
I've got continuum up and
OK done in r486235.
Thanks,
Jeremy
On 12/11/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
please change the names in build.xml. i'll fix things if needed.
thanks,
dims
On 12/11/06, Jeremy Hughes [EMAIL PROTECTED] wrote:
On 12/6/06, Dan Diephouse [EMAIL PROTECTED] wrote:
Woden itself
On 12/6/06, Dan Diephouse [EMAIL PROTECTED] wrote:
Woden itself doesn't even seem to do it (see woden-incubating-1.0.0M6\lib).
Hi Dan, thanks for that :-) AFAIK the only place the M6 jars are is here:
http://ws.zones.apache.org/repository/incubator-woden/jars/
which admittedly does not have
Hi, I just noticed Axis2 zip has woden-1.0.0M6.jar ... this really
should have the word 'incubating' in its name as Woden is in the
incubator.
Cheers,
Jeremy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
)
Issue Type: Bug
Components: samples, build,site
Reporter: Jeremy Hughes
Priority: Minor
FAQ descripton of 'frequently used maven commands' [1] is out of date.
dist-bin and dist-src are used instead of dist-min-bin, dist-std-bin,
dist-min-src, dist-std-src
maven
.
Best,
Sanka
Jeremy Hughes wrote:
Hi, I just tried building the source distribution - I took
instructions from here: http://ws.apache.org/axis2/faq.html#d4
the line in the table says:
maven dist-std-binWill generate the source version of Axis2
standard distribution
so I guess
Hi, I just tried building the source distribution - I took
instructions from here: http://ws.apache.org/axis2/faq.html#d4
the line in the table says:
maven dist-std-bin Will generate the source version of Axis2 standard
distribution
so I guess that should be maven dist-std-src but maven
2) official location for Woden M6 is:
On 11/14/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
1) See
http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.ws.commons.schema/jars/
there is probably some config issue on the repo1 box. No clue.
2) Please use
release tasks.
Cheers,
Jeremy
On 11/14/06, Jeremy Hughes [EMAIL PROTECTED] wrote:
2) official location for Woden M6 is:
On 11/14/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
1) See
http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.ws.commons.schema/jars/
there is probably
Ajith, the ws-commons-java5 home page says:
This is a clean room implementation of several Java classes, which
are a part of Java 5. The purpose is for use with elder Java
versions.
So shouldn't be dependent on java5. Personally I think the project
name ws-commons-java5 is confusing - it
+1
On 8/10/06, David Illsley [EMAIL PROTECTED] wrote:
+1 for Jeff
On 10/08/06, Rajith Attapattu [EMAIL PROTECTED] wrote:
+1 , welcome jeff
Thanks,
Rajith
On 8/10/06, Ruchith Fernando [EMAIL PROTECTED] wrote:
+1
Thanks,
Ruchith
On 8/10/06, R J Scheuerle Jr [EMAIL PROTECTED]
, Jeremy Hughes [EMAIL PROTECTED] wrote:
Hi,
There's some WSDL 2.0 support in WSDL2Java. This uses the Woden
Incabator podling which. The equivalent support in Java2WSDL isn't
there - I guess this is mostly because Woden doesn't currently support
output of WSDL 2.0 documents :-)
Either Axis2 should
about before (ActiveMQ incubating with
Geronimo) but don't remember the outcome. So let's ask
[EMAIL PROTECTED] on what the current policy is.
Could you please help drive that discussion?
thanks,
dims
On 8/9/06, Jeremy Hughes [EMAIL PROTECTED] wrote:
Dims,
Hi, I just saw you made changes to core
Hi,
Axis2 are starting to get ready for a 1.1 release. Since 1.0, it has a
new dependency on the Woden incubator podling. This is a similar issue
to Geronimo including ActiveMQ back in March [1]. Except, unlike
ActiveMQ, Woden was never a project existing outside the ASF.
Does anyone know of any
Hi,
There's some WSDL 2.0 support in WSDL2Java. This uses the Woden
Incabator podling which. The equivalent support in Java2WSDL isn't
there - I guess this is mostly because Woden doesn't currently support
output of WSDL 2.0 documents :-)
Either Axis2 should include Woden in the 1.1
Hi, the HEAD of trunk/java/modules/core now depends on Woden. Woden is
in the incubator right now so I was wondering what are the
implications for Axis2 shipping a new version (1.1?) and including
woden while woden is still in the incubator.
There are restrictions on incubating podlings -
Hi,
I'm looking for a way of determining the svn revision number for a
particular build of an axis2-SNAPSHOT.jar. There wasn't anything in
the MANIFEST.MF - perhaps it could be included?
The information the build process includes in resources.properties
when I build is:
axisVersion=Apache
+1
On 7/6/06, Sanka Samaranayake [EMAIL PROTECTED] wrote:
+1
Sanka
On 7/6/06, Ajith Ranabahu [EMAIL PROTECTED] wrote:
+1 from me
--
Ajith Ranabahu
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands,
were you looking for this:
http://svn.apache.org/repos/asf/webservices/commons/tags/XmlSchema/1.0.1/
On 7/3/06, Sébastien Arod [EMAIL PROTECTED] wrote:
The XMLSchema source repository mentioned on XML Schema web site (
done with it. But anyway, I have to wait till Chathura
gives me the permission. If he had done that already, its not good if I
commit it before him.
-- Chinthaka
Jeremy Hughes wrote:
Hi, the interop event is happening in July [1] at IBM in Toronto.
+1 to implementing WSDL 2.0 support in Axis2
modules which are operational.
I will co-ordinate with Chinthaka for commiting this. It appears
theres some overlap of our work.
Thanks
Chathura
On 5/18/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
On Thu, 2006-05-18 at 14:44 +0100, Jeremy Hughes wrote:
So to get to the point ... if all
Hi, the interop event is happening in July [1] at IBM in Toronto.
+1 to implementing WSDL 2.0 support in Axis2 with Woden and leaving
WSDL 1.1 to WSDL4J.
When Woden gains WSDL 1.1 support we can consider removing WSDL4J all
together in favour of Woden (if the Axis2 community agree to this of
Hi, I've been looking at wsdl4j jars stored in the ibiblio maven2
repository. There are two - axis-wsdl4j [1] and wsdl4j [2].
axis-wsdl4j [1] has these subdirs:
[DIR] 1.2-RC1/08-Nov-2005 17:03 -
[DIR] 1.2-RC2/08-Nov-2005 17:03 -
[DIR] 1.2-RC3/
Glen, when Woden supports WSDL 1.1 I'd expect the test for determining
whether it's a 1.1 or 2.0 doc to be in WSDLReader. It would then give
back a 1.1 Definition or a 2.0 DescriptionElement. But this is after
Woden replaces WSDL4J.
Jeremy
On 3/16/06, Glen Daniels [EMAIL PROTECTED] wrote:
(the
Hi, since wsdl4j is the reference implementation for JSR110 (JWSDL) you
could post this to the JSR mailing list (its actually a Yahoo group) Post to
[EMAIL PROTECTED] (membership required see
http://groups.yahoo.com/group/jsr110-eg-disc/)
Regards,
Jeremy
- Original Message -
From: Rick
52 matches
Mail list logo
