Re: How to set SOAP Action using JAXWS dispatch client API?

[Brian De Pradine]

Hi Isuru,

Not in the Axis2 documentation. The current plan, however, is to update 
the existing JAX-WS related documentation Axis2 as a part of the wider 
effort to update support to JAX-WS 2.2.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Isuru Suriarachchi  wrote on 10/11/2009 06:33:07:

> [image removed] 
> 
> Re: How to set SOAP Action using JAXWS dispatch client API?
> 
> Isuru Suriarachchi 
> 
> to:
> 
> axis-dev
> 
> 10/11/2009 06:33
> 
> Please respond to axis-dev
> 
> Hi Brian,
> 
> Thanks. It works.. Do we have any documents on this kind of stuff?
> 
> Thanks,
> ~Isuru

> On Mon, Nov 9, 2009 at 11:43 PM, Brian De Pradine  
wrote:
> 
> Hi Isuru, 
> 
> You need to add some code similar to the following to your client, 
> 
> import javax.xml.ws.BindingProvider; 
> 
> Map map = dispatch.getRequestContext(); 
> map.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE); 
> map.put(BindingProvider.SOAPACTION_URI_PROPERTY, ...); 
> 
> Pass a String as the BindingProvider.SOAPACTION_URI_PROPERTY in 
> order to specify the SOAP action.. 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 

> 
> From: 
> 
> Isuru Suriarachchi  
> 
> To: 
> 
> axis-dev@ws.apache.org 
> 
> Date: 
> 
> 08/11/2009 07:58 
> 
> Subject: 
> 
> How to set SOAP Action using JAXWS dispatch client API?
> 
> 

> 
> 
> 
> Hi all,
> 
> I'm using a JAXWS dispatch client (without generating proxy code) to
> invoke a simple service. Now I want to engage addressing to this 
> client and test some asynchronous scenarios. But I can't find how to
> set the SOAP Action through this dispatch client API. Can someone 
> who's familiar with our JAXWS client API tell me how to do this?
> 
> Thanks in advance,
> ~Isuru
> 
> 
> 
> 

> 

> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with 
> number 741598. 
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 
3AU 
> 
> 
> 
> 

> 
> 
> 
> -- 
> Senior Software Engineer,
> WSO2 Inc. http://wso2.org/
> Blog : http://isurues.wordpress.com/





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [VOTE] Web Services Reorg Part 1 : Axis2 TLP

[Brian De Pradine]

+1

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?




From:
Glen Daniels 
To:
"gene...@ws.apache.org" , Axis-Dev 

Date:
06/11/2009 17:21
Subject:
[VOTE] Web Services Reorg Part 1 : Axis2 TLP



Greetings, everyone.

A bunch of us here at ApacheCon were talking about the Axis2 TLP idea, and
how to move this forward in the simplest and most effective way.  We came 
up
with *exactly* the same structure that we had proposed a year ago. :)  So,
having only altered the page in order to remove a step (the promotion of
WS-Commons sub-sub-projects to WS subprojects - this isn't really 
necessary
as we can still decide what to do about each sub-sub-project individually
later), I'd like to bring the following proposal up for a VOTE of the Web
Services PMC.  If this passes, I plan to submit this resolution to the 
board
as soon as possible.

http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal

Note that I added just the first few people in the current PMC roster as
examples.  I also nominated myself as the Axis2 chair for now - if anyone
else would like to volunteer to do this, please let me know.  Eventually 
I'd
like to drop one or the other PMC chair role, but for now I'm OK doing 
both.

So if you would, please:

1) VOTE
2) Add yourself to the list of project members on the wiki page if you are 
an
existing PMC member and would like to be on the new Axis2 PMC

Here is my +1 for this proposal.

Thanks,
--Glen








Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: How to set SOAP Action using JAXWS dispatch client API?

[Brian De Pradine]

Hi Isuru,

You need to add some code similar to the following to your client,

import javax.xml.ws.BindingProvider;
 
Map map = dispatch.getRequestContext();
map.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
map.put(BindingProvider.SOAPACTION_URI_PROPERTY, ...);

Pass a String as the BindingProvider.SOAPACTION_URI_PROPERTY in order to 
specify the SOAP action..

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?




From:
Isuru Suriarachchi 
To:
axis-dev@ws.apache.org
Date:
08/11/2009 07:58
Subject:
How to set SOAP Action using JAXWS dispatch client API?



Hi all,

I'm using a JAXWS dispatch client (without generating proxy code) to 
invoke a simple service. Now I want to engage addressing to this client 
and test some asynchronous scenarios. But I can't find how to set the SOAP 
Action through this dispatch client API. Can someone who's familiar with 
our JAXWS client API tell me how to do this?

Thanks in advance,
~Isuru








Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [jira] Resolved: (AXIS2-3987) Axis2 Addressing treats MessageID as a required element

[Brian De Pradine]

That's the tricky bit. It is not us making it mandatory, it is the spec 
stating that it is mandatory. The following is taken from  [1].

In either of the above cases, if the related message lacks a [message id] 
property, the processor MUST fault.

[1] http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#formreplymsg 

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


robert lazarski  wrote on 27/02/2009 13:55:04:

> [image removed] 
> 
> Re: [jira] Resolved: (AXIS2-3987) Axis2 Addressing treats MessageID 
> as a required element
> 
> robert lazarski 
> 
> to:
> 
> axis-dev
> 
> 27/02/2009 13:55
> 
> Please respond to axis-dev
> 
> On Fri, Feb 27, 2009 at 10:43 AM, Brian DePradine (JIRA)
>  wrote:
> >
> > [ https://issues.apache.org/jira/browse/AXIS2-3987?
> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> >
> > Brian DePradine resolved AXIS2-3987.
> > 
> >
> >Resolution: Won't Fix
> >
> > As the message id may be required in some situations, according to
> the WS-Addressing spec, no change will be made.
> >
> 
> But if its optional, why do we make it mandatory? That seems to me to
> be an obvious contradiction, isn't it? It would be a violation of the
> spec if it couldn't be made optional, right?
> 
> Rainy day here ... not that I have dog in this hunt.
> 
> - R
> 
> >> Axis2 Addressing treats MessageID as a required element
> >> ---
> >>
> >> Key: AXIS2-3987
> >> URL: https://issues.apache.org/jira/browse/AXIS2-3987
> >> Project: Axis 2.0 (Axis2)
> >>  Issue Type: Bug
> >>  Components: Addressing
> >> Environment: Ubuntu, jdk 1.5
> >>Reporter: Isuru Eranga Suriarachchi
> >>
> >> According to both WS-Addressing final and submission 
> specifications, the Message Id is an optional element in the header.
> But when I engaged Axis2 addressing to a simple client and set only 
> the Action, it adds a message Id as well. I tried the following 
> option as well. But it didn't work.
> >> options.setProperty(INCLUDE_OPTIONAL_HEADERS, Boolean.FALSE);
> >> So I can't create a message without the optional element 
> "MessageID" using Axis2..
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
> >






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

RE: Axis2 JMSListener on Websphere

[Brian De Pradine]

Hello,

I am not sure what the solution is but you might want to try the forum at 
[1]

[1] http://www.ibm.com/developerworks/forums/forum.jspa?forumID=266

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Martin Gainty <[EMAIL PROTECTED]> wrote on 26/10/2008 14:21:11:

> Good Morning All-
> 
> we really need to know which classloader is loading that class 
> before making any kind of recommendation
> BTW: Weblogic has a custom classLoader hierarchy available in 
> weblogic-application.xml
> http://e-docs.bea.com/wls/docs81/programming/classloading.html
> 
> glassfish has the ability to turn off parent first delegation with 
> delegate="false" attribute specification
> https://glassfish.dev.java.net/nonav/javaee5/docs/DG/beade.html
> 
> I raised this "specifying custom classloader options in Websphere" 
> to IBM on  in a opinion poll 
> *Hopefully* the new IBM WAS will have this capability in 2009
> 
> Maybe Keith / Glen or Brian DePradine can weigh in when they get 
> into their office tommorrow am..
> (although I think Keith and Glen will be in ApacheConUS in New 
> Orleans starting this week..)
> 
> HTH..Keep us apprised!
> Martin Gainty 
> __ 
> Disclaimer and confidentiality note 
> Everything in this e-mail and any attachments relates to the 
> official business of Sender. This transmission is of a confidential 
> nature and Sender does not endorse distribution to any party other 
> than intended recipient. Sender does not necessarily endorse content
> contained within this transmission. 
> 
> 
> > Date: Sat, 25 Oct 2008 20:55:34 -0700
> > From: [EMAIL PROTECTED]
> > To: axis-dev@ws.apache.org
> > Subject: RE: Axis2 JMSListener on Websphere
> > 
> > 
> > Hi mgainty,
> > 
> > Actually that is my jmsContext.xml. I also trying my luck 
> > on JSF forum 
> > ( http://forums.sun.com/thread.jspa?threadID=5342580) 
> > and spring forum 
> > ( http://forum.springframework.org/showthread.php?p=209833#post209833) 

> > 
> > And so far Nabble has been the only helpful forum, thanks to people 
like
> > andreas and you.
> > 
> > I will try the JAVA_OPTIONS you suggestion and see what happens. 
Thanks! 
> > 
> > But any pointers on what is going on? 
> > 
> > The QCFs are created fine with parent classsloader first but with 
parent
> > last everything is messed up. 
> > 
> > 
> > 
> > mgainty wrote:
> > > 
> > > 
> > > as andreas mentioned we need to determine which CL *server 
classloader or
> > > application classloader is loading the class
> > > assuming you're using Spring ConnectionFactories..can we see your
> > > jmsContext.xml it should look something like:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  > > class="org.springframework.jms.core.JmsTemplate">
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  
> > > 
> > >  > > class="org.springframework.jms.core.JmsTemplate">
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  > > resource-ref="true" />
> > > 
> > > 
> > > 
> > >  > > resource-ref="true" />
> > > 
> > >  
> > > 
> > >  > > resource-ref="true" />
> > > 
> > >  
> > > 
> > >  > > resource-ref="true" />
> > > 
> > > 
> > > This sounds like a classloader order problem did you try placing
> > > -Dibm.cl.verbose=ClassToTrace MainClass in your JAVA_OPTS e.g.
> > > java -Dibm.cl.verbose=ClassToTrace
> > > com.ibm.ejs.jms.JMSConnectionFactoryFactory -jar bootstrap.jar
> > > http://www.ibm.com/developerworks/java/library/j-dclp1/
> > > 
> > > Thanks,
> > > Martin 
> > > __ 
> > > Disclaimer and confidentiality note 
> > > Everything in this e-mail and any attachments relates to the 
official
> > > business of Sender. This transmission is of a confidential nature 
and
> > > Sender does not endorse distribution to any party other than 
intended
> > > recipient. Sender does not necessarily endorse content contained 
within
> > > this transmission. 
> > > 
> > > 
> > >> Date: Sat, 25 Oct 2008 18:02:58 -0700
> > >> From: [EMAIL PROTECTED]
> > >> To: axis-dev@ws.apache.org
> > >> Subject: Re: Axis2 JMSListener on Websphere
> > >> 
> > >> 
> > >> Thanks Andreas,
> > >> 
> > >> I tried removing jms.jar from the war and then deployed with 
"parent
> > >> last"
> > >> on WAS. 
> > >> 
> > >> WAS now fills the logs with huge exceptions now : 
> > >> 
> > >> [10/25/08 20:57:34:171 EDT] 0022 ConnectionFac E J2CA0009E: An
> > >> exception occurred while trying to instantiate the
> > >> ManagedConnectionFactory
> > >> class com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory used by 
resource
> > >> jms/appRequestQCF : java.lang.IllegalArgumentException
> > >> 
> > >> [10/25/08 20:57:34:376 EDT] 0022 Helpers W NMSV0605W: A
> > >> javax.naming.Reference object looked up from the context
> 

Re: wsa:MessageID header required?

[Brian De Pradine]

Hi Jarek,

Please see my response below.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Jarek Gawor" <[EMAIL PROTECTED]> wrote on 07/10/2008 20:34:50:

> Hey all,
> 
> Looks like Axis2 requires the wsa:MessageID header to be set when
> using the 2005/08 (final) addressing spec (see
> AddressingValidationHandler.checkMessageIDHeader()).

We only check for the header when the operation that is invoked is a 
request-response mep.

> I'm looking at
> the spec and the MessageID header is marked as optional (not sending
> it might cause problems with message correlation on the ReplyTo or
> FaultTo receiver but that's a separate issue).

Message correlation is not a separate issue, as this is precisely why we 
are checking the
message id. It is also stated in the spec that this should be done 
(admittedly not in the
most obvious way). See below.

> Is this a bug or did I
> miss something?

http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#formreplymsg
(read the last bullet of point 1.)

> 
> Thanks,
> Jarek
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: svn commit: r683656 - in /webservices/axis2/trunk/java/modules: addressing/src/org/apache/axis2/handlers/addressing/AddressingValidationHandler.java kernel/src/org/apache/axis2/addressing/Addressi

[Brian De Pradine]

Hi Glen,

Yes, sorry about that. There is now a new test in the kernel module, 
AddressingBasedDispatcherTest, to cover that function.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Glen Daniels <[EMAIL PROTECTED]> wrote on 08/08/2008 07:21:10:

> Hi Brian:
> 
> This commit caused a broken build (NPE at 
> AddressingValidationHandler.java:51), so I commented out the test which 
> confirms that the ADDR_VALIDATE_ACTION flag works.  I haven't been 
> tracking what's up with this... can you vet that things are working as 
> expected?  Is this functionality used by Synapse?
> 
> Thanks,
> --Glen
> 
> [EMAIL PROTECTED] wrote:
> > Author: pradine
> > Date: Thu Aug  7 10:30:38 2008
> > New Revision: 683656
> > 
> > URL: http://svn.apache.org/viewvc?rev=683656&view=rev
> > Log:
> > Allow components to disable the invocation pattern validation 
> performed by WS-Addressing.
> > 
> > Modified:
> > 
> 
webservices/axis2/trunk/java/modules/addressing/src/org/apache/axis2/handlers/addressing/AddressingValidationHandler.
> java
> > 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/addressing/AddressingConstants.
> java
> > 
> > Modified: 
> 
webservices/axis2/trunk/java/modules/addressing/src/org/apache/axis2/handlers/addressing/AddressingValidationHandler.
> java
> > URL: http://svn.apache.
> 
org/viewvc/webservices/axis2/trunk/java/modules/addressing/src/org/apache/axis2/handlers/addressing/AddressingValidationHandler.
> java?rev=683656&r1=683655&r2=683656&view=diff
> > 
> 
==
> > --- 
> 
webservices/axis2/trunk/java/modules/addressing/src/org/apache/axis2/handlers/addressing/AddressingValidationHandler.
> java (original)
> > +++ 
> 
webservices/axis2/trunk/java/modules/addressing/src/org/apache/axis2/handlers/addressing/AddressingValidationHandler.
> java Thu Aug  7 10:30:38 2008
> > @@ -48,24 +48,18 @@
> >  }
> > 
> >  if (JavaUtils.isTrueExplicitly(flag)) {
> > -// If no AxisOperation has been found at the end of 
> the dispatch phase and addressing
> > -// is in use we should throw an ActionNotSupported 
> Fault, unless we've been told
> > -// not to do this check (by Synapse, for instance)
> > -if (JavaUtils.isTrue(msgContext.
> getProperty(ADDR_VALIDATE_ACTION), true)) {
> > -// Check if the wsa:MessageID is required or not.
> > -checkMessageIDHeader(msgContext);
> > -}
> > +// Check if the wsa:MessageID is required or not.
> > +checkMessageIDHeader(msgContext);
> >  }
> > -
> > -if (JavaUtils.isFalseExplicitly(flag)) {
> > +else {
> >  // Check that if wsaddressing=required that 
> addressing headers were found inbound
> >  checkUsingAddressing(msgContext);
> >  }
> > 
> > -// Check that if wsamInvocationPattern flag is in effect 
> that the replyto and faultto are valid
> > -// This method must always be called to ensure that the 
> async required invocation pattern is
> > -// enforced.
> > -checkWSAMInvocationPattern(msgContext);
> > +// Check that if wsamInvocationPattern flag is in effect 
> that the replyto and faultto are valid.
> > +if (JavaUtils.isTrue(msgContext.
> getProperty(ADDR_VALIDATE_INVOCATION_PATTERN), true)) {
> > +checkWSAMInvocationPattern(msgContext);
> > +}
> > 
> >  return InvocationResponse.CONTINUE;
> >  }
> > @@ -106,7 +100,7 @@
> >  String value =
> >  AddressingHelper.
> getInvocationPatternParameterValue(msgContext.getAxisOperation());
> >  if (log.isTraceEnabled()) {
> > -log.trace("checkAnonymous: value=" + value);
> > +log.trace("checkWSAMInvocationPattern: value=" + value);
> >  }
> >  if(!AddressingConstants.WSAM_INVOCATION_PATTERN_BOTH.
> equals(value)){
> > if (WSAM_INVOCATION_PATTERN_SYNCHRONOUS.equals(value)) {
> > 
> > Modified: 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/addressing/AddressingConstants.
> java
> > URL: http://svn.apache.
> 
org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/addressing/AddressingConstants.
> java?rev=683656&r1=683655&r2=683656&view=diff
> > 
> 
==
> > --- 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/addressing/AddressingConstants.
> java (original)
> > +++ 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/addressing/AddressingConstants.
> java Thu Aug  7 10:30:38 2008
> > @@ -47,6 +47,7 @@
> >  static final String IS_ADDR_INFO_ALREADY_PROCESSED = 
> "IsAddres

Re: [Axis2][VOTE] Axis2 1.4 FINAL - Take #2

[Brian De Pradine]

+1

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Davanum Srinivas <[EMAIL PROTECTED]> wrote on 26/04/2008 17:05:07:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Folks,
> 
> Firstly, Many thanks to Dan Kulp for reviewing the previous cut. 
> I've moved the old directory away (to FINAL-TAKE1 under
> http://people.apache.org/~dims/axis2-1.4/) and placed the new files.
> 
> So please review:
> http://people.apache.org/~dims/axis2-1.4/FINAL/dist/
> 
> The m2 repository is here:
> http://people.apache.org/~dims/axis2-1.4/FINAL/m2-repo/
> 
> SVN Info:
> revision is 651799 on https://svn.apache.
> org/repos/asf/webservices/axis2/branches/java/1_4
> 
> Here's my +1 to declaring the above dist as Axis2 1.4 FINAL.
> 
> Thanks,
> dims
> 
> PS: Here are links to the individual Zip/Jar/Mar files:
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/1_4/axis2-1.4-bin.zip
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/1_4/axis2-1.4-docs.zip
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/1_4/axis2-1.4-src.zip
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/1_4/axis2-1.4-war.zip
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/modules/addressing/1_4/addressing-1.4.mar
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/modules/soapmonitor/1_4/soapmonitor-1.4.mar
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/tools/1_4/axis2-aar-maven-plugin-1.4.jar
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/tools/1_4/axis2-ant-plugin-1.4.jar
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-codegen-wizard-1.4.zip
> http://people.apache.org/~dims/axis2-1.
> 
4/FINAL/dist/ws/axis2/tools/1_4/axis2-eclipse-service-archiver-wizard-1.4.zip
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/tools/1_4/axis2-idea-plugin-1.4.zip
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/tools/1_4/axis2-java2wsdl-maven-plugin-1.4.jar
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/tools/1_4/axis2-mar-maven-plugin-1.4.jar
> http://people.apache.org/~dims/axis2-1.
> 4/FINAL/dist/ws/axis2/tools/1_4/axis2-wsdl2code-maven-plugin-1.4.jar
> 
> PPS: FYI, The Apache SVN is down for an outage/maintainenance. You 
> can see the diffs on axis-cvs mailing list if you are
> curious.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.5 (Cygwin)
> 
> iD8DBQFIE1KygNg6eWEDv1kRAu7wAKDVq0+uCdEWjZosM8Pm1ApUU8NvUwCfW+i0
> jC6ej20Yz6dNAYP71wO0xTY=
> =1WnY
> -END PGP SIGNATURE-
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: Does Axis2 support catalog facility in JAX-WS .

[Brian De Pradine]

Hi Venu,

You should give axis2 1.4 a try. RC1 should be available soon.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Venugopala Chanrayappa <[EMAIL PROTECTED]> wrote on 14/03/2008 10:27:44:

> 
> Hi guys,
> 
> I would like to know, is the axis2 support JAX-WS Catalog Faciltiy or 
not.
> Can some-one reply to this.
> 
> Regards
> Venu
> 
> 
--
> 
> "Be mindful" and let the senses do the rest.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [VOYE][Axis2] Dims as 1.4 Release Manager

[Brian De Pradine]

+1

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?




Dustin Amrhein <[EMAIL PROTECTED]> 
07/03/2008 21:50
Please respond to
axis-dev@ws.apache.org


To
axis-dev@ws.apache.org
cc

Subject
Re: [VOYE][Axis2] Dims as 1.4 Release Manager






+1

Nikhil V Thaker <[EMAIL PROTECTED]> wrote:

+1 

Nikhil Thaker
office: 512 838 9964
[EMAIL PROTECTED] 


Deepal jayasinghe <[EMAIL PROTECTED]> 
03/07/2008 12:13 AM 

Please respond to
axis-dev@ws.apache.org


To
axis-dev@ws.apache.org 
cc

Subject
[VOYE][Axis2] Dims as 1.4 Release Manager








Hi Dims,
>
>
> Deepal,
> Would you have time for Axis2? I can volunteer as Release Manager if 
> you wish or we can share the responsibility as
> usual. Either works for me.
To be honest I was about to send a vote  mail to the list making you as 
the release manager. So I am glad to see you as the release manager here 
is my +1 for you.

And now it is your job to tell us the release plan and how we are going 
to :) .

Thanks
Deepal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



 Looking for last minute shopping deals? Find them fast with Yahoo! 
Search.






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [VOTE] Michele Mazzucco as Axis2 Committer

[Brian De Pradine]

+1 from me.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Davanum Srinivas <[EMAIL PROTECTED]> wrote on 03/03/2008 15:31:26:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Folks,
> 
> I am tired of applying Michele's patches :) So Let's please invite 
> Michele to join us as a committer
> 
> Please see all of Michele's efforts here. Lot's of user mailing list
> participation, tons of JIRA's and Patches!
> 
> http://apache.markmail.org/search/?q=Michele%20Mazzucco
> 
> Thanks,
> dims
> 
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.5 (Cygwin)
> 
> iD8DBQFHzBnOgNg6eWEDv1kRAvDnAKCeCC/O3QqVTlSTd0lmoiaPxPyjQgCfXO2c
> Q4uwcvSTy7ISzs4TEHaR1fo=
> =nRyn
> -END PGP SIGNATURE-
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Axis2] Deploying JAXWS classes from WEB-INF/classes (for TCK)

[Brian De Pradine]

I believe that the jaxws-rt.jar would only be needed if it is required by 
the jaxws-tools.jar, otherwise I do not believe that it is needed.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Davanum Srinivas <[EMAIL PROTECTED]> wrote on 15/02/2008 14:22:13:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> jaxws-api.jar is definitely not needed as we have ours...am not 
sureabout rt.
> 
> thanks,
> dims
> 
> Brian De Pradine wrote:
> | Not sure that these are needed,
> |
> |> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-api.jar
> |> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-rt.jar
> |
> |
> | Cheers
> |
> | Brian DePradine
> | Web Services Development
> | IBM Hursley
> | External  +44 (0) 1962 816319 Internal 246319
> |
> | If you can't find the time to do it right the first time, where will 
you
> | find the time to do it again?
> |
> |
> | Davanum Srinivas <[EMAIL PROTECTED]> wrote on 14/02/2008 19:23:13:
> |
> | Team,
> |
> | Here's what i got working.
> |
> | - Place axis2.xml in WEB-INF/
> | - Make sure you comment out the addressing module in axis2.xml
> | - Make sure you add an entry for JAXWSDeployer in axis2.xml
> | ~  
> | - Drop classes in WEB-INF/classes
> | - Drop wsdl/xsd's in WEB-INF/wsdl
> | - Drop all the jars including jaxws ones in WEB-INF/lib as usual
> | - Here's what my directory structure looks when i deploy the war.
> |
> | C:\tomcat\webapps\axis2\WEB-INF\axis2.xml
> | C:\tomcat\webapps\axis2\WEB-INF\web.xml
> | C:\tomcat\webapps\axis2\WEB-INF\classes\endpoint\Calculator.class
> | C:\tomcat\webapps\axis2\WEB-INF\classes\endpoint\StringProvider.class
> | C:\tomcat\webapps\axis2\WEB-INF\lib\activation-1.1.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\annogen-0.1.0.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\antlr-2.7.7.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axiom-api-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axiom-dom-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axiom-impl-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-adb-codegen-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-adb-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-codegen-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-corba-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-fastinfoset-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-java2wsdl-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jaxbri-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jaxws-api-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jaxws-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jibx-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-json-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jws-api-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-kernel-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-metadata-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-saaj-api-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-saaj-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-spring-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-xmlbeans-SNAPSHOT.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\backport-util-concurrent-3.1.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\commons-codec-1.3.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\commons-fileupload-1.2.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\commons-httpclient-3.1.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\commons-io-1.4.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\commons-logging-1.1.1.jar
> | 
C:\tomcat\webapps\axis2\WEB-INF\lib\geronimo-annotation_1.0_spec-1.1.jar
> | 
C:\tomcat\webapps\axis2\WEB-INF\lib\geronimo-stax-api_1.0_spec-1.0.1.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\httpcore-4.0-alpha6.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\httpcore-nio-4.0-alpha6.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\httpcore-niossl-4.0-alpha6.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jaxb-api-2.1.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jaxb-impl-2.1.6.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jaxb-xjc-2.1.6.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jaxen-1.1.1.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-api.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-rt.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-tools.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jettison-1.0-RC2.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jibx-bind-1.1.5.jar
> | C:\tomcat\webapps\axis2\WEB-INF\lib\jibx-run-1.1.5.jar
> |

Re: [Axis2] Deploying JAXWS classes from WEB-INF/classes (for TCK)

[Brian De Pradine]

Not sure that these are needed,

> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-api.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-rt.jar


Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Davanum Srinivas <[EMAIL PROTECTED]> wrote on 14/02/2008 19:23:13:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Team,
> 
> Here's what i got working.
> 
> - - Place axis2.xml in WEB-INF/
> - - Make sure you comment out the addressing module in axis2.xml
> - - Make sure you add an entry for JAXWSDeployer in axis2.xml
> ~  
> - - Drop classes in WEB-INF/classes
> - - Drop wsdl/xsd's in WEB-INF/wsdl
> - - Drop all the jars including jaxws ones in WEB-INF/lib as usual
> - - Here's what my directory structure looks when i deploy the war.
> 
> C:\tomcat\webapps\axis2\WEB-INF\axis2.xml
> C:\tomcat\webapps\axis2\WEB-INF\web.xml
> C:\tomcat\webapps\axis2\WEB-INF\classes\endpoint\Calculator.class
> C:\tomcat\webapps\axis2\WEB-INF\classes\endpoint\StringProvider.class
> C:\tomcat\webapps\axis2\WEB-INF\lib\activation-1.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\annogen-0.1.0.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\antlr-2.7.7.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axiom-api-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axiom-dom-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axiom-impl-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-adb-codegen-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-adb-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-codegen-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-corba-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-fastinfoset-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-java2wsdl-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jaxbri-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jaxws-api-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jaxws-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jibx-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-json-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-jws-api-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-kernel-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-metadata-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-saaj-api-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-saaj-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-spring-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\axis2-xmlbeans-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\backport-util-concurrent-3.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\commons-codec-1.3.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\commons-fileupload-1.2.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\commons-httpclient-3.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\commons-io-1.4.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\commons-logging-1.1.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\geronimo-annotation_1.0_spec-1.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\geronimo-stax-api_1.0_spec-1.0.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\httpcore-4.0-alpha6.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\httpcore-nio-4.0-alpha6.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\httpcore-niossl-4.0-alpha6.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxb-api-2.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxb-impl-2.1.6.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxb-xjc-2.1.6.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxen-1.1.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-api.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-rt.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jaxws-tools.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jettison-1.0-RC2.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jibx-bind-1.1.5.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\jibx-run-1.1.5.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\log4j-1.2.15.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\mail-1.4.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\mex-impl-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\neethi-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\soapmonitor-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\woden-api-1.0-20080213.045734-9.jar
> 
C:\tomcat\webapps\axis2\WEB-INF\lib\woden-impl-dom-1.0-20080211.200232-8.jar
> 
C:\tomcat\webapps\axis2\WEB-INF\lib\woden-impl-dom-1.0-20080213.045734-9.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\wsdl4j-1.6.2.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\wstx-asl-3.2.4.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\xalan-2.7.0.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\xercesImpl-2.8.1.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\xml-apis-1.3.04.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\xmlbeans-2.3.0.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\XmlSchema-20080214.033952-25.jar
> C:\tomcat\webapps\axis2\WEB-INF\lib\XmlSchema-SNAPSHOT.jar
> C:\tomcat\webapps\axis2\WEB-INF\wsdl\CalculatorService.wsdl
> C:\

Re: svn commit: r620464 - /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/AxisService.java

[Brian De Pradine]

Hi Dims,

It seemed like a reasonable fix at the time, plus I was reusing the fix 
that currently applies to ?wsdl for this same problem. Your solution is 
probably better though and should be applied to ?xsd and ?wsdl. I will 
apply this change to both.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Davanum Srinivas <[EMAIL PROTECTED]> wrote on 11/02/2008 11:43:45:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Brian,
> 
> Why are we special casing just http? would this work better?
> 
>  if (attributeValue.indexOf("://")!=-1){
> attribute.setNodeValue(this.name + "?xsd=" + 
attributeValue);
>  }
> 
> thanks,
> dims
> 
> [EMAIL PROTECTED] wrote:
> | Author: pradine
> | Date: Mon Feb 11 03:32:34 2008
> | New Revision: 620464
> |
> | URL: http://svn.apache.org/viewvc?rev=620464&view=rev
> | Log:
> | Fix for AXIS2-3503.
> |
> | Modified:
> | 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/AxisService.
> java
> |
> | Modified: 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/AxisService.
> java
> | URL:
> http://svn.apache.
> 
org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/AxisService.
> java?rev=620464&r1=620463&r2=620464&view=diff
> | 
> 
==
> | --- 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/AxisService.
> java (original)
> | +++ 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/AxisService.
> java Mon Feb 11 03:32:34 2008
> | @@ -39,7 +39,6 @@
> |  import java.util.Iterator;
> |  import java.util.List;
> |  import java.util.Map;
> | -import java.util.Set;
> |  import java.util.Vector;
> |
> |  import javax.wsdl.Definition;
> | @@ -1087,7 +1086,9 @@
> |  attribute = nodeMap.item(i);
> |  if (attribute.getNodeName().equals("schemaLocation")) {
> |  attributeValue = attribute.getNodeValue();
> | -attribute.setNodeValue(this.name + "?xsd=" + 
> attributeValue);
> | +if (!attributeValue.startsWith("http")) {
> | +attribute.setNodeValue(this.name + "?xsd=" + 
> attributeValue);
> | +}
> |  }
> |  }
> |  }
> | @@ -2323,15 +2324,17 @@
> |Hashtable importedScheams,
> |Hashtable 
> sourceURIToNewLocationMap) {
> |  if (s != null) {
> | -
> | -String newscheamlocation = customSchemaNamePrefix == null 
?
> | -//use the default mode
> | -(getName() + "?xsd=" + 
> getScheamLocationWithDot(sourceURIToNewLocationMap, s)) :
> | -//custom prefix is present - add the custom 
prefix
> | -(customSchemaNamePrefix + 
> getScheamLocationWithDot(sourceURIToNewLocationMap, s));
> |  String schemaLocation = 
xmlSchemaExternal.getSchemaLocation();
> | -xmlSchemaExternal.setSchemaLocation(newscheamlocation);
> | -importedScheams.put(schemaLocation, newscheamlocation);
> | +
> | +if (!schemaLocation.startsWith("http")) {
> | +String newscheamlocation = customSchemaNamePrefix== 
null ?
> | +//use the default mode
> | +(getName() + "?xsd=" + 
> getScheamLocationWithDot(sourceURIToNewLocationMap, s)) :
> | +//custom prefix is present - add the 
> custom prefix
> | +(customSchemaNamePrefix + 
> getScheamLocationWithDot(sourceURIToNewLocationMap, s));
> | + xmlSchemaExternal.setSchemaLocation(newscheamlocation);
> | +importedScheams.put(schemaLocation, 
newscheamlocation);
> | +}
> |  }
> |  }
> |
> |
> |
> |
> | -
> | To unsubscribe, e-mail: [EMAIL PROTECTED]
> | For additional commands, e-mail: [EMAIL PROTECTED]
> |
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.5 (Cygwin)
> 
> iD8DBQFHsDTxgNg6eWEDv1kRAkApAKDmSQde7Of/CGouRvFttoXjDYLlqACfRQJK
> h19aWV8tdRiqT0gxNNkKp6A=
> =kpTQ
> -END PGP SIGNATURE-
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Axis2] JAX-WS 2.1 Merge

