[jira] [Commented] (RAMPART-385) Rampart does check username token password (via callback), even though "NoPassword" was specified in Security Policy

2012-09-13 Thread Simon Jongsma (JIRA) 

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

Simon Jongsma commented on RAMPART-385:
---

Thanks so far Suresh. I was not aware I could specify the WS-SecurityPolicy 
version to be used by Rampart.
Could you instruct me as to where I can specify this?

> Rampart does check username token password (via callback), even though 
> "NoPassword" was specified in Security Policy
> 
>
> Key: RAMPART-385
> URL: https://issues.apache.org/jira/browse/RAMPART-385
> Project: Rampart
>  Issue Type: Question
> Environment: JBoss 5.1.2 
> Axis2 1.6.2 
> Rampart/Rahas 1.6.2
>Reporter: Simon Jongsma
> Attachments: RAMPART-385.patch
>
>
> A Policy was specified on a web service as such:
>   
>   
>sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";>
>   
>
>   
>
>   
>   
> If the request contains username token + password in security header, I would 
> expect (hope) rampart to ignore 
> the password or complain that a password is present (i'm not sure about the 
> meaning of NoPassword in this respect).
> Anyway: rampart will go into the password callback and require us to supply 
> the value.
> Is this correct?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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] [Created] (AXIS2-5420) AXIS2 can't create custom exception from received fault message if a custom string definition exists at the WSDL

2012-09-13 Thread Andy Schmidt (JIRA) 
Andy Schmidt created AXIS2-5420:
---

 Summary: AXIS2 can't create custom exception from received fault 
message if a custom string definition exists at the WSDL
 Key: AXIS2-5420
 URL: https://issues.apache.org/jira/browse/AXIS2-5420
 Project: Axis2
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.6.2
Reporter: Andy Schmidt
Priority: Minor
 Fix For: 1.6.3


The .net implementation of the WCF framework delivered me following schema 
definitions in the wsdl file:

http://schemas.microsoft.com/2003/10/Serialization/";
xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/";>











The resulting problem on the side of AXIS2 is that AXIS2 is generating a String 
class definition from the XSD definition . If a custom fault is received AXIS2 creats 
a custom exception by using reflection and throws a error by invoking line:

java.lang.reflect.Constructor constructor = 
exceptionClass.getConstructor(String.class);

The misstake is that the String.class is resolved as the generated class 
definition from AXIS2 and not java.lang.String. So it will be better to use the 
full qualified name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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-5420) AXIS2 can't create custom exception from received fault message if a custom string definition exists at the WSDL

2012-09-13 Thread Andy Schmidt (JIRA) 

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

Andy Schmidt updated AXIS2-5420:


Attachment: InterfaceImplementationTemplate.xsl

I has been fixed this issue by replacing 'String.class' with 
'java.lang.String.class' in line 524 and 794.

java.lang.reflect.Constructor constructor = 
exceptionClass.getConstructor(java.lang.String.class);

> AXIS2 can't create custom exception from received fault message if a custom 
> string definition exists at the WSDL
> 
>
> Key: AXIS2-5420
> URL: https://issues.apache.org/jira/browse/AXIS2-5420
> Project: Axis2
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.6.2
>Reporter: Andy Schmidt
>Priority: Minor
> Fix For: 1.6.3
>
> Attachments: InterfaceImplementationTemplate.xsl
>
>
> The .net implementation of the WCF framework delivered me following schema 
> definitions in the wsdl file:
>  elementFormDefault="qualified"
> targetNamespace="http://schemas.microsoft.com/2003/10/Serialization/";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
> xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/";>
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> The resulting problem on the side of AXIS2 is that AXIS2 is generating a 
> String class definition from the XSD definition  nillable="true" type="xs:string" />. If a custom fault is received AXIS2 
> creats a custom exception by using reflection and throws a error by invoking 
> line:
> java.lang.reflect.Constructor constructor = 
> exceptionClass.getConstructor(String.class);
> The misstake is that the String.class is resolved as the generated class 
> definition from AXIS2 and not java.lang.String. So it will be better to use 
> the full qualified name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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] [Comment Edited] (AXIS2-5420) AXIS2 can't create custom exception from received fault message if a custom string definition exists at the WSDL

2012-09-13 Thread Andy Schmidt (JIRA) 

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

Andy Schmidt edited comment on AXIS2-5420 at 9/13/12 11:40 PM:
---

