[jira] Created: (AXIS2-4301) jsps are duplicated in webapp\axis2-web of the binary distribution

[Charitha Kankanamge (JIRA)]

jsps are duplicated in webapp\axis2-web of the binary distribution
--

 Key: AXIS2-4301
 URL: https://issues.apache.org/jira/browse/AXIS2-4301
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
 Environment: Axis2-1.5-SNAPSHOT
Reporter: Charitha Kankanamge
Assignee: Amila Chinthaka Suriarachchi
 Fix For: 1.5


There are duplicate jsps included in the webapp\axis2-web directory of the 
binary distribution zip. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: How to manage web service in axis

[Charitha Kankanamge]

Hi,
WSO2 Web Services Application Server (Which is built on Apache Axis2)
provides a lot of web service management facilities such as service
activation/inactivation, request/response statistics, message tracing,
monitoring etc..
You can download the latest version from [1] and have a look.

[1]http://wso2.org/projects/wsas/java

Regards
Charitha

http://charithaka.blogspot.com

sara wrote:

> Hi,
> Does anyone knows how to manage web service, such as start, stop web
> service, and get metric information about web service in axis? or how
> to extend axis to provide these functions?
> Any advice is appreciated.
> Thanks.
> 2009-02-17
> 
> sara

[jira] Updated: (AXIS2-4156) ?wsdl returns an AxisFault if the port address of the wsdl is blank and modifyUserWSDLPortAddress set to true in services.xml

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-4156:
---

Attachment: calculatorService.aar

Attached service archive

> ?wsdl returns an AxisFault if the port address of the wsdl is blank and 
> modifyUserWSDLPortAddress set to true in services.xml
> -
>
> Key: AXIS2-4156
> URL: https://issues.apache.org/jira/browse/AXIS2-4156
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: wsdl
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
> Attachments: calculatorService.aar
>
>
> Please deploy the attached service in axis2 and issue ?wsdl. You will get the 
> following exception.
> org.apache.axis2.AxisFault: invalid epr is given epr ==>
> at 
> org.apache.axis2.description.AxisService.getLocationURI(AxisService.java:1446)
> at 
> org.apache.axis2.description.AxisService.setPortAddress(AxisService.java:1372)
> at 
> org.apache.axis2.description.AxisService.printDefinitionObject(AxisService.java:1045)
> at 
> org.apache.axis2.description.AxisService.printUserWSDL(AxisService.java:1066)
> at 
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1314)
> at 
> org.wso2.carbon.core.transports.util.Wsdl11Processor$1.printWSDL(Wsdl11Processor.java:43)
> at 
> org.wso2.carbon.core.transports.util.AbstractWsdlProcessor.printWSDL(AbstractWsdlProcessor.java:51)
> at 
> org.wso2.carbon.core.transports.util.Wsdl11Processor.process(Wsdl11Processor.java:57)
> at 
> org.wso2.carbon.core.transports.CarbonServlet.doGet(CarbonServlet.java:129)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
> at 
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
> at 
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:116)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
> at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
> at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
> at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
> at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
> at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
> at java.lang.Thread.run(Thread.java:595)
> This occurs if the service archive includes a wsdl and the wsdl has blank 
> endpoint address. And the services.xml has following parameters.
>  true
> true

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-4156) ?wsdl returns an AxisFault if the port address of the wsdl is blank and modifyUserWSDLPortAddress set to true in services.xml

[Charitha Kankanamge (JIRA)]

?wsdl returns an AxisFault if the port address of the wsdl is blank and 
modifyUserWSDLPortAddress set to true in services.xml
-

 Key: AXIS2-4156
 URL: https://issues.apache.org/jira/browse/AXIS2-4156
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge


Please deploy the attached service in axis2 and issue ?wsdl. You will get the 
following exception.

org.apache.axis2.AxisFault: invalid epr is given epr ==>
at 
org.apache.axis2.description.AxisService.getLocationURI(AxisService.java:1446)
at 
org.apache.axis2.description.AxisService.setPortAddress(AxisService.java:1372)
at 
org.apache.axis2.description.AxisService.printDefinitionObject(AxisService.java:1045)
at 
org.apache.axis2.description.AxisService.printUserWSDL(AxisService.java:1066)
at 
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1314)
at 
org.wso2.carbon.core.transports.util.Wsdl11Processor$1.printWSDL(Wsdl11Processor.java:43)
at 
org.wso2.carbon.core.transports.util.AbstractWsdlProcessor.printWSDL(AbstractWsdlProcessor.java:51)
at 
org.wso2.carbon.core.transports.util.Wsdl11Processor.process(Wsdl11Processor.java:57)
at 
org.wso2.carbon.core.transports.CarbonServlet.doGet(CarbonServlet.java:129)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at 
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at 
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
at 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:595)

This occurs if the service archive includes a wsdl and the wsdl has blank 
endpoint address. And the services.xml has following parameters.

 true
true


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-4150) Message level policies are not added to wsdl2

[Charitha Kankanamge (JIRA)]

Message level policies are not added to wsdl2
-

 Key: AXIS2-4150
 URL: https://issues.apache.org/jira/browse/AXIS2-4150
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.4.1
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Keith Godwin Chapman
Priority: Critical


I have a service with a message level policy defined in its wsdl as follows. 








However this message level policy is not added to the ?wsdl2 of the service

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Resolved: (AXIS2-4102) Typo in AxisServlet init-params

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge resolved AXIS2-4102.


   Resolution: Fixed
Fix Version/s: nightly
 Assignee: Charitha Kankanamge

Fixed in revision 708750 of trunk. Thanks Luis for reporting the bug.

> Typo in AxisServlet init-params
> ---
>
> Key: AXIS2-4102
> URL: https://issues.apache.org/jira/browse/AXIS2-4102
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.4.1
>Reporter: Luis Parravicini
>    Assignee: Charitha Kankanamge
>Priority: Trivial
> Fix For: nightly
>
>
> In webapp/WEB-INF/web.xml of the binary distribution, AxisServlet params 
> axis2.xml.url and axis2.repository.url have as value a hostname localhot 
> instead of localhost.
> The init params are commented and I think they are supplied only as examples 
> but a typo nonetheless.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Error Validating Axis2 Installation

[charitha kankanamge]

blakep wrote:


Hello all! I have been tasked with getting a web service up and running and
chose to use Apache Axis. 


Here is my current setup:
Apache Axis2 1.3 (have also tried 1.4)
Tomcat 5.5.17
Win XP with latest service pack

I installed the Axis war and all the initial links work except for Validate.
When I try to launch HappyAxis.jsp to verify installation of Axis2 I get a
NumberFormatException. I was initally getting a servlet error on startup but
took out the servlet-api-2.3.jar that was in the axis2/web-inf/lib folder.
Guess it was just conflicting with the Tomcat containers servlet-api.jar.

Here is a snippet from startup and then the exception:
...
Sep 16,2008 11:27:34 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive axis2.war
[INFO] default: init
[INFO] AxisServlet: init
[INFO] Deploying module: addressing-1.3
[INFO] Deploying module: script-1.3
[INFO] Deploying module: metadataExchange-1.3
[INFO] Deploying module: ping-1.3
[INFO] Deploying module: soapmonitor-1.3
[INFO] script module activated
[INFO] Deploying Web service: version-1.3.aar
[INFO] jsp: init
Sep 16,2008 11:27:39 AM org.apache.catalina.core.ApplicationContext log
INFO: default: init
Sep 16,2008 11:27:39 AM org.apache.catalina.core.ApplicationContext log
INFO: jsp: init
Sep 16,2008 11:27:39 AM org.apache.catalina.core.ApplicationContext log
INFO: default: init
Sep 16,2008 11:27:39 AM org.apache.catalina.core.ApplicationContext log
INFO: jsp: init
Sep 16,2008 11:27:39 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Sep 16,2008 11:27:39 AM org.apache.jk.common.ChannelSocket init INFO: JK:
ajp13 listening on /0.0.0.0:8009
Sep 16,2008 11:27:39 AM org.apache.jk.server.JKMain start INFO: Jk running
ID=0 time=0/16 config=null
Sep 16,2008 11:27:39 AM org.apache.catalins.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Sep 16,2008 11:27:39 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 6925 ms
[INFO] jsp: init
[INFO] jsp: init
[INFO] jsp: init

[ERROR] Servlet.service() for servet jsp threw exception
java.lang.NumberFormatException: For input string: ""
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:468)
at java.lang.Integer.parseInt(Integer.java:497)
at
org.apache.axis2.transport.http.ProxyConfiguration.confgure(ProxyConfiguration.java:185)

I tried to deploy a test web service in the Tomcat webapps/axis2 folder
(Calculator.jws that is on the apache website) but get the following error:
[INFO] Unable to parse request URL [axis2/Calculator.jws][/axis2/services]
 

I think you followed the instructions given in Apache Axis web site to 
install and deploy services on Axis2 . If you are using Axis2, you 
should follow the instructions given in http://ws.apache.org/axis2/

AFAIK, there is no way to deploy jws in Axis2.


I'm guessing this is related to the fact that the Axis2 installation wont
validate but cant be sure.

Any thoughts on this?

thanks in advance for any assistance,
-Blake 
 




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

[jira] Commented: (AXIS2-3968) Fails to build Axis2-1.4.1 from source distribution

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3968:


We have noticed another issue when proceeding through the workaround(after 
building axis2-maven-mar plugin and aar plugin seperately).

Now I get the following error when building the release artifacts.

D:\axis2\axis2-1.4.1\modules\distribution>mvn clean install
[INFO] Scanning for projects...
[INFO] 
[INFO] Building Apache Axis2 - Distribution
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting directory D:\axis2\axis2-1.4.1\modules\distribution\target
[INFO] [antrun:run {execution: package}]
[INFO] Executing tasks
 [copy] Copying 137 files to 
D:\axis2\axis2-1.4.1\modules\distribution\target\tmp-doc-distro\xdocs\1_4
 [copy] Copied 10 empty directories to 2 empty directories under 
D:\axis2\axis2-1.4.1\modules\distribution\target\tmp-doc-distro\xdocs\1_4
 [copy] Copying 51 files to 
D:\axis2\axis2-1.4.1\modules\distribution\target\tmp-doc-distro\xdocs\1_4
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error executing ant tasks

Embedded error: D:\axis2\axis2-1.4.1\release-docs\readme-files not found.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Aug 08 13:27:43 IST 2008
[INFO] Final Memory: 10M/18M
[INFO] 


> Fails to build Axis2-1.4.1 from source distribution
> ---
>
> Key: AXIS2-3968
> URL: https://issues.apache.org/jira/browse/AXIS2-3968
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.4.1
> Environment: Winxp, Axis2-1.4.1 (Release candidate-2008-08-07), 
> jdk15, maven2.0.8
>    Reporter: Charitha Kankanamge
>Assignee: Nandana Mihindukulasooriya
>
> I couldnot build Axis2-1.4.1 from source distro. See the following output.
> Downloading: 
> http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.4.1/axis2-mar-maven-plugin-1.4.1.jar
> Downloading: 
> http://repo1.maven.org/maven2/org/apache/axis2/axis2-mar-maven-plugin/1.4.1/axis2-mar-maven-plugin-1.4.1.jar
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Plugin could not be found - check that the goal name is correct: 
> Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.axis2 
> -DartifactId=axis2-mar-maven-plugin -Dversion=1.4.1 -Dpackaging=maven-plugin 
> -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=org.apache.axis2 
> -DartifactId=axis2-mar-maven-plugin -Dversion=1.4.1 -Dpackaging=maven-plugin 
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[
> id]
>   org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.4.1
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   ws-zones (http://ws.zones.apache.org/repository2),
>   apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)
>   org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.4.1
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   ws-zones (http://ws.zones.apache.org/repository2),
>   apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)
> [INFO] 
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> 
> [INFO] Total time: 8 seconds
> [INFO] Finished at: Thu Aug 07 21:48:38 IST 2008
> [INFO] Final Memory: 8M/15M
> [INFO] 
> 
> D:\axis2\axis2-1.4.1>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email 

[jira] Updated: (AXIS2-3968) Fails to build Axis2-1.4.1 from source distribution

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3968:
---

Priority: Major  (was: Blocker)

Reduced the severity of bug since there is a workaround.

> Fails to build Axis2-1.4.1 from source distribution
> ---
>
> Key: AXIS2-3968
> URL: https://issues.apache.org/jira/browse/AXIS2-3968
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.4.1
> Environment: Winxp, Axis2-1.4.1 (Release candidate-2008-08-07), 
> jdk15, maven2.0.8
>Reporter: Charitha Kankanamge
>Assignee: Nandana Mihindukulasooriya
>
> I couldnot build Axis2-1.4.1 from source distro. See the following output.
> Downloading: 
> http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.4.1/axis2-mar-maven-plugin-1.4.1.jar
> Downloading: 
> http://repo1.maven.org/maven2/org/apache/axis2/axis2-mar-maven-plugin/1.4.1/axis2-mar-maven-plugin-1.4.1.jar
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Plugin could not be found - check that the goal name is correct: 
> Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.axis2 
> -DartifactId=axis2-mar-maven-plugin -Dversion=1.4.1 -Dpackaging=maven-plugin 
> -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=org.apache.axis2 
> -DartifactId=axis2-mar-maven-plugin -Dversion=1.4.1 -Dpackaging=maven-plugin 
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[
> id]
>   org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.4.1
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   ws-zones (http://ws.zones.apache.org/repository2),
>   apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)
>   org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.4.1
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   ws-zones (http://ws.zones.apache.org/repository2),
>   apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)
> [INFO] 
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> 
> [INFO] Total time: 8 seconds
> [INFO] Finished at: Thu Aug 07 21:48:38 IST 2008
> [INFO] Final Memory: 8M/15M
> [INFO] 
> 
> D:\axis2\axis2-1.4.1>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [jira] Created: (AXIS2-3968) Fails to build Axis2-1.4.1 from source distribution

[Charitha Kankanamge]

This was tested to check whether the 1.4.1 source can be built 
out-of-the-box. As you said, aar-maven-plugin is not in public repos. We 
should add it to a public repo and then I'll test this again.


regards
Charitha

http://charithaka.blogspot.com

keith chapman wrote:

Charitha this is because the axis2-mar-maven plugin is used in the 
build and its not available in public repos. Can you try going into 
modules/tools/axis2-mar-maven-plugin and building that first before 
you attempt to build axis2. (If it fails saying that you need the 
axis2-aar-maven-plugin you may need to build that too).


On Thu, Aug 7, 2008 at 9:53 PM, Charitha Kankanamge (JIRA) 
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:


Fails to build Axis2-1.4.1 from source distribution
---

Key: AXIS2-3968
URL: https://issues.apache.org/jira/browse/AXIS2-3968
Project: Axis 2.0 (Axis2)
 Issue Type: Bug
   Affects Versions: 1.4.1
Environment: Winxp, Axis2-1.4.1 (Release
candidate-2008-08-07), jdk15, maven2.0.8
   Reporter: Charitha Kankanamge
   Assignee: Nandana Mihindukulasooriya
   Priority: Blocker


I couldnot build Axis2-1.4.1 from source distro. See the following
output.

Downloading:

http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.4.1/axis2-mar-maven-plugin-1.4.1.jar
Downloading:

http://repo1.maven.org/maven2/org/apache/axis2/axis2-mar-maven-plugin/1.4.1/axis2-mar-maven-plugin-1.4.1.jar
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Plugin could not be found - check that the goal name is
correct: Unable to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
   mvn install:install-file -DgroupId=org.apache.axis2
-DartifactId=axis2-mar-maven-plugin -Dversion=1.4.1
-Dpackaging=maven-plugin -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the
file there:
   mvn deploy:deploy-file -DgroupId=org.apache.axis2
-DartifactId=axis2-mar-maven-plugin -Dversion=1.4.1
-Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[
id]


 org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.4.1