[Brian De Pradine]

I have raised a JIRA here, 
https://issues.apache.org/jira/browse/AXIS2-3479

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Davanum Srinivas <[EMAIL PROTECTED]> wrote on 27/01/2008 18:34:35:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Brian,
> 
> Could u please add a JIRA lest we forget?
> 
> thanks,
> dims
> 
> Brian De Pradine wrote:
> | The merge of the JAX-WS 2.1 code changes into the trunk is now 
complete.
> | All future development of JAX-WS 2.1 should take place in the trunk. 
The
> | one outstanding issue is with
> | org.apache.axis2.jaxws.sample.MtomSampleTests. It keeps failing 
whenever I
> | run a maven build, but when I run it on it's own, inside Eclipse, it
> | passes every time! To get around this issue I have commented out that 
test
> | for now. The failure I get is captured below.
> |
> | testSendImageAttachmentProperty12(org.apache.axis2.jaxws.sample.
> MtomSampleTests)
> |  Time elapsed: 0.219 sec  <<< FAILURE!
> | junit.framework.AssertionFailedError: Was expecting an exception due 
to
> | sending SOAP12 message to SOAP11 endpoint.
> | at junit.framework.Assert.fail(Assert.java:47)
> | at
> | org.apache.axis2.jaxws.sample.MtomSampleTests.
> testSendImageAttachmentProperty12(MtomSampleTests.java:224)
> | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> | at
> | sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39)
> | at
> | sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25)
> | at java.lang.reflect.Method.invoke(Method.java:585)
> | at junit.framework.TestCase.runTest(TestCase.java:168)
> | at junit.framework.TestCase.runBare(TestCase.java:134)
> | at junit.framework.TestResult$1.protect(TestResult.java:110)
> | at 
junit.framework.TestResult.runProtected(TestResult.java:128)
> | at junit.framework.TestResult.run(TestResult.java:113)
> | at junit.framework.TestCase.run(TestCase.java:124)
> | at junit.framework.TestSuite.runTest(TestSuite.java:232)
> | at junit.framework.TestSuite.run(TestSuite.java:227)
> | at junit.framework.TestSuite.runTest(TestSuite.java:232)
> | at junit.framework.TestSuite.run(TestSuite.java:227)
> | at 
junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> | at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> | at 
junit.framework.TestResult.runProtected(TestResult.java:128)
> | at junit.extensions.TestSetup.run(TestSetup.java:27)
> | at
> | org.junit.internal.runners.OldTestClassRunner.
> run(OldTestClassRunner.java:76)
> | at
> | org.apache.maven.surefire.junit4.JUnit4TestSet.
> execute(JUnit4TestSet.java:62)
> | at
> | org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.
> executeTestSet(AbstractDirectoryTestSuite.java:138)
> | at
> | org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.
> execute(AbstractDirectoryTestSuite.java:125)
> | at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> | at
> | sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39)
> | at
> | sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25)
> | at java.lang.reflect.Method.invoke(Method.java:585)
> | at
> | org.apache.maven.surefire.booter.SurefireBooter.
> runSuitesInProcess(SurefireBooter.java:290)
> | at
> | org.apache.maven.surefire.booter.SurefireBooter.
> main(SurefireBooter.java:818)
> |
> |
> | Cheers
> |
> | Brian DePradine
> | Web Services Development
> | IBM Hursley
> | External  +44 (0) 1962 816319 Internal 246319
> |
> | If you can't find the time to do it right the first time, where will 
you
> | find the time to do it again?
> |
> |
> |
> |
> |
> |
> | Unless stated otherwise above:
> | IBM United Kingdom Limited - Registered in England and Wales with 
number
> | 741598.
> | Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 
3AU
> |
> |
> |
> |
> |
> |
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.5 (Cygwin)
> 
> iD8DBQFHnM67gNg6eWEDv1kRAuz9AKCySZoD82dj8z8eYN7/5g1wLZTjVQCgnoBD
> cqSi0GNVp0+wq/LfauqxhWI=
> =s+bW
> -END PGP SIGNATURE-
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Fw: [Axis2] JAX-WS 2.1 Merge

[Brian De Pradine]

Resend with [Axis2] in the subject.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?

- Forwarded by Brian De Pradine/UK/IBM on 27/01/2008 18:42 -----

Brian De Pradine/UK/[EMAIL PROTECTED] wrote on 27/01/2008 18:32:43:

> 
> The merge of the JAX-WS 2.1 code changes into the trunk is now 
> complete. All future development of JAX-WS 2.1 should take place in 
> the trunk. The one outstanding issue is with  org.apache.axis2.
> jaxws.sample.MtomSampleTests. It keeps failing whenever I run a 
> maven build, but when I run it on it's own, inside Eclipse, it 
> passes every time! To get around this issue I have commented out 
> that test for now. The failure I get is captured below. 
> 
> testSendImageAttachmentProperty12(org.apache.axis2.jaxws.sample.
> MtomSampleTests)  Time elapsed: 0.219 sec  <<< FAILURE! 
> junit.framework.AssertionFailedError: Was expecting an exception due
> to sending SOAP12 message to SOAP11 endpoint. 
> at junit.framework.Assert.fail(Assert.java:47) 
> at org.apache.axis2.jaxws.sample.MtomSampleTests.
> testSendImageAttachmentProperty12(MtomSampleTests.java:224) 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39) 
> at sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25) 
> at java.lang.reflect.Method.invoke(Method.java:585) 
> at junit.framework.TestCase.runTest(TestCase.java:168) 
> at junit.framework.TestCase.runBare(TestCase.java:134) 
> at junit.framework.TestResult$1.protect(TestResult.java:110) 
> at junit.framework.TestResult.runProtected(TestResult.java:128) 
> at junit.framework.TestResult.run(TestResult.java:113) 
> at junit.framework.TestCase.run(TestCase.java:124) 
> at junit.framework.TestSuite.runTest(TestSuite.java:232) 
> at junit.framework.TestSuite.run(TestSuite.java:227) 
> at junit.framework.TestSuite.runTest(TestSuite.java:232) 
> at junit.framework.TestSuite.run(TestSuite.java:227) 
> at 
junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) 
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23) 
> at junit.framework.TestResult.runProtected(TestResult.java:128) 
> at junit.extensions.TestSetup.run(TestSetup.java:27) 
> at org.junit.internal.runners.OldTestClassRunner.
> run(OldTestClassRunner.java:76) 
> at org.apache.maven.surefire.junit4.JUnit4TestSet.
> execute(JUnit4TestSet.java:62) 
> at org.apache.maven.surefire.suite.
> 
AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
> at org.apache.maven.surefire.suite.
> AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) 
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39) 
> at sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25) 
> at java.lang.reflect.Method.invoke(Method.java:585) 
> at org.apache.maven.surefire.booter.SurefireBooter.
> runSuitesInProcess(SurefireBooter.java:290) 
> at org.apache.maven.surefire.booter.SurefireBooter.
> main(SurefireBooter.java:818) 
> 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> 
> 

> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with 
> number 741598. 
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 
3AU 
> 
> 
> 
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

JAX-WS 2.1 Merge

[Brian De Pradine]

The merge of the JAX-WS 2.1 code changes into the trunk is now complete. 
All future development of JAX-WS 2.1 should take place in the trunk. The 
one outstanding issue is with 
org.apache.axis2.jaxws.sample.MtomSampleTests. It keeps failing whenever I 
run a maven build, but when I run it on it's own, inside Eclipse, it 
passes every time! To get around this issue I have commented out that test 
for now. The failure I get is captured below.

testSendImageAttachmentProperty12(org.apache.axis2.jaxws.sample.MtomSampleTests)
 
 Time elapsed: 0.219 sec  <<< FAILURE!
junit.framework.AssertionFailedError: Was expecting an exception due to 
sending SOAP12 message to SOAP11 endpoint.
at junit.framework.Assert.fail(Assert.java:47)
at 
org.apache.axis2.jaxws.sample.MtomSampleTests.testSendImageAttachmentProperty12(MtomSampleTests.java:224)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at 
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)


Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Axis2] JAXWS version in Axis2 1.4

[Brian De Pradine]

Hello devs,

Given that jax-ws 2.1 seems to be an important deliverable for Axis2 1.4, 
and that people other than myself are starting to contribute to the 
development effort. I propose to merge the contents of the jax-ws 2.1 
branch into the trunk and to continue development in the trunk from now 
on. The JIRA for jax-ws 2.1 [1] has been updated with the details of the 
changes that will be moved across for anyone who is interested.

[1] https://issues.apache.org/jira/browse/AXIS2-2722

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Nicholas L Gallardo <[EMAIL PROTECTED]> wrote on 18/01/2008 14:55:34:

> Thanks for pointing out that JIRA Jeff.
> 
> I created a page to jot down a few more thoughts on what must/should
> be done to get the deployment right. What's there is just a start. 
> I'll keep adding to it as I think about this a little more. 
> 
> Any one else should please feel free to add any relevant information 
there.
> 
> http://wiki.apache.org/ws/Axis2/JAX-WS_Integration
> 
> -Nick
> 
> 
> [image removed] Jeff Barrett/Austin/[EMAIL PROTECTED]
> 