I has been fixed this issue by replacing 'String.class' with 
'java.lang.String.class' in line 524 and 794.

java.lang.reflect.Constructor constructor = 
exceptionClass.getConstructor(java.lang.String.class);

You can take a look at the attachted file and merge it to your source code. I 
can't check in.

  was (Author: glance):
I has been fixed this issue by replacing 'String.class' with 
'java.lang.String.class' in line 524 and 794.

java.lang.reflect.Constructor constructor = 
exceptionClass.getConstructor(java.lang.String.class);
  
> AXIS2 can't create custom exception from received fault message if a custom 
> string definition exists at the WSDL
> 
>
> Key: AXIS2-5420
> URL: https://issues.apache.org/jira/browse/AXIS2-5420
> Project: Axis2
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.6.2
>Reporter: Andy Schmidt
>Priority: Minor
> Fix For: 1.6.3
>
> Attachments: InterfaceImplementationTemplate.xsl
>
>
> The .net implementation of the WCF framework delivered me following schema 
> definitions in the wsdl file:
>  elementFormDefault="qualified"
> targetNamespace="http://schemas.microsoft.com/2003/10/Serialization/";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
> xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/";>
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> The resulting problem on the side of AXIS2 is that AXIS2 is generating a 
> String class definition from the XSD definition  nillable="true" type="xs:string" />. If a custom fault is received AXIS2 
> creats a custom exception by using reflection and throws a error by invoking 
> line:
> java.lang.reflect.Constructor constructor = 
> exceptionClass.getConstructor(String.class);
> The misstake is that the String.class is resolved as the generated class 
> definition from AXIS2 and not java.lang.String. So it will be better to use 
> the full qualified name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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] [Created] (AXIS2-5421) Axis2 Can't find ServletConfigParameter

2012-09-13 Thread Moe Jalali (JIRA) 
Moe Jalali created AXIS2-5421:
-

 Summary: Axis2 Can't find ServletConfigParameter
 Key: AXIS2-5421
 URL: https://issues.apache.org/jira/browse/AXIS2-5421
 Project: Axis2
  Issue Type: Bug
  Components: Addressing, deployment, wsdl
Affects Versions: 1.4
 Environment: Weblogic 12.1 , spring
Reporter: Moe Jalali


I am migrating a web service to WebLogic 12.1 from WebSphere. I am getting the 
error: 
Axis2 Can't find ServletConfigParameter 
which causes
DeploymentException: The following error occurred during schema generation: null

I am using 1xis2 1.4 and spring. I have implemented the recommendations on the 
site
http://axis.apache.org/axis2/java/core/docs/spring.html
to resolve weblogic and axis2 jar conflicts. Addressing and Rampart modules 
engage okay. Error happens when making this call from the client

ConfigurationContextFactory.createConfigurationContextFromFileSystem("c:EdlService.ear/EdlService/WEB-INF","c:/EdlService.ear/EdlService/WEB-INF/conf/axis2.xml");


2012-09-13 12:58:46,112 ERROR org.apache.axis2.deployment.ServiceDeployer - The 
EdlService service, which is not valid, caused The following error occurred 
during schema generation: null
org.apache.axis2.deployment.DeploymentException: The following error occurred 
during schema generation: null
at 
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:110)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:179)
at 
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:81)
at 
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:597)
at 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330)
at 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227)
at 
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:131)
at 
org.apache.axis2.deployment.FileSystemConfigurator.loadServices(FileSystemConfigurator.java:147)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:82)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184)
at 
cbp.pspo.tm.edl.ws.externalWSClientStub.CbsaEdlService.createServiceStub(CbsaEdlService.java:109)
at 
cbp.pspo.tm.edl.ws.externalWSClientStub.CbsaEdlService.init(CbsaEdlService.java:96)

CAUSED BY:

Caused by: org.apache.axis2.AxisFault: Axis2 Can't find ServletConfigParameter
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at 
org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier.getServiceObject(SpringServletContextObjectSupplier.java:86)
... 127 more


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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] (AXIS2-5420) AXIS2 can't create custom exception from received fault message if a custom string definition exists at the WSDL

2012-09-13 Thread Hudson (JIRA) 

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

Hudson commented on AXIS2-5420:
---