from the specified remote repositories:
 central (http://repo1.maven.org/maven2),
 ws-zones (http://ws.zones.apache.org/repository2),
 apache-snapshots
(http://people.apache.org/repo/m2-snapshot-repository)

 org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.4.1

from the specified remote repositories:
 central (http://repo1.maven.org/maven2),
 ws-zones (http://ws.zones.apache.org/repository2),
 apache-snapshots
(http://people.apache.org/repo/m2-snapshot-repository)

[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 8 seconds
[INFO] Finished at: Thu Aug 07 21:48:38 IST 2008
[INFO] Final Memory: 8M/15M
[INFO]


D:\axis2\axis2-1.4.1>

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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




--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org



Internal Virus Database is out-of-date.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.4.7/1543 - Release Date: 7/9/2008 6:32 PM
 




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

[jira] Created: (AXIS2-3968) Fails to build Axis2-1.4.1 from source distribution

[Charitha Kankanamge (JIRA)]

Fails to build Axis2-1.4.1 from source distribution
---

 Key: AXIS2-3968
 URL: https://issues.apache.org/jira/browse/AXIS2-3968
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.4.1
 Environment: Winxp, Axis2-1.4.1 (Release candidate-2008-08-07), jdk15, 
maven2.0.8
Reporter: Charitha Kankanamge
Assignee: Nandana Mihindukulasooriya
Priority: Blocker


I couldnot build Axis2-1.4.1 from source distro. See the following output.

Downloading: 
http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.4.1/axis2-mar-maven-plugin-1.4.1.jar
Downloading: 
http://repo1.maven.org/maven2/org/apache/axis2/axis2-mar-maven-plugin/1.4.1/axis2-mar-maven-plugin-1.4.1.jar
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Plugin could not be found - check that the goal name is correct: Unable 
to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.axis2 
-DartifactId=axis2-mar-maven-plugin -Dversion=1.4.1 -Dpackaging=maven-plugin 
-Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.axis2 
-DartifactId=axis2-mar-maven-plugin -Dversion=1.4.1 -Dpackaging=maven-plugin 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[
id]


  org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.4.1

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  ws-zones (http://ws.zones.apache.org/repository2),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)

  org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.4.1

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  ws-zones (http://ws.zones.apache.org/repository2),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)

[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 8 seconds
[INFO] Finished at: Thu Aug 07 21:48:38 IST 2008
[INFO] Final Memory: 8M/15M
[INFO] 

D:\axis2\axis2-1.4.1>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3821) JMS binding details are not included in the generated wsdl (?wsdl)

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3821:
---

Fix Version/s: 1.4.1

Hi Nandana,
Can we please get this issue fixed in 1.4.1?

regards
Charitha

> JMS binding details are not included in the generated wsdl (?wsdl)
> --
>
> Key: AXIS2-3821
> URL: https://issues.apache.org/jira/browse/AXIS2-3821
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.4
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Priority: Blocker
> Fix For: 1.4.1
>
>
> JMS binding details are not available in the generated wsdl. 
>  - Configure a JMS server (Activemq)
>  - Configure JMS settings in axis2.xml
>  - Copy activemq-core-*.jar, activeio-core-*.jar, 
> gerenimo-j2ee-management-*.jar, geronimo-jms_*.jar to Axis2/lib
>  - Start Axis2 server
>  - Issue http://localhost:8080/axis2/services/version?wsdl 
> You will not find the JMS binding details in the wsdl

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Closed: (AXIS2-3529) Axis2 server responds with Http 200 instead of 202 for the request of a dual channel invocation

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge closed AXIS2-3529.
--


This is fixed in Axis2-1.4.1-RC1. Verified and closed the bug.

> Axis2 server responds with Http 200 instead of 202 for the request of a dual 
> channel invocation
> ---
>
> Key: AXIS2-3529
> URL: https://issues.apache.org/jira/browse/AXIS2-3529
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: nightly
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Fix For: 1.4.1, 1.4
>
> Attachments: patch.txt
>
>
> In the dual channel service invocation, Axis2 server is expected to respond 
> to the request message with http 202. This was working correctly in 
> Axis2-1.3. However, server responds with 200 OK for the request in the latest 
> nightly builds. 
> Steps to reproduce:
> 
> 1. Deploy a service in Axis2 server
> 2. Write an dual channel async client
> 3. Invoke the service and monitor the message flow using tcpmon
> When you send the request, you will get http 200 as the response code. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Reopened: (AXIS2-3529) Axis2 server responds with Http 200 instead of 202 for the request of a dual channel invocation

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge reopened AXIS2-3529:



This issue is still there in Axis2-1.4. I always get the following as the 
response in request channel. 

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=UTF-8
Content-Length: 0
Date: Tue, 22 Jul 2008 08:28:59 GMT

 Tested with simpleAxisServer as well as Tomcat6.0.10/Axis2-1.4
Please have a look at this issue.

> Axis2 server responds with Http 200 instead of 202 for the request of a dual 
> channel invocation
> ---
>
> Key: AXIS2-3529
> URL: https://issues.apache.org/jira/browse/AXIS2-3529
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: nightly
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>Priority: Critical
> Fix For: 1.4
>
>
> In the dual channel service invocation, Axis2 server is expected to respond 
> to the request message with http 202. This was working correctly in 
> Axis2-1.3. However, server responds with 200 OK for the request in the latest 
> nightly builds. 
> Steps to reproduce:
> 
> 1. Deploy a service in Axis2 server
> 2. Write an dual channel async client
> 3. Invoke the service and monitor the message flow using tcpmon
> When you send the request, you will get http 200 as the response code. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3529) Axis2 server responds with Http 200 instead of 202 for the request of a dual channel invocation

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3529:
---

Priority: Blocker  (was: Critical)

> Axis2 server responds with Http 200 instead of 202 for the request of a dual 
> channel invocation
> ---
>
> Key: AXIS2-3529
> URL: https://issues.apache.org/jira/browse/AXIS2-3529
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: nightly
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Fix For: 1.4
>
>
> In the dual channel service invocation, Axis2 server is expected to respond 
> to the request message with http 202. This was working correctly in 
> Axis2-1.3. However, server responds with 200 OK for the request in the latest 
> nightly builds. 
> Steps to reproduce:
> 
> 1. Deploy a service in Axis2 server
> 2. Write an dual channel async client
> 3. Invoke the service and monitor the message flow using tcpmon
> When you send the request, you will get http 200 as the response code. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3921) Compile errors in the ADB generated stub (wsdl is attached)

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3921:
---

Attachment: stockquote.wsdl

Attached wsdl

> Compile errors in the ADB generated stub (wsdl is attached)
> ---
>
> Key: AXIS2-3921
> URL: https://issues.apache.org/jira/browse/AXIS2-3921
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: adb
>Affects Versions: 1.4
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Assignee: Amila Chinthaka Suriarachchi
> Attachments: stockquote.wsdl
>
>
> Type mismatch: cannot convert from String to StockQuoteStub.String compile 
> error can be seen in the generated stub. The wsdl is attached here with. 
> Steps to reproduce:
> 
> 1. Generate stub using the following options
> wsdljava -uri http://www.webservicex.net/stockquote.asmx?wsdl -o out
> 2. Import the generated stub in to an IDE with the Axis2 libraries in class 
> path. You will notice compilation failure at the following method in 
> StockQuoteStub.java
> private static synchronized String getUniqueSuffix(){
> // reset the counter if it is greater than 9
> if (counter > 9){
> counter = 0;
> }
> counter = counter + 1; 
> return Long.toString(System.currentTimeMillis()) + "_" + counter; 
> //Complile failure
> }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3921) Compile errors in the ADB generated stub (wsdl is attached)

[Charitha Kankanamge (JIRA)]

Compile errors in the ADB generated stub (wsdl is attached)
---

 Key: AXIS2-3921
 URL: https://issues.apache.org/jira/browse/AXIS2-3921
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: adb
Affects Versions: 1.4
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Amila Chinthaka Suriarachchi
 Attachments: stockquote.wsdl

Type mismatch: cannot convert from String to StockQuoteStub.String compile 
error can be seen in the generated stub. The wsdl is attached here with. 

Steps to reproduce:

1. Generate stub using the following options
wsdljava -uri http://www.webservicex.net/stockquote.asmx?wsdl -o out

2. Import the generated stub in to an IDE with the Axis2 libraries in class 
path. You will notice compilation failure at the following method in 
StockQuoteStub.java
private static synchronized String getUniqueSuffix(){
// reset the counter if it is greater than 9
if (counter > 9){
counter = 0;
}
counter = counter + 1; 
return Long.toString(System.currentTimeMillis()) + "_" + counter; 
//Complile failure

}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [Axis2] Axis2 OSGi bundle. Phase 1

[Charitha Kankanamge]

Hi Saminda,
I followed the steps given in axis2_osgi_integration.pdf and was able to 
deploy sample service and invoke it successfuly. Thanks Saminda.


regards
Charitha

PS:- If you encounter an artifact resolving problem when building sample 
project 
(https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/saminda/osgi_test/), 
make sure to build axis2-trunk first.


Saminda Abeyruwan wrote:



Hi All,

As per the discussion on OSGi-fying Axis2, the improvements have been 
done to "osgi"  module and available for you to test it out. The 
installing and running instruction on top of Eclipse Equinox OSGi 
implementation is available in attached "axis2_osgi_integration.pdf". 
Please feel free to test it and provide your valuable input regarding 
this extension.


Looking forward to hearing your valuable comments.

Thank you!

Saminda
--
Saminda Abeyruwan

Senior Software Engineer
WSO2 Inc. - www.wso2.org 



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



No virus found in this incoming message.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.4.1/1510 - Release Date: 6/19/2008 3:21 PM
 




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

[jira] Updated: (AXIS2-3842) Port/Binding details are not added to the endpoint if both useOriginalwsdl and modifyUserWSDLPortAddress parameters are true in services.xml

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3842:
---

Attachment: calculatorService.aar

Attached screen shot

> Port/Binding details are not added to the endpoint if both useOriginalwsdl 
> and modifyUserWSDLPortAddress parameters are true in services.xml
> 
>
> Key: AXIS2-3842
> URL: https://issues.apache.org/jira/browse/AXIS2-3842
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Assignee: Sanka Samaranayake
> Attachments: calculatorService.aar
>
>
> I have set the following parameters in services.xml
> true
>  true
> However, the generated wsdl does not correctly modify endpoint details. 
> Please deploy the attached service and check the ?wsdl

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (AXIS2-3831) Fails to generate wsdl when deploying annotated .class file using POJODeployer in axis2-1.4

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3831:


Yes. I tried with that. With jarred up annotated class which copied to 
servicejars directory, I was able to view the WSDL and invoke the service 
through a java client. 
However, I couldn't invoke the service in RESTful manner and reported a JIRA a 
few days ago (https://issues.apache.org/jira/browse/AXIS2-3817)


> Fails to generate wsdl when deploying annotated .class file using 
> POJODeployer in axis2-1.4
> ---
>
> Key: AXIS2-3831
> URL: https://issues.apache.org/jira/browse/AXIS2-3831
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Priority: Blocker
>
> I deployed the following annotated class in Axis2-1.4 (Copied the .class file 
> to Axis2_home/repository/pojo)
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> @WebService
> public class ExamplePOJOService {
>   @WebMethod
>   public String reverse(String input) {
>   StringBuffer buff = new StringBuffer();
>   for (int i=input.length()-1; i>=0; i--) {
>   buff.append(input.charAt(i));
>   }
>   return buff.toString();
>   }
> }
> When clicking on the servicename of the http://localhost:8080/axis2/services/ 
> page I got the following exception.
> [ERROR] Error occurred generating WSDL file for Web service implementation 
> class
>  {ExamplePOJOService}: {java.lang.Exception: A WSDL Definition could not be 
> gene
> rated for the implementation class: ExamplePOJOService}
> java.lang.Exception: A WSDL Definition could not be generated for the 
> implementation class: ExamplePOJOService
> at 
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:177)
> at 
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.initialize(JAXWSRIWSDLGenerator.java:371)
> at 
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.getWSDL(JAXWSRIWSDLGenerator.java:364)
> at 
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1319)
> at 
> org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:146)
> at 
> org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
> at 
> org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
> at 
> org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
> at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
> at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
> at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (AXIS2-3831) Fails to generate wsdl when deploying annotated .class file using POJODeployer in axis2-1.4

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3831:


jaxws-rt.jar and jaxws-tools.jar was in Axis2_home/lib directory. Do i need to 
have some other jax-ws jars? 

In Axis2-1.3, just copying an annotated class to Axis2_home/repository/pojo 
directory made and exposed it as a web service. 

> Fails to generate wsdl when deploying annotated .class file using 
> POJODeployer in axis2-1.4
> ---
>
> Key: AXIS2-3831
> URL: https://issues.apache.org/jira/browse/AXIS2-3831
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Priority: Blocker
>
> I deployed the following annotated class in Axis2-1.4 (Copied the .class file 
> to Axis2_home/repository/pojo)
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> @WebService
> public class ExamplePOJOService {
>   @WebMethod
>   public String reverse(String input) {
>   StringBuffer buff = new StringBuffer();
>   for (int i=input.length()-1; i>=0; i--) {
>   buff.append(input.charAt(i));
>   }
>   return buff.toString();
>   }
> }
> When clicking on the servicename of the http://localhost:8080/axis2/services/ 
> page I got the following exception.
> [ERROR] Error occurred generating WSDL file for Web service implementation 
> class
>  {ExamplePOJOService}: {java.lang.Exception: A WSDL Definition could not be 
> gene
> rated for the implementation class: ExamplePOJOService}
> java.lang.Exception: A WSDL Definition could not be generated for the 
> implementation class: ExamplePOJOService
> at 
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:177)
> at 
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.initialize(JAXWSRIWSDLGenerator.java:371)
> at 
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.getWSDL(JAXWSRIWSDLGenerator.java:364)
> at 
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1319)
> at 
> org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:146)
> at 
> org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
> at 
> org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
> at 
> org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
> at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
> at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
> at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3831) Fails to generate wsdl when deploying annotated .class file using POJODeployer in axis2-1.4

[Charitha Kankanamge (JIRA)]

Fails to generate wsdl when deploying annotated .class file using POJODeployer 
in axis2-1.4
---

 Key: AXIS2-3831
 URL: https://issues.apache.org/jira/browse/AXIS2-3831
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Priority: Blocker


I deployed the following annotated class in Axis2-1.4 (Copied the .class file 
to Axis2_home/repository/pojo)

import javax.jws.WebMethod;
import javax.jws.WebService;

@WebService
public class ExamplePOJOService {
@WebMethod
public String reverse(String input) {
StringBuffer buff = new StringBuffer();
for (int i=input.length()-1; i>=0; i--) {
buff.append(input.charAt(i));
}
return buff.toString();
}

}

When clicking on the servicename of the http://localhost:8080/axis2/services/ 
page I got the following exception.

[ERROR] Error occurred generating WSDL file for Web service implementation class
 {ExamplePOJOService}: {java.lang.Exception: A WSDL Definition could not be gene
rated for the implementation class: ExamplePOJOService}
java.lang.Exception: A WSDL Definition could not be generated for the 
implementation class: ExamplePOJOService
at 
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:177)
at 
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.initialize(JAXWSRIWSDLGenerator.java:371)
at 
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.getWSDL(JAXWSRIWSDLGenerator.java:364)
at 
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1319)
at 
org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:146)
at 
org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
at 
org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
at 
org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:595)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3826) Invalid return type of the generated stub causes compile error

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3826:
---

Summary: Invalid return type of the generated stub causes compile error   
(was: Invalid return type of the generated stub causes complie error )

> Invalid return type of the generated stub causes compile error 
> ---
>
> Key: AXIS2-3826
> URL: https://issues.apache.org/jira/browse/AXIS2-3826
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Assignee: Amila Chinthaka Suriarachchi
>
> I generated code using a public wsdl using default code gen options (ADB). 
> However the generated stub shows compile errors due to an invalid return type 
> in following stub method.
> Here the return type String should be java.lang.String
> private static synchronized String getUniqueSuffix(){
> // reset the counter if it is greater than 9
> if (counter > 9){
> counter = 0;
> }
> counter = counter + 1; 
> return Long.toString(System.currentTimeMillis()) + "_" + counter;
> }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3826) Invalid return type of the generated stub causes complie error

[Charitha Kankanamge (JIRA)]

Invalid return type of the generated stub causes complie error 
---

 Key: AXIS2-3826
 URL: https://issues.apache.org/jira/browse/AXIS2-3826
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Amila Chinthaka Suriarachchi


I generated code using a public wsdl using default code gen options (ADB). 
However the generated stub shows compile errors due to an invalid return type 
in following stub method.
Here the return type String should be java.lang.String
private static synchronized String getUniqueSuffix(){
// reset the counter if it is greater than 9
if (counter > 9){
counter = 0;
}
counter = counter + 1; 
return Long.toString(System.currentTimeMillis()) + "_" + counter;
}


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [Axis2][VOTE] Axis2 1.4 FINAL

[Charitha Kankanamge]

+1

Charitha

Davanum Srinivas wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Folks,

After all the excitement of the past few days :) We almost forgot the 
release


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 651268 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 



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFIELfTgNg6eWEDv1kRAtDoAJ9xOJrbhAlQoSnVl7I79C3gDOEFDQCgi7Vy
gtoyG/P/Q3RWxIk1wwBphl0=
=QD87
-END PGP SIGNATURE-