> 
> Jeff Barrett/Austin/[EMAIL PROTECTED] 
> 01/17/2008 09:34 AM 
> 
> Please respond to
> axis-dev@ws.apache.org
> 
> [image removed] 
> To
> 
> [image removed] 
> axis-dev@ws.apache.org
> 
> [image removed] 
> cc
> 
> [image removed] 
> 
> [image removed] 
> Subject
> 
> [image removed] 
> Re: [Axis2] JAXWS version in Axis2 1.4
> 
> [image removed] 
> 
> [image removed] 
> 
> 
> Hi All,
> 
> I agree with Nick's suggestion of certifying based on JAXWS 2.1 rather 
> than 2.0.
> 
> In any case, we need to get the JAXWS deployment hooked into the Axis2 
> deployment.  There's already a JIRA for that: 
> https://issues.apache.org/jira/browse/AXIS2-3223 
> 
> Thanks,
> Jeff
> 
> IBM Software Group - WebSphere Web Services Development
> Phone: 512-838-4587 or Tie Line 678-4587
> Internet e-mail and Sametime ID: [EMAIL PROTECTED]
> 
> 
> 
> Brian De Pradine <[EMAIL PROTECTED]> 
> 01/15/2008 11:17 AM
> Please respond to
> axis-dev@ws.apache.org
> 
> 
> To
> axis-dev@ws.apache.org
> cc
> 
> Subject
> Re: [Axis2] JAXWS version in Axis2 1.4
> 
> 
> 
> 
> 
> 
> 
> Hi Dims, Nick 
> 
> It would be good to get the code that is currently in the jaxws21 branch 

> moved over to the trunk asap. There is also an existing JIRA to cover 
the 
> JAX-WS 2.1 development in general, 
> http://issues.apache.org/jira/browse/AXIS2-2722 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will you 

> find the time to do it again?
> 
> 
> Nicholas L Gallardo <[EMAIL PROTECTED]> wrote on 15/01/2008 17:00:38:
> 
> > Dims,
> > 
> > Thanks for starting the discussion. I wasn't aware of jcp-open. It's
> > good to know there's an open forum for that information.
> > 
> > Wrt. Axis2 1.4, my vote is that we certify based on JAX-WS 2.1 
> > rather than 2.0. Brian has done a large amount of work in the 
> > jaxws21 branch. We can merge that over and then get moving on 
> > running the TCK and seeing where we are. 
> > 
> > -Nick
> > 
> > [image removed] "Davanum Srinivas" <[EMAIL PROTECTED]>
> > 
> 
> > 
> > "Davanum Srinivas" <[EMAIL PROTECTED]> 
> > 01/15/2008 10:19 AM 
> > 
> > Please respond to
> > axis-dev@ws.apache.org 
> > 
> > [image removed] 
> > To 
> > 
> > [image removed] 
> > "axis-dev@ws.apache.org"  
> > 
> > [image removed] 
> > cc 
> > 
> > [image removed] 
> > 
> > [image removed] 
> > Subject 
> > 
> > [image removed] 
> > Re: [Axis2] JAXWS version in Axis2 1.4 
> > 
> > [image removed] 
> > 
> > [image removed] 
> > 
> > 
> > Some discussion on jcp-open as well.
> > 
> > [4] http://news.gmane.org/gmane.comp.apache.jcp%2dopen
> > 
> > -- dims
> > 
> > On Jan 15, 2008 11:17 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> > > Glen, Sandakith, Jeff, Nick, Rich,
> > >
> > > - I believe the jaxws-tck svn and the associated mailing list is 
> ready.
> > > - cxf folks i am told are running JAXWS 2.1 TCK
> &

Re: [Axis2] JAXWS version in Axis2 1.4

[Brian De Pradine]

Hi Dims, Nick

It would be good to get the code that is currently in the jaxws21 branch 
moved over to the trunk asap. There is also an existing JIRA to cover the 
JAX-WS 2.1 development in general, 
http://issues.apache.org/jira/browse/AXIS2-2722

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Nicholas L Gallardo <[EMAIL PROTECTED]> wrote on 15/01/2008 17:00:38:

> Dims,
> 
> Thanks for starting the discussion. I wasn't aware of jcp-open. It's
> good to know there's an open forum for that information.
> 
> Wrt. Axis2 1.4, my vote is that we certify based on JAX-WS 2.1 
> rather than 2.0. Brian has done a large amount of work in the 
> jaxws21 branch. We can merge that over and then get moving on 
> running the TCK and seeing where we are. 
> 
> -Nick
> 
> [image removed] "Davanum Srinivas" <[EMAIL PROTECTED]>
> 

> 
> "Davanum Srinivas" <[EMAIL PROTECTED]> 
> 01/15/2008 10:19 AM 
> 
> Please respond to
> axis-dev@ws.apache.org
> 
> [image removed] 
> To
> 
> [image removed] 
> "axis-dev@ws.apache.org" 
> 
> [image removed] 
> cc
> 
> [image removed] 
> 
> [image removed] 
> Subject
> 
> [image removed] 
> Re: [Axis2] JAXWS version in Axis2 1.4
> 
> [image removed] 
> 
> [image removed] 
> 
> 
> Some discussion on jcp-open as well.
> 
> [4] http://news.gmane.org/gmane.comp.apache.jcp%2dopen
> 
> -- dims
> 
> On Jan 15, 2008 11:17 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> > Glen, Sandakith, Jeff, Nick, Rich,
> >
> > - I believe the jaxws-tck svn and the associated mailing list is 
ready.
> > - cxf folks i am told are running JAXWS 2.1 TCK
> > - Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside.
> >
> > So, what should we do for Axis2 1.4?  I just saw Nick's jira float by
> > [1] and wanted to kick start the discussion. Please see Steve's
> > analysis [2] and the JAXWS change log [3]
> >
> > thanks,
> > dims
> >
> > [1] https://issues.apache.org/jira/browse/AXIS2-3448
> > [2] http://1060.org/blogxter/publish/5
> > [3] http://jcp.
> 
org/aboutJava/communityprocess/maintenance/jsr224/JAXWS_2.1_ChangeLog.pdf
> >
> > --
> > Davanum Srinivas :: http://davanum.wordpress.com
> >
> 
> 
> 
> -- 
> Davanum Srinivas :: http://davanum.wordpress.com
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> [image removed] 





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: Prioritized list of 1.4 things to do

[Brian De Pradine]

Hi Glen,

What is the reasoning behind this requirement:

(1) Remove fault flows? (this is prioritized as critical because we need 
to finish the discussion whether or not we decide to do it)


Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Glen Daniels <[EMAIL PROTECTED]> wrote on 13/11/2007 15:59:59:

> Hi folks:
> 
> Deepal and I just did a quick prioritization pass on the list at [1]. 
> Please take a look and see if it matches your view of the world.  We 
> tried to be pretty simple about it, marking things on a three-level 
> scale where 1 = critical, 2 = important, and 3 = nice to have.
> 
> Couple of quick things to note - 1) we didn't consider how easy/hard 
> these things are; so some of the 3's are going to be 5-minute quick 
> fixes which can get done any time.  2) some of the priorities are about 
> making sure we finish discussion/design on things - so even if it's a 
> (1) that doesn't necessarily mean we'll change any code, just that we 
> MUST have the conversation soon.
> 
> Thanks,
> --G & D
> 
> [1] http://wiki.apache.org/ws/FrontPage/Axis2/post-1%2e3-plans
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Axis2][Strawman] Re-organise AddressingInHandler Code to take account of Security Considerations

[Brian De Pradine]

Hello David,

Please see my comments below.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"David Illsley" <[EMAIL PROTECTED]> wrote on 09/10/2007 14:04:37:

> As discussed a couple of months back, the current one-shot
> WS-Addressing header extraction isn't suited for use with security.
> This is because either:
> 1. Addressing runs before security and populates fields such as
> ReplyTo/FaultTo which, if later found to be invalid would not be
> un(de?)populated (which is a security risk).
> 2. Addressing runs after security, hence interoperable Operation-Level
> security is not possible as it relies on the WS-A Action/WS-A
> RelatesTo for operation identification.
> 
> I've thought about this problem a fair bit and I'm of the opinion that
> security is important enough that we should break the WS-A headers
> apart and change the model slightly.
> 
> The following proposal is very much open to change, but I do believe
> is in the right general direction.
> 
> AddressingDispatchExtractor
>   -- Extracts wsa:Action and/or wsa:RelatesTo value
>   -- Determines the correct AxisOperation/OperationContext for security
> -- Does not set them in normal place on message context in case
> they are invalid
> -- Places them on message context as properties
>   -- Sets WS-A namespace on message context to allow security + later
> WS-A handers to proces the correct headers
> 
> SecurityHandler(s)
>   -- Configured based on the AxisOperation extracted by the
> AddressingDispatchExtractor
>   -- Validates the WS-A headers with the selected namespace (if 
appropriate)
> 
> AddressingRemainderInHandler
>   -- Extracts remaining WS-A headers and sets them on the MessageContext
>   -- Amalgem of AddressingFinalInHandler and 
AddressingSubmissionInHandler
> -- Namespace has already been selected so makes sense to combine

Are you saying that the AddressingRemainderInHandler will no longer set 
the wsa:Action and wsa:RelatesTo values on the message context? I am 
trying to understand what you mean by "Remainder". Isn't this just the 
current AddressingInHandler with the function of the 
AddressingFinalInHandler and AddressingSubmissionInHandler pushed down 
into it?

> 
> General Dispatchers
> 
> SecuredAddressingDispatchValidator
>   --  Verfies that the AxisOperation to be invoked matches the
> AxisOperation used for security configuration
>   -- Only required if security is engaged
> 
> Backwards Compatibility
>   -- For users who haven't modified the WS-A Module  - no backwards 
> copat issues
>   -- For users who have, need to modify their custom module.xml to use
> the new handlers
> 
> Anyone have any thoughts on this?
> Cheers,
> David
> 
> -- 
> David Illsley - IBM Web Services Development
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: So Long, and Thanks for All the Fish

[Brian De Pradine]

Dims,

Thanks for all of your work that you have done. I don't know how we will 
be able to get along without you.
Come back soon.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Davanum Srinivas" <[EMAIL PROTECTED]> wrote on 29/09/2007 18:51:04:

> Dear WS folks,
> 
> FYI, I've asked to resign from the WS PMC as i strongly believe that a
> PMC member should actively participates on the projects. Unfortunately
> due to circumstances beyond my control/comprehension, i'll not be able
> to spend time on the various WS projects.
> 
> I'll miss each and every one of the participants here. It's been a
> long ride since 2001-04-19 when i first showed up on the axis-dev
> mailing list. I hope to be back some day (sooner than later! hope it
> is sooner!). You can still reach me on yahoo IM (dims) or email
> (davanum AT gmail.com). Wish you all the very best of luck.
> 
> thanks,
> dims
> 
> -- 
> Davanum Srinivas :: http://davanum.wordpress.com
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: Axis2 Roadmap questions

[Brian De Pradine]

Jeff,

In axis2 we will require some form of deploy-time processing of 
annotations. The current mechanism of lazily processing the annotations 
when the first message arrives for a JAX-WS web service will not be 
sufficient to support the new web service feature concept of JAX-WS 2.1. 

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Jeff Barrett <[EMAIL PROTECTED]> wrote on 17/09/2007 19:30:40:

> David,
> 
> I think Geronimo does things differently.  I think they process the DDs 
in 
> advance, then modify the annotation values (possibly in the 
> DescriptionBuilderComposite they create) based on the DDs, then persist 
> everything out.  At application startup, they read in the persisted 
> information and build everythign up that way.
> 
> Since they are already EE5 compliant (I believe), they must not need the 

> DD support to be in JAXWS.  I don't think JSR-109 and associated DD 
> support is optional in EE5.
> 
> After studying JSR-109, I think the approach of building the DBCs based 
on 
> the annotations then modifying those DBCs based on the Deployment 
> Descriptors is the best approach, as opposed to putting JSR-109 support 
> into JAXWS.
> 
> Thanks,
> Jeff
> 
> IBM Software Group - WebSphere Web Services Development
> Phone: 512-838-4587 or Tie Line 678-4587
> Internet e-mail and Sametime ID: [EMAIL PROTECTED]
> 
> 
> 
> "David Illsley" <[EMAIL PROTECTED]> 
> 09/17/2007 12:47 PM
> Please respond to
> axis-dev@ws.apache.org
> 
> 
> To
> axis-dev@ws.apache.org
> cc
> 
> Subject
> Re: Axis2 Roadmap questions
> 
> 
> 
> 
> 
> 
> Jeff,
> Presumably Geronimo will need 109 v2 support at some point, or is it
> optional for EE5 and EE6? Maybe that support (if it exists) could be
> used by anyone wanting it with Axis2...
> David
> 
> On 14/09/2007, Jeff Barrett <[EMAIL PROTECTED]> wrote:
> > Hi Dims,
> >
> > I believe the deployment descriptor is defined by JSR-109, not by 
> JAX-WS.
> >
> > I could be wrong, but I don't think anyone was planning on adding 
> JSR-109
> > support (and thus DDs) into the JAXWS (and associated metadata) 
module.
> >
> > Thanks,
> > Jeff
> >
> > IBM Software Group - WebSphere Web Services Development
> > Phone: 512-838-4587 or Tie Line 678-4587
> > Internet e-mail and Sametime ID: [EMAIL PROTECTED]
> >
> >
> >
> > "Davanum Srinivas" <[EMAIL PROTECTED]>
> > 09/14/2007 09:27 AM
> > Please respond to
> > axis-dev@ws.apache.org
> >
> >
> > To
> > axis-dev@ws.apache.org
> > cc
> >
> > Subject
> > Re: Axis2 Roadmap questions
> >
> >
> >
> >
> >
> >
> > Brian,
> >
> > Quick question about 2.1. does it define a descriptor for deploying
> > services? i remember seeing all the test cases in current trunk use
> > the services.xml with jaxws messagereceiver.  hence wondering..
> >
> > thanks,
> > dims
> >
> > On 9/14/07, Brian De Pradine <[EMAIL PROTECTED]> wrote:
> > >
> > > Hello,
> > >
> > > Yes, I am currently working on JAX-WS 2.1 support. It should be 
almost
> > ready
> > > to be moved across to the trunk, but I need to do some more testing
> > first. I
> > > will also have to start raising JIRAs for the remaining bits of 
work, 
> so
> > > that others can join in the fun.
> > >
> > >  Cheers
> > >
> > >  Brian DePradine
> > >  Web Services Development
> > >  IBM Hursley
> > >  External  +44 (0) 1962 816319 Internal 246319
> > >
> > >  If you can't find the time to do it right the first time, where 
will
> > you
> > > find the time to do it again?
> > >
> > >
> > > Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 13/09/2007
> > 19:48:19:
> > >
> > >
> > >  > Yadav, Yogendra (IT) wrote:
> > >  > > Hi Axis2 developers,
> > >  > >
> > >  > > I am interested to know the axis2 roadmap, I could not find 
this
> > >  > > information on the Axis2 web site. I am particularly interested 

> in
> > the
> > >  > > following:
> > >  > > 1. Support for Spring based configuration.
> > >  >
> > >  > We have some support but it can be improved radically if there's

Re: Axis2 Roadmap questions

[Brian De Pradine]

Dims,

No, those details have been delegated to JSR-109 which describes the 
webservices.xml deployment descriptor, amongst other things. As there is 
no implementation of JSR-109 yet we are forced to use the services.xml 
file explicitly.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Davanum Srinivas" <[EMAIL PROTECTED]> wrote on 14/09/2007 15:27:56:

> Brian,
> 
> Quick question about 2.1. does it define a descriptor for deploying
> services? i remember seeing all the test cases in current trunk use
> the services.xml with jaxws messagereceiver.  hence wondering..
> 
> thanks,
> dims
> 
> On 9/14/07, Brian De Pradine <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> >
> > Yes, I am currently working on JAX-WS 2.1 support. It should be almost 
ready
> > to be moved across to the trunk, but I need to do some more testing 
first. I
> > will also have to start raising JIRAs for the remaining bits of work, 
so
> > that others can join in the fun.
> >
> >  Cheers
> >
> >  Brian DePradine
> >  Web Services Development
> >  IBM Hursley
> >  External  +44 (0) 1962 816319 Internal 246319
> >
> >  If you can't find the time to do it right the first time, where will 
you
> > find the time to do it again?
> >
> >
> > Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 13/09/2007 
19:48:19:
> >
> >
> >  > Yadav, Yogendra (IT) wrote:
> >  > > Hi Axis2 developers,
> >  > >
> >  > > I am interested to know the axis2 roadmap, I could not find this
> >  > > information on the Axis2 web site. I am particularly interested 
in the
> >  > > following:
> >  > > 1. Support for Spring based configuration.
> >  >
> >  > We have some support but it can be improved radically if there's a 
need.
> >  > What do you have in mind?
> >  >
> >  > > 2. Support for JAX-WS 2.1.
> >  >
> >  > In progress .. I'm not sure exactly where we are; Brian, are you 
the one
> >  > working on it?
> >  >
> >  > > 3. Jetty and/or Grizzly based HTTP transports for Axis2.
> >  >
> >  > There's a Jetty transport that was written for WSO2 WSAS which is
> >  > available. I've never heard of Grizzly (except in Yellowstone ;-))!
> > Google
> >  > tells me Grizzly must be https://grizzly.dev.java.net/. Sounds like
> > that's
> >  > what we should be using instead of straight Jetty now?
> >  >
> >  > If you're looking for NIO with Jetty 6, then we have a 
better-than-Jetty
> >  > NIO transport that's based on the HTTP Core project! That was 
developed
> >  > for Synapse but its a raw HTTP transport for Axis2 and is now 
committed
> >  > here. It'll be great to do a perf eval of that vs. Jetty 6 and see 
how
> >  > they compare! The reason I said "better-than-Jetty" is because this
> >  > transport does NIO for both reading and writing .. something that 
Synapse
> >  > needed in order to scale well.
> >  >
> >  > > 4. If Axis2 will ever provide full duplex streaming support (I 
can read
> >  > > the input stream via XMLStreamReader in my handler class but 
can't
> > write
> >  > > to the output stream while processing XML events).
> >  >
> >  > It does provide full duplex streaming; it does that now for 
generated ADB
> >  > classes. This is done using OMSourcedElement .. which is basically 
a way
> >  > of deferring Java object -> XML serialization until its absolutely
> >  > necessary. At that time, the Java object can straight write itself 
to the
> >  > XML stream.
> >  >
> >  > Note that it has to be done this way because its necessary for 
Axis2 to
> >  > write the Envelope element etc. before asking the application to 
write
> > out
> >  > the payload. If the application wants to defer reading some of the 
input
> >  > until it starts writing the output that's possible thru the same
> >  > technique- you have an OMSourcedElement impl which hangs onto the
> > incoming
> >  > message context to get at the incoming message too.
> >  >
> >  > Hope this helps,
> >  >
> >  > Sanjiva.
> >  > --
> >  > Sanjiva Weerawarana, Ph.D.
> >  > Founder & Director; Lanka Software Foundati

Re: Axis2 Roadmap questions

[Brian De Pradine]

Hello,

Yes, I am currently working on JAX-WS 2.1 support. It should be almost 
ready to be moved across to the trunk, but I need to do some more testing 
first. I will also have to start raising JIRAs for the remaining bits of 
work, so that others can join in the fun.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 13/09/2007 19:48:19:

> Yadav, Yogendra (IT) wrote:
> > Hi Axis2 developers,
> > 
> > I am interested to know the axis2 roadmap, I could not find this 
> > information on the Axis2 web site. I am particularly interested in the 

> > following:
> > 1. Support for Spring based configuration.
> 
> We have some support but it can be improved radically if there's a need. 

> What do you have in mind?
> 
> > 2. Support for JAX-WS 2.1.
> 
> In progress .. I'm not sure exactly where we are; Brian, are you the one 

> working on it?
> 
> > 3. Jetty and/or Grizzly based HTTP transports for Axis2.
> 
> There's a Jetty transport that was written for WSO2 WSAS which is 
> available. I've never heard of Grizzly (except in Yellowstone ;-))! 
Google 
> tells me Grizzly must be https://grizzly.dev.java.net/. Sounds like 
that's 
> what we should be using instead of straight Jetty now?
> 
> If you're looking for NIO with Jetty 6, then we have a better-than-Jetty 

> NIO transport that's based on the HTTP Core project! That was developed 
> for Synapse but its a raw HTTP transport for Axis2 and is now committed 
> here. It'll be great to do a perf eval of that vs. Jetty 6 and see how 
> they compare! The reason I said "better-than-Jetty" is because this 
> transport does NIO for both reading and writing .. something that 
Synapse 
> needed in order to scale well.
> 
> > 4. If Axis2 will ever provide full duplex streaming support (I can 
read 
> > the input stream via XMLStreamReader in my handler class but can't 
write 
> > to the output stream while processing XML events).
> 
> It does provide full duplex streaming; it does that now for generated 
ADB 
> classes. This is done using OMSourcedElement .. which is basically a way 