Integrated in axis2-1.6 #319 (See 
[https://builds.apache.org/job/axis2-1.6/319/])
AXIS2-5420: Merged r1384482 to the 1.6 branch. (Revision 1384483)

 Result = FAILURE
veithen : 
Files : 
* /axis/axis2/java/core/branches/1_6
* 
/axis/axis2/java/core/branches/1_6/modules/codegen/src/org/apache/axis2/wsdl/template/java/InterfaceImplementationTemplate.xsl
* /axis/axis2/java/core/branches/1_6/modules/saaj


> AXIS2 can't create custom exception from received fault message if a custom 
> string definition exists at the WSDL
> 
>
> Key: AXIS2-5420
> URL: https://issues.apache.org/jira/browse/AXIS2-5420
> Project: Axis2
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.6.2
>Reporter: Andy Schmidt
>Priority: Minor
> Fix For: 1.6.3
>
> Attachments: InterfaceImplementationTemplate.xsl
>
>
> The .net implementation of the WCF framework delivered me following schema 
> definitions in the wsdl file:
>  elementFormDefault="qualified"
> targetNamespace="http://schemas.microsoft.com/2003/10/Serialization/";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
> xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/";>
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> The resulting problem on the side of AXIS2 is that AXIS2 is generating a 
> String class definition from the XSD definition  nillable="true" type="xs:string" />. If a custom fault is received AXIS2 
> creats a custom exception by using reflection and throws a error by invoking 
> line:
> java.lang.reflect.Constructor constructor = 
> exceptionClass.getConstructor(String.class);
> The misstake is that the String.class is resolved as the generated class 
> definition from AXIS2 and not java.lang.String. So it will be better to use 
> the full qualified name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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

Build failed in Jenkins: axis2-1.6 #319

2012-09-13 Thread Apache Jenkins Server 
See 

Changes:

[veithen] AXIS2-5420: Merged r1384482 to the 1.6 branch.

--
[...truncated 6093 lines...]
14K downloaded  (maven-parent-5.pom)
Downloading: http://repo1.maven.org/maven2/org/apache/apache/3/apache-3.pom
3K downloaded  (apache-3.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-settings/2.0.7/maven-settings-2.0.7.pom
1K downloaded  (maven-settings-2.0.7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-model/2.0.7/maven-model-2.0.7.pom
2K downloaded  (maven-model-2.0.7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.4.1/plexus-utils-1.4.1.pom
1K downloaded  (plexus-utils-1.4.1.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.11/plexus-1.0.11.pom
8K downloaded  (plexus-1.0.11.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-9-stable-1/plexus-container-default-1.0-alpha-9-stable-1.pom
3K downloaded  (plexus-container-default-1.0-alpha-9-stable-1.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-containers/1.0.3/plexus-containers-1.0.3.pom
492b downloaded  (plexus-containers-1.0.3.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom
5K downloaded  (plexus-1.0.4.pom)
Downloading: http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom
998b downloaded  (junit-3.8.1.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils-1.0.4.pom
6K downloaded  (plexus-utils-1.0.4.pom)
Downloading: 
http://repo1.maven.org/maven2/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.pom
3K downloaded  (classworlds-1.1-alpha-2.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-profile/2.0.7/maven-profile-2.0.7.pom
1K downloaded  (maven-profile-2.0.7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-artifact-manager/2.0.7/maven-artifact-manager-2.0.7.pom
2K downloaded  (maven-artifact-manager-2.0.7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-repository-metadata/2.0.7/maven-repository-metadata-2.0.7.pom
1K downloaded  (maven-repository-metadata-2.0.7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-artifact/2.0.7/maven-artifact-2.0.7.pom
1K downloaded  (maven-artifact-2.0.7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-beta-2/wagon-provider-api-1.0-beta-2.pom
680b downloaded  (wagon-provider-api-1.0-beta-2.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon/1.0-beta-2/wagon-1.0-beta-2.pom
5K downloaded  (wagon-1.0-beta-2.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-parent/4/maven-parent-4.pom
9K downloaded  (maven-parent-4.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-registry/2.0.7/maven-plugin-registry-2.0.7.pom
1K downloaded  (maven-plugin-registry-2.0.7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-api/2.0.7/maven-plugin-api-2.0.7.pom
1K downloaded  (maven-plugin-api-2.0.7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-archiver/2.2/maven-archiver-2.2.pom
1K downloaded  (maven-archiver-2.2.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/shared/maven-shared-components/3/maven-shared-components-3.pom
1K downloaded  (maven-shared-components-3.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-project/2.0/maven-project-2.0.pom
1K downloaded  (maven-project-2.0.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven/2.0/maven-2.0.pom
8K downloaded  (maven-2.0.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.pom
1K downloaded  (plexus-archiver-1.0-alpha-7.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.6/plexus-components-1.1.6.pom
1K downloaded  (plexus-components-1.1.6.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.8/plexus-1.0.8.pom
7K downloaded  (plexus-1.0.8.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.2/plexus-utils-1.2.pom
767b downloaded  (plexus-utils-1.2.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.5/plexus-1.0.5.pom
5K downloaded  (plexus-1.0.5.pom)
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/plexus-container-default-1.0-alpha-8.pom
7K downloaded  (plexus-container-default-1.0-alpha-8.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
723b downloaded  (maven-artifact-2.0.pom)
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/shared/maven-dependen

[jira] [Commented] (AXIS2-5420) AXIS2 can't create custom exception from received fault message if a custom string definition exists at the WSDL

2012-09-13 Thread Hudson (JIRA) 

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

Hudson commented on AXIS2-5420:
---

Integrated in Axis2 #1774 (See [https://builds.apache.org/job/Axis2/1774/])
AXIS2-5420: Applied patch provided by Andy Schmidt. (Revision 1384482)

 Result = SUCCESS
veithen : 
Files : 
* 
/axis/axis2/java/core/trunk/modules/codegen/src/org/apache/axis2/wsdl/template/java/InterfaceImplementationTemplate.xsl


> AXIS2 can't create custom exception from received fault message if a custom 
> string definition exists at the WSDL
> 
>
> Key: AXIS2-5420
> URL: https://issues.apache.org/jira/browse/AXIS2-5420
> Project: Axis2
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.6.2
>Reporter: Andy Schmidt
>Priority: Minor
> Fix For: 1.6.3
>
> Attachments: InterfaceImplementationTemplate.xsl
>
>
> The .net implementation of the WCF framework delivered me following schema 
> definitions in the wsdl file:
>  elementFormDefault="qualified"
> targetNamespace="http://schemas.microsoft.com/2003/10/Serialization/";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
> xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/";>
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> The resulting problem on the side of AXIS2 is that AXIS2 is generating a 
> String class definition from the XSD definition  nillable="true" type="xs:string" />. If a custom fault is received AXIS2 
> creats a custom exception by using reflection and throws a error by invoking 
> line:
> java.lang.reflect.Constructor constructor = 
> exceptionClass.getConstructor(String.class);
> The misstake is that the String.class is resolved as the generated class 
> definition from AXIS2 and not java.lang.String. So it will be better to use 
> the full qualified name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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] [Resolved] (AXIS2-5420) AXIS2 can't create custom exception from received fault message if a custom string definition exists at the WSDL

2012-09-13 Thread Andreas Veithen (JIRA) 

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

Andreas Veithen resolved AXIS2-5420.


   Resolution: Fixed
Fix Version/s: 1.7.0
 Assignee: Andreas Veithen

> AXIS2 can't create custom exception from received fault message if a custom 
> string definition exists at the WSDL
> 
>
> Key: AXIS2-5420
> URL: https://issues.apache.org/jira/browse/AXIS2-5420
> Project: Axis2
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.6.2
>Reporter: Andy Schmidt
>Assignee: Andreas Veithen
>Priority: Minor
> Fix For: 1.7.0, 1.6.3
>
> Attachments: InterfaceImplementationTemplate.xsl
>
>
> The .net implementation of the WCF framework delivered me following schema 
> definitions in the wsdl file:
>  elementFormDefault="qualified"
> targetNamespace="http://schemas.microsoft.com/2003/10/Serialization/";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
> xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/";>
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> The resulting problem on the side of AXIS2 is that AXIS2 is generating a 
> String class definition from the XSD definition  nillable="true" type="xs:string" />. If a custom fault is received AXIS2 
> creats a custom exception by using reflection and throws a error by invoking 
> line:
> java.lang.reflect.Constructor constructor = 
> exceptionClass.getConstructor(String.class);
> The misstake is that the String.class is resolved as the generated class 
> definition from AXIS2 and not java.lang.String. So it will be better to use 
> the full qualified name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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