[jira] [Created] (AXIS2-5391) AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny

2012-08-16 Thread lakmali erandi baminiwatta (JIRA) 
lakmali erandi baminiwatta created AXIS2-5391:
-

 Summary: AxisService2WSDL20 fails to return the WSDL 2.0 styles 
when the schema has a ComplexElement with XmlSchemaAny
 Key: AXIS2-5391
 URL: https://issues.apache.org/jira/browse/AXIS2-5391
 Project: Axis2
  Issue Type: Bug
Affects Versions: 1.6.1
Reporter: lakmali erandi baminiwatta


When the outmessage has a schema element as below,


   
 
   
 
   


 and when AxisService2WSDL20 checkStyle has got invoked, the following 
exception is thrown for  

Caused by: java.lang.ClassCastException: 
org.apache.ws.commons.schema.XmlSchemaAny cannot be cast to 
org.apache.ws.commons.schema.XmlSchemaElement
at 
org.apache.axis2.description.AxisService2WSDL20.checkStyle(AxisService2WSDL20.java:711)
at 
org.apache.axis2.description.AxisService2WSDL20.generateInterfaceOperationElement(AxisService2WSDL20.java:502).


at 
org.apache.axis2.description.AxisService2WSDL20.getInterfaceElement(AxisService2WSDL20.java:421)
at 
org.apache.axis2.description.AxisService2WSDL20.generateOM(AxisService2WSDL20.java:223)
at 
org.apache.axis2.description.AxisService.printWSDL2(AxisService.java:1785)



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[AXIS2]Transport setting http response satus not working

2012-08-16 Thread Senthivel, Baskaran 
Hello,



I'd like the ability to to change the response status based on our functional 
requirement for implementing CMIS 1.0 specification



For example : I'd like to send in certain cases an http 503 (instead of a 500) 
when a soap fault occurs.



HttpServletResponse resp =  (HttpServletResponse)   
msgContext.getCurrentMessageContext().getProperty(org.apache.axis2.transport.http.HT
 TPConstants.MC_HTTP_SERVLETRESPONSE);

if (resp != null) {

resp.setStatus(503 );

  }




We use Axis2 1.6.2 version.





Kind regards



Baskaran

[jira] [Updated] (AXIS2-5391) AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny

2012-08-16 Thread lakmali erandi baminiwatta (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AXIS2-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

lakmali erandi baminiwatta updated AXIS2-5391:
--

Attachment: AXIS2-5391.diff

Attached the patch (created for axis2-trunk) which fixes the issue.

> AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a 
> ComplexElement with XmlSchemaAny
> -
>
> Key: AXIS2-5391
> URL: https://issues.apache.org/jira/browse/AXIS2-5391
> Project: Axis2
>  Issue Type: Bug
>Affects Versions: 1.6.1
>Reporter: lakmali erandi baminiwatta
> Attachments: AXIS2-5391.diff
>
>
> When the outmessage has a schema element as below,
> 
>
>  
>
>  
>
> 
>  and when AxisService2WSDL20 checkStyle has got invoked, the following 
> exception is thrown for  
> Caused by: java.lang.ClassCastException: 
> org.apache.ws.commons.schema.XmlSchemaAny cannot be cast to 
> org.apache.ws.commons.schema.XmlSchemaElement
>   at 
> org.apache.axis2.description.AxisService2WSDL20.checkStyle(AxisService2WSDL20.java:711)
>   at 
> org.apache.axis2.description.AxisService2WSDL20.generateInterfaceOperationElement(AxisService2WSDL20.java:502).
>   at 
> org.apache.axis2.description.AxisService2WSDL20.getInterfaceElement(AxisService2WSDL20.java:421)
>   at 
> org.apache.axis2.description.AxisService2WSDL20.generateOM(AxisService2WSDL20.java:223)
>   at 
> org.apache.axis2.description.AxisService.printWSDL2(AxisService.java:1785)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

RE: [jira] [Created] (AXIS2-5391) AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny

2012-08-16 Thread Martin Gainty 

package org.apache.axis2.description
public class AxisService2WSDL20 implements WSDL2Constants
.
  private URI [] checkStyle(AxisOperation axisOperation) throws 
URISyntaxException, AxisFault {

  Object next = iterator.next();
if (!(next instanceof XmlSchemaElement)) {
isRPC = false;
}
//the next instanceof XmlSchema is missing 
//if ((next instanceof XmlSchemaElement)) {
XmlSchemaElement innerElement = 
(XmlSchemaElement) next;

Martin 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.


> Date: Thu, 16 Aug 2012 19:06:37 +1100
> From: j...@apache.org
> To: java-dev@axis.apache.org
> Subject: [jira] [Created] (AXIS2-5391) AxisService2WSDL20 fails to return the 
> WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny
> 
> lakmali erandi baminiwatta created AXIS2-5391:
> -
> 
>  Summary: AxisService2WSDL20 fails to return the WSDL 2.0 styles 
> when the schema has a ComplexElement with XmlSchemaAny
>  Key: AXIS2-5391
>  URL: https://issues.apache.org/jira/browse/AXIS2-5391
>  Project: Axis2
>   Issue Type: Bug
> Affects Versions: 1.6.1
> Reporter: lakmali erandi baminiwatta
> 
> 
> When the outmessage has a schema element as below,
> 
> 
>
>  
>
>  
>
> 
> 
>  and when AxisService2WSDL20 checkStyle has got invoked, the following 
> exception is thrown for  
> 
> Caused by: java.lang.ClassCastException: 
> org.apache.ws.commons.schema.XmlSchemaAny cannot be cast to 
> org.apache.ws.commons.schema.XmlSchemaElement
>   at 
> org.apache.axis2.description.AxisService2WSDL20.checkStyle(AxisService2WSDL20.java:711)
>   at 
> org.apache.axis2.description.AxisService2WSDL20.generateInterfaceOperationElement(AxisService2WSDL20.java:502).
> 
> 
>   at 
> org.apache.axis2.description.AxisService2WSDL20.getInterfaceElement(AxisService2WSDL20.java:421)
>   at 
> org.apache.axis2.description.AxisService2WSDL20.generateOM(AxisService2WSDL20.java:223)
>   at 
> org.apache.axis2.description.AxisService.printWSDL2(AxisService.java:1785)
> 
> 
> 
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA 
> administrators: 
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
> 
> 
> -
> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>

[jira] [Commented] (RAMPART-261) Ability to Toggle "mustUnderstand" flag in security header.

2012-08-16 Thread Enda Diggins (JIRA) 

[ 
https://issues.apache.org/jira/browse/RAMPART-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436079#comment-13436079
 ] 

Enda Diggins commented on RAMPART-261:
--

I also had this problem; resolved by patching Rampart with something similar to 
this feature request. I added a boolean field 'mustUnderstandSecurityHeader' to 
RampartConfig. Perhaps someone can suggest a better place for this? I'm happy 
to provide the patch if RampartConfig's the right place.

> Ability to Toggle "mustUnderstand" flag in security header.
> ---
>
> Key: RAMPART-261
> URL: https://issues.apache.org/jira/browse/RAMPART-261
> Project: Rampart
>  Issue Type: New Feature
>  Components: rampart-core
>Affects Versions: 1.4
>Reporter: Earl D. Baugh Jr.
>Priority: Minor
>
> In dealing with a major telcom, I discovered that it's not possible to turn 
> off the mustUnderstand security header attribute.
> This causes issues in that ALL of their web services run thru a "proxy" which 
> understands security, but their back end services do NOT.
> Because of this, all messages that are sent to them must either not have the 
> mustUnderstand attribute, or have it set to "0" or "false", or they simply 
> fail with security violations.   I've checked to see if actor/next would 
> solve the problem, but the only way to get calls to work is to allow for this 
> to be disabled.
> I've inquired to them about changing this behavior, and they have no plans 
> nor intentions (from what I've been able to ascertain) of changing their 
> architecture and moving to something that either strips off the security 
> headers or can properly handle this setting.   Additionally their responses 
> do not have a SOAP header.  That, thankfully I can currently handle with the 
> axis2 ability to set KEY_RAMPART_OUT_POLICY.   They apparently have numerous 
> clients who can handle this, but I was not able to get any info as to what 
> technology they're using.  (the previous version here at my employer had a 
> "very" customized / hacked set of axis1 code that added and monkeyed with 
> various attributes).  
> Since  RAMPART does not get the options from Axis2  to handle the setting of  
> ServiceClient options setProperty( WSDL2Constants.ATTRIBUTE_MUST_UNDERSTAND, 
> "0" ), and can't be configured with the existing flow to sign but not set 
> this value, I've been stuck.
> (signing causes a hard coded "true" to be set for this attribute)
> I would like to suggest / recommend adding some form of option to allow for 
> signing, but not require the mustUnderstand attribute to be set.
> I have made a change to my local code and have a solution that works.  
> In RampartMessageData.java, after line 358 :   if(this.sender && 
> this.policyData != null) {
> a check that would call : secHeader.setMustUnderstand(false)  
> when the option is set would solve this problem, and allow per call control 
> of this behavior.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

2012-08-16 Thread Sven Strohschein (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sven Strohschein updated AXIS2-5379:


Priority: Blocker  (was: Critical)

> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.org/jira/browse/AXIS2-5379
> Project: Axis2
>  Issue Type: Bug
>  Components: wsdl
>Affects Versions: 1.6.2
>Reporter: Sven Strohschein
>Priority: Blocker
> Attachments: hello-rest.wsdl, HelloWebServiceREST.java, services.xml
>
>
> I have developed a simple "hello world" REST web service with WSDL 2.0 and 
> Axis2.
> There are three URL parameters defined, but the third URL parameter can not 
> be processed (ADBException regarding unexpected element). The first two 
> parameters are processed correctly.
> I could not get an answer via the axis2 mailing list regarding this problem ( 
> http://mail-archives.apache.org/mod_mbox/axis-java-user/201207.mbox/%3C500F0ADF.1050108%40gmx.de%3E
>  ), could not find any examples, tutorials or documentation for a REST web 
> service with WSDL 2.0 and more than two parameters.
> The full example code, wsdl, etc. is attached to this issue.
> URL calls
> http://localhost:8080/services/helloWebServiceREST/getHello?input=test -> 
> working
> http://localhost:8080/services/helloWebServiceREST/getHello?input=test&second=test2
>  -> working
> http://localhost:8080/services/helloWebServiceREST/getHello?input=test&second=test2&third=test3
>  -> not working ("org.apache.axis2.databinding.ADBException: Unexpected 
> subelement second")
> http://localhost:8080/services/helloWebServiceREST/getHello?input=test&third=test3
>  -> not working ("org.apache.axis2.databinding.ADBException: Unexpected 
> subelement input")
> Request element
> 
>   
> 
>type="xsd:string"/>
>type="xsd:string"/>
>type="xsd:string"/>
> 
>   
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Fwd: Mandatory svnpubsub migration by Jan 2013

2012-08-16 Thread Andreas Veithen 
FYI: As required by the mail below, I've requested migration to
svnpubsub for the Axis sites; see INFRA-5152. In practice, there are
only two things that change for release managers:

1. The locations of the generated sites in SVN have changed: they are
now all under https://svn.apache.org/repos/asf/axis/site/ and map
1-to-1 to the URLs on the live Web site.
2. All changes to the sites in SVN will be published immediately to
the live Web sites. That means that you no longer need to do an "svn
update" on people.apache.org.

Andreas

PS: I still need to figure out the part about using svnpubsub for distributions.

-- Forwarded message --
From: Joe Schaefer 
Date: Wed, Feb 8, 2012 at 1:26 PM
Subject: Mandatory svnpubsub migration by Jan 2013
To: Apache Infrastructure 


[PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER
INQUIRIES TO infrastruct...@apache.org]

FYI: infrastructure policy regarding website hosting has
changed as of November 2011: we are requiring all websites
and dist/ dirs to be svnpubsub or ASF CMS backed by the end of 2012.
If your PMC has already met this requirement congratulations,
you can ignore the remainder of this post.

As stated on http://www.apache.org/dev/project-site.html#svnpubsub
we are migrating our webserver infrastructure to 100% svnpubsub
over the course of 2012.  If your site does not currently make
use of this technology, it is time to consider a migration effort,
as rsync-based sites will be PERMANENTLY FROZEN in Jan 2013 due

to infra disabling the hourly rsync jobs.  While we recommend
migrating to the ASF CMS [0] for Anakia based or Confluence based
sites, and have provided tooling [1] to help facilitate this,
we are only mandating svnpubsub (which the CMS uses itself).

svnpubsub is a client-server system whereby a client watches an
svn working copy for relevant commit notifications from the svn
server.  It subsequently runs svn up on the working copy, bringing
in the relevant changes.  sites that use static build technologies
that commit the build results to svn are naturally compatible with
svnpubsub; simply file a JIRA ticket with INFRA to request a
migration: any commits to the resulting build tree will be

instantly picked up on the live site.


The CMS is a more elaborate system based on svnpubsub which
provides a webgui for convenient online editing.  Dozens of
sites have already successfully deployed using the CMS and
are quite happy with the results.  The system is sufficiently
flexible to accommodate a wide variety of choices regarding
templating systems and storage formats, but most sites have
standardized on the combination of Django and Markdown.  Talk
to infra if you would like to use the CMS in this or some other
fashion, we'll see what we can do.


NOTE: the policy for dist/ dirs for managing project releases is
similar.  We have setup a dedicated svn server for handling this,
please contact infra when you are ready to start using it.


HTH


[0]: http://www.apache.org/dev/cms
[1]: https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Build failed in Jenkins: axis2-transports-trunk #982

2012-08-16 Thread Apache Jenkins Server 
See 

Changes:

[veithen] Removed unnecessary repositories.

--
[...truncated 428 lines...]
Aug 16, 2012 9:09:48 PM org.apache.axis2.transport.base.AbstractTransportSender 
init
INFO: TCP Sender started
http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2005/08/addressing";>urn:echoOMElementResponseurn:uuid:6d560e31-fc9d-465d-9d45-c059535dd9dehttp://localhost/my";>Isaac Asimov, The Foundation 
TrilogyAug
 16, 2012 9:09:49 PM org.apache.axis2.transport.base.AbstractTransportListener 
stop
INFO: TCP Listener Shutdown
Aug 16, 2012 9:09:49 PM org.apache.axis2.transport.tcp.TCPServer stopServer
INFO: TCP server stopped on port : 
Server stopped 
.
Aug 16, 2012 9:09:49 PM org.apache.axis2.deployment.AxisConfigBuilder 
processDeployers
WARNING: Unable to instantiate deployer 
org.apache.axis2.deployment.ServiceDeployer; see debug logs for more details
Aug 16, 2012 9:09:49 PM org.apache.axis2.deployment.DeploymentEngine 
prepareRepository
INFO: No services directory was found under 

Aug 16, 2012 9:09:49 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing - 

Aug 16, 2012 9:09:49 PM org.apache.axis2.transport.base.AbstractTransportSender 
init
INFO: TCP Sender started
Aug 16, 2012 9:09:50 PM 
org.apache.axis2.transport.base.AbstractTransportListener start
INFO: TCP listener started
Aug 16, 2012 9:09:50 PM org.apache.axis2.transport.tcp.TCPServer startServer
INFO: TCP server started on port : 
Aug 16, 2012 9:09:50 PM org.apache.axis2.deployment.AxisConfigBuilder 
processDeployers
WARNING: Unable to instantiate deployer 
org.apache.axis2.deployment.ServiceDeployer; see debug logs for more details
Aug 16, 2012 9:09:50 PM org.apache.axis2.deployment.DeploymentEngine 
prepareRepository
INFO: No services directory was found under 

Aug 16, 2012 9:09:50 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing - 

Aug 16, 2012 9:09:50 PM org.apache.axis2.transport.base.AbstractTransportSender 
init
INFO: TCP Sender started
http://localhost/my";>Isaac 
Asimov, The Foundation TrilogyAug 16, 
2012 9:09:50 PM org.apache.axis2.transport.base.AbstractTransportListener stop
INFO: TCP Listener Shutdown
Aug 16, 2012 9:09:50 PM org.apache.axis2.transport.tcp.TCPServer stopServer
INFO: TCP server stopped on port : 
Server stopped 
.
Aug 16, 2012 9:09:50 PM org.apache.axis2.deployment.AxisConfigBuilder 
processDeployers
WARNING: Unable to instantiate deployer 
org.apache.axis2.deployment.ServiceDeployer; see debug logs for more details
Aug 16, 2012 9:09:50 PM org.apache.axis2.deployment.DeploymentEngine 
prepareRepository
INFO: No services directory was found under 

Aug 16, 2012 9:09:50 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing - 

Aug 16, 2012 9:09:50 PM org.apache.axis2.transport.base.AbstractTransportSender 
init
INFO: TCP Sender started
Aug 16, 2012 9:09:51 PM 
org.apache.axis2.transport.base.AbstractTransportListener start
INFO: TCP listener started
Aug 16, 2012 9:09:51 PM org.apache.axis2.transport.tcp.TCPServer startServer
INFO: TCP server started on port : 
Aug 16, 2012 9:09:51 PM org.apache.axis2.deployment.AxisConfigBuilder 
processDeployers
WARNING: Unable to instantiate deployer 
org.apache.axis2.deployment.ServiceDeployer; see debug logs for more details
Aug 16, 2012 9:09:51 PM org.apache.axis2.deployment.DeploymentEngine 
prepareRepository
INFO: No services directory was found under 

Aug 16, 2012 9:09:51 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing - 

Aug 16, 2012 9:09:51 PM org.apache.axis2.transport.base.AbstractTransportSender 
init
INFO: TCP Sender

Jenkins build is back to normal : axis2-transports-trunk #983

2012-08-16 Thread Apache Jenkins Server 
See 


-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org