> of deferring Java object -> XML serialization until its absolutely 
> necessary. At that time, the Java object can straight write itself to 
the 
> XML stream.
> 
> Note that it has to be done this way because its necessary for Axis2 to 
> write the Envelope element etc. before asking the application to write 
out 
> the payload. If the application wants to defer reading some of the input 

> until it starts writing the output that's possible thru the same 
> technique- you have an OMSourcedElement impl which hangs onto the 
incoming 
> message context to get at the incoming message too.
> 
> Hope this helps,
> 
> Sanjiva.
> -- 
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Axis2] Test Failure

[Brian De Pradine]

Thanks, it's fixed now.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Deepal jayasinghe <[EMAIL PROTECTED]> wrote on 04/09/2007 12:10:02:

> Yes , I am also getting the same exception
> 
> Thanks
> Deepal
> >
> > Hello Amila,
> >
> > Sorry, but this still doesn't work. I get the same error as before, as
> > shown below. I think there may be an
> > extra slash before the drive letter, F: in this case, that probably
> > shouldn't be there.
> >
> > Running org.apache.axis2.xmlbeans.WSDL2Java1Test
> > Retrieving schema at 'wsat.xsd', relative to
> > 'file:*/F:/Drivers/axis2/modules/xml*
> > *beans/test-resources/'.*
> > 04-Sep-2007 11:38:03
> > org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2Entity
> > Resolver resolveEntity
> > INFO: Resolving schema with publicId [null] and systemId [wsat.xsd]
> > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > org.apache.axis2.wsdl.cod
> > egen.CodeGenerationException: java.lang.RuntimeException: Schema
> > writing failed!
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.
> generate(CodeGenerationEngine.java:265)
> >
> > at
> > org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.
> codeGenerate(WSDL2JavaSuccessTestBase.java:172)
> >
> > at
> > org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.
> generateAndCompile(WSDL2JavaSuccessTestBase.java:157)
> >
> > at
> > org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.
> testWSDLFile(WSDL2JavaSuccessTestBase.java:104)
> >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25)
> >
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at junit.framework.TestCase.runTest(TestCase.java:168)
> > at junit.framework.TestCase.runBare(TestCase.java:134)
> > at junit.framework.TestResult$1.protect(TestResult.java:110)
> > at 
junit.framework.TestResult.runProtected(TestResult.java:128)
> > at junit.framework.TestResult.run(TestResult.java:113)
> > at junit.framework.TestCase.run(TestCase.java:124)
> > at junit.framework.TestSuite.runTest(TestSuite.java:232)
> > at junit.framework.TestSuite.run(TestSuite.java:227)
> > at
> > org.junit.internal.runners.OldTestClassRunner.
> run(OldTestClassRunner.java:76)
> >
> > at
> > org.apache.maven.surefire.junit4.JUnit4TestSet.
> execute(JUnit4TestSet.java:62)
> >
> > at
> > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.
> executeTestSet(AbstractDirectoryTestSuite.java:138)
> >
> > at
> > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.
> execute(AbstractDirectoryTestSuite.java:125)
> >
> > at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25)
> >
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> > org.apache.maven.surefire.booter.SurefireBooter.
> runSuitesInProcess(SurefireBooter.java:290)
> >
> > at
> > org.apache.maven.surefire.booter.SurefireBooter.
> main(SurefireBooter.java:818)
> >
> > Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > java.lang.RuntimeException: Schema writing failed!
> > at
> > org.apache.axis2.wsdl.codegen.emitter.
> AxisServiceBasedMultiLanguageEmitter.
> emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1371)
> >
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.
> generate(CodeGenerationEngine.java:247)
> >
> > ... 26 more
> > Caused by: java.lang.RuntimeException: Schema writing failed!
> > at
> > org.apache.axis2.wsdl.codegen.writer.SchemaWriter.
> writeSchema(SchemaWriter.java:59)
> >
> > at
> > org.apache.axis2.wsdl.codegen.emitter.
> AxisServiceBasedMultiLanguageEmitter.
> writeWSDLFiles(AxisServiceBasedMultiLanguageEmitter.java:1411)
> >
> > at
> > org.apache.axis2.wsdl.codegen.emitter.
> AxisServiceBasedMultiLanguageEmitter.
> emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1342)
> >
> > ... 27 more
> > Caused by: java.io.FileNotFoundException:
> > F:\Drivers\axis2\modules\xmlbeans\out_
> > put_classes\test1\resources\file:*\F:
> \Drivers\axis2\modules\xmlbeans\test-resources\wsat.xsd*
> > (The filename, directory name, or volume label syntax is incorrect)
> > at java.io.FileOutputStream.open(Native Method)
> > at java.io.Fi

Re: [Axis2] Test Failure

[Brian De Pradine]

Hello Amila,

Sorry, but this still doesn't work. I get the same error as before, as 
shown below. I think there may be an
extra slash before the drive letter, F: in this case, that probably 
shouldn't be there.

Running org.apache.axis2.xmlbeans.WSDL2Java1Test
Retrieving schema at 'wsat.xsd', relative to 'file:
/F:/Drivers/axis2/modules/xml
beans/test-resources/'.
04-Sep-2007 11:38:03 
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2Entity
Resolver resolveEntity
INFO: Resolving schema with publicId [null] and systemId [wsat.xsd]
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
org.apache.axis2.wsdl.cod
egen.CodeGenerationException: java.lang.RuntimeException: Schema writing 
failed!
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.codeGenerate(WSDL2JavaSuccessTestBase.java:172)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.generateAndCompile(WSDL2JavaSuccessTestBase.java:157)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.testWSDLFile(WSDL2JavaSuccessTestBase.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at 
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.RuntimeException: Schema writing failed!
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1371)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247)
... 26 more
Caused by: java.lang.RuntimeException: Schema writing failed!
at 
org.apache.axis2.wsdl.codegen.writer.SchemaWriter.writeSchema(SchemaWriter.java:59)
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeWSDLFiles(AxisServiceBasedMultiLanguageEmitter.java:1411)
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1342)
... 27 more
Caused by: java.io.FileNotFoundException: 
F:\Drivers\axis2\modules\xmlbeans\out_
put_classes\test1\resources\file:
\F:\Drivers\axis2\modules\xmlbeans\test-resources\wsat.xsd (The filename, 
directory name, or volume label syntax is incorrect)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:179)
at java.io.FileOutputStream.(FileOutputStream.java:131)
at 
org.apache.axis2.wsdl.codegen.writer.SchemaWriter.writeSchema(SchemaWriter.java:50)
... 29 more
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.89 sec 
<<< FAILURE!

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Amila Suriarachchi" <[EMAIL PROTECTED]> wrote on 04/09/2007 
05:58:32:

> I am working on linux and had set the file seperator as "/"
> now I replace it with  File.separator. please try it now.

> If you can't find the time to do it right the first time, where will
> you find the time to do it ag

Re: [Axis2] Test Failure

[Brian De Pradine]

Hello Amila,

I don't believe that it is fixed yet. Now I get the following:

Running org.apache.axis2.xmlbeans.WSDL2Java1Test
Retrieving schema at 'wsat.xsd', relative to 
'file:/F:/Drivers/axis2/modules/xml
beans/test-resources/'.
03-Sep-2007 17:01:28 
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2Entity
Resolver resolveEntity
INFO: Resolving schema with publicId [null] and systemId [wsat.xsd]
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
org.apache.axis2.wsdl.cod
egen.CodeGenerationException: java.lang.RuntimeException: Schema writing 
failed!

at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.codeGenerate(WSDL2JavaSuccessTestBase.java:172)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.generateAndCompile(WSDL2JavaSuccessTestBase.java:157)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.testWSDLFile(WSDL2JavaSuccessTestBase.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at 
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.RuntimeException: Schema writing failed!
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1371)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247)
... 26 more
Caused by: java.lang.RuntimeException: Schema writing failed!
at 
org.apache.axis2.wsdl.codegen.writer.SchemaWriter.writeSchema(SchemaWriter.java:59)
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeWSDLFiles(AxisServiceBasedMultiLanguageEmitter.java:1411)
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1342)
... 27 more
Caused by: java.io.FileNotFoundException: 
F:\Drivers\axis2\modules\xmlbeans\out_put_classes\test1\resources\file:\F:\Drivers\axis2\modules\xmlbeans\test-resourc
es\wsat.xsd (The filename, directory name, or volume label syntax is 
incorrect)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:179)
at java.io.FileOutputStream.(FileOutputStream.java:131)
at 
org.apache.axis2.wsdl.codegen.writer.SchemaWriter.writeSchema(SchemaWriter.java:50)
... 29 more
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.609 sec 
<<< FAILURE!

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Amila Suriarachchi" <[EMAIL PROTECTED]> wrote on 03/09/2007 
14:45:45:

> fixed. please take an update.
> 
> Amila.

> On 9/3/07, Brian De Pradine <[EMAIL PROTECTED]> wrote: 
> 
> Hello all, 
> 
> I am trying to build the trunk and I get the following failure in 
> the XMLBeans module. Has anyone else seen this? 
> 
> Running org.apa

[Axis2] Test Failure

[Brian De Pradine]

Hello all,

I am trying to build the trunk and I get the following failure in the 
XMLBeans module. Has anyone else seen this?

Running org.apache.axis2.xmlbeans.WSDL2Java1Test
Retrieving schema wsdl:imported from 'wsat.xsd', relative to 
'file:/F:/Drivers/a
xis2/modules/xmlbeans/test-resources/'.
Retrieving schema wsdl:imported from 'wsat.xsd', relative to 
'file:/F:/Drivers/a
xis2/modules/xmlbeans/test-resources/'.
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
org.apache.axis2.wsdl.cod
egen.CodeGenerationException: java.lang.RuntimeException: WSDL writing 
failed!
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.codeGenerate(WSDL2JavaSuccessTestBase.java:172)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.generateAndCompile(WSDL2JavaSuccessTestBase.java:157)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.testWSDLFile(WSDL2JavaSuccessTestBase.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at 
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.RuntimeException: WSDL writing failed!
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1371)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247)
... 26 more
Caused by: java.lang.RuntimeException: WSDL writing failed!
at 
org.apache.axis2.wsdl.codegen.writer.WSDL11Writer.writeWSDL(WSDL11Writer.java:81)
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeWSDLFiles(AxisServiceBasedMultiLanguageEmitter.java:1438)
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1342)
... 27 more
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of 
range: -1
at java.lang.String.substring(String.java:1768)
at 
org.apache.axis2.wsdl.codegen.writer.WSDL11Writer.writeWSDL(WSDL11Writer.java:107)
at 
org.apache.axis2.wsdl.codegen.writer.WSDL11Writer.writeWSDL(WSDL11Writer.java:78)
... 29 more
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.344 sec 
<<< FAILURE!

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [axis2] Importing source in Eclipse

[Brian De Pradine]

There are currently a few issues with "mvn eclipse:eclipse". It works for 
the most part, but there are some things that have to be fixed up 
manually. One of these is that any module that is packaged as a mar 
doesn't have the .classpath file generated. If you remove the line 
mar from the modules pom and rerun the command then it 
works. This affects the eclipse projects: addressing, axis2-scripting, 
mex, ping and soapmonitor.

To build the axis2-kernel eclipse project will require you to modify the 
java build path property to add the test-resources/deployment directory to 
the excluded list for the test-resources directory.
To build the axis2-codegen eclipse project will require you to delete all 
of the src directories that are not a part of the axis2-codegen project 
from the java build path property. 

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Davanum Srinivas" <[EMAIL PROTECTED]> wrote on 01/08/2007 15:07:03:

> please run "mvn eclipse:eclipse"
> 
> -- dims
> 
> On 8/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Hi All,
> >
> > I am new to maven and interested in axis2 development. Could anybody 
suggest
> > me how to import axis2 project in eclipse. So i can start my 
contribution to
> > axis2 team.
> >
> > thanks,
> >  Deepak Jerambhai Pansheriya
> >  Tata Consultancy Services
> >  Yantra Park -(STPI)
> >  Mailto: [EMAIL PROTECTED]
> >  Website: http://www.tcs.com
> >  
> >  Experience certainty. IT Services
> >Business Solutions
> >Outsourcing
> > =-=-=
> > Notice: The information contained in this e-mail
> > message and/or attachments to it may contain
> > confidential or privileged information. If you are
> > not the intended recipient, any dissemination, use,
> > review, distribution, printing or copying of the
> > information contained in this e-mail message
> > and/or attachments to it are strictly prohibited. If
> > you have received this communication in error,
> > please notify us by reply e-mail or telephone and
> > immediately and permanently delete the message
> > and any attachments. Thank you
> >
> >
> >
> >
> 
> 
> -- 
> Davanum Srinivas :: http://davanum.wordpress.com
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: Proposed Sandesha2 Hackathon

[Brian De Pradine]

Hello Paul,

I would like to come along as well. Thanks.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Paul Fremantle" <[EMAIL PROTECTED]> wrote on 26/06/2007 12:03:48:

> Folks
> 
> We are proposing to hold a Sandesha2 Hackathon in Fareham, England, on
> July 9th and 10th. The plan is to hold it in the Lysses House Hotel,
> Fareham. WSO2 will sponsor the meeting rooms and lunches for the day.
> The hotel has WiFi in place and is near the centre of Fareham, a brisk
> walk from the railway station.
> 
> The aims of this F2F are to discuss the architecture of Sandesha2,
> understand how to improve and refactor the codebase, and also discuss
> plans for supporting WSRM1.1 fully and interop around that.
> 
> Any Sandesha committer is more than welcome. The aim is to be a
> working session, so please come with the intention of working hard on
> the Sandesha codebase.
> 
> If you plan on attending, please reply to this note. In addition, if
> you need help with the arrangements, you can contact me.
> 
> Regards,
> 
> Paul
> 
> -- 
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
> 
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
> 
> "Oxygenating the Web Service Platform", www.wso2.com
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Axis2] Switch either to maven or maven2

[Brian De Pradine]

+1 for moving to maven2.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Glen Daniels <[EMAIL PROTECTED]> wrote on 29/05/2007 17:23:45:

> +1 for M2 - despite some issues it's way faster, and that's goodness.
> 
> --Glen
> 
> Davanum Srinivas wrote:
> > +1 to maven2 in time for Axis2 1.3. Currently items that need to be
> > worked on are:
> > 
> > 1. Get tests in integration module to work.
> > 2. Add assemblies to generate the src and bin dist.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

RE: Addressing Exception

[Brian De Pradine]

Hello Aldrin,

The lib directory is not the correct location for the class. You need to 
locate your axis2-kernel.jar, and insert the class into the 
org/apache/axis2/addressing directory of the jar.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?




<[EMAIL PROTECTED]> 
29/05/2007 10:30
Please respond to
axis-dev@ws.apache.org


To

cc

Subject
RE: Addressing Exception






 
There is no difference after putting the EndPointReferenceHelper.class in 
the lib folder of axis2.
It?s really a great if you can provide some help

From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 29, 2007 2:39 PM
To: axis-dev@ws.apache.org
Subject: RE: Addressing Exception
 

Hello Aldrin, 

Which exception is that? The server-side NoClassDefFoundError, or the 
client-side AxisFault? 

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


<[EMAIL PROTECTED]> wrote on 29/05/2007 07:39:13:

> But still it?s giving the same exception 
>   
> 
> From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> Sent: Monday, May 28, 2007 7:48 PM
> To: axis-dev@ws.apache.org
> Subject: RE: Addressing Exception 
>   
> 
> Hello Aldrin, 
> 
> Ahh ... Well that's a different issue. You might want to consider 
> raising a JIRA issue stating that savan does not work with axis2 1.
> 2. That can be done here [1] 
> 
> If you can't wait for a new version of savan then you can get around
> your immediate problem by returning to the version of axis2 that 
> worked with savan, and simply copying the EndpointReferenceHelper 
> class to the same location in the axis2-kernel jar of the axis2 that
> you are using. 
> 
> [1] http://issues.apache.org/jira/browse/SAVAN 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> <[EMAIL PROTECTED]> wrote on 28/05/2007 14:27:24:
> 
> > 
> > I deployed the new axis2.war.But then I have another problem it?s 
> > not able to configure savan.It?s not reading savan configuration 
> > file from WEB-INF. 
> > That?s the reason I had downloaded some other version of axis2. 
> > I am not able to figure how this is linked to savan. 
> > 
> > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, May 28, 2007 6:29 PM
> > To: axis-dev@ws.apache.org
> > Subject: RE: Addressing Exception 
> > 
> > 
> > Hello Aldrin, 
> > 
> > I have checked both the binary and the war versions and the 
> > EndpointRefereneHelper class is in both of them. 
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319 Internal 246319
> > 
> > If you can't find the time to do it right the first time, where will
> > you find the time to do it again?
> > 
> > 
> > <[EMAIL PROTECTED]> wrote on 28/05/2007 13:53:21:
> > 
> > > I had downloaded from there only previously.But it was war 
distribution. 
> > > Should I download war or binary distribution? 
> > > 
> > > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > > Sent: Monday, May 28, 2007 6:19 PM
> > > To: axis-dev@ws.apache.org
> > > Subject: RE: Addressing Exception 
> > > 
> > > 
> > > Hello Aldrin, 
> > > 
> > > Hmmm ... that's very odd. I recommend that you replace your axis2 
> > > installation with one from here [1] 
> > > 
> > > [1] http://ws.apache.org/axis2/download/1_2/download.cgi 
> > > 
> > > Cheers
> > > 
> > > Brian DePradine
> > > Web Services Development
> > > IBM Hursley
> > > External  +44 (0) 1962 816319 Internal 246319
> > > 
> > > If you can't find the time to do it right the first time, where will
> > > you find the time to do it again?
> > > 
> > > 
> > > <[EMAIL PROTECTED]> wrote on 28/05/2007 13:09:38:
> > > 
> > > > 
> > > > I could find axis2-kernel-1.2.jar.But there is not 
> > EndPointReferenceHelper 
> > > > 
> > > > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
&

RE: Addressing Exception

[Brian De Pradine]

Hello Aldrin,

Which exception is that? The server-side NoClassDefFoundError, or the 
client-side AxisFault?

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


<[EMAIL PROTECTED]> wrote on 29/05/2007 07:39:13:

> But still it?s giving the same exception 
> 
> 
> From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> Sent: Monday, May 28, 2007 7:48 PM
> To: axis-dev@ws.apache.org
> Subject: RE: Addressing Exception
> 
> 
> Hello Aldrin, 
> 
> Ahh ... Well that's a different issue. You might want to consider 
> raising a JIRA issue stating that savan does not work with axis2 1.
> 2. That can be done here [1] 
> 
> If you can't wait for a new version of savan then you can get around
> your immediate problem by returning to the version of axis2 that 
> worked with savan, and simply copying the EndpointReferenceHelper 
> class to the same location in the axis2-kernel jar of the axis2 that
> you are using. 
> 
> [1] http://issues.apache.org/jira/browse/SAVAN 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> <[EMAIL PROTECTED]> wrote on 28/05/2007 14:27:24:
> 
> > 
> > I deployed the new axis2.war.But then I have another problem it?s 
> > not able to configure savan.It?s not reading savan configuration 
> > file from WEB-INF. 
> > That?s the reason I had downloaded some other version of axis2. 
> > I am not able to figure how this is linked to savan. 
> > 
> > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, May 28, 2007 6:29 PM
> > To: axis-dev@ws.apache.org
> > Subject: RE: Addressing Exception 
> > 
> > 
> > Hello Aldrin, 
> > 
> > I have checked both the binary and the war versions and the 
> > EndpointRefereneHelper class is in both of them. 
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319 Internal 246319
> > 
> > If you can't find the time to do it right the first time, where will
> > you find the time to do it again?
> > 
> > 
> > <[EMAIL PROTECTED]> wrote on 28/05/2007 13:53:21:
> > 
> > > I had downloaded from there only previously.But it was war 
distribution. 
> > > Should I download war or binary distribution? 
> > > 
> > > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > > Sent: Monday, May 28, 2007 6:19 PM
> > > To: axis-dev@ws.apache.org
> > > Subject: RE: Addressing Exception 
> > > 
> > > 
> > > Hello Aldrin, 
> > > 
> > > Hmmm ... that's very odd. I recommend that you replace your axis2 
> > > installation with one from here [1] 
> > > 
> > > [1] http://ws.apache.org/axis2/download/1_2/download.cgi 
> > > 
> > > Cheers
> > > 
> > > Brian DePradine
> > > Web Services Development
> > > IBM Hursley
> > > External  +44 (0) 1962 816319 Internal 246319
> > > 
> > > If you can't find the time to do it right the first time, where will
> > > you find the time to do it again?
> > > 
> > > 
> > > <[EMAIL PROTECTED]> wrote on 28/05/2007 13:09:38:
> > > 
> > > > 
> > > > I could find axis2-kernel-1.2.jar.But there is not 
> > EndPointReferenceHelper 
> > > > 
> > > > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > > > Sent: Monday, May 28, 2007 5:14 PM
> > > > To: axis-dev@ws.apache.org
> > > > Subject: RE: Addressing Exception 
> > > > 
> > > > 
> > > > Hello Aldrin, 
> > > > 
> > > > Apologies, I have got the name wrong. It should be something like 
> > > > axis2-kernel-1.2.jar 
> > > > 
> > > > Cheers
> > > > 
> > > > Brian DePradine
> > > > Web Services Development
> > > > IBM Hursley
> > > > External  +44 (0) 1962 816319 Internal 246319
> > > > 
> > > > If you can't find the time to do it right the first time, where 
will
> > > > you find the time to do it again?
> > > > 
> > > > 
> > > >