-
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]

[jira] Created: (AXIS2-3698) HTTP ports are not included in the generated wsdl if the service is deployed in a server configured with both http and https transports

[Charitha Kankanamge (JIRA)]

HTTP ports are not included in the generated wsdl if the service is deployed in 
a server configured with both http and https transports
---

 Key: AXIS2-3698
 URL: https://issues.apache.org/jira/browse/AXIS2-3698
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: nightly
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Sanka Samaranayake
Priority: Critical
 Attachments: RestService.aar

I have a pojo service and which worked fine with previous axis2 builds. I 
usually generate code by specifying httpsoap11 port name of the generated wsdl 
(?wsdl). When I tried to generate code using the same httpsoap11 port in the 
recent Axis2 nightlies, it failed due to the requested port is not available in 
the wsdl (?wsdl).
It seems that http ports are not included in the generated wsdl if both http 
and https transports are configured in the servlet container. 

Steps to reproduce:

1. Deploy the attached service in tomcat which is configured with both http and 
https transports
2. access http://localhost:8080/axis2 and select the deployed service
3. Check the generated wsdl



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3698) HTTP ports are not included in the generated wsdl if the service is deployed in a server configured with both http and https transports

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3698:
---

Attachment: RestService.aar

Attached service archive

> HTTP ports are not included in the generated wsdl if the service is deployed 
> in a server configured with both http and https transports
> ---
>
> Key: AXIS2-3698
> URL: https://issues.apache.org/jira/browse/AXIS2-3698
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: wsdl
>Affects Versions: nightly
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Assignee: Sanka Samaranayake
>Priority: Critical
> Attachments: RestService.aar
>
>
> I have a pojo service and which worked fine with previous axis2 builds. I 
> usually generate code by specifying httpsoap11 port name of the generated 
> wsdl (?wsdl). When I tried to generate code using the same httpsoap11 port in 
> the recent Axis2 nightlies, it failed due to the requested port is not 
> available in the wsdl (?wsdl).
> It seems that http ports are not included in the generated wsdl if both http 
> and https transports are configured in the servlet container. 
> Steps to reproduce:
> 
> 1. Deploy the attached service in tomcat which is configured with both http 
> and https transports
> 2. access http://localhost:8080/axis2 and select the deployed service
> 3. Check the generated wsdl

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3659) Wsdl2 code generation falis

[Charitha Kankanamge (JIRA)]

Wsdl2 code generation falis
---

 Key: AXIS2-3659
 URL: https://issues.apache.org/jira/browse/AXIS2-3659
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.4
 Environment: winxp, jdk15, 1.4-RC1
Reporter: Charitha Kankanamge
Priority: Blocker


I tried to generate code using wsdl2 of default version service. Code gen fails 
with the following exception.

C:\Axis2\axis2-1.4\axis2-637511\bin>wsdl2java.bat -uri 
http://localhost:8080/axis2/services/Version?wsdl2 -wv 2.0 -o 
C:\Axis2\axis2-1.4\axis2-637511\bin\out
Using AXIS2_HOME:   C:\Axis2\axis2-1.4\axis2-637511
Using JAVA_HOME:D:\Program Files\Java\jdk1.5.0_14
Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException
: Error parsing WSDL
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:159)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: WSDLException: faultCode=OTHER_ERROR: Fatal error.: 
axisversion.sample: java.net.UnknownHostException: axisversion.sample
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.Socket.connect(Socket.java:520)
at java.net.Socket.connect(Socket.java:470)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
at sun.net.www.http.HttpClient.(HttpClient.java:231)
at sun.net.www.http.HttpClient.New(HttpClient.java:304)
at sun.net.www.http.HttpClient.New(HttpClient.java:321)
at 
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
at 
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
at 
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
at java.net.URLConnection.getContent(URLConnection.java:682)
at java.net.URL.getContent(URL.java:1021)
at 
org.apache.woden.internal.wsdl20.assertions.Description1001.validate(Description1001.java:28)
at 
org.apache.woden.internal.wsdl20.validation.WSDLValidator.checkAssertions(WSDLValidator.java:109)
at 
org.apache.woden.internal.wsdl20.validation.WSDLValidator.validate(WSDLValidator.java:77)
at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:207)
at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:233)
at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:268)
at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:127)
at org.apache.axis2.description.WSDL20ToAxisServiceBuilder.readInTheWSDL
File(WSDL20ToAxisServiceBuilder.java:1181)
at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.(WSDL20ToAxisServiceBuilder.java:151)
at 
org.apache.axis2.description.WSDL20ToAllAxisServicesBuilder.(WSDL20ToAllAxisServicesBuilder.java:53)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:102)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
at 
org.apache.woden.internal.wsdl20.assertions.Description1001.validate(Description1001.java:42)
at 
org.apache.woden.internal.wsdl20.validation.WSDLValidator.checkAssertions(WSDLValidator.java:109)
at 
org.apache.woden.internal.wsdl20.validation.WSDLValidator.validate(WSDLValidator.java:77)
at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:207)
at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:233)
at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:268)
at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:127)
at org.apache.axis2.description.WSDL20ToAxisServiceBuilder.readInTheWSDL
File(WSDL20ToAxisServiceBuilder.java:1181)
at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.(WSDL20ToAxisServiceBuilder.java:151)
at 
org.apache.axis2.description.WSDL20ToAllAxisServicesBuilder.(WSDL20ToAllAxisServicesBuilder.java:53)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:102)
... 2 more

Steps to reproduce:
===
1. Start Axis2server
2. Enter following command
wsdl2java.bat -uri http://localhost:8080/axis2/services/Version?wsdl2 -wv 2.0 
-o C:\Axis2\axis2-1.4\axis2-637511\bin\out

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the

[jira] Commented: (AXIS2-3073) commons-logging and log4j property files should not be placed at the root of axis2 binary distro

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3073:


Hi Dims,
Sorry for misunderstanding. I saw a couple of comments which does not directly 
relates to the issue i originally reported. 
I have seen that config files are placed in either conf or lib directories in 
most app servers. I thought it would be nice to have the same structure in 
Axis2 binary distro. Therefore I reported this minor usability issue a few 
months back. 
I saw the property files are located at the root in Axis2-1.4 RC1 and therefore 
reopened the issue.

I have no strong objections for placing them at the root since this is not a 
functionality issue, just a suggestion to improve usability. (It was my mistake 
to report this under Bug, this should have been reported as a suggestion)

regards
Charitha

> commons-logging and log4j property files should not be placed at the root of 
> axis2 binary distro
> 
>
> Key: AXIS2-3073
> URL: https://issues.apache.org/jira/browse/AXIS2-3073
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.3
>    Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>Priority: Minor
> Fix For: 1.4
>
>
> Currently commons-logging.properties and log4j.properties are located at the 
> root of axis2-1.3 RC3 binary distribution. These files should be placed 
> either in conf or lib directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3636) Axis2-1.4-RC1: Advanced-rmi sample client fails

[Charitha Kankanamge (JIRA)]

Axis2-1.4-RC1: Advanced-rmi sample client fails
---

 Key: AXIS2-3636
 URL: https://issues.apache.org/jira/browse/AXIS2-3636
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples
Affects Versions: 1.4
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge


Advanced-rmi sample client fails with the following exceptions. 


C:\Axis2\axis2-1.4\axis2-637511\samples\advanced-rmi>ant run_client
Buildfile: build.xml

init:

clean:
   [delete] Deleting directory 
C:\Axis2\axis2-1.4\axis2-637511\samples\advanced-rmi\classes
   [delete] Deleting directory C:\Axis2\axis2-1.4\axis2-637511\dist

run_client:
 [echo] Running the RMI clients
[mkdir] Created dir: 
C:\Axis2\axis2-1.4\axis2-637511\samples\advanced-rmi\classes
[mkdir] Created dir: C:\Axis2\axis2-1.4\axis2-637511\dist
[javac] Compiling 15 source files to 
C:\Axis2\axis2-1.4\axis2-637511\samples\advanced-rmi\classes
[javac] Note: 
C:\Axis2\axis2-1.4\axis2-637511\samples\advanced-rmi\src\sample\rmi\server\dto\TestComplexBean.java
 uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
  [jar] Building jar: C:\Axis2\axis2-1.4\axis2-637511\dist\rmi_client.jar
 [java] 2008-03-19 21:01:00,687 INFO  
org.apache.axis2.deployment.ModuleDeployer - Deploying module: 
metadataExchange-637511 - 
file:/C:/Axis2/axis2-1.4/axis2-637511/lib/mex-637511.jar
 [java] java.lang.reflect.UndeclaredThrowableException
 [java] at 
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:194)
 [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:747)
 [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:201)
 [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:104)
 [java] at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
 [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [java] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 [java] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [java] at java.lang.reflect.Method.invoke(Method.java:585)
 [java] at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
 [java] at org.apache.tools.ant.Task.perform(Task.java:348)
 [java] at org.apache.tools.ant.Target.execute(Target.java:357)
 [java] at org.apache.tools.ant.Target.performTasks(Target.java:385)
 [java] at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
 [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
 [java] at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
 [java] at 
org.apache.tools.ant.Project.executeTargets(Project.java:1181)
 [java] at org.apache.tools.ant.Main.runBuild(Main.java:698)
 [java] at org.apache.tools.ant.Main.startAnt(Main.java:199)
 [java] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
 [java] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
 [java] Caused by: java.lang.reflect.UndeclaredThrowableException
 [java] at $Proxy0.method1(Unknown Source)
 [java] at 
sample.rmi.client.TestService1.testMethod1(TestService1.java:68)
 [java] at sample.rmi.client.TestService1.main(TestService1.java:124)
 [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [java] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 [java] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [java] at java.lang.reflect.Method.invoke(Method.java:585)
 [java] at 
org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217)
 [java] at 
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152)
 [java] ... 20 more
 [java] Caused by: org.apache.axis2.AxisFault: The service cannot be found 
for the endpoint reference (EPR) 127.0.0.1/axis2/services/Service1
 [java] at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:481)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
 [java] at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
 [java] at 
org.apache.axis2.client.ServiceClient.sendRece

[jira] Reopened: (AXIS2-3073) commons-logging and log4j property files should not be placed at the root of axis2 binary distro

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge reopened AXIS2-3073:



These two files (commons-logging.properties and logs4j.properties) are still 
placed at the root of binary distro. Retested with Axis2-1.4 RC1.



> commons-logging and log4j property files should not be placed at the root of 
> axis2 binary distro
> 
>
> Key: AXIS2-3073
> URL: https://issues.apache.org/jira/browse/AXIS2-3073
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.3
>    Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>Priority: Minor
> Fix For: 1.4
>
>
> Currently commons-logging.properties and log4j.properties are located at the 
> root of axis2-1.3 RC3 binary distribution. These files should be placed 
> either in conf or lib directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Reopened: (AXIS2-3412) Custom exception handling issue with pojos

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge reopened AXIS2-3412:



Reopened the issue as requested by Pär Malmqvist.

> Custom exception handling issue with pojos
> --
>
> Key: AXIS2-3412
> URL: https://issues.apache.org/jira/browse/AXIS2-3412
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: nightly
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>Priority: Critical
> Fix For: 1.4
>
> Attachments: CustomexceptionService.aar, CustomExceptionService.wsdl
>
>
> 'Duplicate nested type CustomException' Compile error can be seen in the 
> generated stub if a service is deployed using a pojo which throws a custom 
> exception. 
> A similar issue has been reported by par Malmqvist in the Axis2 user list. 
> See http://marc.info/?l=axis-user&m=119805625224409&w=2 for more information.
> Steps to reproduce:
> ===
> 1. Create service impl class and custom exception class as follows
> public class CustomexceptionService {
>   
> public int addOneToPositiveValue(int value) throws CustomException {
>   if(value < 1) {
>   throw(new CustomException());
>   }
>  
>   return(value + 1);
>   }
>   }
> public class CustomException extends Exception{
>   
>private static final long serialVersionUID = 9;
>   public CustomException() {
>   super();
>   }
>   public String toString() {
>   return(super.toString() + "org.test.CustomException");
>   }
> }
> 2. Create a service archive and deploy the service
> 3. Generate client stub using the ?wsdl of the service
> wsdl2java.bat -uri 
> http://10.100.1.118:9762/services/CustomExceptionService?wsdl -o 
> C:\wsas\wsas-2.2\qa-build2\wso2wsas-SNAPSHOT\bin\out -p org.mytest
> 4. Check the generated stub

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

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

[Charitha Kankanamge]

+1

Charitha
Sanka Samaranayake wrote:



+1

Sanka

On Fri, Mar 7, 2008 at 11:43 AM, Deepal jayasinghe <[EMAIL PROTECTED] 
> wrote:


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]





--
Sanka Samaranayake
WSO2 Inc.

http://sankas.blogspot.com/
http://www.wso2.org/ 





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

Re: [axis2] VOTE: Erange Jayasundera for committer

[Charitha Kankanamge]

+1 to Eranga!

Thanks!
Charitha

Sanjiva Weerawarana wrote:

Eranga is the one who implemented the CORBA module and is working to 
improve it as well. He did the original work as part of his MSc 
project and is currently working in the ICT Agency in Sri Lanka.


I'm of course +1 for Eranga becoming a committer.

Sanjiva.





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

[jira] Created: (AXIS2-3529) Axis2 server responds with Http 200 instead of 202 for the request of a dual channel invocation

[Charitha Kankanamge (JIRA)]

Axis2 server responds with Http 200 instead of 202 for the request of a dual 
channel invocation
---

 Key: AXIS2-3529
 URL: https://issues.apache.org/jira/browse/AXIS2-3529
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: nightly
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe
Priority: Critical


In the dual channel service invocation, Axis2 server is expected to respond to 
the request message with http 202. This was working correctly in Axis2-1.3. 
However, server responds with 200 OK for the request in the latest nightly 
builds. 

Steps to reproduce:

1. Deploy a service in Axis2 server
2. Write an dual channel async client
3. Invoke the service and monitor the message flow using tcpmon

When you send the request, you will get http 200 as the response code. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3527) Cannot exclude bean properties of a parent class

[Charitha Kankanamge (JIRA)]

Cannot exclude bean properties of a parent class


 Key: AXIS2-3527
 URL: https://issues.apache.org/jira/browse/AXIS2-3527
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: nightly
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe


AFAIK, bean properties of a parent class can be excluded by defining 
beanPropertyRules parameter in the services.xml. However this feature seems 
broken in the current Axis2 version (snapshot). 
It has been noticed that the properties of child can be excluded with the above 
approach.

Steps to reproduce:
===
1. Deploy the attached service archive
2. Get the wsdl of the service by issuing ?wsdl
3. Check the excluded property in the wsdl

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Java2WSDL

[Charitha Kankanamge]

Hello Pudur,
Please have a look at the Axis2 reference guide 
http://ws.apache.org/axis2/1_3/reference.html


regards
Charitha
Ramaswamy, Pudur wrote:

How can I use JAVA2WSDL command? Is there a online help or 
documantation? I see good documentation for WSDL2Java tool.


I tried to use the java2WSDL as below but I’m getting the following error:

java2wsdl -cp . -cn com.mydomain.myclass -of AccountServices.wsdl

Using AXIS2_HOME: C:\axis2-1.3

Using JAVA_HOME:***88

An error occured while generating 
codejava.lang.ClassNotFoundException: com.mydomain.myclass


I ran the command in command prompt at one level above the com directory.

Thanks,

-pudur

DISCLAIMER:
This message contains privileged and confidential information and is 
intended only for an individual named. If you are not the intended 
recipient, you should not disseminate, distribute, store, print, copy 
or deliver this message. Please notify the sender immediately by 
e-mail if you have received this e-mail by mistake and delete this 
e-mail from your system. E-mail transmission cannot be guaranteed to 
be secure or error-free as information could be intercepted, 
corrupted, lost, destroyed, arrive late or incomplete or contain 
viruses. The sender, therefore, does not accept liability for any 
errors or omissions in the contents of this message which arise as a 
result of e-mail transmission. If verification is required, please 
request a hard-copy version.






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

Re: Interopertability issues with Axis2 ADB and .NET client

[Charitha Kankanamge]

Hi Rick,

AFAIK there wouldn't be any issues with .NET interoperability. A few 
months ago we did interop tests against .NET stack and most of the 
scenarios were successful. If you use Axis2-1.3 or the latest SNAPSHOT, 
.NET client/server should interoperate properly.


regards
Charitha

ricko xavier wrote:


Hello,
 