RE: Addressing Exception

[Brian De Pradine]

Hello Aldrin,

Ahh ... Well that's a different issue. You might want to consider raising 
a JIRA issue stating that savan does not work with axis2 1.2. That can be 
done here [1]

If you can't wait for a new version of savan then you can get around your 
immediate problem by returning to the version of axis2 that worked with 
savan, and simply copying the EndpointReferenceHelper class to the same 
location in the axis2-kernel jar of the axis2 that you are using.

[1] http://issues.apache.org/jira/browse/SAVAN

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


<[EMAIL PROTECTED]> wrote on 28/05/2007 14:27:24:

> 
> I deployed the new axis2.war.But then I have another problem it?s 
> not able to configure savan.It?s not reading savan configuration 
> file from WEB-INF.
> That?s the reason I had downloaded some other version of axis2.
> I am not able to figure how this is linked to savan.
> 
> From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> Sent: Monday, May 28, 2007 6:29 PM
> To: axis-dev@ws.apache.org
> Subject: RE: Addressing Exception
> 
> 
> Hello Aldrin, 
> 
> I have checked both the binary and the war versions and the 
> EndpointRefereneHelper class is in both of them. 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> <[EMAIL PROTECTED]> wrote on 28/05/2007 13:53:21:
> 
> > I had downloaded from there only previously.But it was war 
distribution. 
> > Should I download war or binary distribution? 
> > 
> > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, May 28, 2007 6:19 PM
> > To: axis-dev@ws.apache.org
> > Subject: RE: Addressing Exception 
> > 
> > 
> > Hello Aldrin, 
> > 
> > Hmmm ... that's very odd. I recommend that you replace your axis2 
> > installation with one from here [1] 
> > 
> > [1] http://ws.apache.org/axis2/download/1_2/download.cgi 
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319 Internal 246319
> > 
> > If you can't find the time to do it right the first time, where will
> > you find the time to do it again?
> > 
> > 
> > <[EMAIL PROTECTED]> wrote on 28/05/2007 13:09:38:
> > 
> > > 
> > > I could find axis2-kernel-1.2.jar.But there is not 
> EndPointReferenceHelper 
> > > 
> > > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > > Sent: Monday, May 28, 2007 5:14 PM
> > > To: axis-dev@ws.apache.org
> > > Subject: RE: Addressing Exception 
> > > 
> > > 
> > > Hello Aldrin, 
> > > 
> > > Apologies, I have got the name wrong. It should be something like 
> > > axis2-kernel-1.2.jar 
> > > 
> > > Cheers
> > > 
> > > Brian DePradine
> > > Web Services Development
> > > IBM Hursley
> > > External  +44 (0) 1962 816319 Internal 246319
> > > 
> > > If you can't find the time to do it right the first time, where will
> > > you find the time to do it again?
> > > 
> > > 
> > > <[EMAIL PROTECTED]> wrote on 28/05/2007 06:19:39:
> > > 
> > > > Hi Brian 
> > > > 
> > > > I couldn?t find  kernel.jar in my lib folder. 
> > > > 
> > > > Thanks And Regards 
> > > > Smitha Aldrin 
> > > > 
> > > > 
> > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> > > > Sent: Monday, May 28, 2007 10:12 AM
> > > > To: axis-dev@ws.apache.org
> > > > Subject: RE: Addressing Exception 
> > > > 
> > > > Hi Brian 
> > > > 
> > > > Good Morning!! 
> > > > 
> > > > This is how the message exchange happens... 
> > > > 
> > > > Host: 127.0.0.1:8081 
> > > > Transfer-Encoding: chunked 
> > > > 
> > > > 23f 
> > > > http://www.w3.org/2005/08/addressing"; 
xmlns:soapenv="http://www.w3.
> > > > 
org/2003/05/soap-envelope">http://localhost:
> > > > 8081/axis2/services/PublisherService > > > Address>http://www.w3.org/2005/08/addressing/anonymous > 

[Axis2] JAX-WS 2.1

[Brian De Pradine]

Hello Devs,

Sun have recently announced a JAX-WS 2.1 Maintenance Release which adds a 
number of new features to the existing JAX-WS 2.0. These include direct 
support for WS-Addressing, and new support for the WebServiceFeature 
configuration model. For further info please look here, [1]. I propose to 
extend our current JAX-WS 2.0 support in axis2 to support the JAX-WS 2.1 
MR. I have just created a branch [2] in which the development will take 
place, with the aim being to merge this back into the trunk at a suitable 
point in the future.

[1] http://jcp.org/en/jsr/detail?id=224
[2] http://svn.apache.org/viewvc/webservices/axis2/branches/java/jaxws21/

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

RE: Addressing Exception

[Brian De Pradine]

Hello Aldrin,

I have checked both the binary and the war versions and the 
EndpointRefereneHelper class is in both of them.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


<[EMAIL PROTECTED]> wrote on 28/05/2007 13:53:21:

> I had downloaded from there only previously.But it was war distribution.
> Should I download war or binary distribution?
> 
> From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> Sent: Monday, May 28, 2007 6:19 PM
> To: axis-dev@ws.apache.org
> Subject: RE: Addressing Exception
> 
> 
> Hello Aldrin, 
> 
> Hmmm ... that's very odd. I recommend that you replace your axis2 
> installation with one from here [1] 
> 
> [1] http://ws.apache.org/axis2/download/1_2/download.cgi 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> <[EMAIL PROTECTED]> wrote on 28/05/2007 13:09:38:
> 
> > 
> > I could find axis2-kernel-1.2.jar.But there is not 
EndPointReferenceHelper 
> > 
> > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, May 28, 2007 5:14 PM
> > To: axis-dev@ws.apache.org
> > Subject: RE: Addressing Exception 
> > 
> > 
> > Hello Aldrin, 
> > 
> > Apologies, I have got the name wrong. It should be something like 
> > axis2-kernel-1.2.jar 
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319 Internal 246319
> > 
> > If you can't find the time to do it right the first time, where will
> > you find the time to do it again?
> > 
> > 
> > <[EMAIL PROTECTED]> wrote on 28/05/2007 06:19:39:
> > 
> > > Hi Brian 
> > > 
> > > I couldn?t find  kernel.jar in my lib folder. 
> > > 
> > > Thanks And Regards 
> > > Smitha Aldrin 
> > > 
> > > 
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> > > Sent: Monday, May 28, 2007 10:12 AM
> > > To: axis-dev@ws.apache.org
> > > Subject: RE: Addressing Exception 
> > > 
> > > Hi Brian 
> > > 
> > > Good Morning!! 
> > > 
> > > This is how the message exchange happens... 
> > > 
> > > Host: 127.0.0.1:8081 
> > > Transfer-Encoding: chunked 
> > > 
> > > 23f 
> > > http://www.w3.org/2005/08/addressing"; xmlns:soapenv="http://www.w3.
> > > org/2003/05/soap-envelope">http://localhost:
> > > 8081/axis2/services/PublisherService > > Address>http://www.w3.org/2005/08/addressing/anonymous > > Address>urn:uuid:
> > > C93761FC5FE5CF50DA1180087094009uuid:
> > > dummyMethod > > dummyMethod xmlns:ns1="http://tempuri.org/"; /> > > Body>0 
> > > 
> > > 
> > > HTTP/1.1 202 Accepted 
> > > Server: Apache-Coyote/1.1 
> > > X-Powered-By: Servlet 2.4; JBoss-4.0.2 (build: CVSTag=JBoss_4_0_2 
> > > date=200505022023)/Tomcat-5.5 
> > > Content-Type: text/xml;charset=UTF-8 
> > > Transfer-Encoding: chunked 
> > > Date: Fri, 25 May 2007 09:58:14 GMT 
> > > 
> > > 0 
> > > 
> > > 
> > > 
> > > 
> > > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > > Sent: Friday, May 25, 2007 7:59 PM
> > > To: axis-dev@ws.apache.org
> > > Subject: RE: Addressing Exception 
> > > 
> > > 
> > > Hello Aldrin, 
> > > 
> > > Hmm ... in axis2 version 1.2 that class should definitely be in 
> > > kernel.jar. Classloading issue maybe? 
> > > 
> > > Anyway, looking at the stack trace for the other issue, it suggests 
> > > a problem with the action processing. What does TCPMon show for the 
> > > request message? 
> > > 
> > > Cheers
> > > 
> > > Brian DePradine
> > > Web Services Development
> > > IBM Hursley
> > > External  +44 (0) 1962 816319 Internal 246319
> > > 
> > > If you can't find the time to do it right the first time, where will
> > > you find the time to do it again?
> > > 
> > > 
> > > <[EMAIL PROTECTED]> wrote on 25/05/2007 15:06:47:
> 

RE: Addressing Exception

[Brian De Pradine]

Hello Aldrin,

Hmmm ... that's very odd. I recommend that you replace your axis2 
installation with one from here [1]

[1] http://ws.apache.org/axis2/download/1_2/download.cgi

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


<[EMAIL PROTECTED]> wrote on 28/05/2007 13:09:38:

> 
> I could find axis2-kernel-1.2.jar.But there is not 
EndPointReferenceHelper
> 
> From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> Sent: Monday, May 28, 2007 5:14 PM
> To: axis-dev@ws.apache.org
> Subject: RE: Addressing Exception
> 
> 
> Hello Aldrin, 
> 
> Apologies, I have got the name wrong. It should be something like 
> axis2-kernel-1.2.jar 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> <[EMAIL PROTECTED]> wrote on 28/05/2007 06:19:39:
> 
> > Hi Brian 
> > 
> > I couldn?t find  kernel.jar in my lib folder. 
> > 
> > Thanks And Regards 
> > Smitha Aldrin 
> > 
> > 
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, May 28, 2007 10:12 AM
> > To: axis-dev@ws.apache.org
> > Subject: RE: Addressing Exception 
> > 
> > Hi Brian 
> > 
> > Good Morning!! 
> > 
> > This is how the message exchange happens... 
> > 
> > Host: 127.0.0.1:8081 
> > Transfer-Encoding: chunked 
> > 
> > 23f 
> > http://www.w3.org/2005/08/addressing"; xmlns:soapenv="http://www.w3.
> > org/2003/05/soap-envelope">http://localhost:
> > 8081/axis2/services/PublisherService > Address>http://www.w3.org/2005/08/addressing/anonymous > Address>urn:uuid:
> > C93761FC5FE5CF50DA1180087094009uuid:
> > dummyMethod > dummyMethod xmlns:ns1="http://tempuri.org/"; /> > Body>0 
> > 
> > 
> > HTTP/1.1 202 Accepted 
> > Server: Apache-Coyote/1.1 
> > X-Powered-By: Servlet 2.4; JBoss-4.0.2 (build: CVSTag=JBoss_4_0_2 
> > date=200505022023)/Tomcat-5.5 
> > Content-Type: text/xml;charset=UTF-8 
> > Transfer-Encoding: chunked 
> > Date: Fri, 25 May 2007 09:58:14 GMT 
> > 
> > 0 
> > 
> > 
> > 
> > 
> > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > Sent: Friday, May 25, 2007 7:59 PM
> > To: axis-dev@ws.apache.org
> > Subject: RE: Addressing Exception 
> > 
> > 
> > Hello Aldrin, 
> > 
> > Hmm ... in axis2 version 1.2 that class should definitely be in 
> > kernel.jar. Classloading issue maybe? 
> > 
> > Anyway, looking at the stack trace for the other issue, it suggests 
> > a problem with the action processing. What does TCPMon show for the 
> > request message? 
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319 Internal 246319
> > 
> > If you can't find the time to do it right the first time, where will
> > you find the time to do it again?
> > 
> > 
> > <[EMAIL PROTECTED]> wrote on 25/05/2007 15:06:47:
> > 
> > > Hi Brian 
> > > 
> > > I have addressing.mar in my axis2.war 
> > > I am using axis1.2 
> > > 
> > > 
> > > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > > Sent: Friday, May 25, 2007 7:33 PM
> > > To: axis-dev@ws.apache.org
> > > Subject: Re: Addressing Exception 
> > > 
> > > 
> > > Hello Aldrin, 
> > > 
> > > Let's start with the server side exception. Which version of axis2 
> > > are you using? In the latest axis2 version that class should be in 
> > > kernel.jar, however, in earlier versions of axis2 it was in 
> addressing.mar 
> > > 
> > > Cheers
> > > 
> > > Brian DePradine
> > > Web Services Development
> > > IBM Hursley
> > > External  +44 (0) 1962 816319 Internal 246319
> > > 
> > > If you can't find the time to do it right the first time, where will
> > > you find the time to do it again?
> > > 
> > > 
> > > <[EMAIL PROTECTED]> wrote on 25/05/2007 13:20:36:
> > > 
> > > > Hi 
> > > > 
> > > > I am getting the following exception  at the server 
> &g

RE: Addressing Exception

[Brian De Pradine]

Hello Aldrin,

Apologies, I have got the name wrong. It should be something like 
axis2-kernel-1.2.jar

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


<[EMAIL PROTECTED]> wrote on 28/05/2007 06:19:39:

> Hi Brian
> 
> I couldn?t find  kernel.jar in my lib folder.
> 
> Thanks And Regards
> Smitha Aldrin
> 
> 
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Monday, May 28, 2007 10:12 AM
> To: axis-dev@ws.apache.org
> Subject: RE: Addressing Exception
> 
> Hi Brian
> 
> Good Morning!!
> 
> This is how the message exchange happens...
> 
> Host: 127.0.0.1:8081
> Transfer-Encoding: chunked
> 
> 23f
> http://www.w3.org/2005/08/addressing"; xmlns:soapenv="http://www.w3.
> org/2003/05/soap-envelope">http://localhost:
> 8081/axis2/services/PublisherService Address>http://www.w3.org/2005/08/addressing/anonymous Address>urn:uuid:
> C93761FC5FE5CF50DA1180087094009uuid:
> dummyMethod dummyMethod xmlns:ns1="http://tempuri.org/"; /> Body>0
> 
> 
> HTTP/1.1 202 Accepted
> Server: Apache-Coyote/1.1
> X-Powered-By: Servlet 2.4; JBoss-4.0.2 (build: CVSTag=JBoss_4_0_2 
> date=200505022023)/Tomcat-5.5
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Fri, 25 May 2007 09:58:14 GMT
> 
> 0
> 
> 
> 
> 
> From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> Sent: Friday, May 25, 2007 7:59 PM
> To: axis-dev@ws.apache.org
> Subject: RE: Addressing Exception
> 
> 
> Hello Aldrin, 
> 
> Hmm ... in axis2 version 1.2 that class should definitely be in 
> kernel.jar. Classloading issue maybe? 
> 
> Anyway, looking at the stack trace for the other issue, it suggests 
> a problem with the action processing. What does TCPMon show for the 
> request message? 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> <[EMAIL PROTECTED]> wrote on 25/05/2007 15:06:47:
> 
> > Hi Brian 
> > 
> > I have addressing.mar in my axis2.war 
> > I am using axis1.2 
> > 
> > 
> > From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> > Sent: Friday, May 25, 2007 7:33 PM
> > To: axis-dev@ws.apache.org
> > Subject: Re: Addressing Exception 
> > 
> > 
> > Hello Aldrin, 
> > 
> > Let's start with the server side exception. Which version of axis2 
> > are you using? In the latest axis2 version that class should be in 
> > kernel.jar, however, in earlier versions of axis2 it was in 
addressing.mar 
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319 Internal 246319
> > 
> > If you can't find the time to do it right the first time, where will
> > you find the time to do it again?
> > 
> > 
> > <[EMAIL PROTECTED]> wrote on 25/05/2007 13:20:36:
> > 
> > > Hi 
> > > 
> > > I am getting the following exception  at the server 
> > > 
> > > java.lang.NoClassDefFoundError: org/apache/axis 
> > > 2/addressing/EndpointReferenceHelper 
> > > 
> > > And at the client ...Is it possible for anyone to give me some clue? 

> > > 
> > > Exception in thread "main" org.apache.axis2.AxisFault: A header 
> > > representing a Message Addressing Property is not valid and the 
> > > message cannot be processed 
> > >   at org.apache.axis2.addressing.AddressingFaultsHelper.
> > > triggerAddressingFault(AddressingFaultsHelper.java:150) 
> > >   at org.apache.axis2.addressing.AddressingFaultsHelper.
> > > triggerActionMismatchFault(AddressingFaultsHelper.java:81) 
> > >   at org.apache.axis2.handlers.addressing.AddressingInHandler.
> > > extractActionInformation(AddressingInHandler.java:276) 
> > >   at org.apache.axis2.handlers.addressing.AddressingInHandler.
> > > extractAddressingInformation(AddressingInHandler.java:159) 
> > >   at 
org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(
> > > AddressingInHandler.java:95) 
> > >   at org.apache.axis2.engine.Phase.invoke(Phase.java:383) 
> > >   at 
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) 
> > >   at

RE: Addressing Exception

[Brian De Pradine]

Hello Aldrin,

Hmm ... in axis2 version 1.2 that class should definitely be in 
kernel.jar. Classloading issue maybe?

Anyway, looking at the stack trace for the other issue, it suggests a 
problem with the action processing. What does TCPMon show for the request 
message?

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


<[EMAIL PROTECTED]> wrote on 25/05/2007 15:06:47:

> Hi Brian
> 
> I have addressing.mar in my axis2.war
> I am using axis1.2
> 
> 
> From: Brian De Pradine [mailto:[EMAIL PROTECTED] 
> Sent: Friday, May 25, 2007 7:33 PM
> To: axis-dev@ws.apache.org
> Subject: Re: Addressing Exception
> 
> 
> Hello Aldrin, 
> 
> Let's start with the server side exception. Which version of axis2 
> are you using? In the latest axis2 version that class should be in 
> kernel.jar, however, in earlier versions of axis2 it was in 
addressing.mar 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> <[EMAIL PROTECTED]> wrote on 25/05/2007 13:20:36:
> 
> > Hi 
> > 
> > I am getting the following exception  at the server 
> > 
> > java.lang.NoClassDefFoundError: org/apache/axis 
> > 2/addressing/EndpointReferenceHelper 
> > 
> > And at the client ...Is it possible for anyone to give me some clue? 
> > 
> > Exception in thread "main" org.apache.axis2.AxisFault: A header 
> > representing a Message Addressing Property is not valid and the 
> > message cannot be processed 
> >   at org.apache.axis2.addressing.AddressingFaultsHelper.
> > triggerAddressingFault(AddressingFaultsHelper.java:150) 
> >   at org.apache.axis2.addressing.AddressingFaultsHelper.
> > triggerActionMismatchFault(AddressingFaultsHelper.java:81) 
> >   at org.apache.axis2.handlers.addressing.AddressingInHandler.
> > extractActionInformation(AddressingInHandler.java:276) 
> >   at org.apache.axis2.handlers.addressing.AddressingInHandler.
> > extractAddressingInformation(AddressingInHandler.java:159) 
> >   at 
org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(
> > AddressingInHandler.java:95) 
> >   at org.apache.axis2.engine.Phase.invoke(Phase.java:383) 
> >   at 
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) 
> >   at org.apache.axis2.engine.AxisEngine.
> receiveFault(AxisEngine.java:354) 
> >   at org.apache.axis2.description.OutInAxisOperationClient.send(
> > OutInAxisOperation.java:370) 
> >   at 
org.apache.axis2.description.OutInAxisOperationClient.execute(
> > OutInAxisOperation.java:294) 
> >   at org.apache.axis2.client.ServiceClient.sendReceive(
> > ServiceClient.java:520) 
> >   at org.apache.axis2.client.ServiceClient.sendReceive(
> > ServiceClient.java:500) 
> >   at org.apache.savan.eventing.client.EventingClient.subscribe(
> > EventingClient.java:73) 
> >   at publisher.client.Client.doSubscribe(Client.java:101) 
> >   at publisher.client.Client.run(Client.java:52) 
> >   at publisher.client.Client.main(Client.java:40) 
> > 
> > 
> > 
> > The information contained in this electronic message and any 
> > attachments to this message are intended for the exclusive use of 
> > the addressee(s) and may contain proprietary, confidential or 
> > privileged information. If you are not the intended recipient, you 
> > should not disseminate, distribute or copy this e-mail. Please 
> > notify the sender immediately and destroy all copies of this message
> > and any attachments. 
> > 
> > WARNING: Computer viruses can be transmitted via email. The 
> > recipient should check this email and any attachments for the 
> > presence of viruses. The company accepts no liability for any damage
> > caused by any virus transmitted by this email.
> > 
> > www.wipro.com

> 
> 
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with 
> number 741598. 
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 
3AU 
> 
> 
> 

> 
> 
> The information contained in this electronic message and any 
> attachments to this message are intended for the exclusive use of 
> the addressee(s) and may contain proprietary, confidential or 
> privilege

Re: Addressing Exception

[Brian De Pradine]

Hello Aldrin,

Let's start with the server side exception. Which version of axis2 are you 
using? In the latest axis2 version that class should be in kernel.jar, 
however, in earlier versions of axis2 it was in addressing.mar

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


<[EMAIL PROTECTED]> wrote on 25/05/2007 13:20:36:

> Hi
> 
> I am getting the following exception  at the server
> 
> java.lang.NoClassDefFoundError: org/apache/axis
> 2/addressing/EndpointReferenceHelper 
> 
> And at the client ...Is it possible for anyone to give me some clue?
> 
> Exception in thread "main" org.apache.axis2.AxisFault: A header 
> representing a Message Addressing Property is not valid and the 
> message cannot be processed
>   at org.apache.axis2.addressing.AddressingFaultsHelper.
> triggerAddressingFault(AddressingFaultsHelper.java:150)
>   at org.apache.axis2.addressing.AddressingFaultsHelper.
> triggerActionMismatchFault(AddressingFaultsHelper.java:81)
>   at org.apache.axis2.handlers.addressing.AddressingInHandler.
> extractActionInformation(AddressingInHandler.java:276)
>   at org.apache.axis2.handlers.addressing.AddressingInHandler.
> extractAddressingInformation(AddressingInHandler.java:159)
>   at 
org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(
> AddressingInHandler.java:95)
>   at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
>   at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
>   at 
org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:354)
>   at org.apache.axis2.description.OutInAxisOperationClient.send(
> OutInAxisOperation.java:370)
>   at org.apache.axis2.description.OutInAxisOperationClient.execute(
> OutInAxisOperation.java:294)
>   at org.apache.axis2.client.ServiceClient.sendReceive(
> ServiceClient.java:520)
>   at org.apache.axis2.client.ServiceClient.sendReceive(
> ServiceClient.java:500)
>   at org.apache.savan.eventing.client.EventingClient.subscribe(
> EventingClient.java:73)
>   at publisher.client.Client.doSubscribe(Client.java:101)
>   at publisher.client.Client.run(Client.java:52)
>   at publisher.client.Client.main(Client.java:40)
> 
> 
> 
> The information contained in this electronic message and any 
> attachments to this message are intended for the exclusive use of 
> the addressee(s) and may contain proprietary, confidential or 
> privileged information. If you are not the intended recipient, you 
> should not disseminate, distribute or copy this e-mail. Please 
> notify the sender immediately and destroy all copies of this message
> and any attachments. 
> 
> WARNING: Computer viruses can be transmitted via email. The 
> recipient should check this email and any attachments for the 
> presence of viruses. The company accepts no liability for any damage
> caused by any virus transmitted by this email.
> 
> www.wipro.com





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Vote][Axis2] Sumedha Rubasinghe as a committer

[Brian De Pradine]

+1 from me.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Deepal Jayasinghe <[EMAIL PROTECTED]> wrote on 20/03/2007 06:26:53:

> Hi All,
> 
> I would like to propose Sumedha Rubasinghe as an Apache Axis2/Java
> committer. He has contributed Axis2 , AXIOM a lot specially implementing
> SAAJ module. In addition to that he is very active in the community and
> giving him a commitership will encourage him to contribute more and more
> into the project.
> 
> Following are the list of JIRAs that he has summited patches.
> https://issues.apache.org/jira/browse/SANDESHA2-50
> https://issues.apache.org/jira/browse/WSCOMMONS-147
> https://issues.apache.org/jira/browse/WSCOMMONS-152
> https://issues.apache.org/jira/browse/WSCOMMONS-156
> https://issues.apache.org/jira/browse/WSCOMMONS-157
> https://issues.apache.org/jira/browse/WSCOMMONS-176
> https://issues.apache.org/jira/browse/AXIS2-2199
> https://issues.apache.org/jira/browse/AXIS2-2283
> https://issues.apache.org/jira/browse/AXIS2-2331
> https://issues.apache.org/jira/browse/AXIS2-1956
> 
> 
> Here is my +1 for making Samudha as a commiter.
> 
> Thanks,
> Deepal
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [axis2] A couple of Addressing questions

[Brian De Pradine]

Hello Glen,

See my response below.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Glen Daniels <[EMAIL PROTECTED]> wrote on 20/03/2007 17:11:58:

> Hi folks:
> 
> Why do we have a separate AddressingValidationHandler?  Wouldn't it make 

> more sense simply to do any addressing-specific validation right in the 
> AddressingInHandler or the AddressingBasedDispatcher?  Is it possible to 

> simplify this?

I believe that historically the AddressingBasedDispatcher is not meant to 
be tied to strongly to ws-addressing. Hence it is not a part of the 
Addressing module :-(. This has meant the need to have a separate 
AddressingValidation handler. However, I believe that David is planning 
some refactoring of the dispatchers which may mean that we can revisit 
this.

> Also, rather than having separate Handlers for the different versions of 

> addressing, wouldn't it make more sense to have just one 
> AddressingInHandler and then let that do version-specific work with its 
> own utility classes?  A separate handler seems like overkill.

I had considered refactoring the inbound processing into one handler, but 
elected not to do it in the end. At the time, I was taking the approach of 
"if it ain't broke, don't fix it." Now, I have no objections to doing it 
if folks feel that this is the best way to go.

> 
> Thanks,
> --Glen
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [axis2] Re: svn commit: r516065 - /webservices/rampart/trunk/java/modules/rampart-integration/src/test/resources/security/complete.service.xml

[Brian De Pradine]

Hi Ruchith,

I modified the code recently to only send the message id and the relates 
to headers in an async response. It is meant to be a small performance 
tweak.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Ruchith Fernando" <[EMAIL PROTECTED]> wrote on 08/03/2007 
16:05:52:

> resend with the axis2 prefix :-)
> 
> On 3/8/07, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
> > Hi devs,
> >
> > We had a build break in Rampart due to the "MessageId" addressing
> > header being absent in the response message. Is this behavior correct?
> >
> > Thanks,
> > Ruchith
> >
> > On 3/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > Author: ruchithf
> > > Date: Thu Mar  8 07:00:53 2007
> > > New Revision: 516065
> > >
> > > URL: http://svn.apache.org/viewvc?view=rev&rev=516065
> > > Log:
> > > Fixed the build break, there's no wsa:MessageId header in the 
> response to sign
> > >
> > > Modified:
> > > webservices/rampart/trunk/java/modules/rampart-
> integration/src/test/resources/security/complete.service.xml
> > >
> > > Modified: webservices/rampart/trunk/java/modules/rampart-
> integration/src/test/resources/security/complete.service.xml
> > > URL: http://svn.apache.
> org/viewvc/webservices/rampart/trunk/java/modules/rampart-
> integration/src/test/resources/security/complete.service.xml?
> view=diff&rev=516065&r1=516064&r2=516065
> > > 
> 
==
> > > --- webservices/rampart/trunk/java/modules/rampart-
> integration/src/test/resources/security/complete.service.xml (original)
> > > +++ webservices/rampart/trunk/java/modules/rampart-
> integration/src/test/resources/security/complete.service.xml Thu Mar
> 8 07:00:53 2007
> > > @@ -22,7 +22,7 @@
> > > SKIKeyIdentifier
> > > 
> SKIKeyIdentifier
> > >  alice
> > > -{Element}{http://www.w3.
> org/2005/08/addressing}To;{Element}{http://www.w3.
> org/2005/08/addressing}ReplyTo;{Element}{http://www.w3.
> org/2005/08/addressing}MessageID;{Element}{http://docs.oasis-open.
> org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}
> Timestamp
> > > +{Element}{http://www.w3.
> org/2005/08/addressing}To;{Element}{http://www.w3.
> org/2005/08/addressing}ReplyTo;{Element}{http://docs.oasis-open.
> org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}
> Timestamp
> > >
> > >  //xenc:EncryptedData/xenc:
> CipherData/xenc:CipherValue
> > >
> > >
> > >
> > >
> >
> >
> > --
> > www.ruchith.org
> > www.wso2.org
> >
> 
> 
> -- 
> www.ruchith.org
> www.wso2.org
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: svn commit: r512869 - /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AddressingBasedDispatcher.java

[Brian De Pradine]

Hi Sanjiva,

If this problem can be fixed in the Sandesha layer that will be better 
than the current fix. I will revert the changes.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 05/03/2007 02:59:15:

> Brian De Pradine wrote:
> > 
> > In this scenario the server sends a response message to the client. 
The 
> > client then tries to send an acknowledgement to the server, but the 
> > acknowledgement gets lost, for whatever reason. This means that the 
> > WS-RM layer, in the server, will eventually time-out and send the 
> > response message again. This time the client should send an 
> > acknowledgement to cover both the original and the duplicate response 
> > messages.
> > 
> > This scenario is broken because the duplicate response never makes it 
to 
> > the WS-RM layer on the client side, because the 
> > AddressingBasedDispatcher recognises it as a duplicate and throws an 
> > exception instead. This means that the WS-RM layer never gets driven 
to 
> > send the second acknowledgement. The result is that the server will 
> > simply keep sending duplicate responses forever (almost)!
> > 
> > In order to get this scenario to work the AddressingBasedDispatcher 
will 
> > need to dispatch any duplicate messages as normal, instead of deciding 

> > that they are 'bad' and throwing an exception. This will allow WS-RM 
to 
> > be easily added into the picture at any time. This also means that if 
> > there is no WS-RM engaged then a service will potentially be driven 
more 
> > than once if there are duplicate messages (created by some other 
means). 
> > This shouldn't be a problem, however, because web services are meant 
to 
> > be stateless entities anyway :-) If you do happen to have a web 
service 
> > that is not stateless then you will need to engage WS-RM to ensure 
that 
> > it is not driven by duplicates.
> 
> OK I understand the scenario but I'm -1 on this because it breaks normal 

> users. You can't say that Web services are stateless and therefore its 
ok 
> to just let messages get delivered repeatedly violating our MEP concept!
> 
> RM is a lower level thing than MEPS- its infrastructural. The MEP should 

> not be marked complete if the message hasn't been received to the 
> satisfaction of the lower level.
> 
> If what Chamikara suggests will fix this for RM that's great but no 
matter 
> what this change is not acceptable because its breaking the definition 
of 
> a MEP. Think of a TCP analogy: TCP users a protocol similar to RM to 
> resend packets. Anyone who implements something like HTTP over TCP 
doesn't 
> need to be concerned with the response being delivered twice!!
> 
> Sanjiva.
> -- 
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Director; Open Source Initiative; http://www.opensource.org/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: svn commit: r512869 - /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AddressingBasedDispatcher.java

[Brian De Pradine]

Hi Sanjiva,

I will try my best. :-)

Here is a WS-RM scenario that currently doesn't work,

Client  Server
--  --
   |   1. Response|
   |  <-  |
   |   2. Ack |
   |  >X  |
   |   3. Duplicate   |
   |  <-  |
   |   4. Ack |
   |  ->  |
   |  |
   |  |

In this scenario the server sends a response message to the client. The 
client then tries to send an acknowledgement to the server, but the 
acknowledgement gets lost, for whatever reason. This means that the WS-RM 
layer, in the server, will eventually time-out and send the response 
message again. This time the client should send an acknowledgement to 
cover both the original and the duplicate response messages.

This scenario is broken because the duplicate response never makes it to 
the WS-RM layer on the client side, because the AddressingBasedDispatcher 
recognises it as a duplicate and throws an exception instead. This means 
that the WS-RM layer never gets driven to send the second acknowledgement. 
The result is that the server will simply keep sending duplicate responses 
forever (almost)!

In order to get this scenario to work the AddressingBasedDispatcher will 
need to dispatch any duplicate messages as normal, instead of deciding 
that they are 'bad' and throwing an exception. This will allow WS-RM to be 
easily added into the picture at any time. This also means that if there 
is no WS-RM engaged then a service will potentially be driven more than 
once if there are duplicate messages (created by some other means). This 
shouldn't be a problem, however, because web services are meant to be 
stateless entities anyway :-) If you do happen to have a web service that 
is not stateless then you will need to engage WS-RM to ensure that it is 
not driven by duplicates.

I hope this helps.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 02/03/2007 02:57:26:

> Hi Brian,
> 
> That doesn't make sense to me- if the MEP has completed then the message 

> is arriving after everything has happened. The MEP would not have been 
> marked complete unless RM successfully delivered the message to the 
receiver.
> 
> So if after that a message arrives referring to a completed operation 
then 
> we can reject it in addressing right away.
> 
> Can you explain a scenario where someone like WS-RM will do anything 
> useful with it? And what will happen if there's no WS-RM etc. around at 
> all and this method doesn't catch this repeated message?
> 
> Thanks,
> 
> Sanjiva.
> 
> Brian De Pradine wrote:
> > 
> > Hello,
> > 
> > Apologies for not making the intent clearer. We are not swallowing the 

> > message, but instead simply allowing it to continue on it's way 
through 
> > the flow. The idea is that we do not have enough information in the 
> > AddressingBasedDispatcher to determine that such messages are 'bad'. 
> > Instead we want to allow other layers such as WS-RM to see, and 
possibly 
> > handle, such duplicate messages.
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319 Internal 246319
> > 
> > If you can't find the time to do it right the first time, where will 
you 
> > find the time to do it again?
> > 
> > 
> > Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 01/03/2007 
01:47:46:
> > 
> >  > +1 but I'm confused why we'd remove this exception .. if someone 
sends a
> >  > response message again we should be saying "nope been there done 
that
> >  > already" back to the sender. If you eat the exception and log it 
they 
> > have
> >  > no info. What is broken about the old code?
> >  >
> >  > Sanjiva.
> >  >
> >  > David Illsley wrote:
> >  > > Hi Brian,
> >  > > I think it's important that if this (message being swallowed) is
> >  > > happening, that we make it very obvous. What do you think about
> >  > > logging at a higher level than debug?
> >  > > David
&g

Re: svn commit: r512869 - /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AddressingBasedDispatcher.java

[Brian De Pradine]

Hello,

Apologies for not making the intent clearer. We are not swallowing the 
message, but instead simply allowing it to continue on it's way through 
the flow. The idea is that we do not have enough information in the 
AddressingBasedDispatcher to determine that such messages are 'bad'. 
Instead we want to allow other layers such as WS-RM to see, and possibly 
handle, such duplicate messages.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 01/03/2007 01:47:46:

> +1 but I'm confused why we'd remove this exception .. if someone sends a 

> response message again we should be saying "nope been there done that 
> already" back to the sender. If you eat the exception and log it they 
have 
> no info. What is broken about the old code?
> 
> Sanjiva.
> 
> David Illsley wrote:
> > Hi Brian,
> > I think it's important that if this (message being swallowed) is
> > happening, that we make it very obvous. What do you think about
> > logging at a higher level than debug?
> > David
> > 
> > On 28/02/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >> Author: pradine
> >> Date: Wed Feb 28 09:43:07 2007
> >> New Revision: 512869
> >>
> >> URL: http://svn.apache.org/viewvc?view=rev&rev=512869
> >> Log:
> >> Do something more useful than throw an exception.
> >>
> >> Modified:
> >> 
> >> 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AddressingBasedDispatcher.
> java 
> >>
> >>
> >> Modified: 
> >> 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AddressingBasedDispatcher.
> java 
> >>
> >> URL: 
> >> http://svn.apache.
> 
org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AddressingBasedDispatcher.
> java?view=diff&rev=512869&r1=512868&r2=512869 
> >>
> >> 
> 
==
> >>
> >> --- 
> >> 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AddressingBasedDispatcher.
> java 
> >> (original)
> >> +++ 
> >> 
> 
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AddressingBasedDispatcher.
> java 
> >> Wed Feb 28 09:43:07 2007
> >> @@ -137,16 +137,18 @@
> >>  log.debug(msgctx.getLogIDString()+" 
> >> "+Messages.getMessage("checkingrelatesto",
> >>  relatesTo));
> >>  }
> >> -if ((relatesTo != null) && !"".equals(relatesTo)) {
> >> +if (relatesTo != null && !"".equals(relatesTo)) {
> >>  OperationContext operationContext =
> >>  msgctx.getConfigurationContext()
> >>  .getOperationContext(relatesTo);
> >>
> >>  if (operationContext != null) {
> >>  if(operationContext.isComplete()){
> >> -// If the dispatch happens because of the 
> >> RelatesTo and the mep is complete
> >> -// we should throw a more descriptive fault.
> >> -throw new 
> >> AxisFault(Messages.getMessage("duplicaterelatesto",relatesTo));
> >> +if(LoggingControl.debugLoggingAllowed && 
> >> log.isDebugEnabled()){
> >> +log.debug(msgctx.getLogIDString()+" 
> >> Operation context is marked as complete. Calling cleanup on it.");
> >> +}
> >> +operationContext.cleanup();
> >> +return InvocationResponse.CONTINUE;
> >>  }
> >> 
> >> msgctx.setAxisOperation(operationContext.getAxisOperation());
> >>  msgctx.setOperationContext(operationContext);
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> > 
> > 
> 
> -- 
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Director; Open Source Initiative; http://www.opensource.org/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Vote][Axis2] Isuru Eranga Suriarachchi as a committer

[Brian De Pradine]

Here's my +1.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?




"Thilina Gunarathne" <[EMAIL PROTECTED]> 
31/01/2007 12:00
Please respond to
axis-dev@ws.apache.org


To
"Axis developer list" 
cc

Subject
[Vote][Axis2] Isuru Eranga Suriarachchi as a committer






Hi All,
   I would like to propose Isuru Eranga Suriarachchi as an Apache
Axis2/java committer.

   Isuru started with improving and contributing to Axis2
documentation. Later he implemented JSON support for Axis2  and has
been adding more and more features. I  am confident that he will
contribute to more and more areas in Axis2. His knowledge  on Axiom &
Axis2 (Specially the transport layers) would help us a lot in the
future.

Following are his contributions so far,
http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=Isuru+Eranga+Suriarachchi&q=b


Here is my vote: +1

Thanks,
Thilina...

-- 
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AXIS2] [VOTE] Committer Nomination for Mike Rheinheimer and Ann Robinson

[Brian De Pradine]

+1 for both

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


R J Scheuerle Jr <[EMAIL PROTECTED]> wrote on 19/01/2007 01:11:33:

> I would like to nomimate Mike Rheinheimer and Ann Robinson as 
committers.
> 
> Mike Rheinheimer is an active contributor to the JAX-WS effort.
> His primary responsibility is the JAX-WS application handler code, but 
he has 
> also made significant contributions to the exception flow and tests.
> In addition, Mike is a StAX and JAX-RPC expert.
> 
> Ann Robinson has contributed the Message Context Serialization to AXIS2.
> As part of that work, Ann acquired an understanding of the AXIS2 
> message flow and message object relationships. She is also 
> contributing to the JAX-WS effort.
> Ann is an expert on SAAJ, StAX, and JAX-RPC. In addition, she has a 
> thorough knowledge of Axiom.
> 
> Both of these candidates have several years of Web Service 
> development experience. Making them committers will increase our 
> ability to complete and improve the JAX-WS implementation. 
> 
> 
> 
> Rich Scheuerle
> IBM Web Services
> Apache Axis2 ([EMAIL PROTECTED])

Re: [VOTE][Axis2] Move Savan module out of the Axis2 into a new Apache WS subproject

[Brian De Pradine]

+1 from me.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Sanka Samaranayake" <[EMAIL PROTECTED]> wrote on 19/01/2007 05:00:27:

> Hi,
> 
> Savan is a WS-Eventing implementation on top Axis2 and currently 
> lives as a module inside Axis2. 
> 
> I propose we move it into a separate Apache WS sub project which 
> will make Axis2 codebase clean
> and also to do separate releases of Savan. 
> 
> Here is my +1 !!
> 
> Thanks,
> Sanka
> 
> 
> -- 
> Sanka Samaranayake
> WSO2 Inc.
> 
> http://sankas.blogspot.com/
> http://www.wso2.org/ 

Re: [Axis2] Reference parameters read as OMText only

[Brian De Pradine]

Hello Esteban,

Please raise a jira to cover this issue. Thanks.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Esteban León Soto <[EMAIL PROTECTED]> wrote on 17/01/2007 14:04:48:

> Reference parameters are read as text fields and not as xs:anyType as 
> specified in WS-Addressing specs
> 
> 
> AddressingFinalInHandler:53
> 
> toEPR.addReferenceParameter(soapHeaderBlock.getQName(), 
> soapHeaderBlock.getText());
> 
> I would have expected something similar to
> 
> toEPR.addReferenceParameter(soapHeaderBlock);
> 
> Cheers,
> Esteban
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: [Axis2] Defaulting behaviour when a wsa:To header is omitted from a request message.

[Brian De Pradine]

Hi Eran,

My response is below.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Eran Chinthaka <[EMAIL PROTECTED]> wrote on 01/12/2006 18:25:13:

> > As an alternative, there is an existing property called
> > org.apache.axis2.Constants.Configuration.TRANSPORT_IN_URL that already
> > holds the inbound transport URL. If some code wants to use the 
transport
> > URL then maybe we should consider stipulating that the code must 
always
> > use this property to perform the lookup?
> 
> On the other way round, if some one wants to look at the addressing To
> value set it as a property to message context or look in envelope.
> Presence of the above TRANSPORT_IN_URL is not a must.
> But presence of messagecontext.to is a must.

Yes this is also an alternative, I will consider if i can make this work 
for me.

Re: [Axis2] Defaulting behaviour when a wsa:To header is omitted from a request message.

[Brian De Pradine]

Hi Eran,

Please see my comments included below ...

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Eran Chinthaka <[EMAIL PROTECTED]> wrote on 25/11/2006 15:31:18:

> Hi Brian,
> 
> Seems to be a good observation. I agree with some of them, but not all 
:).
> 
> The reason behind we keeping endpoint information inside message context
> has no direct connection with WS-A. All the information in message
> context can be filled by anyone, starting from transport handlers,
> through addressing handler till user handlers. Please do not understand
> that those information are only from WS-A headers.

You are correct when you say that anyone can change any of the properties 
of the message context, and it is this very capability that is responsible 
for this problem. Currently, the wsa:To message addressing property is 
saved in the message context using MessageContext.setTo(), which delegates 
to Options.setTo(). However, the HTTP transport also saves the transport 
URL to that same location, by also using MessageContext.setTo(). Until 
now, this has not been a problem as the was:To message addressing property 
will simply overwrite the transport URL. The change that I want to make is 
to simply extend this current behaviour, of overwriting the transport URL, 
to the situation where the wsa:To message addressing property has been 
omitted, and the default value for the wsa:To message addressing property 
must be used.

> 
> I agree with you about your claim on invalid messages being sent by
> Axis2, if that is happening now. If that is the case, we need to fix it
> in the sending logic and not in dispatchers or message context.

The issue here is not with the sending logic, but with the inbound 
processing logic. The WS-addressing final inbound handler must be able to 
understand that the absence of a was:To header, in a message that includes 
other mandatory ws-addressing headers, is semantically equivalent to the 
presence of the header, 
http://www.w3.org/2005/08/addressing/anonymous. Once this 
logic is available then the handler will be spec compliant, and we will be 
able to add the capability to omit optional headers.

> 
> Brian De Pradine wrote:
> 
> > 
> > 3) if ws-addressing is engaged, and there are ws-addressing headers in
> > the message, and one of them is the wsa:To header then it will be used
> > to determine the service.
> 
> I don't think we can hard code a requirement like this in to Axis2.
> Admin of Axis2 will decide the order of dispatchers and depending on
> that one dispatcher will find the operation and the service.
> 
> For example, one will use wsa:To to reach to an endpoint but some more
> information in SOAP action/request URI or QName of the first child of
> the body will be used inside the engine to identify the service.

It wasn't my intention to suggest that this was a strict behaviour of 
Axis2, only that it will be the current behaviour if the administrator 
decides to engage WS-Addressing with Axis2.

> 
> 
> 
> -- Chinthaka
> 
> [attachment "signature.asc" deleted by Brian De Pradine/UK/IBM] 

As an alternative, there is an existing property called 
org.apache.axis2.Constants.Configuration.TRANSPORT_IN_URL that already 
holds the inbound transport URL. If some code wants to use the transport 
URL then maybe we should consider stipulating that the code must always 
use this property to perform the lookup?

[Axis2] Defaulting behaviour when a wsa:To header is omitted from a request message.

[Brian De Pradine]

Hello all,

Currently, there is a comment in the AddressingFinalInHandler to the 
effect that if no wsa:To header is found in an inbound request message 
then we do not use the wsa:Anonymous URL as its default value. This is to 
allow an alternative, such as the transport URL, to be used instead. I 
believe that this is the wrong option for the following reasons:

1) It is not compliant with the WS-Addressing core spec.