I have Axis2 WS Stack run on JBOSS server using axis2 default binding 
ADB. The client is .NET. Will there be any interoperatibilty issues???
 
Also, vice-versa if my client uses Axis2 ADB and .NET WS stack will 
there be any issues ?? Any replies are appreicated ???
 
Rick





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

[jira] Updated: (AXIS2-3412) Custom exception handling issue with pojos

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3412:
---

Attachment: CustomExceptionService.wsdl

Attached wsdl

> Custom exception handling issue with pojos
> --
>
> Key: AXIS2-3412
> URL: https://issues.apache.org/jira/browse/AXIS2-3412
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: nightly
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Assignee: Amila Chinthaka Suriarachchi
>Priority: Critical
> Attachments: CustomexceptionService.aar, CustomExceptionService.wsdl
>
>
> 'Duplicate nested type CustomException' Compile error can be seen in the 
> generated stub if a service is deployed using a pojo which throws a custom 
> exception. 
> A similar issue has been reported by par Malmqvist in the Axis2 user list. 
> See http://marc.info/?l=axis-user&m=119805625224409&w=2 for more information.
> Steps to reproduce:
> ===
> 1. Create service impl class and custom exception class as follows
> public class CustomexceptionService {
>   
> public int addOneToPositiveValue(int value) throws CustomException {
>   if(value < 1) {
>   throw(new CustomException());
>   }
>  
>   return(value + 1);
>   }
>   }
> public class CustomException extends Exception{
>   
>private static final long serialVersionUID = 9;
>   public CustomException() {
>   super();
>   }
>   public String toString() {
>   return(super.toString() + "org.test.CustomException");
>   }
> }
> 2. Create a service archive and deploy the service
> 3. Generate client stub using the ?wsdl of the service
> wsdl2java.bat -uri 
> http://10.100.1.118:9762/services/CustomExceptionService?wsdl -o 
> C:\wsas\wsas-2.2\qa-build2\wso2wsas-SNAPSHOT\bin\out -p org.mytest
> 4. Check the generated stub

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (AXIS2-3412) Custom exception handling issue with pojos

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3412:


Hello Amila,
Actually I didn't explicitly use a wsdl for codegen. As I mentioned in the 
steps, I used ?wsdl of the attached service. I have attached it for your 
reference.

regards
Charitha

> Custom exception handling issue with pojos
> --
>
> Key: AXIS2-3412
> URL: https://issues.apache.org/jira/browse/AXIS2-3412
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: nightly
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Assignee: Amila Chinthaka Suriarachchi
>Priority: Critical
> Attachments: CustomexceptionService.aar, CustomExceptionService.wsdl
>
>
> 'Duplicate nested type CustomException' Compile error can be seen in the 
> generated stub if a service is deployed using a pojo which throws a custom 
> exception. 
> A similar issue has been reported by par Malmqvist in the Axis2 user list. 
> See http://marc.info/?l=axis-user&m=119805625224409&w=2 for more information.
> Steps to reproduce:
> ===
> 1. Create service impl class and custom exception class as follows
> public class CustomexceptionService {
>   
> public int addOneToPositiveValue(int value) throws CustomException {
>   if(value < 1) {
>   throw(new CustomException());
>   }
>  
>   return(value + 1);
>   }
>   }
> public class CustomException extends Exception{
>   
>private static final long serialVersionUID = 9;
>   public CustomException() {
>   super();
>   }
>   public String toString() {
>   return(super.toString() + "org.test.CustomException");
>   }
> }
> 2. Create a service archive and deploy the service
> 3. Generate client stub using the ?wsdl of the service
> wsdl2java.bat -uri 
> http://10.100.1.118:9762/services/CustomExceptionService?wsdl -o 
> C:\wsas\wsas-2.2\qa-build2\wso2wsas-SNAPSHOT\bin\out -p org.mytest
> 4. Check the generated stub

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3412) Custom exception handling issue with pojos

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3412:
---

Attachment: CustomexceptionService.aar

Attached service archive

> Custom exception handling issue with pojos
> --
>
> Key: AXIS2-3412
> URL: https://issues.apache.org/jira/browse/AXIS2-3412
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: nightly
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Assignee: Amila Chinthaka Suriarachchi
>Priority: Critical
> Attachments: CustomexceptionService.aar
>
>
> 'Duplicate nested type CustomException' Compile error can be seen in the 
> generated stub if a service is deployed using a pojo which throws a custom 
> exception. 
> A similar issue has been reported by par Malmqvist in the Axis2 user list. 
> See http://marc.info/?l=axis-user&m=119805625224409&w=2 for more information.
> Steps to reproduce:
> ===
> 1. Create service impl class and custom exception class as follows
> public class CustomexceptionService {
>   
> public int addOneToPositiveValue(int value) throws CustomException {
>   if(value < 1) {
>   throw(new CustomException());
>   }
>  
>   return(value + 1);
>   }
>   }
> public class CustomException extends Exception{
>   
>private static final long serialVersionUID = 9;
>   public CustomException() {
>   super();
>   }
>   public String toString() {
>   return(super.toString() + "org.test.CustomException");
>   }
> }
> 2. Create a service archive and deploy the service
> 3. Generate client stub using the ?wsdl of the service
> wsdl2java.bat -uri 
> http://10.100.1.118:9762/services/CustomExceptionService?wsdl -o 
> C:\wsas\wsas-2.2\qa-build2\wso2wsas-SNAPSHOT\bin\out -p org.mytest
> 4. Check the generated stub

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3412) Custom exception handling issue with pojos

[Charitha Kankanamge (JIRA)]

Custom exception handling issue with pojos
--

 Key: AXIS2-3412
 URL: https://issues.apache.org/jira/browse/AXIS2-3412
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: nightly
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Amila Chinthaka Suriarachchi
Priority: Critical
 Attachments: CustomexceptionService.aar

'Duplicate nested type CustomException' Compile error can be seen in the 
generated stub if a service is deployed using a pojo which throws a custom 
exception. 

A similar issue has been reported by par Malmqvist in the Axis2 user list. See 
http://marc.info/?l=axis-user&m=119805625224409&w=2 for more information.

Steps to reproduce:
===
1. Create service impl class and custom exception class as follows
public class CustomexceptionService {

  public int addOneToPositiveValue(int value) throws CustomException {
if(value < 1) {
throw(new CustomException());
}
   
return(value + 1);
}
}

public class CustomException extends Exception{

 private static final long serialVersionUID = 9;
public CustomException() {
super();
}
public String toString() {
return(super.toString() + "org.test.CustomException");
}

}

2. Create a service archive and deploy the service
3. Generate client stub using the ?wsdl of the service
wsdl2java.bat -uri 
http://10.100.1.118:9762/services/CustomExceptionService?wsdl -o 
C:\wsas\wsas-2.2\qa-build2\wso2wsas-SNAPSHOT\bin\out -p org.mytest
4. Check the generated stub



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: java2wsdl maven2 plugin is broken

[Charitha Kankanamge]

Hi Virgil,
I'm sorry I have updated the axis2 docs for WSDL2Code maven plugin, Not 
for java2wsdl. However, you will be able to update your pom.xml for 
java2wsdl by using the following.



   
   
   org.apache.axis2
   axis2-java2wsdl-maven-plugin
   1.3
   
   
   
   java2wsdl
   
   
   com.foo.myservice.MyHandler
   
   
   
   
   
   

regards
Charitha

Trasca Virgil wrote:


Hi,

 Until this will be applied on the oficiall apache axis2 site can you please 
send me the full and correct pom.xml for using java2wsdl?

Thank you,
Virgil

- Original Message 
From: Charitha Kankanamge <[EMAIL PROTECTED]>
To: axis-dev@ws.apache.org
Sent: Tuesday, December 18, 2007 8:38:15 AM
Subject: Re: java2wsdl maven2 plugin is broken


Trasca Virgil wrote:

 

3) if you check 

   

http://ws.apache.org/axis2/tools/1_3/maven-plugins/maven-java2wsdl-plugin.html 
 


you will see

org.apache.axis2.maven2. Is this entry on apache
   


site wrong? I tried this and is not working. I get no
 


wsdl file.


   

Yes. This is a bug in the site. I have resolved it in the axis2 trunk 
documents. Please see https://issues.apache.org/jira/browse/AXIS2-3288


regards
Charitha

 


Thank you,
Virgil



- Original Message 
From: Saminda Abeyruwan <[EMAIL PROTECTED]>
To: axis-dev@ws.apache.org
Sent: Monday, December 17, 2007 9:29:14 PM
Subject: Re: java2wsdl maven2 plugin is broken

It should be

org.apache.axis2
   axis2-aar-maven-plugin


not
org.apache.axis2.maven2


On Dec 18, 2007 12:54 AM, Saminda Abeyruwan <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


   s/Axi2/Axis2


   On Dec 18, 2007 12:53 AM, Saminda Abeyruwan <[EMAIL PROTECTED]
   <mailto:[EMAIL PROTECTED]>> wrote:

   Hi,

   Axi2 1.3 related tools and Maven2 plugins are available in
   Maven2 standard repository (http://repo1.maven.org/maven2/).
   


ex:
 

  
   


http://repo1.maven.org/maven2/org/apache/axis2/axis2-wsdl2code-maven-plugin/1.3/axis2-wsdl2code-maven-plugin-1.3.jar
 


   You will be able to get this plugin without specifying any
   pluging repository in your pom.xml .

   Thank you

   Saminda



   On Dec 17, 2007 10:56 PM, Trasca Virgil
   <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
   


wrote:
 


   Hi,

  I am trying to use java2wsdl maven2 plugin. my pom.xml
   look like

  
  org.apache.axis2.maven2

axis2-java2wsdl-maven-plugin

  
  myFullClassName
  
  1.3
  


   when I call mvn java2wsdl:java2wsdl I get BUILD ERROR
   failed to resolve artifact, Unable to download artifact
   from any repository.

   Also when I try to download directly the plugin all the
   available links show Not Found - 404 error.

  
   


http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/tools/1_3/axis2-java2wsdl-maven-plugin-1.3.jar
 

  
   


<http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/tools/1_3/axis2-java2wsdl-maven-plugin-1.3.jar>
 


   All these links are broken.

   Thank you,
   Virgil



  
   


-
 


   To unsubscribe, e-mail:
   


[EMAIL PROTECTED]
 


   <mailto:[EMAIL PROTECTED]>
   For additional commands, e-mail:
   [EMAIL PROTECTED]
   <mailto:[EMAIL PROTECTED]>




   -- 
   Saminda Abeyruwan


   Senior Software Engineer
   WSO2 Inc. - www.wso2.org <http://www.wso2.org> 





   -- 
   Saminda Abeyruwan


   Senior Software Engineer
   WSO2 Inc. - www.wso2.org <http://www.wso2.org>




--
Saminda Abeyruwan

Senior Software Engineer
WSO2 Inc. - www.wso2.org <http://www.wso2.org>

   




 




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070

A bug in the hand is better than one as yet undetected



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

Re: java2wsdl maven2 plugin is broken

[Charitha Kankanamge]

Trasca Virgil wrote:

3) if you check 
http://ws.apache.org/axis2/tools/1_3/maven-plugins/maven-java2wsdl-plugin.html 
you will see


org.apache.axis2.maven2. Is this entry on apache site wrong? 
I tried this and is not working. I get no
wsdl file.
 

Yes. This is a bug in the site. I have resolved it in the axis2 trunk 
documents. Please see https://issues.apache.org/jira/browse/AXIS2-3288


regards
Charitha


Thank you,
Virgil



- Original Message 
From: Saminda Abeyruwan <[EMAIL PROTECTED]>
To: axis-dev@ws.apache.org
Sent: Monday, December 17, 2007 9:29:14 PM
Subject: Re: java2wsdl maven2 plugin is broken

It should be

org.apache.axis2
axis2-aar-maven-plugin


not
org.apache.axis2.maven2


On Dec 18, 2007 12:54 AM, Saminda Abeyruwan <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


s/Axi2/Axis2


On Dec 18, 2007 12:53 AM, Saminda Abeyruwan <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:

Hi,

Axi2 1.3 related tools and Maven2 plugins are available in
Maven2 standard repository (http://repo1.maven.org/maven2/). ex:


http://repo1.maven.org/maven2/org/apache/axis2/axis2-wsdl2code-maven-plugin/1.3/axis2-wsdl2code-maven-plugin-1.3.jar

You will be able to get this plugin without specifying any
pluging repository in your pom.xml .

Thank you

Saminda



On Dec 17, 2007 10:56 PM, Trasca Virgil
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

Hi,

   I am trying to use java2wsdl maven2 plugin. my pom.xml
look like

   
   org.apache.axis2.maven2
 
 axis2-java2wsdl-maven-plugin

   
   myFullClassName
   
   1.3
   


when I call mvn java2wsdl:java2wsdl I get BUILD ERROR
failed to resolve artifact, Unable to download artifact
from any repository.

Also when I try to download directly the plugin all the
available links show Not Found - 404 error.


http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/tools/1_3/axis2-java2wsdl-maven-plugin-1.3.jar

<http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/tools/1_3/axis2-java2wsdl-maven-plugin-1.3.jar>

All these links are broken.

Thank you,
Virgil




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




-- 
Saminda Abeyruwan


Senior Software Engineer
WSO2 Inc. - www.wso2.org <http://www.wso2.org> 





-- 
Saminda Abeyruwan


Senior Software Engineer
WSO2 Inc. - www.wso2.org <http://www.wso2.org>




--
Saminda Abeyruwan

Senior Software Engineer
WSO2 Inc. - www.wso2.org <http://www.wso2.org>




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070

A bug in the hand is better than one as yet undetected



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

[jira] Created: (AXIS2-3397) Incorrectly handled java.net.URI data type in the generated schema

[Charitha Kankanamge (JIRA)]

Incorrectly handled java.net.URI data type in the generated schema
--

 Key: AXIS2-3397
 URL: https://issues.apache.org/jira/browse/AXIS2-3397
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: nightly
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Amila Chinthaka Suriarachchi
Priority: Critical


I have a pojo with the following method.

public URI echoURI(URI inuri){
return inuri;
}

When exposing this as a web service in Axis2 , the generated schema (?xsd) is 
invalid. See the following excerpt from the schema.

















The relevant schema element type should be anyURI.




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3388) Hotupdate seems to be broken in the latest snapshots

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3388:
---

Attachment: charithacal.rar

Attached service

> Hotupdate seems to be broken in the latest snapshots
> 
>
> Key: AXIS2-3388
> URL: https://issues.apache.org/jira/browse/AXIS2-3388
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: nightly
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Priority: Blocker
> Attachments: charithacal.rar
>
>
> Hotupdate does not work with the latest snapshot builds.
> Given below are the steps to reproduce the issue.
> 1. Enable hotupdate in axis2.xml
> 2. Deploy the attached service (Which is an exploded service, hence unzip the 
> archive and copy in to /repository/services directory)
> 3. Open the services.xml and uncomment the  element
> 4. Enter ?wsdl url and check policy element
> the change will not be affected. 
> I tested the above scenario with axis2-1.3 and hotupdate worked fine with 
> that. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3388) Hotupdate seems to be broken in the latest snapshots

[Charitha Kankanamge (JIRA)]

Hotupdate seems to be broken in the latest snapshots


 Key: AXIS2-3388
 URL: https://issues.apache.org/jira/browse/AXIS2-3388
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: deployment
Affects Versions: nightly
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Priority: Blocker


Hotupdate does not work with the latest snapshot builds.
Given below are the steps to reproduce the issue.

1. Enable hotupdate in axis2.xml
2. Deploy the attached service (Which is an exploded service, hence unzip the 
archive and copy in to /repository/services directory)
3. Open the services.xml and uncomment the  element
4. Enter ?wsdl url and check policy element

the change will not be affected. 

I tested the above scenario with axis2-1.3 and hotupdate worked fine with that. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3382) NPE throws when invoking jax-ws calculator sample service

[Charitha Kankanamge (JIRA)]

NPE throws when invoking jax-ws calculator sample service
-

 Key: AXIS2-3382
 URL: https://issues.apache.org/jira/browse/AXIS2-3382
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Lahiru Sandakith
Priority: Critical


- Deploy jaxws-calculator-1.3.aar (Either in tomcat or standalone axis2 server)
- Issue the following request
  http://127.0.0.1:8080/axis2/services/CalculatorService/add?value1=1&value2=3 

You will get java.lang.NullPointerException

This issue has been reported by a user in the axis2 user list as well. 



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3379) wsdl2 codegen fails if the wsdl2 includes schema imports

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3379:
---

Attachment: calculatorImportSchema.aar

attached service archive