2) It prevents us from optimising the set of WS-Addressing headers 
included in a message.

Consider the following request:


   http://www.w3.org/2005/08/addressing"; 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  
 http://localhost:8081/axis2/services/MyService
 
 http://www.w3.org/2005/08/addressing/anonymous
 
 urn:uuid:7A171A996AC3CC11641979655001
 urn:echo
  
  
 .
  
   

it will result in the following response:


   http://www.w3.org/2005/08/addressing"; 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  
 http://www.w3.org/2005/08/addressing/anonymous
 
 http://www.w3.org/2005/08/addressing/none
 
 urn:uuid:0839A16552C8EF67E911641979660934
 urn:echo
 http://www.w3.org/2005/08/addressing/reply
">urn:uuid:7A171A996AC3CC11641979655001
  
  
 .
  
   

Instead what we would prefer that the following request be sent:


   http://www.w3.org/2005/08/addressing"; 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  
 http://localhost:8081/axis2/services/MyService
 urn:uuid:7A171A996AC3CC11641979655001
 urn:echo
  
  
 .
  
   

which would provoke the following response:


   http://www.w3.org/2005/08/addressing"; 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  
 
 http://www.w3.org/2005/08/addressing/none
 
 urn:uuid:0839A16552C8EF67E911641979660934
 urn:echo
 urn:uuid:7A171A996AC3CC11641979655001
  
  
 .
  
   

Notice that in the second request-response pair we are able to leave out 
optional headers, as they contain values that match the defaults specified 
in the spec. In the request we omitted the wsa:ReplyTo header. In the 
response we omitted the wsa:To header (and the relationship type attribute 
of the wsa:RelatesTo header). The current Axis2 behaviour prevents us from 
generating a response message that omits the wsa:To field. The benefit of 
doing this is a performance one, i.e. fewer SOAP headers => better 
performance.

I am proposing that axis2 provide the following behaviour instead:

1) If ws-addressing is not engaged then the transport URL can be used to 
identify the service

2) if ws-addressing is engaged, but there are no ws-addressing headers in 
the message then the transport URL can be used to identify the service

3) if ws-addressing is engaged, and there are ws-addressing headers in the 
message, and one of them is the wsa:To header then it will be used to 
determine the service.

4) if ws-addressing is engaged, and there are ws-addressing headers in the 
message, and the wsa:To header is not one of them then the default value 
will be used ( Note: For an inbound request message, an address of 
wsa:Anonymous will likely result in a "Service not found" fault. This 
means that, if addressing is being used, the wsa:To field of a request 
message should always be provided explicitly. For a response message, the 
AddressingBasedDispatcher will use the wsa:RelatesTo field to correlate 
the response to the original request, so dispatching is not an issue in 
this case.) 

All comments welcome.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?

Re: [Vote][Axis2] Nikhil Thaker as a Committer

[Brian De Pradine]

+1 from me.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


R J Scheuerle Jr <[EMAIL PROTECTED]> wrote on
03/11/2006 15:56:06:

> I would like to nominate Nikhil Thaker as a committer.
> 
> Nikhil has contributed key portions of the JAX-WS component: client

> dispatch/proxy, resource injection, server provider, JAX-WS/JAX-B
tests
> 
> He has opened and contributed to 29 JIRA issues: https://issues.
> apache.org/jira/secure/IssueNavigator.jspa?
> reset=true&reporterSelect=specificuser&reporter=nthaker
> 
> Thanks,
> 
> Rich Scheuerle
> IBM Web Services
> Apache Axis2 ([EMAIL PROTECTED])
> 512-838-5115 (IBM TL 678-5115)

Re: [Axis2] using the EndpointReferenceHelper class

[Brian De Pradine]

Ok. I'll only make the change in trunk.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Davanum Srinivas" <[EMAIL PROTECTED]>
wrote on 03/11/2006 13:36:04:

> Just trunk please.
> 
> thanks,
> dims
> 
> On 11/3/06, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> > Hi guys,
> > Let's do this change only in the trunk.. Hope it's ok with Chamikara...
> >
> > Don't like to take any chances in the 1.1 branch at this point...
> >
> > ~Thilina
> >
> > On 11/3/06, Brian De Pradine <[EMAIL PROTECTED]> wrote:
> > >
> > > Hello Chamikara,
> > >
> > > Your proposal sounds reasonable. I will move the 
> EndpointReferenceHelper in
> > > the trunk and 1.1 branches.
> > >
> > >  Cheers
> > >
> > >  Brian DePradine
> > >  Web Services Development
> > >  IBM Hursley
> > >  External  +44 (0) 1962 816319      
  Internal 246319
> > >
> > >  If you can't find the time to do it right the first
time, where will you
> > > find the time to do it again?
> > >
> > >
> > > "Chamikara Jayalath" <[EMAIL PROTECTED]>
wrote on 03/11/200609:56:18:
> > >
> > >
> > >  > Hi All,
> > >  >
> > >  > One solution for this may be to move the EndpointReferenceHelper
> > >  > class the the Kernel module. AFAIK most of the
stuff that were in
> > >  > the axis2-common module were moved here.
> > >  >
> > >  > Chamikara
> > >  >
> > >
> > >
> > > > On 11/3/06, Chamikara Jayalath <[EMAIL PROTECTED]>
wrote:
> > > > Hi All,
> > >  >
> > >  > In Sandesha I am using the EndpointReference
class which is present
> > >  > in the Axis2 kernel module. But it seems like
the methods to
> > >  > serialize this are present in a EndpointReferenceHelper
class which
> > >  > is only present in the Addressing module  (
i.e. addressing.mar). So
> > >  > it is not possible to use this from outside.
Is there a way to use
> > >  > this without a ugly code repeat.
> > >  >
> > >  > Thanks,
> > >  > Chamikara
> >
> >
> > --
> > http://webservices.apache.org/~thilina/
> > http://thilinag.blogspot.com/
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 
> -- 
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: [Axis2] using the EndpointReferenceHelper class

[Brian De Pradine]

Hello Chamikara,

Your proposal sounds reasonable. I will
move the EndpointReferenceHelper in the trunk and 1.1 branches.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Chamikara Jayalath" <[EMAIL PROTECTED]>
wrote on 03/11/2006 09:56:18:

> Hi All,
> 
> One solution for this may be to move the EndpointReferenceHelper 
> class the the Kernel module. AFAIK most of the stuff that were in

> the axis2-common module were moved here.
> 
> Chamikara
> 

> On 11/3/06, Chamikara Jayalath <[EMAIL PROTECTED]>
wrote:
> Hi All,
> 
> In Sandesha I am using the EndpointReference class which is present

> in the Axis2 kernel module. But it seems like the methods to 
> serialize this are present in a EndpointReferenceHelper class which

> is only present in the Addressing module  ( i.e. addressing.mar).
So
> it is not possible to use this from outside. Is there a way to use

> this without a ugly code repeat.
> 
> Thanks,
> Chamikara

Re: [Axis2]Embdeding Jetty to Axis2

[Brian De Pradine]

+1 from me.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Jaliya Ekanayake" <[EMAIL PROTECTED]>
wrote on 08/10/2006 15:20:49:

> Hi All,
> 
> One other advantage is that we can simply give an Axis2 server for
the user 
> as well.
> All they want is to start the Axis2 server which is based on Jetty.
> 
> Thanks,
> -Jaliya
> 
> 
> - Original Message - 
> From: "Srinath Perera" <[EMAIL PROTECTED]>
> To: 
> Cc: "Thilina Gunarathne" <[EMAIL PROTECTED]>; "Jaliya
Ekanayake" 
> <[EMAIL PROTECTED]>
> Sent: Sunday, October 08, 2006 7:56 AM
> Subject: [Axis2]Embdeding Jetty to Axis2
> 
> 
> > Hi All;
> > Myself and jaliya were talking about trying to do lot of async
> > requests using Axis2 client .. it falis at about 40-50 requests
and we
> > belive that is becouse ..simple HTTP server can't handle the
load.
> >
> > I was looking at the jetty and found out that Jetty6 allow you
to
> > embed it to the application tightly. For an example
> >
> > Server server = new Server(8080);
> > Context root = new Context(server,"/",Context.SESSIONS);
> > root.addServlet(new ServletHolder(new HelloServlet(serviceMap)),
"/*");
> > server.start();
> >
> > Will create a new server and add a servlet.
> >
> > I belive if we embdeded Jetty to Axis2
> > 1) Axis2 can use jetty as the listener for async messages
> > 2) Axis2 can started up standalone using jetty
> >
> > I belive I could port our Axis2 servlet to jetty pretty easily.
> >
> > If people agree I think we should have it as a module and if
it is
> > sucessful I think we should switch to it as our default container
some
> > day
> >
> > thoughts?
> > Srinath
> >
> >
> >
> > -- 
> > 
> > Srinath Perera:
> >   http://www.cs.indiana.edu/~hperera/
> >   http://www.bloglines.com/blog/hemapani
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: [Axis2] Build failure

[Brian De Pradine]

Apologies. I appear to have missed that
one.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Ruchith Fernando" <[EMAIL PROTECTED]>
wrote on 30/09/2006 15:00:48:

> Ok... the malicious commit that caused the build failure seems to
be
> the commit to svn revision 451179 [1]. This is due to a bug [2] in
> axiom-1.1.1.
> 
> Devs *PLEASE* do run the integration test cases before you commit
and
> make sure they pass!!!
> 
> Earlier I commented out the test scenario that failed due to [1] and
> now I added it back and made changes to EndpointReferenceHelper#toOM()
> to work with axiom-1.1.1 [3].
> 
> Thanks,
> Ruchith
> 
> 
> [1] http://svn.apache.org/viewvc?view=rev&rev=451179
> [2] https://issues.apache.org/jira/browse/WSCOMMONS-103
> [3] http://svn.apache.org/viewvc?view=rev&rev=451602
> 
> 
> On 9/30/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
> > Hi Dennis,
> >
> > I updated the Rampart code to add the correct resource property
in the
> > exception (SVN revision 451552). But this is caused by another
> > exception and you should be able get that out properly now.
> >
> > BTW please make sure you have the latest wss4j-SNAPSHOT.jar in
you
> > maven repo as well.I just ran this test with JDK 1.5 and it passed.
> >
> > Thanks,
> > Ruchith
> >
> > On 9/30/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
> > > I'm getting a failure on org.apache.rampart.RampartTest
in integration:
> > >
> > > java.lang.RuntimeException: Undefined 'org.apache.axiom.om.impl.
> llom.OMElementImpl' resource property
> > >         at org.apache.rampart.RampartException.
> getMessage(RampartException.java:81)
> > >         at org.apache.rampart.RampartException.
> (RampartException.java:61)
> > >         at org.apache.rampart.RampartException.
> (RampartException.java:67)
> > >         at org.apache.rampart.util.RampartUtil.
> getToken(RampartUtil.java:450)
> > >         at org.apache.rampart.util.RampartUtil.
> getSecConvToken(RampartUtil.java:359)
> > >
> > > I updated to latest jars first by running "maven clean
jar
> > > -Dmaven.test.skip=true", then ran "maven -o".
After the first failure I
> > > repeated this process, with the same result. I'm running
JDK 1.5.0_07 on
> > > Linux.
> > >
> > >   - Dennis
> > >
> > > --
> > > Dennis M. Sosnoski
> > > SOA, Web Services, and XML
> > > Training and Consulting
> > > http://www.sosnoski.com - http://www.sosnoski.co.nz
> > > Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > www.ruchith.org
> >
> 
> 
> -- 
> www.ruchith.org
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: FW: Creating or setting header options

[Brian De Pradine]

Hello Joe,

Have you  engaged the addressing
module in your client? If you haven't then follow the details here,

http://ws.apache.org/axis2/1_0/userguide3.html#EchoNonBlockingDualClient

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Joe Wyrembelski" <[EMAIL PROTECTED]> wrote
on 30/08/2006 20:18:58:

> 
> Basic Question: 
> What do I need to do in order to get header options to show up in
my
> envelope?
> 
> Environment: 
> Using Axis2 to generate my client (with XMLBeans as my binding
> technology). Generated the code using the "-s -t -p com.mypackage
-d
> xmlbeans" options.
> 
> When I create my stub using the defaults, I get a good set of HTML
> headers
> 
> DEBUG header:69 - >> "POST /service.asmx HTTP/1.1[\r][\n]"
> DEBUG header:69 - >> "User-Agent: Axis/2.0[\r][\n]"
> DEBUG header:69 - >> "SOAPAction: Create[\r][\n]"
> DEBUG header:69 - >> "Host: [\r][\n]"
> DEBUG header:69 - >> "Transfer-Encoding: chunked[\r][\n]"
> DEBUG header:69 - >> "Content-Type: text/xml; charset=UTF-8[\r][\n]"
> 
> 
> But the headers in the soap envelope aren't correct. In fact, they
are
> empty.
> 
> 
> 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>    
>    
> 
> 
> Ultimately, I think I need my envelope to look liks:
> 
> 
> 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse
> curity-secext-1.0.xsd"
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
> urity-utility-1.0.xsd">
>    
>       Create
>    
> urn:uuid:867a6c22-d0f5-43ff-95cc-89a1d6d43068
> eID>
>       
>          
>    
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>          
>       
>       **
>       
>          
> wsu:Id="Timestamp-66232358-fd32-4332-9555-3e55153854dd">
>             **
>             **
>          
>          
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
> urity-utility-1.0.xsd"
> wsu:Id="SecurityToken-2ce8562a-6bdd-45a1-9fb6-99f5011fa97e">
>    
> **
>             
> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-t
> oken-profile-1.0#PasswordText">**
>             **
>             **
>          
>       
>    
> 
> 
> I've tried: 
> 
> 
> Attempt #1: Get the ServiceClient from my Stub and set it's options
> 
> ServiceClient sc = stub._getServiceClient(); Options sco =
> serviceClient.getOptions(); sco.setAction("Create");
> sco.setMessageId(UUID.randomUUID().toString());
> 
> Attempt #2: Get the ServiceClient from my Stub and set it's options's
> properties
> 
> sco.setProperty(AddressingConstants.WSA_ACTION, "Create");
> sco.setProperty(AddressingConstants.WSA_MESSAGE_ID,
> UUID.randomUUID().toString());
> 
> Attempt #3: Both
> Attempt #4: Setting the service client back into the Stub Attempt
#5:
> Setting the options back into the service client Attempt #5: Creating
a
> new options and setting those into the service client Attempt #6:
> Creating a new endpoint according to the post
> "http://marc.theaimsgroup.com/?l=axis-user&m=115435987605651&w=4"

> 
> Etc. 
> 
> So what do I have to do? And where in the documentation should I have
> found this? 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: [Axis2] Re: [jira] Commented: (AXIS2-993) org.apache.axis2.addressing.EndpointReference should explicitly save the WS-Addressing namespace

[Brian De Pradine]

"Eran Chinthaka (JIRA)" <[EMAIL PROTECTED]>
wrote on 17/08/2006 14:48:15:

> I'd like to keep it as it is and rather than implementing toOM and

> fromOM inside that, we can do the same using one of the following

> options, without touching the EPR class.
> 
> 1. Extending from EPR class, we can have two different sub classes

> for two specs. But this must make sure that EPR class can be used
as
> it is without its sub classes for some users, who do not want to 
> worry abt the WS-A spec. 
> 
> 2. Delegate to a helper class for fromOM and toOM. 
> AddressingHelper.toOM(epr, addressingNamespace)
> AddressingHelper.fromOM(omElement)
> 

In order to move this forward, I propose that we do the following:

1. Change the signature of the helper methods to the
following,

AddressingHelper.toOM(epr, qname, addressingNamespace)
AddressingHelper.fromOM(omElement, addressingNamespace)
AddressingHelper.fromOM(omElement)

The qname, passed to the toOM() method,
is the name of the element that will contain the EndpointRefereneceType.
The addressingNamespace, passed to the fromOM() method, is used to explicitly
specify which namespace to use for the deserialization. If the namespace
of the omElement EndpointReferenceType did not match this namespace then
that would be a fault.

2. Deprecate, or remove, toOM() and
fromOM() from EndpointReference

3. Deprecate, or remove, setName() and
getName() from EndpointReference

Does this sound reasonable?

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?

[Axis2] Re: [jira] Commented: (AXIS2-993) org.apache.axis2.addressing.EndpointReference should explicitly save the WS-Addressing namespace

[Brian De Pradine]

Hello all,

Eran suggested that we move this discussion
to the axis-dev list. Please find my comments below.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Eran Chinthaka (JIRA)" <[EMAIL PROTECTED]>
wrote on 17/08/2006 14:48:15:

>     [ http://issues.apache.org/jira/browse/AXIS2-993?
> page=comments#action_12428656 ] 
>             
> Eran Chinthaka commented on AXIS2-993:
> --
> 
> Brian,
> 
> This is one of the problems I've been looking at for some time. IMO,
> EndpointReference class better be independent of WS-A. We got the

> attributed of the EPR class by looking at 2005/08 spec, but after

> that it had nothing to do with that. 

Why does the EndpointReference class need to be independent
of the WS-Addressing
namespace? This is the aspect of this discussion that
I haven't understood yet.
Considering that in axis2 ALL EPRs are represented
using instances of this class
it seems to me that the addressing namespace is an
important attribute to capture.

> I'd like to keep it as it is and rather than implementing toOM and

> fromOM inside that, we can do the same using one of the following

> options, without touching the EPR class.
> 
> 1. Extending from EPR class, we can have two different sub classes

> for two specs. But this must make sure that EPR class can be used
as
> it is without its sub classes for some users, who do not want to 
> worry abt the WS-A spec. 
> 

EndpointReference is currently used to represent EPRs
for both specs, and
I believe that this works well. The change that I
am proposing would 
preserve this without the need for subclassing, which
just adds complexity
for no extra benefit, in this case.

> 2. Delegate to a helper class for fromOM and toOM. 
> AddressingHelper.toOM(epr, addressingNamespace)
> AddressingHelper.fromOM(omElement)
> 

I think that we are probably in agreement that having
methods to correctly
serialize/deserialize EPRs are a good thing. I believe
that we differ on
where this code should live. I believe that this code
should be in the
EndpointReference class, rather than some helper class,
as this leads to
better encapsulation, and ultimately code that is
easier to understand.

> For further discussions, if required, lets move this to axis-dev 
> mailing list. 
> 
> -- Chinthaka
> 
> > org.apache.axis2.addressing.EndpointReference should explicitly

> save the WS-Addressing namespace
> > 
> 
> >
> >                 Key:
AXIS2-993
> >                 URL:
http://issues.apache.org/jira/browse/AXIS2-993
> >             Project: Apache Axis
2.0 (Axis2)
> >          Issue Type: Improvement
> >          Components: Addressing
> >            Reporter: Brian DePradine
> >         Attachments: newerpatch.txt, newpatch.txt,
patch.txt
> >
> >
> > Currently, the EndpointReference class always assumes that it
is a
> representation of endpoint references based on the WS-Addressing 
> 2005/08 (final) spec. However, this class is also used to represent

> endpoint references based on the 2004/08 (submission) spec. The 
> problem is that the methods toOM() and fromOM() only work correctly

> in the former case. If the EndpointReference class is modified to

> explicitly save the WS-Addressing namespace then these methods can

> be made to work correctly for both specs. Patch to follow.
> 
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:

> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
>         
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: [Axis2] Build failed

[Brian De Pradine]

Hello,

The compile problem that I was having
was due to my build environment. When I trashed my environment and recreated
it the compile problem went away.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


Brian De Pradine/UK/[EMAIL PROTECTED] wrote on 07/07/2006
16:33:43:

> 
> Hi, 
> 
> I tried again with revision 419900, and I got the same problem with

> the integration module :-( 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319         Internal
246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> "Rajith Attapattu" <[EMAIL PROTECTED]> wrote on 07/07/2006
15:26:33:
> 
> > Brian,
> > 
> > The build was sucessfull for me. Maybe try again.
> > 
> > thanks Ajith and dims for the support
> > 
> > Regards,
> > 
> > Rajith
> 
> > On 7/7/06, Brian De Pradine <[EMAIL PROTECTED]> wrote:

> > 
> > Hello, 
> > 
> > I can now build the adb-codegen module, but I now get a build
error 
> > in the integration module. Looking at the code it seems that
the 
> > class modules\integration\target\rpc-
> > test2\src\com\example\www\ServiceNameStub.java is making the

> > following method call: 
> > 
> > toEnvelope(org.apache.axiom.soap.SOAPFactory,int,java.lang.String,
> > com.example.www.ServiceNameStub.MyComplexType,boolean), 
> > 
> > but the only method that exists in the class is: 
> > 
> > toEnvelope(org.apache.axiom.soap.SOAPFactory,int,com.example.www.
> > ServiceNameStub.MyComplexType,java.lang.String,boolean). 
> > 
> > Notice that MyComplexType and String are swapped. The details
of the
> > failure are included below. 
> > 
> >     [echo] Running codegen RPC WSDLs - take 2 
> >     [java] log4j:WARN No appenders could be found for
logger (org.
> > apache.axis2.addressing.wsdl.WSDL11ActionHelper). 
> >     [java] log4j:WARN Please initialize the log4j system
properly. 
> >     [mkdir] Created dir: F:
> > \Drivers\axis2\modules\integration\target\rpc-test2\build 
> >     [mkdir] Created dir: F:
> > \Drivers\axis2\modules\integration\target\rpc-test2\build\classes

> >     [mkdir] Created dir: F:
> > \Drivers\axis2\modules\integration\target\rpc-test2\build\lib

> >     [mkdir] Created dir: F:
> > \Drivers\axis2\modules\integration\target\rpc-test2\test 
> >     [echo] Stax Availability= true 
> >     [echo] Axis2 Availability= true 
> >     [javac] Compiling 2 source files to F:
> > \Drivers\axis2\modules\integration\target\rpc-test2\build\classes

> > F:\Drivers\axis2\modules\integration\target\rpc-
> > test2\src\com\example\www\ServiceNameStub.java:128: cannot find
symbol 
> > symbol  : method toEnvelope(org.apache.axiom.soap.SOAPFactory,int,
> > java.lang.String,com.example.www.ServiceNameStub.MyComplexType,boolean)

> > location: class com.example.www.ServiceNameStub 
> >                  
                     
   env = 
> > toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),

> >                  
                     
              ^ 
> > F:\Drivers\axis2\modules\integration\target\rpc-
> > test2\src\com\example\www\ServiceNameStub.java:234: cannot find
symbol 
> > symbol  : method toEnvelope(org.apache.axiom.soap.SOAPFactory,int,
> > java.lang.String,com.example.www.ServiceNameStub.MyComplexType,boolean)

> > location: class com.example.www.ServiceNameStub 
> >                  
                     
   env = 
> > toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),

> >                  
                     
              ^ 
> > Note: F:\Drivers\axis2\modules\integration\target\rpc-
> > test2\src\com\example\www\ServiceNameStub.java uses unchecked
or 
> > unsafe operations. 
> > Note: Recompile with -Xlint:unchecked for details. 
> > 2 errors 
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319        
Internal 246319
> > 
> > If you can't find the time to do it right the first time, where
will
> > you find the time to do it again?
> > 
> > 
> > "Davanum Srinivas" <[EMAIL PROTECTED]> wrote
on 07/07/2006 11:54:03: 
> > 
> > 
> > > Please check now..
> > > 
> > > -- dims
> >

Re: [Axis2] Build failed

[Brian De Pradine]

Hi,

I tried again with revision 419900,
and I got the same problem with the integration module :-(

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Rajith Attapattu" <[EMAIL PROTECTED]>
wrote on 07/07/2006 15:26:33:

> Brian,
> 
> The build was sucessfull for me. Maybe try again.
> 
> thanks Ajith and dims for the support
> 
> Regards,
> 
> Rajith

> On 7/7/06, Brian De Pradine <[EMAIL PROTECTED]>
wrote:
> 
> Hello, 
> 
> I can now build the adb-codegen module, but I now get a build error

> in the integration module. Looking at the code it seems that the 
> class modules\integration\target\rpc-
> test2\src\com\example\www\ServiceNameStub.java is making the 
> following method call: 
> 
> toEnvelope(org.apache.axiom.soap.SOAPFactory,int,java.lang.String,
> com.example.www.ServiceNameStub.MyComplexType,boolean), 
> 
> but the only method that exists in the class is: 
> 
> toEnvelope(org.apache.axiom.soap.SOAPFactory,int,com.example.www.
> ServiceNameStub.MyComplexType,java.lang.String,boolean). 
> 
> Notice that MyComplexType and String are swapped. The details of the
> failure are included below. 
> 
>     [echo] Running codegen RPC WSDLs - take 2 
>     [java] log4j:WARN No appenders could be found for logger
(org.
> apache.axis2.addressing.wsdl.WSDL11ActionHelper). 
>     [java] log4j:WARN Please initialize the log4j system
properly. 
>     [mkdir] Created dir: F:
> \Drivers\axis2\modules\integration\target\rpc-test2\build 
>     [mkdir] Created dir: F:
> \Drivers\axis2\modules\integration\target\rpc-test2\build\classes

>     [mkdir] Created dir: F:
> \Drivers\axis2\modules\integration\target\rpc-test2\build\lib 
>     [mkdir] Created dir: F:
> \Drivers\axis2\modules\integration\target\rpc-test2\test 
>     [echo] Stax Availability= true 
>     [echo] Axis2 Availability= true 
>     [javac] Compiling 2 source files to F:
> \Drivers\axis2\modules\integration\target\rpc-test2\build\classes

> F:\Drivers\axis2\modules\integration\target\rpc-
> test2\src\com\example\www\ServiceNameStub.java:128: cannot find symbol

> symbol  : method toEnvelope(org.apache.axiom.soap.SOAPFactory,int,
> java.lang.String,com.example.www.ServiceNameStub.MyComplexType,boolean)

> location: class com.example.www.ServiceNameStub 
>                    
                     
 env = 
> toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),

>                    
                     
            ^ 
> F:\Drivers\axis2\modules\integration\target\rpc-
> test2\src\com\example\www\ServiceNameStub.java:234: cannot find symbol

> symbol  : method toEnvelope(org.apache.axiom.soap.SOAPFactory,int,
> java.lang.String,com.example.www.ServiceNameStub.MyComplexType,boolean)

> location: class com.example.www.ServiceNameStub 
>                    
                     
 env = 
> toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),

>                    
                     
            ^ 
> Note: F:\Drivers\axis2\modules\integration\target\rpc-
> test2\src\com\example\www\ServiceNameStub.java uses unchecked or 
> unsafe operations. 
> Note: Recompile with -Xlint:unchecked for details. 
> 2 errors 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319         Internal
246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> "Davanum Srinivas" <[EMAIL PROTECTED]> wrote on 07/07/2006
11:54:03:
> 
> 
> > Please check now..
> > 
> > -- dims
> > 
> > On 7/7/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > > I think I know the problem here.
> > > I modified the XMLSchema project to add a few new methods
and fix some
> > > bugs. However the XMLSchema had two builds for maven 1 and
maven 2 and
> > > these build scripts were putting the jars in two different
repo
> > > locations. Hence I changed the maven 1 build script to have
the
> > > correct group id ("org.apache.ws.commons").Somehow
it seems that the
> > > snapshots are not built according to the  new script.
> > >
> > > Rajitha, What you can do for now is to get the latest source
from SVN
> > > from here [1] and run maven on it. that should copy the
jar to the
> > > correct repo location. Meanwhile I'll buzz dims and see
what is wrong
> > > with the automatic build.
> > >
> > > Ajith
>

Re: [Axis2] Build failed

[Brian De Pradine]

Hello,

I can now build the adb-codegen module,
but I now get a build error in the integration module. Looking at the code
it seems that the class modules\integration\target\rpc-test2\src\com\example\www\ServiceNameStub.java
is making the following method call:

toEnvelope(org.apache.axiom.soap.SOAPFactory,int,java.lang.String,com.example.www.ServiceNameStub.MyComplexType,boolean),

but the only method that exists in the
class is:

toEnvelope(org.apache.axiom.soap.SOAPFactory,int,com.example.www.ServiceNameStub.MyComplexType,java.lang.String,boolean).

Notice that MyComplexType and String
are swapped. The details of the failure are included below.

    [echo] Running codegen
RPC WSDLs - take 2
    [java] log4j:WARN No appenders
could be found for logger (org.apache.axis2.addressing.wsdl.WSDL11ActionHelper).
    [java] log4j:WARN Please
initialize the log4j system properly.
    [mkdir] Created dir: F:\Drivers\axis2\modules\integration\target\rpc-test2\build
    [mkdir] Created dir: F:\Drivers\axis2\modules\integration\target\rpc-test2\build\classes
    [mkdir] Created dir: F:\Drivers\axis2\modules\integration\target\rpc-test2\build\lib
    [mkdir] Created dir: F:\Drivers\axis2\modules\integration\target\rpc-test2\test
    [echo] Stax Availability=
true
    [echo] Axis2 Availability=
true
    [javac] Compiling 2 source
files to F:\Drivers\axis2\modules\integration\target\rpc-test2\build\classes
F:\Drivers\axis2\modules\integration\target\rpc-test2\src\com\example\www\ServiceNameStub.java:128:
cannot find symbol
symbol  : method toEnvelope(org.apache.axiom.soap.SOAPFactory,int,java.lang.String,com.example.www.ServiceNameStub.MyComplexType,boolean)
location: class com.example.www.ServiceNameStub
           
                     
         env = toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
           
                     
                    ^
F:\Drivers\axis2\modules\integration\target\rpc-test2\src\com\example\www\ServiceNameStub.java:234:
cannot find symbol
symbol  : method toEnvelope(org.apache.axiom.soap.SOAPFactory,int,java.lang.String,com.example.www.ServiceNameStub.MyComplexType,boolean)
location: class com.example.www.ServiceNameStub
           
                     
         env = toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
           
                     
                    ^
Note: F:\Drivers\axis2\modules\integration\target\rpc-test2\src\com\example\www\ServiceNameStub.java
uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked
for details.
2 errors

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Davanum Srinivas" <[EMAIL PROTECTED]>
wrote on 07/07/2006 11:54:03:

> Please check now..
> 
> -- dims
> 
> On 7/7/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I think I know the problem here.
> > I modified the XMLSchema project to add a few new methods and
fix some
> > bugs. However the XMLSchema had two builds for maven 1 and maven
2 and
> > these build scripts were putting the jars in two different repo
> > locations. Hence I changed the maven 1 build script to have the
> > correct group id ("org.apache.ws.commons").Somehow
it seems that the
> > snapshots are not built according to the  new script.
> >
> > Rajitha, What you can do for now is to get the latest source
from SVN
> > from here [1] and run maven on it. that should copy the jar to
the
> > correct repo location. Meanwhile I'll buzz dims and see what
is wrong
> > with the automatic build.
> >
> > Ajith
> >
> > [1] https://svn.apache.
> org/repos/asf/webservices/commons/trunk/modules/XmlSchema
> >
> > On 7/7/06, Ruchith Fernando <[EMAIL PROTECTED]>
wrote:
> > > Hi Rajith,
> > >
> > > Please make sure you have the latest XmlSchema-SNAPSHOT.jar
in you
> > > local maven repo.
> > >
> > > If you were building with the "-o" options please
try without it.
> > >
> > > Thanks,
> > > Ruchith
> > >
> > > On 7/7/06, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
> > > > btw, when I checked the soource repository
> > > > org.apache.ws.commons.schema.XmlSchemaType
> > > > does not have the method getMetaInfoMap() .
> > > >
> > > > So is this latest XmlSchemaType not checked into svn
or a problem with
> > > > ExtensionUtility?
> > > >
> > > > A quick fix is appreciated :-)
> > > >
> > > > -Regards
> > > >
> > > > Rajith
> > > >
> > > >
> > > > On 7/6/06, Rajith Attapattu <[EMAIL PROTECTED]
> wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I get the following compilation errors and would
be 
> gratefull if somebody
> > > > can shed some light !!
> > > > > Is there an updated XmlSchema version on maven
repos? or is the
> > > > ExtensionUtility out of date?
> > > > >
> > > > > Btw I am on the lates revision.
> > > > >
> > > > > -Rajith
> > > > >
> > > > > java:compile:
> > > > >     [echo] Comp

[Axis2] Fw: Dispatchers

[Brian De Pradine]

Should have added [Axis2] to the subject
originally.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?

- Forwarded by Brian
De Pradine/UK/IBM on 06/06/2006 13:40 -----

Brian De Pradine/UK/IBM wrote on 06/06/2006 11:02:12:

> Hello,
> 
> Does anyone know why the core/conf/axis2.xml file includes the 
> RequestURIBasedDispatcher and the SOAPActionBasedDispatcher in the

> Transport phase of the Inflow? This seems to contradict the phase

> descriptions in the section "Processing an Incoming SOAP Message"
of
> the Apache Axis2 Architecture Guide. It is also different from the

> InFaultFlow definition, in the same axis2.xml file, where the 
> RequestURIBasedDispatcher and the SOAPActionBasedDispatcher are 
> included in the Dispatch phase.
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319         Internal
246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?

Dispatchers

[Brian De Pradine]

Hello,

Does anyone know why the core/conf/axis2.xml
file includes the RequestURIBasedDispatcher and the SOAPActionBasedDispatcher
in the Transport phase of the Inflow? This seems to contradict the phase
descriptions in the section "Processing an Incoming SOAP Message"
of the Apache Axis2 Architecture Guide. It is also different from the InFaultFlow
definition, in the same axis2.xml file, where the RequestURIBasedDispatcher
and the SOAPActionBasedDispatcher are included in the Dispatch phase.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?

Re: [axis2] Hello

[Brian De Pradine]

Glad that's sorted out. My main interest
is to ensure that Axis2 has a complete implementation of the WS-Addressing
specs, both 2004/08 and 2005/08. From what I have seen, this has already
been done for the most part, and I may end up just submitting a few more
unit tests, and patches for any defects that I may find. For example, I
have already identified that none fault response messages always include
an addressing header similar to the following:

        urn:uuid:39C96FAC83790886C811489061932341

but, according to the WS-Addressing
2005/08 spec, this should be as follows:

        urn:uuid:39C96FAC83790886C811489061932341

I have already raised JIRA issue AXIS2-779
to cover this. I will also keep an eye out for any other JIRA issues that
I may be able to help with.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


Eran Chinthaka <[EMAIL PROTECTED]> wrote
on 29/05/2006 09:24:35:

> It should not be there, just removed that. Thanks for pointing that
out.
> 
> -- Chinthaka
> 
> Brian De Pradine wrote:
> > 
> > Hi Eran,
> > 
> > The module.xml file for the Addressing module contains the following
> > description,
> > 
> >     This is WS-Addressing implementation
on Axis2.
> > Currently we have implemented Submission version (2004/08) and
Proposed
> > Recommendation. This is not complete as far as the fault handling
is
> > concerned. But we are working on that. 
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > IBM Hursley
> > External  +44 (0) 1962 816319        
Internal 246319
> > 
> > If you can't find the time to do it right the first time, where
will you
> > find the time to do it again?
> > 
> > 
> > Eran Chinthaka <[EMAIL PROTECTED]> wrote on 28/05/2006
19:31:28:
> > 
> >> Hi Brian,
> >>
> >> First let me welcome u to the list :).
> >>
> >> Which module.xml is stating that ? We fixed most of the fault
handling
> >> stuff when we were doing WS-A interop and I don't think there
aren't
> >> much of work left there.
> >>
> >> But as Dims stated there are some issues we have which are
filed in
> >> JIRA. We really appreciate if you can help with them.
> >>
> >> Thanks,
> >> Chinthaka
> >>
> >> Brian De Pradine wrote:
> >> >
> >> > Hello everyone,
> >> >
> >> > My name is Brian, and I plan to do some work on Axis2.
I have spent that
> >> > past few weeks going through the code in order to find
my way around,
> >> > and I am now ready to get started. I was looking at
the Addressing
> >> > support, and I saw a comment in the module.xml file
that stated that the
> >> > fault handling for Addressing has not been done yet,
so I thought that I
> >> > might start there.
> >> >
> >> > Cheers
> >> >
> >> > Brian DePradine
> >> > Web Services Development
> >> > External  +44 (0) 1962 816319      
  Internal 246319
> >> >
> >> > If you can't find the time to do it right the first
time, where will you
> >> > find the time to do it again?
> >>
> >>
> >> [attachment "signature.asc" deleted by Brian De
Pradine/UK/IBM]
> 
> 
> [attachment "signature.asc" deleted by Brian De Pradine/UK/IBM]

Re: [axis2] Hello

[Brian De Pradine]

Hi Eran,

The module.xml file for the Addressing
module contains the following description,

    This
is WS-Addressing implementation on Axis2. Currently we have implemented
Submission version (2004/08) and Proposed Recommendation. This is not complete
as far as the fault handling is concerned. But we are working on that.


Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


Eran Chinthaka <[EMAIL PROTECTED]> wrote
on 28/05/2006 19:31:28:

> Hi Brian,
> 
> First let me welcome u to the list :).
> 
> Which module.xml is stating that ? We fixed most of the fault handling
> stuff when we were doing WS-A interop and I don't think there aren't
> much of work left there.
> 
> But as Dims stated there are some issues we have which are filed in
> JIRA. We really appreciate if you can help with them.
> 
> Thanks,
> Chinthaka
> 
> Brian De Pradine wrote:
> > 
> > Hello everyone,
> > 
> > My name is Brian, and I plan to do some work on Axis2. I have
spent that
> > past few weeks going through the code in order to find my way
around,
> > and I am now ready to get started. I was looking at the Addressing
> > support, and I saw a comment in the module.xml file that stated
that the
> > fault handling for Addressing has not been done yet, so I thought
that I
> > might start there.
> > 
> > Cheers
> > 
> > Brian DePradine
> > Web Services Development
> > External  +44 (0) 1962 816319        
Internal 246319
> > 
> > If you can't find the time to do it right the first time, where
will you
> > find the time to do it again?
> 
> 
> [attachment "signature.asc" deleted by Brian De Pradine/UK/IBM]

[axis2] Hello

[Brian De Pradine]

Hello everyone,

My name is Brian, and I plan to do some
work on Axis2. I have spent that past few weeks going through the code
in order to find my way around, and I am now ready to get started. I was
looking at the Addressing support, and I saw a comment in the module.xml
file that stated that the fault handling for Addressing has not been done
yet, so I thought that I might start there.

Cheers

Brian DePradine
Web Services Development
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?