> wsdl2 codegen fails if the wsdl2 includes schema imports
> 
>
> Key: AXIS2-3379
> URL: https://issues.apache.org/jira/browse/AXIS2-3379
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: wsdl
>Affects Versions: 1.3
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Assignee: Keith Godwin Chapman
>Priority: Blocker
> Attachments: calculatorImportSchema.aar
>
>
> wsdl2 codegen fails with the following exception if the wsdl2 document 
> includes schema imports.
> Service archive is attached here with.
> C:\Axis2\Axis2-1.3\axis2-1.3\bin>wsdl2java.bat -uri 
> http://10.100.1.118:9762/services/calculatorImportSchema?wsdl2 -wv 2 -o 
> C:\Axis2\Axis2-1.3\axis2-1.3\bin\out
> Using AXIS2_HOME:   C:\Axis2\Axis2-1.3\axis2-1.3
> Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_12
> Exception in thread "main" 
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
> at 
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:147)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: org.apache.axis2.AxisFault
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
> at 
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateService(WSDL20ToAxisServiceBuilder.java:236)
> at 
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:101)
> ... 2 more
> Caused by: java.lang.NullPointerException
> at 
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.createAxisMessage(WSDL20ToAxisServiceBuilder.java:976)
> at 
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateOperations(WSDL20ToAxisServiceBuilder.java:926)
> at 
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.processInterface(WSDL20ToAxisServiceBuilder.java:849)
> at 
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.processService(WSDL20ToAxisServiceBuilder.java:306)
> at 
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateService(WSDL20ToAxisServiceBuilder.java:233)
> ... 3 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3379) wsdl2 codegen fails if the wsdl2 includes schema imports

[Charitha Kankanamge (JIRA)]

wsdl2 codegen fails if the wsdl2 includes schema imports


 Key: AXIS2-3379
 URL: https://issues.apache.org/jira/browse/AXIS2-3379
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Keith Godwin Chapman
Priority: Blocker


wsdl2 codegen fails with the following exception if the wsdl2 document includes 
schema imports.

Service archive is attached here with.

C:\Axis2\Axis2-1.3\axis2-1.3\bin>wsdl2java.bat -uri 
http://10.100.1.118:9762/services/calculatorImportSchema?wsdl2 -wv 2 -o 
C:\Axis2\Axis2-1.3\axis2-1.3\bin\out
Using AXIS2_HOME:   C:\Axis2\Axis2-1.3\axis2-1.3
Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_12
Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL

at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:147)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.AxisFault
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateService(WSDL20ToAxisServiceBuilder.java:236)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:101)
... 2 more
Caused by: java.lang.NullPointerException
at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.createAxisMessage(WSDL20ToAxisServiceBuilder.java:976)
at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateOperations(WSDL20ToAxisServiceBuilder.java:926)
at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.processInterface(WSDL20ToAxisServiceBuilder.java:849)
at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.processService(WSDL20ToAxisServiceBuilder.java:306)
at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateService(WSDL20ToAxisServiceBuilder.java:233)
... 3 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: JAX-WS: problems with annotated methods

[Charitha Kankanamge]

Hi Nick,

Nicholas L Gallardo wrote:


Keith,

Are you talking about a JAX-WS specific deployer, or the POJO 
deployer? I'm not aware of a JAX-WS specific one, but certainly agree 
that one is needed.


My guess as to what's happening...

Right now, we have POJO deployment, but we don't have good JAX-WS 
integration into the deployment infrastructure. You're bean is being 
picked up as a POJO and deployed as such which is where the 
"echoMethod" entry is coming from.


Then, when your request hits the JAXWSMessageReceiver the first time, 
the JAX-WS layer goes through its own metadata initialization. This 
includes building up not only a 
EndpointDescription/OperationDescription, but a set of 
AxisService/AxisOperation objects to match. These are being mapped to 
"echomethodString" which is where the other entry comes from.


When you say "It takes echoMethod and echomethodString as two 
different methods.", what exactly do you mean there? They are 
reflected as two operations in the WSDL?


If you deploy the jax-ws service and access http://localhost:8080/axis2, 
you should see the above two methods as available operations of the 
service. As I explained in the first mail, I did not include a wsdl in 
the service jar.




To the point of the WSDL 1.1 generation, that leads me to believe this 
isn't being deployed as a JAX-WS endpoint at all. We've known for a 
while that since we don't have formal tooling for JAX-WS that there is 
no generation. I'm guessing that you're endpoint is being deployed as 
a normal POJO endpoint using the base Axis2 runtime instead of JAX-WS.


Regards,

-Nick


Inactive hide details for "keith chapman" 
<[EMAIL PROTECTED]>"keith chapman" <[EMAIL PROTECTED]>



*"keith chapman" <[EMAIL PROTECTED]>*

11/20/2007 01:49 AM
Please respond to
axis-dev@ws.apache.org



To

axis-dev@ws.apache.org

cc


Subject

Re: JAX-WS: problems with annotated methods




Hi,

This is due to a bug in the jaxws deployer and MessageReceiver. This 
can be solved as follows,


During deployment name the axisOperation according to the annotation 
("echomethodString") in this case and put a parameter into the 
axisOperation stating the actual method name, therefore in the 
messageReceiver we know which method to call. Can somebody familiar 
with JaxWS code do this fix please.


Thanks,
Keith.
On Nov 20, 2007 11:42 AM, Charitha Kankanamge <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


  Hi devs,

  I was trying to deploy jax-ws based service using axis2. Here is my
  service impl class. please note that, I did not include any wsdl
  inside
  the service jar.

  @WebService(name= "WSASJAX_Service2", targetNamespace =
  "_http://www.webtest.org/jaxws_";)
  public class jaxwsservice2 {
  @WebMethod(operationName = "echomethodString")
  public String echoMethod(String s){
  return s;
  }

  }

  Axis2 does not handle this service correctly. It takes
  echoMethod and
  echomethodString as two different methods. Also Axis2 was unable to
  generate wsdl1.1 using the above service impl class. WSDL
  generation was
  successful when I removed the annotation members of @WEbMethod
  annotation.

  It seems that the Axis2 JAX-WS implementation is unable to
  handle some
  of the annotations which have annon members. I reported a JIRA
  for this
  issue at _https://issues.apache.org/jira/browse/AXIS2-3352_

  since this is a fundamental scenario, it will be great if this is
  resolved ASAP.

  Please let me know if there are any issues in the above steps
  which were
  used to generate jax-ws service.

  regards
  Charitha




  -

  To unsubscribe, e-mail: [EMAIL PROTECTED]
  <mailto:[EMAIL PROTECTED]>
  For additional commands, e-mail: [EMAIL PROTECTED] _
  <mailto:[EMAIL PROTECTED]>




--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers._
__http://wso2.org/_




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070

A bug in the hand is better than one as yet undetected



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

[jira] Created: (AXIS2-3365) Code generation fails if a wsdl has schema imports and that wsdl is included in a service archive with useOriginalWsdl = true

[Charitha Kankanamge (JIRA)]

Code generation fails if a wsdl has schema imports and that wsdl is included in 
a service archive with useOriginalWsdl = true
-

 Key: AXIS2-3365
 URL: https://issues.apache.org/jira/browse/AXIS2-3365
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: adb
Affects Versions: 1.3
 Environment: Any
Reporter: Charitha Kankanamge
Assignee: Amila Chinthaka Suriarachchi
Priority: Critical


Steps to reproduce:

1. Create a service archive with including a WSDL which has schema import as 
follows.

http://charitha.org/"; 
schemaLocation="http://localhost/repo/calculator.xsd"/>

As you can see above, the schema is hosted in a URL repo.

2. Set useOriginalWsdl=true in services.xml
3. Deploy the service
4. Try to generate client using ?wsdl of the deployed service

Following exception occurs.
Retrieving schema at 
'calculatorService?xsd=http://localhost/repo/calculator.xsd', relative to 'http
://localhost:8080/axis2/services/'.
Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL

at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:150)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: javax.wsdl.WSDLException: WSDLException (at 
/wsdl:definitions/wsdl:types/xsd:schema): fau
ltCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 
'calculatorService?xsd=
http://localhost/repo/calculator.xsd', relative to 
'http://localhost:8080/axis2/services/'.: java.io
.IOException: Server returned HTTP response code: 500 for URL: 
http://localhost:8080/axis2/services/
calculatorService?xsd=http://localhost/repo/calculator.xsd
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:286)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:105)
... 2 more
Caused by: java.io.IOException: Server returned HTTP response code: 500 for 
URL: 
http://localhost:8080/axis2/services/calculatorService?xsd=http://localhost/repo/calculator.xsd
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1170)
at java.net.URL.openStream(URL.java:1007)
at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown Source)
... 11 more
 
This occurs due to the following schema reference in the generated wsdl, which 
is invalid.
schemaLocation="calculatorService?xsd=http://localhost/repo/calculator.xsd";




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: AXIS2 : AxisServlet failed to preload on startup in Web Application

[Charitha Kankanamge]

Hey Viru,

Please configure axis2/weblogic8.1 as specified in 
http://ws.apache.org/axis2/1_3/app_server.html


regards
Charitha

Hosamath, Viru wrote:


Hi,

I have downloaded AXIS2 and deployed axis2.war on weblogic 8.1.

But, getting this exception - any idea?



 




Cingular is now the new AT&T
12555 Cingular Way
Alpharetta GA 30004
Work : (678) 893 3176
Cell : (770) 401 9424
Email: [EMAIL PROTECTED]

-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 20, 2007 3:24 PM

To: axis-dev@ws.apache.org
Subject: Re: New to Axis2 - Need help.

On Nov 20, 2007 1:08 PM, Hosamath, Viru <[EMAIL PROTECTED]> wrote:
 


All,

I'm new to Apache Axis2, I have downloaded Axis 1.4 release.

   



First step: know what you are running. There is no released 1.4 for
Axis2 - you are most likely running the legacy Axis 1.x series. I
recommend the latest Axis2 version 1.3 and to read the docs:

http://ws.apache.org/axis2/

HTH,
Robert

-
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]



 




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070

A bug in the hand is better than one as yet undetected



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

JAX-WS: problems with annotated methods

[Charitha Kankanamge]

Hi devs,

I was trying to deploy jax-ws based service using axis2. Here is my 
service impl class. please note that, I did not include any wsdl inside 
the service jar.


@WebService(name= "WSASJAX_Service2", targetNamespace = 
"http://www.webtest.org/jaxws";)

public class jaxwsservice2 {
   @WebMethod(operationName = "echomethodString")
   public String echoMethod(String s){
   return s;
   }

}

Axis2 does not handle this service correctly. It takes echoMethod and 
echomethodString as two different methods. Also Axis2 was unable to 
generate wsdl1.1 using the above service impl class. WSDL generation was 
successful when I removed the annotation members of @WEbMethod annotation.


It seems that the Axis2 JAX-WS implementation is unable to handle some 
of the annotations which have annon members. I reported a JIRA for this 
issue at https://issues.apache.org/jira/browse/AXIS2-3352


since this is a fundamental scenario, it will be great if this is 
resolved ASAP.


Please let me know if there are any issues in the above steps which were 
used to generate jax-ws service.


regards
Charitha




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

[jira] Reopened: (AXIS2-2477) Unusual service name/epr is presented when a pojo annotation class is deployed

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge reopened AXIS2-2477:



This is not fixed. Retested in axis2-1.3.

> Unusual service name/epr is presented when a pojo annotation class is 
> deployed 
> ---
>
> Key: AXIS2-2477
> URL: https://issues.apache.org/jira/browse/AXIS2-2477
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: jaxws
>Affects Versions: 1.2
> Environment: jdk15, tomcat 6.0.10
>    Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>
> I created a pojo with annotation and named it as 'HelloWorldService'. Then I 
> deployed it on tomcat 6.0.10 and accessed admin console to see the service.
> Following is the name of service shown in admin console.
> HelloWorldServiceService.HelloWorldServicePort
> EPR is given as 
> http://localhost:8080/axis2/services/HelloWorldServiceService.HelloWorldServicePort

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3352) JAX-WS: wsdl11 generation fails if @WebMethod annotation is specified with member values

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3352:
---

Description: 
It seems the axis2 JAX_WS implementation has a lot of problems. For example, I 
wrote the following service implementation class.

@WebService(name= "WSASJAX_Service2", targetNamespace = 
"http://www.charitha.org/jaxws";)
public class jaxwsservice2 {
@WebMethod(operationName = "echomethodString")
public String echoMethod(String s){
return s;
}

}

Then I deployed this as a jar in axis2. I noticed that Axis2 failed to generate 
wsdl11. Also Axis2 takes service method and annotated method name as two 
different operations.
Axis2 admin page lists down the above as two available operations

* echoMethod
* echomethodString

Please note that I did not include any wsdl inside the jar. It just contained 
the service impl class. 


  was:
It seems the axis2 JAX_WS implementation hava a lot of problems. For example, I 
wrote the following service implementation class.

@WebService(name= "WSASJAX_Service2", targetNamespace = 
"http://www.charitha.org/jaxws";)
public class jaxwsservice2 {
@WebMethod(operationName = "echomethodString")
public String echoMethod(String s){
return s;
}

}

Then I deployed this as a jar in axis2. I noticed that Axis2 failed to generate 
wsdl11. Also Axis2 takes service method and annotated method name as two 
different operations.
Axis2 admin page lists down the above as two available operations

* echoMethod
* echomethodString

Please note that I did not include any wsdl inside the jar. It just contained 
the service impl class. 



> JAX-WS: wsdl11 generation fails if @WebMethod annotation is specified with 
> member values
> 
>
> Key: AXIS2-3352
> URL: https://issues.apache.org/jira/browse/AXIS2-3352
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: jaxws
>    Affects Versions: 1.3
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Priority: Blocker
>
> It seems the axis2 JAX_WS implementation has a lot of problems. For example, 
> I wrote the following service implementation class.
> @WebService(name= "WSASJAX_Service2", targetNamespace = 
> "http://www.charitha.org/jaxws";)
> public class jaxwsservice2 {
>   @WebMethod(operationName = "echomethodString")
>   public String echoMethod(String s){
>   return s;
>   }
> }
> Then I deployed this as a jar in axis2. I noticed that Axis2 failed to 
> generate wsdl11. Also Axis2 takes service method and annotated method name as 
> two different operations.
> Axis2 admin page lists down the above as two available operations
> * echoMethod
> * echomethodString
> Please note that I did not include any wsdl inside the jar. It just contained 
> the service impl class. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3352) JAX-WS: wsdl11 generation fails if @WebMethod annotation is specified with member values

[Charitha Kankanamge (JIRA)]

JAX-WS: wsdl11 generation fails if @WebMethod annotation is specified with 
member values


 Key: AXIS2-3352
 URL: https://issues.apache.org/jira/browse/AXIS2-3352
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: jaxws
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Priority: Blocker


It seems the axis2 JAX_WS implementation hava a lot of problems. For example, I 
wrote the following service implementation class.

@WebService(name= "WSASJAX_Service2", targetNamespace = 
"http://www.charitha.org/jaxws";)
public class jaxwsservice2 {
@WebMethod(operationName = "echomethodString")
public String echoMethod(String s){
return s;
}

}

Then I deployed this as a jar in axis2. I noticed that Axis2 failed to generate 
wsdl11. Also Axis2 takes service method and annotated method name as two 
different operations.
Axis2 admin page lists down the above as two available operations

* echoMethod
* echomethodString

Please note that I did not include any wsdl inside the jar. It just contained 
the service impl class. 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [VOTE] Sanjaya Karunasena as an Axis2 commiter

[Charitha Kankanamge]

+1

thanks!
Charitha

Deepal Jayasinghe wrote:


Hi all,

Sanjaya Karunasena has done enough work to become as a commiter , he has
implemented fastinforset [FI] support in Axis2. And giving he commiter
access will encourage him to contribute some more to the project and
will make our job easier [no need to commit the patches].

Here my +1 for Sanjaya as an Axis2 commiter.

Thanks
Deepal



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



 




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070

A bug in the hand is better than one as yet undetected



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

[jira] Commented: (AXIS2-3274) Axis2 kernel logging on WAS 6.1

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3274:


Hi Pierre,
I couldn't reproduce this error with Websphere6.1/Axis21.3 on Winxp. I tried by 
deploying a service but did not get LogConfiguration exception. The only 
additional step i did was, set the application class loader first while 
deploying axis2.war. If you still experience this issue, please provide us 
detailed steps to reproduce the problem with the necessary services archives 
etc..

thanks
Charitha 

> Axis2 kernel logging on WAS 6.1
> ---
>
> Key: AXIS2-3274
> URL: https://issues.apache.org/jira/browse/AXIS2-3274
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: kernel
>Affects Versions: 1.3
> Environment: Axis2 1.3 under Websphere 6.1
>Reporter: Pierre Casenove
>Assignee: Charitha Kankanamge
>Priority: Minor
>
>  When deploying Axis2 based application, websphere tries to instantiates 
> AxisServlet and throws following exception:
>  Caused by: org.apache.commons.logging.LogConfigurationException:
>  java.lang.ClassNotFoundException:
>  org.apache.commons.logging.impl.Log4jFactory
>at 
> org.apache.commons.logging.LogFactory$2.run(LogFactory.java:609)
>at 
> java.security.AccessController.doPrivileged(AccessController.java:193)
>at 
> org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:561)
>at 
> org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:352)
>at 
> org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
>at
>  org.apache.axis2.transport.http.AxisServlet.(AxisServlet.java:79)
>  The root cause is explained here :
>  
> http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions?highlight=%28websphere%29
>  In order to get everything works, I had to modify axis2-kernel.jar to add a 
> commons-logging.properties containing:
>  priority=1
>  
> org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
>  org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
> I tried to first put this file in my web app classpath but it didn't work.
> The only solution was to put it in Axis2 Kernel jar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3339) axis2-wsdl2code-maven-plugin-1.3.jar is not available in the suggested mirror

[Charitha Kankanamge (JIRA)]

axis2-wsdl2code-maven-plugin-1.3.jar is not available in the suggested mirror
-

 Key: AXIS2-3339
 URL: https://issues.apache.org/jira/browse/AXIS2-3339
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: Tools
Reporter: Charitha Kankanamge
Priority: Critical


axis2-wsdl2code-maven-plugin-1.3.jar is not available in the suggested mirror 
site. please update this reference.

Suggested mirror is 
http://government-grants.org/mirrors/apache.org/ws/axis2/tools/1_3/axis2-wsdl2code-maven-plugin-1.3.jar

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Resolved: (AXIS2-3307) Incorrect configuration in maven-wsdl2code-plugin.html doc

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge resolved AXIS2-3307.


   Resolution: Fixed
Fix Version/s: nightly

Fixed in trunk revision 594441.

> Incorrect configuration in maven-wsdl2code-plugin.html doc
> --
>
> Key: AXIS2-3307
> URL: https://issues.apache.org/jira/browse/AXIS2-3307
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>    Assignee: Charitha Kankanamge
>Priority: Critical
> Fix For: nightly
>
>
> XML configuration of the pom is wrong in maven-wsdl2code-plugin.html. It 
> should be corrected as follows.
> 
> org.apache.axis2
> axis2-wsdl2code-maven-plugin
> 1.3
> 
>   
> 
>   wsdl2code
> 
>   
>  com.your.package
>   src/main/wsdl/yourfile.wsdl
>   xmlbeans  
> 
>   
> 
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Assigned: (AXIS2-3307) Incorrect configuration in maven-wsdl2code-plugin.html doc

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge reassigned AXIS2-3307:
--

Assignee: Charitha Kankanamge  (was: Sanka Samaranayake)

> Incorrect configuration in maven-wsdl2code-plugin.html doc
> --
>
> Key: AXIS2-3307
> URL: https://issues.apache.org/jira/browse/AXIS2-3307
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>    Assignee: Charitha Kankanamge
>Priority: Critical
> Fix For: nightly
>
>
> XML configuration of the pom is wrong in maven-wsdl2code-plugin.html. It 
> should be corrected as follows.
> 
> org.apache.axis2
> axis2-wsdl2code-maven-plugin
> 1.3
> 
>   
> 
>   wsdl2code
> 
>   
>  com.your.package
>   src/main/wsdl/yourfile.wsdl
>   xmlbeans  
> 
>   
> 
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Resolved: (AXIS2-3257) fix documentation on the axis2 website

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge resolved AXIS2-3257.


Resolution: Fixed

Fixed in Axis2 trunk revision 594441

> fix documentation on the axis2 website
> --
>
> Key: AXIS2-3257
> URL: https://issues.apache.org/jira/browse/AXIS2-3257
> Project: Axis 2.0 (Axis2)
>  Issue Type: Task
>  Components: documentation, samples, build,site
>Affects Versions: 1.3, 1.2, 1.1.1, 1.1
> Environment: Axis2 website
>Reporter: Hellmut Adolphs
>    Assignee: Charitha Kankanamge
> Fix For: 1.4
>
>
> The right configuration inside the POM should be for example something like 
> this:
>  
> org.apache.axis2
> axis2-wsdl2code-maven-plugin
> 1.3
> 
>   
> 
>   wsdl2code
> 
>   
>  com.your.package
>src/main/wsdl/yourfile.wsdl
>xmlbeans 
>  
>   
> 
>  
> NOT this:
> 
> 
>
>   org.apache.axis2.maven2
>   axis2-wsdl2code-maven-plugin
>   
>   
>   
>   wsdl2code
>   
>
>   
>   com.foo.myservice
>   
>  
>   
> 
> 
> In particular configuration belongs inside execution not executions.  This is 
> causing a lot of confusion for some people out there...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Resolved: (AXIS2-3288) Maven2 WSDL2Code Plug-in Guide has incorrect and missing descriptions.

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge resolved AXIS2-3288.


   Resolution: Fixed
Fix Version/s: nightly

Fixed in Axis2 trunk revision 594441. 

> Maven2 WSDL2Code Plug-in Guide has incorrect and missing descriptions.
> --
>
> Key: AXIS2-3288
> URL: https://issues.apache.org/jira/browse/AXIS2-3288
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3
>Reporter: Naozo Yoshioka
>Assignee: Charitha Kankanamge
> Fix For: nightly
>
>
> Maven2 WSDL2Code Plug-in Guide
> http://ws.apache.org/axis2/tools/1_3/maven-plugins/maven-wsdl2code-plugin.html
> incorrect and missing descriptions like below.
> org.apache.axis2.maven2
> must be replaced by
> org.apache.axis2
> Map of namespace URI to packages. Example:   
> uri1 package1   
> 
> must be replaced by
> Map of namespace URI to packages. Example:   
> uri1 package1   
> 
> The row for unwarp is missing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3309) NPE throws when starting axis2server if NIO https transport is enabled in axis2.xml

[Charitha Kankanamge (JIRA)]

NPE throws when starting axis2server if NIO https transport is enabled in 
axis2.xml
---

 Key: AXIS2-3309
 URL: https://issues.apache.org/jira/browse/AXIS2-3309
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Priority: Critical


- Uncomment  section and NIO https transport receiver section in 
axis2.xml
- Restart Axis2 server

Startup fails with the following exception.
[FATAL] [SimpleAxisServer] Shutting down. Error starting SimpleAxisServer
java.lang.NullPointerException
at 
org.apache.axis2.transport.nhttp.HttpCoreNIOSSLSender.getSSLContext(HttpCoreNIOSSLSender.
java:81)
at 
org.apache.axis2.transport.nhttp.HttpCoreNIOSender.init(HttpCoreNIOSender.java:96)
at 
org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationCo
ntextFactory.java:270)
at 
org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.jav
a:201)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura
tionContextFactory.java:76)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSy
stem(ConfigurationContextFactory.java:180)
at 
org.apache.axis2.transport.SimpleAxis2Server.(SimpleAxis2Server.java:50)
at 
org.apache.axis2.transport.SimpleAxis2Server.main(SimpleAxis2Server.java:101)
[SimpleAxisServer] Shutting down. Error starting SimpleAxisServer

in this case, Axis2server cannot be started due to absence of the default trust 
store and keystore files. However the error does not indicate anything about 
the actual reason.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (AXIS2-3307) Incorrect configuration in maven-wsdl2code-plugin.html doc

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3307:


Please check bug id=AXIS2-3255 for more information.

> Incorrect configuration in maven-wsdl2code-plugin.html doc
> --
>
> Key: AXIS2-3307
> URL: https://issues.apache.org/jira/browse/AXIS2-3307
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Priority: Critical
>
> XML configuration of the pom is wrong in maven-wsdl2code-plugin.html. It 
> should be corrected as follows.
> 
> org.apache.axis2
> axis2-wsdl2code-maven-plugin
> 1.3
> 
>   
> 
>   wsdl2code
> 
>   
>  com.your.package
>   src/main/wsdl/yourfile.wsdl
>   xmlbeans  
> 
>   
> 
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3307) Incorrect configuration in maven-wsdl2code-plugin.html doc

[Charitha Kankanamge (JIRA)]

Incorrect configuration in maven-wsdl2code-plugin.html doc
--

 Key: AXIS2-3307
 URL: https://issues.apache.org/jira/browse/AXIS2-3307
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Priority: Critical


XML configuration of the pom is wrong in maven-wsdl2code-plugin.html. It should 
be corrected as follows.


org.apache.axis2
axis2-wsdl2code-maven-plugin
1.3

  

  wsdl2code

  
 com.your.package
  src/main/wsdl/yourfile.wsdl
  xmlbeans  

  

 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3306) Documentation/samples are not up-to-date with Callback API changes

[Charitha Kankanamge (JIRA)]

Documentation/samples are not up-to-date with Callback API changes
--

 Key: AXIS2-3306
 URL: https://issues.apache.org/jira/browse/AXIS2-3306
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: documentation, samples
Affects Versions: 1.3
Reporter: Charitha Kankanamge


Callback class is deprecated in Axis2-1.3, however  the documents and samples 
are not updated accordingly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3299) Interop issue: Utf16 Mtom failure with MS WCF

[Charitha Kankanamge (JIRA)]

Interop issue: Utf16 Mtom failure with MS WCF 
--

 Key: AXIS2-3299
 URL: https://issues.apache.org/jira/browse/AXIS2-3299
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
 Environment: server=WCF, Client=jdk15/axis2-1.3/winxp
Reporter: Charitha Kankanamge
Assignee: Thilina Gunarathne
Priority: Blocker


Interop fails with following exception when mtom is used with utf 16 encoding.

org.apache.axis2.AxisFault: The input stream for an incoming message is null.
at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:71)
at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at 
org.tempuri.MtomServiceStub.EchoBinaryAsString(MtomServiceStub.java:239)
at 
org.tempuri.tempuri.mtom.soap11.utf16.MtomServiceSoap11Utf16StubTest.testEchoBinaryAsString(MtomServiceSoap11Utf16StubTest.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Steps to reproduce


 - Generate client stubs using the following MS Interop endpoint 
   http://131.107.72.15/MTOM_Service_Indigo/Soap11MtomUtf16.svc?wsdl 
- Write a client and try to invoke service

ie:-
public class MtomServiceSoap11Utf16StubTest extends TestCase {

MtomServiceStub stub = null;

protected void setUp() throws Exception {
stub = new 
MtomServiceStub("http://131.107.72.15/MTOM_Service_Indigo/Soap11MtomUtf16.svc/MtomTest";);

stub._getServiceClient().getOptions().setProperty(Constants.Configuration.ENABLE_MTOM,
 Constants.VALUE_TRUE);

stub._getServiceClient().getOptions().setProperty(Constants.Configuration.CHARACTER_SET_ENCODING,"utf-16");

//
stub._getServiceClient().getOptions().setProperty(Constants.Configuration.TRANSPORT_URL,
//
"http://localhost:8085/MTOM_Service_Indigo/Soap11MtomUtf16.svc/MtomTest";);
   
stub._getServiceClient().getOptions().setProperty(Constants.Configuration.TRANSPORT_URL,

"http://localhost:8085/MTOM_Service_Indigo/Soap11MtomUtf16.svc/MtomTest";);
}

public void testEchoBinaryAsString() {

String testString = "new test string";
DataHandler dataHandler = new DataHandler(new 
ByteArrayDataSource(testString.getBytes()));
try {
String returnStirng = stub.EchoBinaryAsString(dataHandler);
assertEquals(returnStirng, "new test string");
} catch (RemoteException e) {
e.printStackTrace();
fail();
}
}

public void testEchoStringAsBinary() {
String testString = "new test string";
try {
DataHandler dataHandler = stub.EchoStringAsBinary(testString);
String result = getStringFromDataHandler(dataHandler);
assertEquals(result,"new test string");
} catch (RemoteException e) {
fail();
} catch (IOException e) {
fail();
}
}

public void testEchoBinaryArrayAsStringArray() {

String testString = "new test string";
DataHandler dataHandlers[] = new DataHandler[2];
dataHandlers[0] = new DataHandler(new 
ByteArrayDataSource(testString.getBytes()));
dataHandlers[1] = new DataHandler(new 
ByteArrayDataSource(testString.getBytes()));

ArrayOfbase64Binary arrayOfbase64Binary = new ArrayOfbase64Binary();
arrayOfbase64Binary.setBase64Binary(dataHandlers);

try {
String[] result = 
stub.EchoBinaryArrayAsStringArray(arrayOfbase64Binary).getString();
assertEquals(result.length,2);
assertEquals(result[0],"new test string");
assertEquals(result[1],"new test string");
} catch (RemoteException e) {
fail();
}

}

public void testEchoBinaryFieldAsString() {

String testString = "new test string";
DataHandler dataHandler = new DataHandler(new 
ByteArrayDataSource(testString.getBytes()));
MtomTestStruct mtomTestStruct = new MtomTestStruct();
mtomTestStruct.setName("test data");
mtomTestStruct.setArray(dataHandler);
try {
String result = stub.EchoBinaryFieldAsString(mtomTestStruct);
   

[jira] Created: (AXIS2-3241) Stubs generated for all the ports in wsdl2 code generation

[Charitha Kankanamge (JIRA)]

Stubs generated for all the ports in wsdl2 code generation
--

 Key: AXIS2-3241
 URL: https://issues.apache.org/jira/browse/AXIS2-3241
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.3
Reporter: Charitha Kankanamge
Assignee: Keith Godwin Chapman
Priority: Critical


Multiple set of stubs are generated if wsdl2 is used. Please make wsdl1.1 and 
wsdl2 code generation consistent by setting default port (Soap12 port as in 
wsdl1.1)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3239) Custom fault handling issue in code-first approach

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3239:
---

Attachment: Faultclient.java
userTest-test-client.jar
AxisFaultservice.aar

Attached service archive, generated stub jar and client source

> Custom fault handling issue in code-first approach
> --
>
> Key: AXIS2-3239
> URL: https://issues.apache.org/jira/browse/AXIS2-3239
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.3
> Environment: winxp, jdk15, 
>    Reporter: Charitha Kankanamge
>Priority: Blocker
> Attachments: AxisFaultservice.aar, Faultclient.java, 
> userTest-test-client.jar
>
>
> This issue has been identified and discussed by Jay Zawar in the following 
> mailing threads. 
> http://marc.info/?l=axis-user&m=119132155713767&w=2
> http://marc.info/?l=axis-user&m=119131613622185&w=2
> There seems to be an issue with custom fault handling when code-first 
> approach is used. Axis2 Faulthandling sample works fine since it is used 
> contract-first method.  
> Steps to reproduce:
> ===
> 1. Write the service implementation class which returns a customexception
> public class AService {
> public long Add(int a, int b, int exceptionThrown) throws CustomException {
>   
>   if (exceptionThrown != 0) {
>   System.out.println("CustomException to b 
> instantiated");
>   
>   CustomException e = new CustomException();
>   e.setCustomMsg("bar");
>   throw e;
>   }
>   
>   
>   return a+b;}
> }
> 2. Write CustomeException class 
> public class CustomException extends java.lang.Exception implements 
> Serializable{
>   private static final long serialVersionUID = 1542353156105984960L;
>   private String customMsg = "This is my error";
>   public String getCustomMsg() {return customMsg;}
>   public void setCustomMsg(String customMsg) {this.customMsg= "custom : " 
> +customMsg;}
> }
> 3. Bundle the service archive correctly and deploy it.
> 4. Generate ADB client code
> 5. Write a client 
> public class Faultclient {
>   
>   public static void main(String[] args) {
>   try {
>   UserTestStub stub;
>   stub = new 
> UserTestStub("http://localhost:9764/services/userTest";);
>   UserTestStub.Add req = new UserTestStub.Add();
>   req.setA(4);
>   req.setB(5);
>   req.setExceptionThrown(2);
>   UserTestStub.AddResponse res;
>   res = stub.Add(req);
>   System.out.println(res.get_return());
>   } catch (AxisFault e1) {
>   e1.printStackTrace();
>   e1.getCause();
>   } catch (CustomExceptionException0 e) {
>   System.out.println("Error");
>   } catch (RemoteException e) {
>   e.printStackTrace();
>   }
>   }
> 6. I'm always getting 'org.apache.axis2.AxisFault: Exception occurred while 
> trying to invoke service method Add' error at the client side, though I 
> expected customexception specified in the service.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3239) Custom fault handling issue in code-first approach

[Charitha Kankanamge (JIRA)]

Custom fault handling issue in code-first approach
--

 Key: AXIS2-3239
 URL: https://issues.apache.org/jira/browse/AXIS2-3239
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
 Environment: winxp, jdk15, 
Reporter: Charitha Kankanamge
Priority: Blocker


This issue has been identified and discussed by Jay Zawar in the following 
mailing threads. 

http://marc.info/?l=axis-user&m=119132155713767&w=2

http://marc.info/?l=axis-user&m=119131613622185&w=2

There seems to be an issue with custom fault handling when code-first approach 
is used. Axis2 Faulthandling sample works fine since it is used contract-first 
method.  

Steps to reproduce:
===
1. Write the service implementation class which returns a customexception

public class AService {
public long Add(int a, int b, int exceptionThrown) throws CustomException {

if (exceptionThrown != 0) {
System.out.println("CustomException to b 
instantiated");

CustomException e = new CustomException();
e.setCustomMsg("bar");
throw e;
}


return a+b;}
}
2. Write CustomeException class 

public class CustomException extends java.lang.Exception implements 
Serializable{
private static final long serialVersionUID = 1542353156105984960L;
private String customMsg = "This is my error";
public String getCustomMsg() {return customMsg;}
public void setCustomMsg(String customMsg) {this.customMsg= "custom : " 
+customMsg;}
}

3. Bundle the service archive correctly and deploy it.
4. Generate ADB client code
5. Write a client 

public class Faultclient {

public static void main(String[] args) {
try {
UserTestStub stub;
stub = new 
UserTestStub("http://localhost:9764/services/userTest";);
UserTestStub.Add req = new UserTestStub.Add();

req.setA(4);
req.setB(5);
req.setExceptionThrown(2);

UserTestStub.AddResponse res;
res = stub.Add(req);
System.out.println(res.get_return());
} catch (AxisFault e1) {
e1.printStackTrace();
e1.getCause();
} catch (CustomExceptionException0 e) {
System.out.println("Error");
} catch (RemoteException e) {
e.printStackTrace();
}
}

6. I'm always getting 'org.apache.axis2.AxisFault: Exception occurred while 
trying to invoke service method Add' error at the client side, though I 
expected customexception specified in the service.




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: So Long, and Thanks for All the Fish

[Charitha Kankanamge]

Hi Dims,
Wish you all the best in your future endeavors. Thanks for the enormous 
help provided for all WS projects and hope to see you again as an active 
member.


Thanks and regards
Charitha

Davanum Srinivas wrote:


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

 




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070

A bug in the hand is better than one as yet undetected



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

[jira] Updated: (AXIS2-3234) The generated WSDL2 (?wsdl2) does not have soap11, http bindings if the wsdl is included in service archive

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3234:
---

Attachment: charithacal.aar

Attached service archive

> The generated WSDL2 (?wsdl2) does not have soap11, http bindings if the wsdl 
> is included in service archive
> ---
>
> Key: AXIS2-3234
> URL: https://issues.apache.org/jira/browse/AXIS2-3234
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: wsdl
>Affects Versions: 1.3
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Priority: Critical
> Attachments: charithacal.aar
>
>
> The generated wsdl2 (?wsdl2) does not have soap11 and http bindings if a wsdl 
> is included in the service archive. 
> Steps to reproduce:
> 
> 1. Deploy the attached service archive (Which includes a wsdl in META-INF 
> directory)
> 2. Enter wsdl2 uri (http://:/axis2/services/testservice?wsdl2)
> Check "wsdl2:binding" elements. You will see only the Soap12 binding there. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3234) The generated WSDL2 (?wsdl2) does not have soap11, http bindings if the wsdl is included in service archive

[Charitha Kankanamge (JIRA)]

The generated WSDL2 (?wsdl2) does not have soap11, http bindings if the wsdl is 
included in service archive
---

 Key: AXIS2-3234
 URL: https://issues.apache.org/jira/browse/AXIS2-3234
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Priority: Critical
 Attachments: charithacal.aar

The generated wsdl2 (?wsdl2) does not have soap11 and http bindings if a wsdl 
is included in the service archive. 

Steps to reproduce:

1. Deploy the attached service archive (Which includes a wsdl in META-INF 
directory)
2. Enter wsdl2 uri (http://:/axis2/services/testservice?wsdl2)

Check "wsdl2:binding" elements. You will see only the Soap12 binding there. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [AXIS2] Nominate Roy Wood and Dustin Amrhein to COMMITTER

[Charitha Kankanamge]

+1

regards
Charitha

R J Scheuerle Jr wrote:


I would like to nominate Dustin Amrhein and Roy Wood to committer status.

Dustin is an active contributor to the metadata module.
Dustin proposed the MetaDataQuery functionality in June 2006 (AXIS2-872).
He has provided solutions to many deep issues including object 
representation, annotation
validation, SWA attachment parameter support, classloading and 
performance caching.
His contributions to the jaxws module include JAXWS executor work, 
JAXWS marshalling fixes and async timeout work.

He has provided patches for 35 JIRA issues.

Roy has been an active contributor to Axis2 since September 2006.
He contributed the initial code for collecting annotation and 
reflective class information (AXIS2-1195, etc)

This was the foundation of the metadata module.
Roy works closely with Jeff Barrett to maintain and improve the 
metadata layer code.
Roy has contributed patches for a variety of issues in the jaxws 
module, include changes that helped

us achieve JAX-WS CTS compliance with Geronimo.
Altogether Roy has contributed patches for 27 JIRA issues.

Thanks !
Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
512-838-5115 (IBM TL 678-5115)





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

[AXIS2][Fwd: MTOM attachement caching]

[Charitha Kankanamge]

forwarding with [AXIS2] prefix
--- Begin Message ---

Hi all,
MTOM attachement caching can be enabled in axis2.xm by specifying 
cacheAttachments=true with an attachment directory in file system. When 
sending a large file, it is cached in the specified directory. However, 
this temporary file (*.att) is not removed once the file transfer is 
completed. I would like to know whether this is the intended behavior or 
a bug in MTOM?


regards
Charitha


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




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

MTOM attachement caching

[Charitha Kankanamge]

Hi all,
MTOM attachement caching can be enabled in axis2.xm by specifying 
cacheAttachments=true with an attachment directory in file system. When 
sending a large file, it is cached in the specified directory. However, 
this temporary file (*.att) is not removed once the file transfer is 
completed. I would like to know whether this is the intended behavior or 
a bug in MTOM?


regards
Charitha


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

Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take3)

[Charitha Kankanamge]

Here is my +1 for 1.3 release.

All samples worked out of the box in Winxp/jdk15 environment. When 
running userguide samples, users may need to go through the associated 
xdocs (eg:- modules.html) to configure logging module.


regards
Charitha


Deepal jayasinghe wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

I have uploaded Axis2 1.3 (take3) into my Apache home location [1]
again . As a result of we found a few issues in 1.3 take2 I had to
upload the artifacts again and call for a new vote. I will keep open
the vote for 72 hrs from now and will do the Axis2 1.3 release on
Monday 13th Aug 2007.

You can find both IntelliJ idea and Eclipse plugin artifacts in the
tools folder [2]

Please try to cover the following areas when testing.
- - Code generation
- - Sessions
- - Web application
- - In different application servers
- - Both JDK 1.5 and JDK 1.4
- - Java2WSDL
- - POJOs
- - And whatever the JIRA we have marked as fixed.

You can find maven2 repository under my home directory as well [3]. I
have host the web site for 1.3 in [4] please have a look at that as well

I will do the final release on Friday (10th Aug 2007), here is my +1
for the release date as well as for release artifacts.


[1] : http://people.apache.org/~deepal/axis2/1.3-take3/
[2] : http://www-lk.wso2.com/~deepal/1.3-tools/
[3] : http://people.apache.org/~deepal/axis2/1.3-take3/m2-repo/
[4] : http://www-lk.wso2.com/~deepal/axis2/


P.S : Please note that I need to have two more PMC vote to go ahead
with the release, so please give us the support by voting for the release.


Thanks
Deepal
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGvFhvjOGcXNDx0CARAh+4AJ49M1d86/v39C6Z0WnMcxsK5RgF3QCdGD8d
43gXJ+tvuyHhc/nI1t1u1fw=
=sqos
-END PGP SIGNATURE-


-
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]

[jira] Commented: (AXIS2-3109) OMException when using the http async msg receiver

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3109:


Hi Michele,
The attached axis2.xml is invalid since It throws xml parsing error when 
opening it in a browser. Seems 'http transport receiver' section was not 
uncommented correctly. Anyway, I tried to reproduce this issue by uncommenting 
following sections in an axis2.xml in a fresh installation. 


9000
true


 
true


Also, I commented out   elements. I used your 
server.xml and placed it in tomcat/conf.
Then I restarted tomcat. I was able to access admin console and get services 
list and happyaxis page without such issue.

After that, I changed my axis2.xml to enable JMS transport as you did in your 
configuration. I got an internal server error with that change. According to 
this, there is a problem with JMS transport and NIOlistener combination and 
this is not a pure NIOListener issue.

Exception with JMS+HttpcoreNIOListener


[ERROR] javax/jms/JMSException
org.apache.axis2.deployment.DeploymentException: javax/jms/JMSException
at 
org.apache.axis2.deployment.AxisConfigBuilder.processTransportReceivers(AxisConfigBuilder.java:484)
at 
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:118)
at 
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:615)
at 
org.apache.axis2.deployment.WarBasedAxisConfigurator.(WarBasedAxisConfigurator.java:146)
at 
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
at 
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at 
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:133)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
at 
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:888)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:624)
at 
org.apache.tomcat.util.net.NioEndpoint$Worker.run(NioEndpoint.java:1465)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NoClassDefFoundError: javax/jms/JMSException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
at java.lang.Class.getConstructor0(Class.java:2671)
at java.lang.Class.newInstance0(Class.java:321)
at java.lang.Class.newInstance(Class.java:303)
at 
org.apache.axis2.deployment.AxisConfigBuilder.processTransportReceivers(AxisConfigBuilder.java:479)
... 17 more
[ERROR] java.lang.NullPointerException: loading repository from classpath
java.lang.NullPointerException
at 
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:137)
at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:571)
at 
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:231)
at 
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:64)
at 
org.apache.axis2.deployment.RepositoryListener.(RepositoryListener.java:59)
at 
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:134)
at 
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:217)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at 
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
at 
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at 
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:133)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at 
org.apache.catalina.core.StandardHostVa

[jira] Created: (AXIS2-3111) Invalid readme is included in war distro

[Charitha Kankanamge (JIRA)]

Invalid readme is included in war distro


 Key: AXIS2-3111
 URL: https://issues.apache.org/jira/browse/AXIS2-3111
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Charitha Kankanamge
Assignee: sumedha rubasinghe
Priority: Minor


the existing readme.txt included in war distro is wrong.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3110) Additional readme is included in axis2 Docs distribution

[Charitha Kankanamge (JIRA)]

Additional readme is included in axis2 Docs distribution


 Key: AXIS2-3110
 URL: https://issues.apache.org/jira/browse/AXIS2-3110
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: documentation
Reporter: Charitha Kankanamge
Assignee: sumedha rubasinghe
Priority: Minor


When unzipping axis2-1.3-docs.zip, I noticed that two readme files were 
included in the distribution. One is located at ..\axis2-1.3-docs\axis2-1.3 and 
the other is located at ..\axis2-1.3-docs\axis2-1.3\docs. The second readme is 
invalid.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3102) Continuously undeploy and deploy services when setting hotupdate to true

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3102:
---

Summary: Continuously undeploy and deploy services when setting hotupdate 
to true  (was: Continuously undeploy and deploy services when setting hotupdate 
set to true)

Changed summary

> Continuously undeploy and deploy services when setting hotupdate to true
> 
>
> Key: AXIS2-3102
> URL: https://issues.apache.org/jira/browse/AXIS2-3102
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.3
> Environment: winxp, jdk15, tomcat 6
>Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Attachments: multipleDeployment.JPG
>
>
> When setting hotupdate=true, axis2 undeploys and deploys the modified service 
> continuously multiple times.  See the attached screen shot of tomcat console.
> Steps to reproduce:
> ===
> 1. Set hotupdate=true in axis2.xml
> 2. Restart tomcat
> 3. Modify a services.xml in a service archive.
> 4. Check tomcat console

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3102) Continuously undeploy and deploy services when setting hotupdate to true

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3102:
---

Attachment: multipleDeployment.JPG

Attached screen shot.

> Continuously undeploy and deploy services when setting hotupdate to true
> 
>
> Key: AXIS2-3102
> URL: https://issues.apache.org/jira/browse/AXIS2-3102
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.3
> Environment: winxp, jdk15, tomcat 6
>Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Attachments: multipleDeployment.JPG
>
>
> When setting hotupdate=true, axis2 undeploys and deploys the modified service 
> continuously multiple times.  See the attached screen shot of tomcat console.
> Steps to reproduce:
> ===
> 1. Set hotupdate=true in axis2.xml
> 2. Restart tomcat
> 3. Modify a services.xml in a service archive.
> 4. Check tomcat console

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3102) Continuously undeploy and deploy services when setting hotupdate set to true

[Charitha Kankanamge (JIRA)]

Continuously undeploy and deploy services when setting hotupdate set to true


 Key: AXIS2-3102
 URL: https://issues.apache.org/jira/browse/AXIS2-3102
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: deployment
Affects Versions: 1.3
 Environment: winxp, jdk15, tomcat 6
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe
Priority: Blocker


When setting hotupdate=true, axis2 undeploys and deploys the modified service 
continuously multiple times.  See the attached screen shot of tomcat console.

Steps to reproduce:
===
1. Set hotupdate=true in axis2.xml
2. Restart tomcat
3. Modify a services.xml in a service archive.
4. Check tomcat console

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3099:
---

Attachment: axis2-Jorge-edited-by-notepad.xml

Attached axis2.xml(file provided by Jorge, edited using windows notepad)

> Internal server error when modifying axis2.xml in axis2 1.3 war distribution
> 
>
> Key: AXIS2-3099
> URL: https://issues.apache.org/jira/browse/AXIS2-3099
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.3
> Environment: Windows XP SP2, Tomcat 6.0, Java 6.0
>Reporter: Jorge Fernández
>Priority: Blocker
> Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, 
> excepcion.txt
>
>
> Whenever I modify axis2.xml of the war distribution, I get an error page from 
> listServices page or when I display an WSDL
> In Hapiness Page I see:
> Examinin Version Service:
> There was a problem in Axis2 version service , may be the service not 
> available or some thing has gone wrong. But this does not mean system is not 
> working ! Try to upload some other service and check to see whether it is 
> working.
> For stoping that problem I have to backup and restore the original axis2.xml 
> file that came in the war distribution
> When that happens I receive this at the client the message in the attached 
> file when invoking the service.
> Also I can see that each time I run tomcat, my services.xml is updated, 
> apparently with no changes but is modified on disk and the same happens with 
> axis2.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3099:


I observed following when investigating the issue further.

- If you have reference in axis2.xml for a non-existing module (Module which is 
not available in WEB-INF\modules directory), you get an internal server error 
when accessing listservices page in axis2 admin console. I removed rampart 
reference (Which was not available in modules directory) from axis2.xml and 
added . Then the happyaxis page did not throw an 
error and available services were shown in listservices page. So, the current 
behavior is, when you have a reference for a non-existing module, you get 
internal server error in axis2 admin console. 

- We replaced default axis2.xml with the axis2.xml file provided by Jorge. 
First, we got the same error what Jorge had observed. Then we opened Jorge's 
axis2.xml from a windows notepad editor and found out that there were some 
invalid end of line characters in it. We removed those invalid characters and 
restarted tomcat. Then we did not get such error.

The file opened and edited by notepad is attached here with. Copy it to your 
conf directory and check again. Please let us know if you encounter this issue 
again.

> Internal server error when modifying axis2.xml in axis2 1.3 war distribution
> 
>
> Key: AXIS2-3099
> URL: https://issues.apache.org/jira/browse/AXIS2-3099
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.3
> Environment: Windows XP SP2, Tomcat 6.0, Java 6.0
>Reporter: Jorge Fernández
>Priority: Blocker
> Attachments: axis2.xml, excepcion.txt
>
>
> Whenever I modify axis2.xml of the war distribution, I get an error page from 
> listServices page or when I display an WSDL
> In Hapiness Page I see:
> Examinin Version Service:
> There was a problem in Axis2 version service , may be the service not 
> available or some thing has gone wrong. But this does not mean system is not 
> working ! Try to upload some other service and check to see whether it is 
> working.
> For stoping that problem I have to backup and restore the original axis2.xml 
> file that came in the war distribution
> When that happens I receive this at the client the message in the attached 
> file when invoking the service.
> Also I can see that each time I run tomcat, my services.xml is updated, 
> apparently with no changes but is modified on disk and the same happens with 
> axis2.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3099:


Hi Jorge,
I did not see your last two comments when I was checking this issue. Sorry for 
that. As you mentioned, I tried to engage a module globally by setting . When I set this, I got the same error you received. This 
happens both in tomcat6 and 5.5.2. There should be an issue with module 
engagement and this must be a blocker.
regards
Charitha

> Internal server error when modifying axis2.xml in axis2 1.3 war distribution
> 
>
> Key: AXIS2-3099
> URL: https://issues.apache.org/jira/browse/AXIS2-3099
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.3
> Environment: Windows XP SP2, Tomcat 6.0, Java 6.0
>Reporter: Jorge Fernández
>Priority: Critical
> Attachments: excepcion.txt
>
>
> Whenever I modify axis2.xml of the war distribution, I get an error page from 
> listServices page or when I display an WSDL
> In Hapiness Page I see:
> Examinin Version Service:
> There was a problem in Axis2 version service , may be the service not 
> available or some thing has gone wrong. But this does not mean system is not 
> working ! Try to upload some other service and check to see whether it is 
> working.
> For stoping that problem I have to backup and restore the original axis2.xml 
> file that came in the war distribution
> When that happens I receive this at the client the message in the attached 
> file when invoking the service.
> Also I can see that each time I run tomcat, my services.xml is updated, 
> apparently with no changes but is modified on disk and the same happens with 
> axis2.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge commented on AXIS2-3099:


Jorge,
What did you modify in axis2.xml? I think you did not update axis2.xml 
correctly. You will get an internal server error If there is an XML syntax 
error in axis2.xml. 
I just tried with modifying axis2.xml in axis2.war without having such issue. 
Yes.. I was able to get the same error by modifying axis2.xml incorrectly. (By 
dropping close tag of an xml element). Please check your axis2.xml again and 
let us know.

regards
Charitha

> Internal server error when modifying axis2.xml in axis2 1.3 war distribution
> 
>
> Key: AXIS2-3099
> URL: https://issues.apache.org/jira/browse/AXIS2-3099
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.3
> Environment: Windows XP SP2, Tomcat 6.0, Java 6.0
>Reporter: Jorge Fernández
>Priority: Blocker
> Attachments: excepcion.txt
>
>
> Whenever I modify axis2.xml of the war distribution, I get an error page from 
> listServices page or when I display an WSDL
> In Hapiness Page I see:
> Examinin Version Service:
> There was a problem in Axis2 version service , may be the service not 
> available or some thing has gone wrong. But this does not mean system is not 
> working ! Try to upload some other service and check to see whether it is 
> working.
> For stoping that problem I have to backup and restore the original axis2.xml 
> file that came in the war distribution
> When that happens I receive this at the client the message in the attached 
> file when invoking the service.
> Also I can see that each time I run tomcat, my services.xml is updated, 
> apparently with no changes but is modified on disk and the same happens with 
> axis2.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3096) Error when building binary distro using source

[Charitha Kankanamge (JIRA)]

Error when building binary distro using source
--

 Key: AXIS2-3096
 URL: https://issues.apache.org/jira/browse/AXIS2-3096
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Priority: Critical


I was trying to build the binary distro using source distribution. According to 
the instructions given in the readme file, I typed 'mvn clean install'.
Here is the output. Seems some artifacts are not available in maven repos.

C:\Axis2\Axis2-1.3\source\axis2-1.3>mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Apache Axis 2.0 - Parent
[INFO]   Apache Axis 2.0 - Kernel
[INFO]   Apache Axis 2.0 - Data Binding
[INFO]   Apache Axis 2.0 - Code Generation
[INFO]   Apache Axis 2.0 - ADB Codegen
[INFO]   Apache Axis 2.0 - tool - MAR Maven Plugin
[INFO]   Apache Axis 2.0 - Addressing
[INFO]   Apache Axis 2.0 - Java2WSDL
[INFO]   Apache Axis 2.0 - Fast Infoset
[INFO]   Apache Axis 2.0 - JiBX Data Binding
[INFO]   Apache Axis 2.0 - SAAJ API
[INFO]   Apache Axis 2.0 - JWS API
[INFO]   Apache Axis 2.0 - JAXWS API
[INFO]   Apache Axis 2.0 - SAAJ
[INFO]   Apache Axis 2.0 - Metadata
[INFO]   Apache Axis 2.0 - JAXWS
[INFO]   Apache Axis 2.0 - Clustering
[INFO]   Apache Axis 2.0 - MTOM Policy
[INFO]   Apache Axis 2.0 - JSON
[INFO]   Apache Axis 2.0 - XMLBeans Data Binding
[INFO]   Apache Axis 2.0 - Scripting
[INFO]   Apache Axis 2.0 - JAXB-RI Data Binding
[INFO]   Apache Axis 2.0 - spring
[INFO]   Apache Axis 2.0 - Integration
[INFO]   Apache Axis 2.0 - MEX
[INFO]   Apache Axis 2.0 - MEX-Module
[INFO]   Apache Axis 2.0 - Ping
[INFO]   Apache Axis 2.0 - tool - AAR Maven Plugin
[INFO]   Apache Axis 2.0 - Version Service
[INFO]   Apache Axis 2.0 - SOAP Monitor
[INFO]   Apache Axis 2.0 - tool - Ant Plugin
[INFO]   Apache Axis 2.0 - Root
[INFO]   Apache Axis 2.0 - tool - Eclipse Codegen Plugin
[INFO]   Apache Axis 2.0 - tool - Eclipse service Plugin
[INFO]   Apache Axis 2.0 - tool - Intellij IDEA Plugin
[INFO]   Apache Axis 2.0 - tool - Java2WSDL Maven Plugin
[INFO]   Apache Axis 2.0 - tool - WSDL2Code Maven Plugin
[INFO]   Apache Axis 2.0 - Web Application module
[INFO]   Apache Axis 2.0 - Samples
Downloading: 
http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.3/axis
2-mar-maven-plugin-1.3.jar
Downloading: 
http://repo1.maven.org/maven2/org/apache/axis2/axis2-mar-maven-plugin/1.3/axis2-mar-mav
en-plugin-1.3.jar
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Plugin could not be found - check that the goal name is correct: Unable 
to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.axis2 
-DartifactId=axis2-mar-maven-plugin \
-Dversion=1.3 -Dpackaging=maven-plugin -Dfile=/path/to/file


  org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.3

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  ws-zones (http://ws.zones.apache.org/repository2),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)

  org.apache.axis2:axis2-mar-maven-plugin:maven-plugin:1.3

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  ws-zones (http://ws.zones.apache.org/repository2),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)

[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 6 seconds
[INFO] Finished at: Tue Aug 07 22:20:02 LKT 2007
[INFO] Final Memory: 8M/14M
[INFO] 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3091) No readme for jaxws-calculator sample

[Charitha Kankanamge (JIRA)]

No readme for jaxws-calculator sample
-

 Key: AXIS2-3091
 URL: https://issues.apache.org/jira/browse/AXIS2-3091
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Charitha Kankanamge
Assignee: Davanum Srinivas


A readme.txt explaining the usage of jaxws-calculator sample should be placed 
in the samples/jaxws-calculator directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3089) [ERROR] TAG_INVALID message appears when generating code with -d xmlbeans option

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3089:
---

Attachment: xmlbeansoutput.JPG

Attached screen shot.

> [ERROR] TAG_INVALID message appears when generating code with -d xmlbeans 
> option
> 
>
> Key: AXIS2-3089
> URL: https://issues.apache.org/jira/browse/AXIS2-3089
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.3
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
> Attachments: xmlbeansoutput.JPG
>
>
> I saw a set of [ERROR] TAG_INVALID messages when generating code using 
> xmlbeans. However the stubs were generated successfully even with this error 
> message.
> See the attached screen shot.
> Steps to reproduce:
> 
> 1. Generate code for Version service using wsdl2java
> wsdl2java.bat -uri http://localhost:8080/axis2/services/Version?wsdl -o 
> C:\Axis2\Axis2-1.3\RC3\axis2-1.3-RC3\bin\out -d xmlbeans
> 2. Check the output

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3089) [ERROR] TAG_INVALID message appears when generating code with -d xmlbeans option

[Charitha Kankanamge (JIRA)]

[ERROR] TAG_INVALID message appears when generating code with -d xmlbeans option


 Key: AXIS2-3089
 URL: https://issues.apache.org/jira/browse/AXIS2-3089
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge


I saw a set of [ERROR] TAG_INVALID messages when generating code using 
xmlbeans. However the stubs were generated successfully even with this error 
message.

See the attached screen shot.

Steps to reproduce:

1. Generate code for Version service using wsdl2java
wsdl2java.bat -uri http://localhost:8080/axis2/services/Version?wsdl -o 
C:\Axis2\Axis2-1.3\RC3\axis2-1.3-RC3\bin\out -d xmlbeans
2. Check the output

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3087) axis2.bat, axis2server.bat and wsdl2java.bat scripts do not work if axis2 directory path is too long

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3087:
---

Attachment: axis2longdirpath.JPG

attached screen shot

> axis2.bat, axis2server.bat and wsdl2java.bat scripts do not work if axis2 
> directory path is too long
> 
>
> Key: AXIS2-3087
> URL: https://issues.apache.org/jira/browse/AXIS2-3087
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.3
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
> Attachments: axis2longdirpath.JPG
>
>
> See the attached screen shot. Axis2.bat, axis2server.bat and wsdl2java.bat 
> scripts quit functioning when AXIS2_HOME path is too long. 
> AXIS2_HOME = C:\Documents and Settings\Charitha Kankanamge\test directory\my 
> test\new folder\my test\new test\long path\long path test\axis2-1.3-RC3
> This path is acceptable since some other batch scripts are working from the 
> same location.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3087) axis2.bat, axis2server.bat and wsdl2java.bat scripts do not work if axis2 directory path is too long

[Charitha Kankanamge (JIRA)]

axis2.bat, axis2server.bat and wsdl2java.bat scripts do not work if axis2 
directory path is too long


 Key: AXIS2-3087
 URL: https://issues.apache.org/jira/browse/AXIS2-3087
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
 Attachments: axis2longdirpath.JPG

See the attached screen shot. Axis2.bat, axis2server.bat and wsdl2java.bat 
scripts quit functioning when AXIS2_HOME path is too long. 

AXIS2_HOME = C:\Documents and Settings\Charitha Kankanamge\test directory\my 
test\new folder\my test\new test\long path\long path test\axis2-1.3-RC3

This path is acceptable since some other batch scripts are working from the 
same location.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3079) Axis2 clustering jar is missing in binary and war distributions

[Charitha Kankanamge (JIRA)]

Axis2 clustering jar is missing in binary and war distributions
---

 Key: AXIS2-3079
 URL: https://issues.apache.org/jira/browse/AXIS2-3079
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: sumedha rubasinghe
Priority: Critical


I was going through the clustering-guide.html and configured axis2.xml to 
enable clustering as described in the document. When I restarted tomcat server, 
following exception was thrown.

[ERROR] Clustering implementation class 
org.apache.axis2.clustering.tribes.TribesClusterManager notfound
org.apache.axis2.deployment.DeploymentException: Clustering implementation 
class org.apache.axis2.clustering.tribes.TribesClusterManager not found
at 
org.apache.axis2.deployment.ClusterBuilder.buildCluster(ClusterBuilder.java:73)
at 
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:169)
at 
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:595)
at 
org.apache.axis2.deployment.WarBasedAxisConfigurator.(WarBasedAxisConfigurator.java:146)
at 
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:497)
at 
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:417)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at 
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4044)
at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
at 
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
at 
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1023)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1015)
at 
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at 
org.apache.catalina.core.StandardService.start(StandardService.java:448)
at 
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
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.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
[ERROR] java.lang.NullPointerException: loading repository from classpath
java.lang.NullPointerException
at 
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:137)
at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:551)
at 
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:231)
at 
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:64)
at 
org.apache.axis2.deployment.RepositoryListener.(RepositoryListener.java:59)
at 
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:132)
at 
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:217)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at 
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:497)
at 
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:417)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at 
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
at

[jira] Created: (AXIS2-3077) Wrong readme files are included in the root directories of axis2 docs and source distribution

[Charitha Kankanamge (JIRA)]

Wrong readme files are included in the root directories of axis2 docs and 
source distribution
-

 Key: AXIS2-3077
 URL: https://issues.apache.org/jira/browse/AXIS2-3077
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
Reporter: Charitha Kankanamge
Assignee: sumedha rubasinghe


Correct readme files are not copied to the root of the axis2 docs and source 
directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (AXIS2-3075) java2wsdl generates an invalid wsdl when the binding style is rpc

[Charitha Kankanamge (JIRA)]

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

Charitha Kankanamge updated AXIS2-3075:
---

Attachment: Mytest.wsdl

attached wsdl

> java2wsdl generates an invalid wsdl when the binding style is rpc
> -
>
> Key: AXIS2-3075
> URL: https://issues.apache.org/jira/browse/AXIS2-3075
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: wsdl
> Environment: winxp, jdk15
>    Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
> Attachments: Mytest.wsdl
>
>
> See the attached wsdl which was generated by java2wsdl.bat with specifying 
> rpc binding. The generated wsdl is invalid and due to that it returns 
> following exception when trying to generate skeleton.
> If rpc binding style is no longer supported when generating wsdl using 
> java2wsdl, please add it to the known issues list.
> [ERROR] RPC-literal type message part parameters should have a type attribute
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
>  RPC-literal type me
> ssage part parameters should have a type attribute
> at 
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addPartToElement(WSDL11ToAxisServiceBuilder.java:1992)
> at 
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getNewComplextType(WSDL11ToAxisServiceBuilder.java:1879)
> at 
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder.createSchemaForPorttype(WSDL11ToAxisServiceBuilder.java:1636)
> at 
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder.generateWrapperSchema(WSDL11ToAxisServiceBuilder.java:1431)
> at 
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:255)
> at 
> org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:109)
> at 
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:141)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Exception in thread "main" 
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
> Steps to reproduce:
> 
> 1. Generate wsdl using java2wsdl.bat
> C:\Axis2\Axis2-1.3\RC3\axis2-1.3-RC3\bin>java2wsdl.bat -cn Mytestservice -of 
> Mytest.wsdl -o . -st rpc

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3075) java2wsdl generates an invalid wsdl when the binding style is rpc

[Charitha Kankanamge (JIRA)]

java2wsdl generates an invalid wsdl when the binding style is rpc
-

 Key: AXIS2-3075
 URL: https://issues.apache.org/jira/browse/AXIS2-3075
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe


See the attached wsdl which was generated by java2wsdl.bat with specifying rpc 
binding. The generated wsdl is invalid and due to that it returns following 
exception when trying to generate skeleton.

If rpc binding style is no longer supported when generating wsdl using 
java2wsdl, please add it to the known issues list.

[ERROR] RPC-literal type message part parameters should have a type attribute
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
 RPC-literal type me
ssage part parameters should have a type attribute
at 
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addPartToElement(WSDL11ToAxisServiceBuilder.java:1992)
at 
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getNewComplextType(WSDL11ToAxisServiceBuilder.java:1879)
at 
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.createSchemaForPorttype(WSDL11ToAxisServiceBuilder.java:1636)
at 
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.generateWrapperSchema(WSDL11ToAxisServiceBuilder.java:1431)
at 
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:255)
at 
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:109)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:141)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL

Steps to reproduce:

1. Generate wsdl using java2wsdl.bat
C:\Axis2\Axis2-1.3\RC3\axis2-1.3-RC3\bin>java2wsdl.bat -cn Mytestservice -of 
Mytest.wsdl -o . -st rpc




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Created: (AXIS2-3073) commons-logging and log4j property files should not be placed at the root of axis2 binary distro

[Charitha Kankanamge (JIRA)]

commons-logging and log4j property files should not be placed at the root of 
axis2 binary distro


 Key: AXIS2-3073
 URL: https://issues.apache.org/jira/browse/AXIS2-3073
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe
Priority: Minor


Currently commons-logging.properties and log4j.properties are located at the 
root of axis2-1.3 RC3 binary distribution. These files should be placed either 
in conf or lib directory.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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