Re: Fwd: [DISCUSS] Axis2 as TLP
Yes, I am in sync with this thought too.. Not only Java and C , All the other related bits and pieces needed to be nicely arranged (Clean and Comfortable) in a hierarchy if Axis2* needed to be a TLP. *(sub projects, tools etc But not dependent projects of course if they are mature enough.. I agree on that there will be gray areas on how to decide this but still.. i guess the community needed to agree on which part goes where ..) I do not think Axis2 currently doing a bad job on that, but still believes there is more to do.. Just my thoughts .. Thanks Lahiru Sandakith On Sat, Nov 1, 2008 at 3:11 AM, Afkham Azeez <[EMAIL PROTECTED]> wrote: > Yes, I also agree that this is the proper thing to do, if ever Axis2 is > made a TLP. > > Azeez > > > On Sat, Nov 1, 2008 at 10:54 AM, Ruchith Fernando < > [EMAIL PROTECTED]> wrote: > >> IMHO Axis2 project as a TLP should be both Java and C. >> >> Thanks, >> Ruchith >> >> On Sat, Nov 1, 2008 at 1:14 AM, Manjula Peiris <[EMAIL PROTECTED]> wrote: >> > >> > On Sat, 2008-11-01 at 09:23 +0530, Samisa Abeysinghe wrote: >> >> It looks to me that the amount of confusion and frustration >> demonstrated >> >> in this thread is due to the mix of topics that we are discussing under >> >> the single topic, namely TLP. >> >> >> >> Some of the matters are not really TLP related. >> >> >> >> On one hand, there is talk about dropping C out of the picture, while >> >> making Axis2 a TLP. So natural tenancy from the C folks is a big NO. >> >> So is that equivalent to saying, no we do not need a TLP? Not really. >> > >> > Yes as a contributor to Axis2/C project my main concern is also on >> > dropping out Axis2/C out of the picture. If we separate out these two >> > projects it may affect Axis2/C project, and I don't think Axis2 will >> > benefited from that either. >> > >> >> >> >> Then there are questions related to activeness. And I do agree that it >> >> is a real problem, that needs to be solved. But IMHO I have doubts if a >> >> TLP would solve it. >> >> >> >> We need a clear list of things that we might be doing, when we become a >> >> TLP. And that list must obviously include the list of projects that >> will >> >> go under that TLP etc. >> >> >> >> Then we also need a separate list, that outlines problems that we have >> >> in the current setup. Including those that might be solved with TLP as >> >> well as those that might not. >> >> >> >> And if we can agree on the above, then we have to identify a media to >> >> collect those lists. A mailing list thread like this is distorting when >> >> it comes to listing things IMHO, so we might need a Wiki that everyone >> >> can edit. >> >> >> >> Thanks, >> >> Samisa... >> >> >> >> >> >> Ajith Ranabahu wrote: >> >> > missed general@ >> >> > >> >> > >> >> > -- Forwarded message -- >> >> > From: Ajith Ranabahu <[EMAIL PROTECTED]> >> >> > Date: Fri, Oct 31, 2008 at 12:04 PM >> >> > Subject: Re: [DISCUSS] Axis2 as TLP >> >> > To: axis-dev@ws.apache.org >> >> > >> >> > >> >> > I should kick myself for not reading Axis2 mail frequently. I just >> >> > spent 20 minutes reading the complete thread and just throwing my 2 >> >> > cents. >> >> > >> >> > 1. I am +1 (not a vote, a token of agreement) on making Axis2 a TLP. >> >> > I have supported the decision in the PMC and I am still in support >> for >> >> > it. As Deepal says I don't understand why people are so much worried >> >> > about making Axis2 a TLP. We have kept all the major components as >> >> > subprojects so far and what difference would it make if we house them >> >> > in a different place ? >> >> > >> >> > 2. I have to agree to Dims that we have not been active as usual. >> >> > There are open Jira's and I haven't had time to fix the few things >> >> > that are pending in my niche projects (XMLSchema and tcpmon) let >> alone >> >> > in Axis2. However I personally feel that it would be easier to do a >> >> > better job (better than being done right now) if the teams are small >> >> > an
Re: [DISCUSS] Axis2 as TLP
TLP is Top Level Project as in http://www.apache.org/dev/project-creation.html On Fri, Oct 31, 2008 at 3:08 PM, emiddio-verizon <[EMAIL PROTECTED]>wrote: > pleaes -- > > someone say what "TLP" stands for - what is the acronym? > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith Gallege http://sandakith.wordpress.com/ http://www.cs.iupui.edu/~lspileth/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2][VOTE] Axis2 1.4.1 - Take #4
+1 Thanks Lahiru Sandakith Gallege On Thu, Aug 21, 2008 at 8:21 AM, Nandana Mihindukulasooriya < [EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I am calling fresh a vote again for Axis2 1.4.1 and only the source > distribution is changed. Only change is removing some binaries that were > accidentally included. > > New source distribution can be found here. Please review. > http://people.apache.org/~nandana/axis2-1.4.1/dist/axis2-1.4.1-src.zip<http://people.apache.org/%7Enandana/axis2-1.4.1/dist/axis2-1.4.1-src.zip> > > thanks, > nandana > > Distributions: > http://people.apache.org/~nandana/axis2-1.4.1/dist<http://people.apache.org/%7Enandana/axis2-1.4.1/dist> > > Maven2 repository: > http://people.apache.org/~nandana/axis2-1.4.1/m2-repo/<http://people.apache.org/%7Enandana/axis2-1.4.1/m2-repo/> > > SVN Info: > https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_4 > (Revision: 684402) > > Here's my +1 to declaring the above dist as Axis2 1.4.1. > > thanks, > nandana > > Links to the individual Distribution/Tool files are listed below: > > Distributions : > http://people.apache.org/~nandana/axis2-1.4.1/dist/axis2-1.4.1-bin.zip<http://people.apache.org/%7Enandana/axis2-1.4.1/dist/axis2-1.4.1-bin.zip> > http://people.apache.org/~nandana/axis2-1.4.1/dist/axis2-1.4.1-docs.zip<http://people.apache.org/%7Enandana/axis2-1.4.1/dist/axis2-1.4.1-docs.zip> > http://people.apache.org/~nandana/axis2-1.4.1/dist/axis2-1.4.1-src.zip<http://people.apache.org/%7Enandana/axis2-1.4.1/dist/axis2-1.4.1-src.zip> > http://people.apache.org/~nandana/axis2-1.4.1/dist/axis2-1.4.1-war.zip<http://people.apache.org/%7Enandana/axis2-1.4.1/dist/axis2-1.4.1-war.zip> > > Tools : > > http://people.apache.org/~nandana/axis2-1.4.1/tools/axis2-aar-maven-plugin-1.4.1.jar<http://people.apache.org/%7Enandana/axis2-1.4.1/tools/axis2-aar-maven-plugin-1.4.1.jar> > > http://people.apache.org/~nandana/axis2-1.4.1/tools/axis2-ant-plugin-1.4.1.jar<http://people.apache.org/%7Enandana/axis2-1.4.1/tools/axis2-ant-plugin-1.4.1.jar> > > http://people.apache.org/~nandana/axis2-1.4.1/tools/axis2-eclipse-codegen-wizard.zip<http://people.apache.org/%7Enandana/axis2-1.4.1/tools/axis2-eclipse-codegen-wizard.zip> > > http://people.apache.org/~nandana/axis2-1.4.1/tools/axis2-eclipse-service-archiver-wizard.zip<http://people.apache.org/%7Enandana/axis2-1.4.1/tools/axis2-eclipse-service-archiver-wizard.zip> > > http://people.apache.org/~nandana/axis2-1.4.1/tools/axis2-mar-maven-plugin-1.4.1.jar<http://people.apache.org/%7Enandana/axis2-1.4.1/tools/axis2-mar-maven-plugin-1.4.1.jar> > > http://people.apache.org/~nandana/axis2-1.4.1/tools/axis2-idea-plugin-1.4.1.zip<http://people.apache.org/%7Enandana/axis2-1.4.1/tools/axis2-idea-plugin-1.4.1.zip> > > http://people.apache.org/~nandana/axis2-1.4.1/tools/axis2-java2wsdl-maven-plugin-1.4.1.jar<http://people.apache.org/%7Enandana/axis2-1.4.1/tools/axis2-java2wsdl-maven-plugin-1.4.1.jar> > > http://people.apache.org/~nandana/axis2-1.4.1/tools/axis2-wsdl2code-maven-plugin-1.4.1.jar<http://people.apache.org/%7Enandana/axis2-1.4.1/tools/axis2-wsdl2code-maven-plugin-1.4.1.jar> > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFIrV3ZmA4ts7hLdV8RAsJPAJ9l2tuD6tbSBOxRbg1E9xNyPcq83ACgiVSo > bKWm+W1YD5ZO1w8EZM+FEsQ= > =Fx2j > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith Gallege http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)
+1 for Nandana as the Release Manager Regards Lahiru Sandakith On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Nandana, > > +1 from me for you to be the Release Manager for 1.4.1 > > IMHO, we should use 1.4 branch. The *ONLY* change should be the > security change. Nothing more. > > thanks, > dims > > On Mon, Jul 7, 2008 at 6:50 AM, Nandana Mihindukulasooriya > <[EMAIL PROTECTED]> wrote: > > I would like to volunteer to be the release manager for Axis2 1.4.1. > > > > I think we can fix the critical issues in the 1.4 branch (or a 1.4.1 > branch > > ) and do the 1.4.1 release. I don't think doing 1.4.1 from the trunk is > the > > appropriate way as trunk is now java 1.5 and has lot of major changes > after > > Axis2 1.4 . However we can fix any issues that are not already fixed in > the > > trunk at the same time when we fix those in the branch. > > > > Hope this is oky with Axis2 release guidelines. > > > > thanks, > > nandana > > > > On Tue, Jul 1, 2008 at 6:39 PM, Davanum Srinivas <[EMAIL PROTECTED]> > wrote: > >> > >> IMHO, The logic is the same as for blockers. If there is a work > >> around, it's not a blocker. So i am +0 on a 1.4.1 since there is a > >> work around that can be documented. > >> > >> That said, If someone is willing to drive a 1.4.1 as the release > >> manager, please do go ahead. > >> > >> thanks, > >> dims > >> > >> On Tue, Jul 1, 2008 at 2:48 AM, Sanka Samaranayake <[EMAIL PROTECTED]> > >> wrote: > >> > Hi, > >> > > >> > For the users who is already using 1.4 version, the workaround would > be > >> > to > >> > define policies in services.xml without using . > >> > Then > >> > the problem is that those policies will appear in > which > >> > is > >> > not correct but security will apply for both format of service URLs. > >> > > >> > Hence +1 for fixing that issue and do 1.4.1 release. > >> > > >> > Thanks, > >> > Sanka > >> > > >> > > >> > On Mon, Jun 30, 2008 at 8:59 PM, Nandana Mihindukulasooriya > >> > <[EMAIL PROTECTED]> wrote: > >> >> > >> >> Hi, > >> >>There are few issues with Axis2 1.4 / Rampart 1.4 with the new > >> >> policy > >> >> configuration. The new policy configuration which allows us to apply > >> >> policies to binding hierarchy is a great feature when in comes to ws > >> >> security policy configuration. It allows security policies to be > >> >> attached to > >> >> the correct attachment points. But there are few issues that need to > be > >> >> fixed in Axis2 1.4. I will list them below. > >> >> 1.) If we configure security using new configuration, service can > >> >> be > >> >> accessed without security. > >> >> In Axis2 1.4, a service is exposed in two EPRs (consider > SOAP > >> >> 1.1 > >> >> binding). > >> >>eg. > >> >> > >> >> > >> >> > http://localhost:8080/axis2/services/SecureService.SecureServiceHttpSoap11Endpoint > >> >>http://localhost:8080/axis2/services/SecureService > >> >> But if we you set the policies using the new configuration, > >> >> if > >> >> you do a web service call to the older EPR, you can access the > service > >> >> without any security even though it is secured using the binding > >> >> hierarchy. > >> >> This happens because if we call the old EPR, it is not dispatched to > a > >> >> binding. But this leaves the service vulnerable. I think we should > >> >> dispatch > >> >> to one of the bindings may be using soap envelope version if we have > >> >> only > >> >> one binding with that soap version. We should have a way to dispatch > >> >> messages which comes to old EPR to one of the bindings else we should > >> >> have > >> >> an option to disable that EPR. > >> >> > >> >> 2.) In the out flow, policies are not set correctly in the > binding > >> >> message. > >> >>
[jira] Resolved: (AXIS2-3889) The Axis2-Codegen tool does not contain all the codegen options presented
[ https://issues.apache.org/jira/browse/AXIS2-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3889. - Resolution: Fixed Committed . Thanks Saminda svn commit -m "Applying patch by saminda wijerathne. This patch will add the missing features of codegen tools which are available in the command line tool" Sending axis2-eclipse-codegen-plugin/src/main/java/org/apache/axis2/tool/codegen/WSDL2JavaGenerator.java Sending axis2-eclipse-codegen-plugin/src/main/java/org/apache/axis2/tool/codegen/eclipse/CodeGenWizard.java Sending axis2-eclipse-codegen-plugin/src/main/java/org/apache/axis2/tool/codegen/eclipse/ui/OptionsPage.java Adding axis2-eclipse-codegen-plugin/src/main/java/org/apache/axis2/tool/codegen/eclipse/ui/WSDLJavaAdvanceDialog.java Transmitting file data Committed revision 674026. > The Axis2-Codegen tool does not contain all the codegen options presented > - > > Key: AXIS2-3889 > URL: https://issues.apache.org/jira/browse/AXIS2-3889 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: Tools > Environment: ide: Eclipse > java: jdk 1.5 >Reporter: saminda wijeratne >Assignee: Lahiru Sandakith > Attachments: AXIS2-3889_missing_codegen_wsdl2java_features.txt > > > Axis2-Codegen tool currently does not implement all the features available in > the codegen provided by the axis2. these missing features should be added to > the eclipse tool. > following are the currently implmented features. > x -o Specify a directory path for the generated code. > x -a Generate async style code only (Default: off). > x -s Generate sync style code only (Default: off). > Takes precedence over -a. > x -p Specify a custom package name for the generated > code. > x -l Valid languages are java and c (Default: java). > x -t Generate a test case for the generated code. > x -ss Generate server side code (i.e. skeletons) > (Default: off). > x -sd Generate service descriptor (i.e. services.xml). > (Default: off). Valid with -ss. > x -d Valid databinding(s) are adb, xmlbeans, jibx and > jaxbri (Default: adb). > x -g Generates all the classes. Valid only with -ss. > x -pn Choose a specific port when there are multiple > ports in the wsdl. > x -snChoose a specific service when there are multiple > services in the wsdl. > x -ns2p ns1=pkg1,ns2=pkg2 Specify a custom package name for each namespace > specified in the wsdls schema. > x -ssi Generate an interface for the service > implementation (Default: off). -- 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-3855) automate the axis2 tools eclipse plugin projects creations at the maven2 at build time with additional parameters
[ https://issues.apache.org/jira/browse/AXIS2-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610561#action_12610561 ] Lahiru Sandakith commented on AXIS2-3855: - patch committed , thanks saminda. svn commit -m "Applying patch by saminda wijerathne. This patch will add the stax dependency to the plugin" Sendingaxis2-eclipse-codegen-plugin/pom.xml Transmitting file data . Committed revision 674019. > automate the axis2 tools eclipse plugin projects creations at the maven2 at > build time with additional parameters > - > > Key: AXIS2-3855 > URL: https://issues.apache.org/jira/browse/AXIS2-3855 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Reporter: saminda wijeratne >Assignee: Lahiru Sandakith > Attachments: AXIS2-3855-patch-service-plugin.txt, > AXIS2-3855_missing_geranimo_stax_and_filter.txt, patch.txt > > > Currently after the build we cannot directly import the both eclipse-services > and the eclipse-codegen plugins as plugin projects to eclipse without > manually copying the contents of the conf folder to the relevant project > locations. We need to improve the maven2 build of these two projects to > automate to copy these. -- 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-3178) ANT scripts stop working after "Code Generator Wizard - Eclipse Plug-in" installed
[ https://issues.apache.org/jira/browse/AXIS2-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3178. - Resolution: Fixed This was fixed already int the trunk by removing the ant dependencies in the plugin.xml files. Also as mentioned, a workaround also exits. > ANT scripts stop working after "Code Generator Wizard - Eclipse Plug-in" > installed > -- > > Key: AXIS2-3178 > URL: https://issues.apache.org/jira/browse/AXIS2-3178 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 > Environment: Eclipse 3.3 (JEE Distro / Europa) >Reporter: Dustin Henson >Assignee: Lahiru Sandakith > > In Eclipse you can run ant scripts using the External Tools toolbar item. > These stop working after the Code Generator Wizard is installed. The two > areas don't seem like they should be related and I don't have any lead as to > the cause, but I can recreate it consistently on my computer. > To recreate: > - Download and install the JEE Distro (Europa) of Eclipse 3.3 > - Create a simple ant script: > > > Test > > > - Set the ant script to run as an External Tools > Ant Build > - Test it and it works > - Download and install the 1.3 version of the "Code Generator Wizard - > Eclipse Plug-in" tool > - Restart Eclipse > - Run the ANT script again and it hangs. Checking the error log via the > Plug-in Development Perspective shows the following error: > Error logged from Ant UI: > java.net.SocketTimeoutException: Accept timed out > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.PlainSocketImpl.accept(Unknown Source) > at java.net.ServerSocket.implAccept(Unknown Source) > at java.net.ServerSocket.accept(Unknown Source) > at > org.eclipse.ant.internal.ui.launchConfigurations.RemoteAntBuildListener$ServerConnection.run(RemoteAntBuildListener.java:95) -- 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-3799) InvocationTargetException in eclipse plug-in Axis2_Codegen_Wizard_1.3.0
[ https://issues.apache.org/jira/browse/AXIS2-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3799. - Resolution: Fixed Confirming the issue resolved with the patch for AXIS2-3792. Thanks Jeff for the patch. > InvocationTargetException in eclipse plug-in Axis2_Codegen_Wizard_1.3.0 > --- > > Key: AXIS2-3799 > URL: https://issues.apache.org/jira/browse/AXIS2-3799 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: ide plugins >Affects Versions: 1.4 > Environment: Windows XP, SDK 1.5, Eclipse 3.2.1 Axis2 1.4 >Reporter: Denis > Assignee: Lahiru Sandakith > > After pressing a finish button in codegen wizard arises a > InvocationTargetException. It exception is caused by an exception of "class > not found". > The given error is eliminated by addition in plug-in a libraries > geronimo-stax-api_1.0_spec-1.0.1.jar. The library also may be imported in > plugin.xml file. -- 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-3163) BUG in service archiver plugin for eclipse of latest version (1.3)
[ https://issues.apache.org/jira/browse/AXIS2-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609508#action_12609508 ] Lahiru Sandakith commented on AXIS2-3163: - You need to add the service class dependency jars to the created service archive at the third party dependency page. 1.3 / 1.4 and current trunk nightly works for me on Europa. thanks Lahiru Sandakith > BUG in service archiver plugin for eclipse of latest version (1.3) > -- > > Key: AXIS2-3163 > URL: https://issues.apache.org/jira/browse/AXIS2-3163 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 >Reporter: Ashok kariyappa > Assignee: Lahiru Sandakith > > Not able to archive the file using this wizard. it is not supporting > properly , > it wont give error or any thing it simply wont work . > > it wont go forward if click on the next button . > when click the second time it will start proceding and once the Generate > service XML screen comes , it wont proceed will stop there. > somebody mention this issue earlier, they said , it is resolved in new > version, but not. > i am having the new version 1.3 of codegen and service archiver . the same > problem with this.. > regards > ashok.k -- 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-3145) Eclipse codegen plugin namespace error
[ https://issues.apache.org/jira/browse/AXIS2-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3145. - Resolution: Fixed Resolved the issue in the trunk Commit Log svn commit -m "Fixing the issue 3145" Sending axis2-idea-plugin/src/main/java/org/apache/axis2/tools/bean/NamespaceFinder.java Transmitting file data . Committed revision 673035. > Eclipse codegen plugin namespace error > -- > > Key: AXIS2-3145 > URL: https://issues.apache.org/jira/browse/AXIS2-3145 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 > Environment: WindowsXP SP2, Eclipse 3.3.0, > axis2-eclipse-codegen-plugin 1.3 >Reporter: Suran Jayathilaka >Assignee: Lahiru Sandakith > Attachments: AXIS2-3145-idea.patch, AXIS2-3145.patch > > > WSDL generated by the plugin has schemaTargetNameSpace with a "/xsd" suffix. > Axis2 expects the schemaTargetNameSpace without that suffix. (i.e. the ?wsld > doesn't have the suffix.) -- 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-3881) The temporary folder created to create the aar file is not unique
[ https://issues.apache.org/jira/browse/AXIS2-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3881. - Resolution: Fixed applied the patch to the trunk, thanks saminda wijeratne Commit Log svn commit -m "Applying the patch by saminda wijeratne for the issue 3881" Sending axis2-eclipse-service-plugin/src/main/java/org/apache/axis2/tool/service/control/Controller.java Transmitting file data . Committed revision 673020. > The temporary folder created to create the aar file is not unique > - > > Key: AXIS2-3881 > URL: https://issues.apache.org/jira/browse/AXIS2-3881 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools > Environment: Java : jdk 1.5 > OS : Ubuntu 8.04 > eclipse : ganymede >Reporter: saminda wijeratne > Attachments: AXIS2-3881_patch.txt > > > The temporary folder created in order to setup the neccessary folder > structure and files for later creation for aar file does not have a unique > name. This can result in following problems. > 1. incase of such a folder exist in the tmp folder it will be deleted > 2. if any files were added externaly to the folder while creating the aar > file the generted aar file would contain those unwanted files also. > 3. In a rare case of more than one eclipse instances attempt to create the > aar file the files and folders will overwrite/replace each others files > creating invalid file/folders for the aar and missing neccessary > files/folders. -- 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-3855) automate the axis2 tools eclipse plugin projects creations at the maven2 at build time with additional parameters
[ https://issues.apache.org/jira/browse/AXIS2-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3855. - Resolution: Fixed Resolving the issue. Commit Log === svn commit -m "committing the AXIS2-3855-patch-service-plugin.txt by saminda wijeratne for the issue 3855" Sendingmodules/tool/axis2-eclipse-service-plugin/pom.xml Sendingmodules/tool/conf/service/.classpath Transmitting file data .. Committed revision 673001. > automate the axis2 tools eclipse plugin projects creations at the maven2 at > build time with additional parameters > - > > Key: AXIS2-3855 > URL: https://issues.apache.org/jira/browse/AXIS2-3855 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Reporter: saminda wijeratne >Assignee: Lahiru Sandakith > Attachments: AXIS2-3855-patch-service-plugin.txt, patch.txt > > > Currently after the build we cannot directly import the both eclipse-services > and the eclipse-codegen plugins as plugin projects to eclipse without > manually copying the contents of the conf folder to the relevant project > locations. We need to improve the maven2 build of these two projects to > automate to copy these. -- 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-3792 patch has been commited
NP Jeff, and thanks for getting it through. I have resolved the issue. Thanks Lahiru Sandakith. On Fri, Jun 27, 2008 at 11:01 PM, Jeff Barrett <[EMAIL PROTECTED]> wrote: > Hi, > > I wanted to let you know that I commited the patch (with a few minor > modifications) that was submitted for > https://issues.apache.org/jira/browse/AXIS2-3792 . I didn't realize the > Jira was assigned to you until after I did the commit; I hope you don't > mind. I thought it needed to be fixed so someone could work on > https://issues.apache.org/jira/browse/AXIS2-3871 and test the resulting > fix. > > The patch was committed in revision 672331 > > Thanks, > Jeff > > IBM Software Group - WebSphere Web Services Development > Phone: 512-838-4587 or Tie Line 678-4587 > Internet e-mail and Sametime ID: [EMAIL PROTECTED] > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Resolved: (AXIS2-3792) codegen plugin fails due to missing jar
[ https://issues.apache.org/jira/browse/AXIS2-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3792. - Resolution: Fixed Thanks Jeff for committing this patch to the trunk. Resolving the issue. > codegen plugin fails due to missing jar > --- > > Key: AXIS2-3792 > URL: https://issues.apache.org/jira/browse/AXIS2-3792 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.4 > Environment: 1.4 of the codegen Eclipse plugin >Reporter: Kent Tong > Assignee: Lahiru Sandakith >Priority: Blocker > Attachments: svnDiff-head.txt, svnDiff.txt > > > When clicking "Finish" in the last step to generate Java code from WSDL, the > following exception occurs. > I believe this is a bug introduced by the commit > http://mail-archives.apache.org/mod_mbox/ws-axis-cvs/200802.mbox/[EMAIL > PROTECTED] > This change causes the plug in to use the ConcurrentHashMap class. That class > is provided by > backport-util-concurrent-2.2.jar but that jar file is not included in in the > plug's distribution (v1.4). > Here is the Eclipse console log: > > Install location: > file:/c:/eclipse/ > Configuration file: > file:/c:/eclipse/configuration/config.ini loaded > Configuration location: > file:/c:/eclipse/configuration/ > Framework located: > file:/c:/eclipse/plugins/org.eclipse.osgi_3.3.2.R33x_v20080105.jar > Framework classpath: > file:/c:/eclipse/plugins/org.eclipse.osgi_3.3.2.R33x_v20080105.jar > Splash location: > c:\eclipse\plugins\org.eclipse.platform_3.3.3.r33x_r20080129\splash.bmp > Debug options: > file:/C:/eclipse/.options not found > Time to load bundles: 16 > Starting application: 1078 > !SESSION 2008-05-05 16:17:28.265 > --- > > eclipse.buildId=M20080221-1800 > java.version=1.6.0_05 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US > Command-line arguments: -os win32 -ws win32 -arch x86 -debug -consoleLog > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.531 > !MESSAGE NLS unused message: _UI_LABEL_UNDEFINED_ARG1 in: > org.eclipse.wst.wsdl.u > i.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.531 > !MESSAGE NLS unused message: _UI_LABEL_UNDEFINED_ARG2 in: > org.eclipse.wst.wsdl.u > i.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.546 > !MESSAGE NLS unused message: _UI_LABEL_OR_UNDEFINED_ARG2 in: > org.eclipse.wst.wsd > l.ui.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.562 > !MESSAGE NLS unused message: _UI_LABEL_OR_UNDEFINED_ARG3 in: > org.eclipse.wst.wsd > l.ui.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.578 > !MESSAGE NLS unused message: _UI_LABEL_NO_OBJECT_SPECIFIED_ARG1 in: > org.eclipse. > wst.wsdl.ui.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.578 > !MESSAGE NLS unused message: _UI_LABEL_NO_PARAMETERS_SPECIFIED in: > org.eclipse.w > st.wsdl.ui.internal.messages > Application Started: 11000 > Retrieving document at > 'C:\eclipse\workspace\SimpleServcie\SimpleService.wsdl'. > Retrieving document at > 'C:\eclipse\workspace\SimpleServcie\SimpleService.wsdl'. > java.lang.reflect.InvocationTargetException > at > org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:383) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934) > at > org.apache.axis2.tool.codegen.eclipse.CodeGenWizard.doFinishWSDL2Java(CodeGenWizard.java:353) > at > org.apache.axis2.tool.codegen.eclipse.CodeGenWizard.performFinish(CodeGenWizard.java:171) > at > org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742) > at > org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at > org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) > at > org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) > at org.eclipse.swt.widgets.D
[jira] Resolved: (AXIS2-2847) Axis2 Webapp contains warning when relayed through validation of Eclipse WTP
[ https://issues.apache.org/jira/browse/AXIS2-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-2847. - Resolution: Won't Fix In Eclipse WTP Integration we have came to conclusion to skip validating the axis2 jsp folder at the time of the dynamic web project creation. The reason behind this is performance issue that when ever user needs a project with the axis2 web services support and with the webapp console this validation happen and it took some time. So I think it is reasonable decision that to get user out of that since these are pre produced jsps by axis2. Thanks Lahiru Sandakith. > Axis2 Webapp contains warning when relayed through validation of Eclipse WTP > > > Key: AXIS2-2847 > URL: https://issues.apache.org/jira/browse/AXIS2-2847 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 > Environment: Eclipse WTP 2.0 >Reporter: Lahiru Sandakith >Assignee: Lahiru Sandakith >Priority: Minor > > Axis2 Webapp consist of warnings as reported on > https://bugs.eclipse.org/bugs/show_bug.cgi?id=193647 > Bugzilla Bug 193647 JSP validation warnings after adding Axis 2 facets. -- 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-3800) The eclipse plug-in version is 1.3 instead 1.4
[ https://issues.apache.org/jira/browse/AXIS2-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3800. - Resolution: Fixed There is a property in parent pom.xml as 1.3.0 and when the build run, because of the label replacing in the plugin.xml it will be replaced with the correct version.. So the release manager need to edit that and build the plugin when ever there is a eclipse plugin release. now I change it to 1.4.1, as its now on post 1.4 Thanks Lahiru Sandakith > The eclipse plug-in version is 1.3 instead 1.4 > -- > > Key: AXIS2-3800 > URL: https://issues.apache.org/jira/browse/AXIS2-3800 > Project: Axis 2.0 (Axis2) > Issue Type: Wish > Components: ide plugins >Affects Versions: 1.4 > Environment: Axis2 1.4, Eclipse plug-ins. >Reporter: Denis > Assignee: Lahiru Sandakith >Priority: Minor > -- 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-3855) automate the axis2 tools eclipse plugin projects creations at the maven2 at build time with additional parameters
[ https://issues.apache.org/jira/browse/AXIS2-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608348#action_12608348 ] Lahiru Sandakith commented on AXIS2-3855: - I have reviewed and committed this patch in to the trunk. Committed on New Revision: 671485 Thanks Saminda, its great that we have this improvement on directly importing the plugin project in to eclipse workbench for developers for directly to startup developing with out manual classpath and other setting altering. I have tested this patch with latest eclipse jee ganymede and with maven 2.0.8 > automate the axis2 tools eclipse plugin projects creations at the maven2 at > build time with additional parameters > - > > Key: AXIS2-3855 > URL: https://issues.apache.org/jira/browse/AXIS2-3855 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Reporter: saminda wijeratne > Assignee: Lahiru Sandakith > Attachments: patch.txt > > > Currently after the build we cannot directly import the both eclipse-services > and the eclipse-codegen plugins as plugin projects to eclipse without > manually copying the contents of the conf folder to the relevant project > locations. We need to improve the maven2 build of these two projects to > automate to copy these. -- 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-3855) automate the axis2 tools eclipse plugin projects creations at the maven2 at build time with additional parameters
[ https://issues.apache.org/jira/browse/AXIS2-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3855: --- Assignee: Lahiru Sandakith > automate the axis2 tools eclipse plugin projects creations at the maven2 at > build time with additional parameters > - > > Key: AXIS2-3855 > URL: https://issues.apache.org/jira/browse/AXIS2-3855 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Reporter: saminda wijeratne > Assignee: Lahiru Sandakith > Attachments: patch.txt > > > Currently after the build we cannot directly import the both eclipse-services > and the eclipse-codegen plugins as plugin projects to eclipse without > manually copying the contents of the conf folder to the relevant project > locations. We need to improve the maven2 build of these two projects to > automate to copy these. -- 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-3792) codegen plugin fails due to missing jar
[ https://issues.apache.org/jira/browse/AXIS2-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3792: --- Assignee: Lahiru Sandakith (was: Amila Chinthaka Suriarachchi) > codegen plugin fails due to missing jar > --- > > Key: AXIS2-3792 > URL: https://issues.apache.org/jira/browse/AXIS2-3792 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.4 > Environment: 1.4 of the codegen Eclipse plugin >Reporter: Kent Tong > Assignee: Lahiru Sandakith >Priority: Blocker > Attachments: svnDiff-head.txt, svnDiff.txt > > > When clicking "Finish" in the last step to generate Java code from WSDL, the > following exception occurs. > I believe this is a bug introduced by the commit > http://mail-archives.apache.org/mod_mbox/ws-axis-cvs/200802.mbox/[EMAIL > PROTECTED] > This change causes the plug in to use the ConcurrentHashMap class. That class > is provided by > backport-util-concurrent-2.2.jar but that jar file is not included in in the > plug's distribution (v1.4). > Here is the Eclipse console log: > > Install location: > file:/c:/eclipse/ > Configuration file: > file:/c:/eclipse/configuration/config.ini loaded > Configuration location: > file:/c:/eclipse/configuration/ > Framework located: > file:/c:/eclipse/plugins/org.eclipse.osgi_3.3.2.R33x_v20080105.jar > Framework classpath: > file:/c:/eclipse/plugins/org.eclipse.osgi_3.3.2.R33x_v20080105.jar > Splash location: > c:\eclipse\plugins\org.eclipse.platform_3.3.3.r33x_r20080129\splash.bmp > Debug options: > file:/C:/eclipse/.options not found > Time to load bundles: 16 > Starting application: 1078 > !SESSION 2008-05-05 16:17:28.265 > --- > > eclipse.buildId=M20080221-1800 > java.version=1.6.0_05 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US > Command-line arguments: -os win32 -ws win32 -arch x86 -debug -consoleLog > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.531 > !MESSAGE NLS unused message: _UI_LABEL_UNDEFINED_ARG1 in: > org.eclipse.wst.wsdl.u > i.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.531 > !MESSAGE NLS unused message: _UI_LABEL_UNDEFINED_ARG2 in: > org.eclipse.wst.wsdl.u > i.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.546 > !MESSAGE NLS unused message: _UI_LABEL_OR_UNDEFINED_ARG2 in: > org.eclipse.wst.wsd > l.ui.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.562 > !MESSAGE NLS unused message: _UI_LABEL_OR_UNDEFINED_ARG3 in: > org.eclipse.wst.wsd > l.ui.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.578 > !MESSAGE NLS unused message: _UI_LABEL_NO_OBJECT_SPECIFIED_ARG1 in: > org.eclipse. > wst.wsdl.ui.internal.messages > > !ENTRY org.eclipse.osgi 2 1 2008-05-05 16:17:32.578 > !MESSAGE NLS unused message: _UI_LABEL_NO_PARAMETERS_SPECIFIED in: > org.eclipse.w > st.wsdl.ui.internal.messages > Application Started: 11000 > Retrieving document at > 'C:\eclipse\workspace\SimpleServcie\SimpleService.wsdl'. > Retrieving document at > 'C:\eclipse\workspace\SimpleServcie\SimpleService.wsdl'. > java.lang.reflect.InvocationTargetException > at > org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:383) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934) > at > org.apache.axis2.tool.codegen.eclipse.CodeGenWizard.doFinishWSDL2Java(CodeGenWizard.java:353) > at > org.apache.axis2.tool.codegen.eclipse.CodeGenWizard.performFinish(CodeGenWizard.java:171) > at > org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742) > at > org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at > org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) > at > org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) > at org.eclipse.swt.widgets.D
[Axis2] Deploying a annotated bean with JAXWS Deployer
Hi,
Please see these steps I did and help me where did it went wrong
Test done with Axis2 Trunk
** Create this anotated class
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService
public class TestJAXWSEchoService {
@WebMethod
public String echo(String s) {
return s;
}
}
** compile it and created a jar (TestJAXWSEchoService.jar) with that and put
it in the repository/servicejars directory
** check for the entery on axis2.xml with the JAXWSDeployer
** copy the jaxws-tools.jar and jaxwsrt.jar ship by sun to the axis2 lib
directory
** start axis2server
** results
[INFO] Deploying artifact : TestJAXWSEchoService.jar
[INFO] Deploying JAXWS annotated class TestJAXWSEchoService as a service -
TestJAXWSEchoServiceService.TestJAXWSEchoServicePort
** it was deployed with the name
TestJAXWSEchoServiceService.TestJAXWSEchoServicePorts , is this the
correct name according to the 2.1 specification?
** acess url http://localhost:8080/axis2/services/
Deployed services
TestJAXWSEchoServiceService.TestJAXWSEchoServicePort
Available operations
* echo
** to access the wsdl
http://localhost:8080/axis2/services/TestJAXWSEchoServiceService.TestJAXWSEchoServicePort?wsdl
Unable to generate WSDL 1.1 for this service
−
If you wish Axis2 to automatically generate the WSDL 1.1, then please +set
useOriginalwsdl as false in your services.xml
javax.xml.ws.WebServiceException: Error occurred generating WSDL file for
Web service implementation class {TestJAXWSEchoService}:
{java.lang.Exception: A WSDL Definition could not be generated for the
implementation class: TestJAXWSEchoService}
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:187)
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)
Caused by: java.lang.Exception: A WSDL Definition could not be generated for
the implementation class: TestJAXWSEchoService
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:177)
... 10 more
** As I refered into
http://ws.apache.org/axis2/1_4/jaxws-guide.html#BottomUpService it seems the
pojo is enough and there is not need to attach a wsdl in to this.
--
Thanks
Lahiru Sandakith
http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Commented: (AXIS2-3823) Validation errors on axis2.xml and web.xml of axis2-web app
[ https://issues.apache.org/jira/browse/AXIS2-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600677#action_12600677 ] Lahiru Sandakith commented on AXIS2-3823: - Please provide the patch, I will review it for you. > Validation errors on axis2.xml and web.xml of axis2-web app > --- > > Key: AXIS2-3823 > URL: https://issues.apache.org/jira/browse/AXIS2-3823 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: admin console >Affects Versions: 1.4 > Environment: Ubuntu Linux > Jdk 1.5.0.6 > Eclipse WTP 3.0 >Reporter: saminda wijeratne > > We were using axis2-web app in eclipse wtp 3.0 regarding a jsp validation > issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=186429) when we came > across 2 validation failure warnings for the axis2.xml and the web.xml of the > axis2-web app. > 1. > Description ResourcePathLocationType > CHKJ3010W: Welcome Files cannot begin or end with a /. web.xml > aa/WebContent/WEB-INF > [EMAIL PROTECTED] > (welcomeFile: /axis2-web/index.jsp) Validation Message > 2. > Description ResourcePathLocationType > No grammar constraints (DTD or XML schema) detected for the document. > axis2.xml aa/WebContent/WEB-INF/conf line 1 XML Problem > with a little bit of checking we found that the first warning was due to the > following tag in the web.xml > /axis2-web/index.jsp > removing the "/" in the begining removes the warning. > i.e. having the tag instead as, > axis2-web/index.jsp > the 2nd warning could be removed by adding a dtd definition to the axis2.xml > such as > > but does not know the real neccesity of such a tag to the web project. > with the above modification the system works without any breaks. and works as > usual. > I can create and send a patch using the above mentioned solutions for the > validation failures. I would like your ideas and suggestions on this regard. > Thank you -- 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: Estimated Complexity field in Jira
+1 for the idea, This will help in defining the time lines as well. Thanks Sandakith On Wed, May 7, 2008 at 8:00 AM, Samisa Abeysinghe < [EMAIL PROTECTED]> wrote: > I find that we have a field called "Estimated Complexity" in our Jira. > I propose that we use this field to mark issues to help people pick what > to fix based on their expertise. Specially helps with new contributions. > I find that the Harmony project is using this. The possible values are: > > * Unknown > * Novice > * Moderate > * Advanced > * Guru > * Needs James Gosling > > > I know we traverse through Jiras before a release to pick what to be > fixed. We may take a moment to mark this field as well. > > Thoughts please... > > Samisa... > > -- > Samisa Abeysinghe > > http://people.apache.org/~samisa/ <http://people.apache.org/%7Esamisa/> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for Axis2 1.4
Hi Dims, I had a quick test with axis2 eclipse plugins with the new artifacts and its all fine for me. Lets include the axis2 eclipse and idea plugins for the 1.4 tools release. Thanks Lahiru Sandakith On Wed, Apr 16, 2008 at 9:20 AM, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote: > I've had a quick test with the publish jars with the current work I'm > doing and it looks good. > > +1 for all. > > Saminda > > On Tue, Apr 15, 2008 at 7:20 PM, Davanum Srinivas <[EMAIL PROTECTED]> > wrote: > > > Oops! i just uploaded the dist's this morning. We can cut another > > 1.4.2 for xmlschema. > > > > -- dims > > > > On Tue, Apr 15, 2008 at 9:45 AM, Lawrence Mandel <[EMAIL PROTECTED]> > > wrote: > > > Dims, > > > > > > John did some testing with Woden and XmlSchema 1.4.1 and found a > > > regression with chameleon includes. He's going to respond shortly > > with > > > specifics. > > > > > > > > > Lawrence > > > > > > > > > > > > > > > > > > > > > Davanum Srinivas <[EMAIL PROTECTED]> > > > 04/11/2008 10:41 AM > > > > > > Please respond to > > > axis-dev@ws.apache.org > > > > > > > > > To > > > axis-dev@ws.apache.org > > > cc > > > [EMAIL PROTECTED], [EMAIL PROTECTED] > > > Subject > > > Re: [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for > > Axis2 > > > > > > > > > 1.4 > > > > > > > > > > > > > > > > > > > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > > Lawrence, > > > > > > looks like we have enough votes for this to pass, but will still have > > to > > > wait for a total of 72 hours. > > > > > > In the mean time, please go ahead and put out a vote for woden with > > jars > > > from this vote. > > > > > > thanks, > > > dims > > > > > > Lawrence Mandel wrote: > > > | Everything looks good after a quick sanity check with Woden. Here's > > my > > > +1 > > > | for XmlSchema and Axiom. I didn't test Neethi. > > > | > > > | Lawrence > > > | \ > > > | > > > | > > > | > > > | > > > | Davanum Srinivas <[EMAIL PROTECTED]> > > > | 04/10/2008 12:47 AM > > > | Please respond to > > > | axis-dev@ws.apache.org > > > | > > > | > > > | To > > > | Axis developer list , > > [EMAIL PROTECTED] > > > | cc > > > | > > > | Subject > > > | [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for > > Axis2 > > > 1.4 > > > | > > > | > > > | > > > | > > > | > > > | > > > | Folks, > > > | > > > | Here are the src/bin dist artifacts, the maven2 repo and a > > revisions.txt > > > | with the svn information: > > > | > > > | > > > http://people.apache.org/~dims/axis2-1.4-commons/<http://people.apache.org/%7Edims/axis2-1.4-commons/> > > > | > > > | > > > | Please VOTE: > > > | > > > | [ ] - Ship XmlSchema 1.4.1 > > > | [ ] - Don't Ship XmlSchema 1.4.1 > > > | > > > | [ ] - Ship Axiom 1.2.6 > > > | [ ] - Don't Axiom 1.2.6 > > > | > > > | [ ] - Ship Neethi 2.0.3 > > > | [ ] - Don't Ship Neethi 2.0.3 > > > | > > > | Here's my +1 for all 3 distributions. > > > | > > > | thanks, > > > | dims > > > > > > - > > - > > > 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] > > > > > > -BEGIN PGP SIGNATURE- > > > Version: GnuPG v1.4.5 (Cygwin) > > > > > > iD8DBQFH/3iAgNg6eWEDv1kRAnSMAJ4pCg41/QNxG8uwUUrKB7PQZoTaTwCeKDH+ > > > Z4XH0iKScqHq0pF9xjvZez8= > > > =LMDo > > > -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] > > > > > > > > > > > > > > -- > > Davanum Srinivas :: http://davanum.wordpress.com > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Saminda Abeyruwan > > Senior Software Engineer > WSO2 Inc. - www.wso2.org -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Commented: (AXIS2-3382) NPE throws when invoking jax-ws calculator sample service
[ https://issues.apache.org/jira/browse/AXIS2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579781#action_12579781 ] Lahiru Sandakith commented on AXIS2-3382: - Hi Roy, no objection on place it again, Thanks Lahiru > 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 > Fix For: 1.4 > > Attachments: Fix_for_Axis2_3382.txt > > > - 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]
Re: [axis2] VOTE: Erange Jayasundera for committer
+1 to Eranga, On Fri, Feb 29, 2008 at 10:23 PM, Sanjiva Weerawarana <[EMAIL PROTECTED]> 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. > -- > Sanjiva Weerawarana, Ph.D. > Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ > Member; Apache Software Foundation; http://www.apache.org/ > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] Writing custom deployer for JAXWS that picks classes from WEB-INF/classes
Hi Dims, Yes, I will do that and let you know the results. Thanks Lahiru On Fri, Feb 15, 2008 at 9:13 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Lahiru, > > Yes, in fact, we can place all the jars in say tomcat's common lib, then > we'd only be touching the web.xml in the WAR > and adding a axis2.xml in WEB-INF. We are allowed to do just those changes > to the TCK war as i mentioned a week or so ago. > > Please try this with the TCK wars and let us know how it goes. > > thanks, > dims > > Lahiru Sandakith wrote: > | Hi Dims, > | > | What I initially thought of this was to modify axis2.war, like a > scenario of > | getting the TCK war and have a merge. > | But your suggestion seems to be more appropriate because here we can > | parallely deploy all the TCK wars in container. > | > | Thanks > | Lahiru > | > | On Thu, Feb 14, 2008 at 11:03 PM, Davanum Srinivas <[EMAIL PROTECTED]> > | wrote: > | > | Roy, > | > | We would not have any repository structure at all. We would > | > | - take an existing WAR from TCK > | - drop Axis2 jars into WEB-INF/lib > | - drop a axis2.xml into WEB-INF/ > | > | That's should be the only changes. > | > | Then WAR it again and drop it into tomcat\webapps directory. > | > | thanks, > | dims > | > | Roy Wood wrote: > | | Dims (et.al.), > | | > | | I agree that Plan B would be the quickest approach, especially as we > | | prepare for TCK. > | | > | | But, for Plan A: Assuming our new 'WARDeployer' recurses a war > directory > | | structure, what would our directory structure look like then? > | | > | | I'm assuming something like this: (where war1directory and > war2directory > | | are expanded .wars) > | | > | | repository > | | | > | | |- - - - - - jaxws-services > | | | > | | |- - - - war1directory > | | | > | | |- - - - war2directory > | | > | | > | | Is that correct? Or, is 'jaxws-services' a directory that we wouldn't > | have > | | visibility to for TCK? > | | > | | > | | Roy A. Wood, Jr. > | | WebSphere Development - Web Services > | | [EMAIL PROTECTED] > | | 512-838-0663 T/L:678-0663 FAX:512-838-3703 > | | 11501 Burnet Road, Austin TX 78758 (Internal ZIP: 9372) > | | > | | > | | > | | Nicholas L Gallardo/Austin/[EMAIL PROTECTED] > | | 02/14/2008 11:01 AM > | | Please respond to > | | axis-dev@ws.apache.org > | | > | | > | | To > | | axis-dev@ws.apache.org > | | cc > | | > | | Subject > | | Re: [Axis2] Writing custom deployer for JAXWS that picks classes from > | | WEB-INF/classes > | | > | | > | | > | | > | | > | | > | | Dims, > | | > | | Yep, I see the problem now... I was coming at it thinking that the > | | directory you would be specifying for the deployer would be > | | "$AXIS2_HOME/repository/jaxws-services" and that the file extension > | would > | | be ".war". > | | > | | I agree with Dustin in that having the deployment engine recurse seems > | | like a good solution (which you're already looking into). :) > | | > | | -Nick > | | > | | > | | Davanum Srinivas <[EMAIL PROTECTED]> > | | > | | > | | Davanum Srinivas <[EMAIL PROTECTED]> > | | 02/14/2008 10:32 AM > | | > | | Please respond to > | | axis-dev@ws.apache.org > | | > | | > | | > | | > | | To > | | > | | axis-dev@ws.apache.org > | | > | | cc > | | > | | > | | Subject > | | > | | Re: [Axis2] Writing custom deployer for JAXWS that picks classes from > | | WEB-INF/classes > | | > | | > | | > | | > | | > | | Nick, > | | > | | The way the deployment engine is written a custom deployer has to > | specify > | | a specific directory and a file extension. the > | | deployment engine looks into the directory (1 level only, not > recursive) > | | and finds files with the specific extension. > | | When it finds one of those, it will call the custom deployers deploy > | | method for *that* specific file. > | | > | | Do you see the problem now? > | | > | | Also please see below. > | | > | | thanks, > | | dims > | | > | | Nicholas L Gallardo wrote: > | | | I guess I'm missing something then. It's not clear to me what that > | text > | | | file is providing. Let me further my example... > | | | > | | | $AXIS2_HOME/repository/jaxws-services/ > | | | > | | | SimpleJAXWSService.war/ > | | | | > | | | |---WEB-INF/wsdl/SimpleService.wsdl > | | | | > | | | |---WEB-INF/classes/org/ap
Re: [Axis2] Writing custom deployer for JAXWS that picks classes from WEB-INF/classes
> | | service impl) > | | > | | Would the text file be used in this second case? If so, would it just > | be > | | used to isolate the class that is the target service from any other > | classes > | | in the module? I feel like I'm missing something here, but it seems > | like > | | you should be able to pickup the necessary info without the need for > | that > | | text file. > | > | Am not looking at this option because it's not how WAR's are packaged > for > | the TCKs. > | > | | -Nick > | | > | | > | | > | | > | | > | | Davanum Srinivas > | | <[EMAIL PROTECTED] > | | m> To > | |axis-dev@ws.apache.org > | | 02/14/2008 09:53 cc > | | AM > | | Subject > | |Re: [Axis2] Writing custom > | deployer > | | Please respond to for JAXWS that picks classes > from > | | [EMAIL PROTECTED] WEB-INF/classes > | |e.org > | | > | | > | | > | | > | | > | | > | | > | | > | | > | | Nick, > | | > | | yep. Under jaxws-services, there could be jar's or text files (enough > | | information inside - fully qualified name of the > | | class with annotations) > | | > | | thanks, > | | dims > | | > | | Nicholas L Gallardo wrote: > | | | Dims, > | | | > | | | So with Plan B, I'm assuming your directory structure would look > like > | | this? > | | | > | | | $AXIS2_HOME/repository > | | | | > | | | |-> modules/ > | | | | > | | | |-> services/ > | | | | > | | | |-> jaxws-services/ > | | | > | | | Given that, then someone would come along and drop their WARs > directly > | in > | | | there? > | | | > | | | -Nick > | | | > | | | > | | | > | | | > | | | > | | | Davanum Srinivas > | | | <[EMAIL PROTECTED] > | | | m> > | | To > | | |axis-dev@ws.apache.org > | | | 02/13/2008 04:13 > | | cc > | | | PM > | | | > | | Subject > | | |[Axis2] Writing custom > deployer > | | for > | | | Please respond to JAXWS that picks classes from > | | | [EMAIL PROTECTED] WEB-INF/classes > | | |e.org > | | | > | | | > | | | > | | | > | | | > | | | > | | | > | | | > | | | > | | | Deepal, Roy, Sandakith, Jeff, > | | | > | | | Currently, when one writes a deployer, it needs to have a directory > | and a > | | | file extension for it. The deployment engine > | | | scans all the directories and if it finds a file with that extension > | it > | | | will invoke it. > | | | > | | | Problem is in the TCK case, all we have are classes in > WEB-INF/classes > | | with > | | | the package names dictating the directory > | | | structure under it (and the class files deep somewhere inside) > | | | > | | | Plan A: Is there to write a new deployer that can traverse the file > | | system > | | | by itself (NOT by the deployment engine)? > | | | > | | | Plan B: Just create a directory called jaxws-services and drop a > text > | | file > | | | or xml file with enough information (just the > | | | class name is enough). then we can use the current way deployment > | engine > | | | works... > | | | > | | | Thoughts please? > | | | > | | | thanks, > | | | dims > | | > | | - > | | 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] > | > | > > - - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (Cygwin) > > iD8DBQFHtHtegNg6eWEDv1kRAp1xAKDHrdNuGTCvceCDuOYOc/pL7//zYACcDfRH > zsiXXE1c3d2tls86GzRooFs= > =0aSY > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] Writing custom deployer for JAXWS that picks classes from WEB-INF/classes
Hi Dims/All, My feeling is, though the plan A will be faster we will have more flexibility if we are following plan A. Thanks Lahiru On Thu, Feb 14, 2008 at 3:43 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Deepal, Roy, Sandakith, Jeff, > > Currently, when one writes a deployer, it needs to have a directory and a > file extension for it. The deployment engine > scans all the directories and if it finds a file with that extension it > will invoke it. > > Problem is in the TCK case, all we have are classes in WEB-INF/classes > with the package names dictating the directory > structure under it (and the class files deep somewhere inside) > > Plan A: Is there to write a new deployer that can traverse the file system > by itself (NOT by the deployment engine)? > > Plan B: Just create a directory called jaxws-services and drop a text file > or xml file with enough information (just the > class name is enough). then we can use the current way deployment engine > works... > > Thoughts please? > > thanks, > dims > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (Cygwin) > > iD8DBQFHs2twgNg6eWEDv1kRAkxIAJ9gPVKAVCdbbOqQfN4Tiba865ktgACeP+iB > FBvU9GjSZHu3VGItGcV2kVA= > =ryHL > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] Generating WSDL for JAXWS artifacts
Hi Dims, I am thinking of not extending the pojo deployer on this regard. Since the forward set of deployable service artifact of the sun TCK are in the form of war files and seems we are not allowed it to change them as we want. We have to get our deployment mechanism to get them sorted out. How about using our axis2 webapp and then have an extension to the deployment from plugable component as TCK suit and made the sun specific wars deployable and we can have the services up on Axis2. Actually we can make this deployment extension as JAXWS Deployer in JAXWS module. This was my idea rather than going for the POJO Deployer on this. Thoughts ? Thanks Lahiru Sandakith On Feb 5, 2008 4:16 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Deepal, Sandakith, > > Right now we pick up just a few of the annotations from a java class. > Namely the ones in > org.apache.axis2.description.java2wsdlAnnotationConstants. I believe we > need to take into account *all* possible > annotations in the spec to pass the TCK. > > ~String WEB_SERVICE = "javax.jws.WebService"; > ~String WEB_METHOD = "javax.jws.WebMethod"; > ~String WEB_PARAM = "javax.jws.WebParam"; > ~String WEB_RESULT = "javax.jws.WebResult"; > ~String TARGETNAMESPACE = "targetNamespace"; > ~String NAME = "name"; > ~String SERVICE_NAME = "serviceName"; > ~String EXCLUDE = "exclude"; > ~String ACTION = "action"; > ~String WSDL_LOCATION = "wsdlLocation"; > ~String OPERATION_NAME ="operationName"; > > One option that was taken by the Geronimo team was to use the JAXWS RI's > wsgen tool programatically. We should probably > start looking at the same as well. > > We need to figure out how to support user specified WSDL's as well in the > PojoDeployer..Thoughts? > > thanks, > dims > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (Cygwin) > > iD8DBQFHp5XYgNg6eWEDv1kRAu9yAKCnNI0KoFMIEIv2Re4BupJEvYIVKwCgnfS8 > j1O6XscwHo5eDOauyZvJIJQ= > =/MI4 > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
Hi Dims, As I understood in the forward set of testcases of the TCK we have a set of sun war files which we can not make any changes for that other than some parts of the web.xml. We have to get our deployment configured in to deploying this and pass the testcases. On the reverse set of test cases we have set of wsdls that we have to codegenerate the services and pass the test cases by deploying those services. Thanks Lahiru On Feb 6, 2008 1:34 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Jeff, > > looks like we need more information from the folks who have the TCK. > specifically some layout hints on where the service > classes are and where the wsdl's and xsd's are. > > ~From what i can tell with the information we have now. We need to be able > to plugin the RI's wsgen to generate wsdl if > it's absent. We need to be able to pick up wsdl/xsd for a specific service > if they are already in the war. and we need > to be able to pick up all the classes with webservice and > webservicesprovider annotations from the war and turn them > into services. > > thanks, > dims > > Jeff Barrett wrote: > | ims, > | > | My understanding of what the TCK permits is the same as yours. You can > | remove the RI-specific DDs and can add your own vendor-specific DDs. > | However, anything that exists in the TCK application archive (such as > | classes, WSDL, etc) must remain as is. So, the classes couldn't be > moved > | from WEB-INF/classes to some POJO-deployer-specific location. Another > | consideration is that a single TCK application archive, I believe, > | contains multiple services AND there may be multiple TCK application > | archive. > | > | Is any of that going to cause problems for the POJO deployer? > | > | I talked with Roy Wood about this a bit, and I got the impression that > | having multiple archives and multiple services may be a problem that > needs > | to be fixed in the POJO deployer. Also, that it would be possible to > | point the POJO deployer at a specific directory or archive, so it could > be > | pointed to an "installed applications" directory and be able to find the > | services there. It seems to me that would work for the TCKs. > | > | Thoughts? > | > | Thanks, > | Jeff > | > | IBM Software Group - WebSphere Web Services Development > | Phone: 512-838-4587 or Tie Line 678-4587 > | Internet e-mail and Sametime ID: [EMAIL PROTECTED] > | > | > | > | Davanum Srinivas <[EMAIL PROTECTED]> > | 02/04/2008 04:45 PM > | Please respond to > | axis-dev@ws.apache.org > | > | > | To > | axis-dev@ws.apache.org > | cc > | > | Subject > | [Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml > | > | > | > | > | > | > | Resending using [Axis2] since looks like no one looks at the emails > | otherwise :) > | > | Davanum Srinivas wrote: > | | One more observation: > | | > | | In PojoDeployer, we can't specify a custom wsdl (yet!) When one writes > a > | | WebServiceProvider, typically they provide a > | | wsdl and the xsd's. > | | > | | -- dims > | | > | | Davanum Srinivas wrote: > | | | Sandakith, Roy, > | | | Looks like PojoDeployer picks up only the javax.jws.WebService > | | | annotation and not the javax.xml.ws.WebServiceProvider > | | | annotation. > | | | > | | | Sandakith, > | | | ~From what i know, we cannot modify WAR's shipped by the TCK. Only > | | | changes allowed are removing sun specific dd's and > | | | adding our own and maybe change the port #'s...This may have an > effect > | | | on which way to lean using PojoDeployer vs > | | | JAXWSMessageReceiver in services.xml as we cannot modify the WAR's > to > | | | suit the pojo deployer. Please note that all the > | | | existing services.xml in the modules\jaxws are handwritten :( > | | | > | | | thanks, > | | | dims > > - - > 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] > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (Cygwin) > > iD8DBQFHqME4gNg6eWEDv1kRAisTAJ9VgDn6Iu/WWxQQmAGOf5iWW6posQCgvbVz > NiM/pP0YGE4/+AFCCoyuwnI= > =oDOA > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: mvn error finding Woden 20071221 SNAPSHOT
Actually the woden is now split in to components and we have 1.0-SNAPSHOTjars woden-api/ <http://people.apache.org/repo/m2-snapshot-repository/org/apache/woden/woden-api/> woden-impl-dom/ <http://people.apache.org/repo/m2-snapshot-repository/org/apache/woden/woden-impl-dom/> woden-impl-om/ <http://people.apache.org/repo/m2-snapshot-repository/org/apache/woden/woden-impl-om/> available and changing the axis2 patent pom did passed the full build for me. we can move to 1.0-SNAPSHOT now. Thanks Sandakith. On Jan 30, 2008 9:12 AM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote: > Hi Tom, > > On Jan 30, 2008 3:28 AM, Tom Seelbach <[EMAIL PROTECTED]> wrote: > > > I'm running a local build of just axis2 kernel and I get this error. > > If you look at > > http://people.apache.org/repo/m2-snapshot-repository/org/apache/woden/woden/1.0-incubating-SNAPSHOT/maven-metadata.xml, > > it seems to point to 20071221.1400302-825.jar but that jar is not > > there. > > > > Does this have something to do with Woden graduating from incubator? Or > > have i hosed my local build env. (this is not the continuum build which is > > running fine). > > > backing up woden folder of the m2 repository, then building the kernel > did not download woden and only the metadate came, > still axis2 module parent had 1.0-incubating-SNAPSHOT > > we need to move to 1.0-SNAPSHOT as it did > graduated. > But the problem is again > http://people.apache.org/repo/m2-snapshot-repository/org/apache/woden/woden/1.0-SNAPSHOT/ > did not have a artifact up there. We need to contact woden people to get > an artifact up there. > > Thanks > Sandakith > > > > > > > thanks, > > Tom > > > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: mvn error finding Woden 20071221 SNAPSHOT
Hi Tom, On Jan 30, 2008 3:28 AM, Tom Seelbach <[EMAIL PROTECTED]> wrote: > I'm running a local build of just axis2 kernel and I get this error. If > you look at > http://people.apache.org/repo/m2-snapshot-repository/org/apache/woden/woden/1.0-incubating-SNAPSHOT/maven-metadata.xml, > it seems to point to 20071221.1400302-825.jar but that jar is not there. > > Does this have something to do with Woden graduating from incubator? Or > have i hosed my local build env. (this is not the continuum build which is > running fine). backing up woden folder of the m2 repository, then building the kernel did not download woden and only the metadate came, still axis2 module parent had 1.0-incubating-SNAPSHOT we need to move to 1.0-SNAPSHOT as it did graduated. But the problem is again http://people.apache.org/repo/m2-snapshot-repository/org/apache/woden/woden/1.0-SNAPSHOT/ did not have a artifact up there. We need to contact woden people to get an artifact up there. Thanks Sandakith > > > thanks, > Tom > >
Re: [Axis2] JAXWS version in Axis2 1.4
Sent this mail to jcp-open@ and cc'ed geir Hi All, Apache Axis2 1.3 (moving towards 1.4) is contain an implementation of JSR 224 (JAXWS 2.1). In order to test the implementation for full compatibility with JSR-224 the respective JAXWS 2.1 TCK would be needed. Apache Axis2 team would like to kindly request the Apache responsible person(s) to request that TCK from Sun! As the person who like to work on this in perspective of Axis2, I have submitted my NDA on TCK on fax. -- Best Regards send another copy to [EMAIL PROTECTED] as well Thanks Lahiru Sandakith On Jan 26, 2008 9:32 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Please drop a note to jcp-open@ and cc geir. I believe the cxf folks have > the 2.1 TCK already. worth dropping another > email to [EMAIL PROTECTED] as well. the jcp page is probably outdated. > > thanks, > dims > > Lahiru Sandakith wrote: > | Hi Dims/Nick, > | > | So what will be our strategy on obtaining the TCK 2.1 version. from the > jcp > | page on apache (http://www.apache.org/jcp/) it says we only have the 2.0 > , > | Shall I post a request mail to the jcp-open list? > | > | Thanks > | Lahiru > | > | On Jan 25, 2008 7:31 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > | > | Lahiru, > | > | these are open questions. Remember the sun RI implementation also has a > | sun-jaxws.xml which is a sun specific deployment > | descriptor. CXF also has its own. From what i recall the CXF TCK folks > use > | a stylesheet to convert the sun deployment > | descriptor into a CXF specific one. > | > | thanks, > | dims > | > | Lahiru Sandakith wrote: > | | Hi Dims, > | | Ok, So where can I find these features that will be included. I am not > | that > | | familiar with the spec, but currently looking in to it. > | | I am +1 on adding extra key/value pairs in services.xml , but aren't > | that > | | violates the TCK compliance. I mean having additional configurations > | to > | | the Axis2 for deployment. > | | > | | Thanks > | | Lahiru > | | > | | On Jan 25, 2008 5:13 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > | | > | | Lahiru, > | | > | | Yep, both work!. We need to figure out a couple of more things. See if > | | there are jaxws "features" that can/need to be > | | turned on/off and maybe add some key/value pairs in services.xml to > | | control them. Some annotations may be overridden by > | | deployment descriptors. We need to come up with a list of those and be > | | able to specify them in services.xml too. Stay tuned. > | | > | | thanks, > | | dims > | | > | | Lahiru Sandakith wrote: > | | | Hi Devs, > | | | > | | | +1 for the total JAXWS support on Axis2 1.4. And also +1 for going > | with > | | | JAXWS 2.1, lets merge it to the trunk. > | | | I have done some testing with the sample available in the and as I > saw > | | it > | | | now the AAR based model works with JAXWS MR. > | | | Also JSR 181 annotated pojos are working with the POJO Deployer with > | | current > | | | Axis2 trunk. > | | | > | | | Thanks > | | | Lahiru Sandakith > | | | > | | | On Jan 16, 2008 10:20 AM, Deepal jayasinghe <[EMAIL PROTECTED]> > wrote: > | | | > | | |> Hi Dims > | | |>> , Nick, Rich, > | | |>> > | | |>> - I believe the jaxws-tck svn and the associated mailing list is > | | ready. > | | |>> - cxf folks i am told are running JAXWS 2.1 TCK > | | |>> - Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside. > | | |>> > | | |>> So, what should we do for Axis2 1.4? I just saw Nick's jira float > | by > | | |>> [1] and wanted to kick start the discussion. Please see Steve's > | | |>> analysis [2] and the JAXWS change log [3] > | | |>> > | | |> We really need to have full support of JAXWS in Axis2 1.4 , most > | | |> importantly it will be great of we could have a sample and a > document > | | |> explaining how to use Axis2 JAXWS. > | | |> > | | |> -Deepal > | | |>> thanks, > | | |>> dims > | | |>> > | | |>> [1] https://issues.apache.org/jira/browse/AXIS2-3448 > | | |>> [2] http://1060.org/blogxter/publish/5 > | | |>> [3] > | | |> > | | > | > http://jcp.org/aboutJava/communityprocess/maintenance/jsr224/JAXWS_2.1_ChangeLog.pdf > | | |>> > | | |> > | | |> > - > | | |> To unsubscribe, e-mail: [EMAIL PROTECTED] > | | |> For additional commands, e-mail: [EMAIL PROTECTED] > | |
Re: [Axis2] JAXWS version in Axis2 1.4
Hi Dims/Nick, So what will be our strategy on obtaining the TCK 2.1 version. from the jcp page on apache (http://www.apache.org/jcp/) it says we only have the 2.0, Shall I post a request mail to the jcp-open list? Thanks Lahiru On Jan 25, 2008 7:31 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Lahiru, > > these are open questions. Remember the sun RI implementation also has a > sun-jaxws.xml which is a sun specific deployment > descriptor. CXF also has its own. From what i recall the CXF TCK folks use > a stylesheet to convert the sun deployment > descriptor into a CXF specific one. > > thanks, > dims > > Lahiru Sandakith wrote: > | Hi Dims, > | Ok, So where can I find these features that will be included. I am not > that > | familiar with the spec, but currently looking in to it. > | I am +1 on adding extra key/value pairs in services.xml , but aren't > that > | violates the TCK compliance. I mean having additional configurations > to > | the Axis2 for deployment. > | > | Thanks > | Lahiru > | > | On Jan 25, 2008 5:13 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > | > | Lahiru, > | > | Yep, both work!. We need to figure out a couple of more things. See if > | there are jaxws "features" that can/need to be > | turned on/off and maybe add some key/value pairs in services.xml to > | control them. Some annotations may be overridden by > | deployment descriptors. We need to come up with a list of those and be > | able to specify them in services.xml too. Stay tuned. > | > | thanks, > | dims > | > | Lahiru Sandakith wrote: > | | Hi Devs, > | | > | | +1 for the total JAXWS support on Axis2 1.4. And also +1 for going > with > | | JAXWS 2.1, lets merge it to the trunk. > | | I have done some testing with the sample available in the and as I saw > | it > | | now the AAR based model works with JAXWS MR. > | | Also JSR 181 annotated pojos are working with the POJO Deployer with > | current > | | Axis2 trunk. > | | > | | Thanks > | | Lahiru Sandakith > | | > | | On Jan 16, 2008 10:20 AM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > | | > | |> Hi Dims > | |>> , Nick, Rich, > | |>> > | |>> - I believe the jaxws-tck svn and the associated mailing list is > | ready. > | |>> - cxf folks i am told are running JAXWS 2.1 TCK > | |>> - Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside. > | |>> > | |>> So, what should we do for Axis2 1.4? I just saw Nick's jira float > by > | |>> [1] and wanted to kick start the discussion. Please see Steve's > | |>> analysis [2] and the JAXWS change log [3] > | |>> > | |> We really need to have full support of JAXWS in Axis2 1.4 , most > | |> importantly it will be great of we could have a sample and a document > | |> explaining how to use Axis2 JAXWS. > | |> > | |> -Deepal > | |>> thanks, > | |>> dims > | |>> > | |>> [1] https://issues.apache.org/jira/browse/AXIS2-3448 > | |>> [2] http://1060.org/blogxter/publish/5 > | |>> [3] > | |> > | > http://jcp.org/aboutJava/communityprocess/maintenance/jsr224/JAXWS_2.1_ChangeLog.pdf > | |>> > | |> > | |> - > | |> 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] > |> > |> > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (Cygwin) > > iD8DBQFHmeuggNg6eWEDv1kRAqQVAJ9Inm+mx7gNlgedDTtZaKGLct5RywCfRV0l > iMkGJx9YbMF5e2eiFPXngwA= > =u1Wb > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] JAXWS version in Axis2 1.4
Hi Dims, Ok, So where can I find these features that will be included. I am not that familiar with the spec, but currently looking in to it. I am +1 on adding extra key/value pairs in services.xml , but aren't that violates the TCK compliance. I mean having additional configurations to the Axis2 for deployment. Thanks Lahiru On Jan 25, 2008 5:13 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Lahiru, > > Yep, both work!. We need to figure out a couple of more things. See if > there are jaxws "features" that can/need to be > turned on/off and maybe add some key/value pairs in services.xml to > control them. Some annotations may be overridden by > deployment descriptors. We need to come up with a list of those and be > able to specify them in services.xml too. Stay tuned. > > thanks, > dims > > Lahiru Sandakith wrote: > | Hi Devs, > | > | +1 for the total JAXWS support on Axis2 1.4. And also +1 for going with > | JAXWS 2.1, lets merge it to the trunk. > | I have done some testing with the sample available in the and as I saw > it > | now the AAR based model works with JAXWS MR. > | Also JSR 181 annotated pojos are working with the POJO Deployer with > current > | Axis2 trunk. > | > | Thanks > | Lahiru Sandakith > | > | On Jan 16, 2008 10:20 AM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > | > |> Hi Dims > |>> , Nick, Rich, > |>> > |>> - I believe the jaxws-tck svn and the associated mailing list is > ready. > |>> - cxf folks i am told are running JAXWS 2.1 TCK > |>> - Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside. > |>> > |>> So, what should we do for Axis2 1.4? I just saw Nick's jira float by > |>> [1] and wanted to kick start the discussion. Please see Steve's > |>> analysis [2] and the JAXWS change log [3] > |>> > |> We really need to have full support of JAXWS in Axis2 1.4 , most > |> importantly it will be great of we could have a sample and a document > |> explaining how to use Axis2 JAXWS. > |> > |> -Deepal > |>> thanks, > |>> dims > |>> > |>> [1] https://issues.apache.org/jira/browse/AXIS2-3448 > |>> [2] http://1060.org/blogxter/publish/5 > |>> [3] > |> > http://jcp.org/aboutJava/communityprocess/maintenance/jsr224/JAXWS_2.1_ChangeLog.pdf > |>> > |> > |> - > |> To unsubscribe, e-mail: [EMAIL PROTECTED] > |> For additional commands, e-mail: [EMAIL PROTECTED] > |> > |> > | > | > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (Cygwin) > > iD8DBQFHmctQgNg6eWEDv1kRApVLAJ4s2aMe9uC8L6/ZcFZc8wDTqz/8TgCg6MC6 > 860fJMf/6+GT4DnydrNI8fQ= > =9z/Y > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] JAXWS version in Axis2 1.4
Hi Devs, +1 for the total JAXWS support on Axis2 1.4. And also +1 for going with JAXWS 2.1, lets merge it to the trunk. I have done some testing with the sample available in the and as I saw it now the AAR based model works with JAXWS MR. Also JSR 181 annotated pojos are working with the POJO Deployer with current Axis2 trunk. Thanks Lahiru Sandakith On Jan 16, 2008 10:20 AM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > Hi Dims > > , Nick, Rich, > > > > - I believe the jaxws-tck svn and the associated mailing list is ready. > > - cxf folks i am told are running JAXWS 2.1 TCK > > - Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside. > > > > So, what should we do for Axis2 1.4? I just saw Nick's jira float by > > [1] and wanted to kick start the discussion. Please see Steve's > > analysis [2] and the JAXWS change log [3] > > > We really need to have full support of JAXWS in Axis2 1.4 , most > importantly it will be great of we could have a sample and a document > explaining how to use Axis2 JAXWS. > > -Deepal > > thanks, > > dims > > > > [1] https://issues.apache.org/jira/browse/AXIS2-3448 > > [2] http://1060.org/blogxter/publish/5 > > [3] > http://jcp.org/aboutJava/communityprocess/maintenance/jsr224/JAXWS_2.1_ChangeLog.pdf > > > > > > > --------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [axis2] proposal: jaxws-integration module
+1 for moving the tests in to an independent module jaxws-integration. Thanks Lahiru Sandakith On Jan 25, 2008 2:25 AM, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote: > All, > > As we start the process of integrating the JAX-WS runtime into the Axis2 > deployment model, it seems like a good time to revisit the existing > structure for the jaxws module. I'm specifically interested in improving the > structure of how function or end-to-end tests are added in. > > Right now, the modules/jaxws/test bucket is a mix of both unit tests and > function tests. I'd like to split that up and introduce a new module, > jaxws-integration, that has the function tests in a more organized framework > than exists today. This would also allow us to remove the wonky JAXWSTest > driver that exists today, making it easier to drop unit tests in and run > them individually. > > As time goes on, if we need a special location for deployment code for > JAX-WS, this module can serve as a repository for that. > > Thoughts? > > -Nick > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: running axis2 from eclipse
Hi Marlon, I select a module where normally all the dependencies are set, ex integration will be good because it has all the dependencies set to run integration test. then I execute this part of the code inside a class main method , ConfigurationContext confContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem( AXIS2_REPOSITORY_LOCATION, AXIS2_CONFIG_FILE); SimpleHTTPServer simpleHttpServer = new SimpleHTTPServer(confContext,8080); simpleHttpServer.start(); Thanks Lahiru Sandakith On Jan 24, 2008 11:28 PM, Marlon Luz <[EMAIL PROTECTED]> wrote: > Hi All, > > I already checkout the axis2 source code from subversion to my Eclipse > IDE! All dependencies are OK and the all code was built by Eclipse Build > Automatically. Now, I want run axis2 server from eclipse IDE, how I do that > ? > > br, > Marlon Luz > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: how to deploy axis2 from Eclipse IDE ?
Hi Marlon, These will help you, http://www.eclipse.org/webtools/community/tutorials/BottomUpAxis2WebService/bu_tutorial.html http://wso2.org/library/1719 http://wso2.org/library/2839 Thanks Lahiru Sandakith On Jan 25, 2008 12:07 AM, Marlon Luz <[EMAIL PROTECTED]> wrote: > Hi all, > > I checkout axis2 source code from svn How I can deploy axis2 from > Eclipse IDE ? Run a ant build.xml? wich build.xml and wich module ? > > br, > Marlon Luz > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Resolved: (AXIS2-3324) Document JSR181 support
[ https://issues.apache.org/jira/browse/AXIS2-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3324. - Resolution: Fixed Added the documentation under the pojo guide in axis2. Fixed in Committed revision 614423. > Document JSR181 support > --- > > Key: AXIS2-3324 > URL: https://issues.apache.org/jira/browse/AXIS2-3324 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Paul Fremantle > Assignee: Lahiru Sandakith > > Although there is JSR181 annotation support there is no documentation. Even > the sample doesn't even have a README! -- 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: WSAS-603 - I am getting the same stack exception -- Still reproductible
n.java:206) > [java] at org.mortbay.jetty.handler.HandlerCollection.handle( > HandlerCollection.java:114) > [java] at org.mortbay.jetty.handler.HandlerWrapper.handle( > HandlerWrapper.java:139) > [java] at org.mortbay.jetty.Server.handle(Server.java:324) > [java] at org.mortbay.jetty.HttpConnection.handleRequest( > HttpConnection.java:505) > [java] at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete( > HttpConnection.java:828) > [java] at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514) > [java] at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java > :211) > [java] at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java > :380) > [java] at > org.mortbay.io<http://org.mortbay.io.nio.selectchannelendpoint.ru/> > .nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395) > [java] at org.mortbay.thread.BoundedThreadPool$PoolThread.run( > BoundedThreadPool.java:450) > > Please suggest what to do. > > Thank you, > Virgil > - Original Message > From: Lahiru Sandakith <[EMAIL PROTECTED]> > To: axis-dev@ws.apache.org > Sent: Thursday, January 17, 2008 12:26:52 PM > Subject: Re: WSAS-603 - I am getting the same stack exception > > Hi Vergil, > The issue was fixed in the svn trunk and can you please verify with the > axis2 nightly build, and get back to us. > Also this will be available in the next Axis2 and therefore WSAS also. > Thanks > Lahiru Sandakith. > > > On Jan 17, 2008 2:30 PM, Afkham Azeez <[EMAIL PROTECTED]> wrote: > > > It should be the same issue since it is the same Axis2 that is used by > > WSAS. Please try out the Axis2 nightly build at > > http://people.apache.org/dist/axis2/nightly/ > > > > > > Thanks > > Azeez > > > > > > On Jan 17, 2008 1:49 PM, Trasca Virgil <[EMAIL PROTECTED] > wrote: > > > > > Hi Azeez, > > > > > >Sorry for insisting so much. I am not using WSAS 2.1 only > > > axis2.war 1.3. Because of that I want you to confirm me that what I > > > found is the same issue (as I am using Axis1.3 and you are saying > > > about wsas). Also if it is the same issue I am intersted when it will be > > > fixed in Axis2.war as I am using this one and not WSAS. I assume it > > > will be fixed in Axis2 1.4. > > > > > > When will 1.4 be released? Till then is it possible that you will send > > > me an updated jar file that will contain the fix so I can test it? > > > > > > Thank you, > > > Virgil > > > > > > - Original Message > > > From: Afkham Azeez <[EMAIL PROTECTED]> > > > To: axis-dev@ws.apache.org > > > Sent: Thursday, January 17, 2008 8:29:38 AM > > > Subject: Re: WSAS-603 - I am getting the same stack exception > > > > > > Hi Virgil, > > > WSAS is an enterprise ready Web services engine powered by Apache > > > Axis2. You could deploy Axis2 Web services on WSAS and also there are many > > > more value additions. The JIRA you cited is related to this product. In > > > fact, the WSAS 2.1 release was based on Axis2 1.3, and the next > > > 2.2release contains many bug fixes to Axis2 including the issue you cited. > > > > > > For further information see: > > > > > > 1. http://wso2.com/products/wsas/ > > > 2. https://wso2.org/projects/wsas/java > > > 3. http://wso2.org/library/821 > > > > > > Thanks > > > Azeez > > > > > > On Jan 17, 2008 11:44 AM, Trasca Virgil <[EMAIL PROTECTED]> > > > wrote: > > > > > > > Hi, > > > > > > > > What is WSAS? I am using Axis2 1.3 & ADB and I get this > > > > exception stack. Can you confirm me that the issue I found is the same > > > > like > > > > http://wso2.org/jira/browse/WSAS-603? > > > > > > > > Thank you, > > > > Virgil > > > > > > > > > > > > - Original Message > > > > From: Afkham Azeez <[EMAIL PROTECTED] > > > > > To: axis-dev@ws.apache.org > > > > Sent: Thursday, January 17, 2008 7:29:15 AM > > > > Subject: Re: WSAS-603 - I am getting the same stack exception > > > > > > > > FYI, issue WSAS-603 has been fixed. The WSAS 2.2 release will be > > > > available next week. You will be able to download it from > > > > https://wso2.org/projects/wsas/java > > > > . You could also check this out
[Axis2] Test failures in current trunk
Hi devs, There is an test failure in the latest trunk [INFO] Test Source directory: /home/sandakith/ProjectCheckouts/axis2/Axis2_m2_trunk/modules/jaxbri/target/schema/src added. [INFO] [compiler:testCompile] [INFO] Compiling 76 source files to /home/sandakith/ProjectCheckouts/axis2/Axis2_m2_trunk/modules/jaxbri/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /home/sandakith/ProjectCheckouts/axis2/Axis2_m2_trunk/modules/jaxbri/target/surefire-reports --- T E S T S --- Running org.temp.doclitbare.DocLitBareWSDLTest Error in WSDL : DocLitBareService.wsdl Exception: java.lang.NullPointerException java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at org.apache.ws.commons.schema.XmlSchemaSerializer.setupNamespaces( XmlSchemaSerializer.java:291) at org.apache.ws.commons.schema.XmlSchemaSerializer.serializeSchemaElement( XmlSchemaSerializer.java:102) at org.apache.ws.commons.schema.XmlSchemaSerializer.serializeSchema( XmlSchemaSerializer.java:83) at org.apache.ws.commons.schema.XmlSchema.serialize_internal( XmlSchema.java:418) at org.apache.ws.commons.schema.XmlSchema.write(XmlSchema.java:391) at org.apache.axis2.description.AxisService2WSDL11.generateOM( AxisService2WSDL11.java:204) at org.apache.ws.java2wsdl.Java2WSDLBuilder.generateWSDL( Java2WSDLBuilder.java:255) at org.temp.doclitbare.DocLitBareWSDLTest.testVersion( DocLitBareWSDLTest.java:43) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run( OldTestClassRunner.java:76) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute( JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet( AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute( AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess( SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main( SurefireBooter.java:879) Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.118 sec <<< FAILURE! Results : Failed tests: testVersion(org.temp.doclitbare.DocLitBareWSDLTest) Thoughts ? -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Resolved: (AXIS2-3325) No logging in POJODeployer at all
[ https://issues.apache.org/jira/browse/AXIS2-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3325. - Resolution: Fixed Assignee: Lahiru Sandakith (was: Deepal Jayasinghe) added logging for the pojo deployer Fixed in Committed revision 613119. > No logging in POJODeployer at all > - > > Key: AXIS2-3325 > URL: https://issues.apache.org/jira/browse/AXIS2-3325 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Paul Fremantle >Assignee: Lahiru Sandakith > > I tried to find out what was happening with the JAXWS POJODeployer, but as > there is no logging I couldn't. -- 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: WSAS-603 - I am getting the same stack exception
Hi Vergil, The issue was fixed in the svn trunk and can you please verify with the axis2 nightly build, and get back to us. Also this will be available in the next Axis2 and therefore WSAS also. Thanks Lahiru Sandakith. On Jan 17, 2008 2:30 PM, Afkham Azeez <[EMAIL PROTECTED]> wrote: > It should be the same issue since it is the same Axis2 that is used by > WSAS. Please try out the Axis2 nightly build at > http://people.apache.org/dist/axis2/nightly/ > > Thanks > Azeez > > > On Jan 17, 2008 1:49 PM, Trasca Virgil <[EMAIL PROTECTED]> wrote: > > > Hi Azeez, > > > >Sorry for insisting so much. I am not using WSAS 2.1 only > > axis2.war 1.3. Because of that I want you to confirm me that what I > > found is the same issue (as I am using Axis1.3 and you are saying about > > wsas). Also if it is the same issue I am intersted when it will be fixed in > > Axis2.war as I am using this one and not WSAS. I assume it will be fixed > > in Axis2 1.4. > > > > When will 1.4 be released? Till then is it possible that you will send > > me an updated jar file that will contain the fix so I can test it? > > > > Thank you, > > Virgil > > > > - Original Message > > From: Afkham Azeez <[EMAIL PROTECTED]> > > To: axis-dev@ws.apache.org > > Sent: Thursday, January 17, 2008 8:29:38 AM > > Subject: Re: WSAS-603 - I am getting the same stack exception > > > > Hi Virgil, > > WSAS is an enterprise ready Web services engine powered by Apache Axis2. > > You could deploy Axis2 Web services on WSAS and also there are many more > > value additions. The JIRA you cited is related to this product. In fact, the > > WSAS 2.1 release was based on Axis2 1.3, and the next 2.2 release > > contains many bug fixes to Axis2 including the issue you cited. > > > > For further information see: > > > > 1. http://wso2.com/products/wsas/ > > 2. https://wso2.org/projects/wsas/java > > 3. http://wso2.org/library/821 > > > > Thanks > > Azeez > > > > On Jan 17, 2008 11:44 AM, Trasca Virgil <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > What is WSAS? I am using Axis2 1.3 & ADB and I get this > > > exception stack. Can you confirm me that the issue I found is the same > > > like > > > http://wso2.org/jira/browse/WSAS-603? > > > > > > Thank you, > > > Virgil > > > > > > > > > - Original Message > > > From: Afkham Azeez <[EMAIL PROTECTED]> > > > To: axis-dev@ws.apache.org > > > Sent: Thursday, January 17, 2008 7:29:15 AM > > > Subject: Re: WSAS-603 - I am getting the same stack exception > > > > > > FYI, issue WSAS-603 has been fixed. The WSAS 2.2 release will be > > > available next week. You will be able to download it from > > > https://wso2.org/projects/wsas/java. You could also check this out in > > > the nightly build. > > > > > > Thanks > > > Azeez > > > > > > On Jan 17, 2008 12:00 AM, Trasca Virgil <[EMAIL PROTECTED]> > > > wrote: > > > > > > > Hi all, > > > > > > > > I found this issue > > > > > > > > http://wso2.org/jira/browse/WSAS-603 > > > > > > > > While calling a deployed (jetty) web service I am getting a very > > > > similar stack > > > > > > > > [java] java.lang.NullPointerException > > > > [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr( > > > > BaseNsStreamWriter.java:468) > > > > [java] at com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute( > > > > BaseNsStreamWriter.java:230) > > > > [java] at org.apache.axiom.om > > > > .impl.MTOMXMLStreamWriter.writeAttribute(MTOMXMLStreamWriter.java > > > > :137) > > > > [java] at > > > > org.apache.axiom.om<http://org.apache.axiom.om.impl.util.omserializerutil.se/> > > > > .impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java > > > > :420) > > > > [java] at > > > > org.apache.axiom.om<http://org.apache.axiom.om.impl.util.omserializerutil.se/> > > > > .impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java > > > > :172) > > > > [java] at > > > > org.apache.axiom.om<http://org.apache.axiom.om.impl.llom.omelementimpl.int/> > > > > .impl.llom.OMElementImpl.internalSeri
[jira] Updated: (AXIS2-3429) JAXWS classloading issues with annotated class with aar based deployment
[
https://issues.apache.org/jira/browse/AXIS2-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith updated AXIS2-3429:
Attachment: jaxws_mr_classloading_issue_fix.txt
attaching the fix
> JAXWS classloading issues with annotated class with aar based deployment
>
>
> Key: AXIS2-3429
> URL: https://issues.apache.org/jira/browse/AXIS2-3429
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Lahiru Sandakith
> Attachments: calculator-jaxws-sample.aar,
> jaxws_mr_classloading_issue_fix.txt
>
>
> When we create a annotated class and create and service archive with the
> services.xml
>
>
> true
>
> http://www.w3.org/2004/08/wsdl/in-out";
>
> class="org.apache.axis2.jaxws.server.JAXWSMessageReceiver"/>
>
> name="ServiceClass">calculator.service.JAXWSCalculatorService
> http://www.w3.org/2004/08/wsdl/in-out";>
>
>
>
>
> deployed the aar and invoked the client
> public class Client {
> public static void main(String[] args) throws Exception{
> CalculatorServiceStub stub = new CalculatorServiceStub();
> CalculatorServiceStub.Add add = new CalculatorServiceStub.Add();
> add.setValue1(10);
> add.setValue2(20);
> try {
> stub.add(add);
> } catch (RemoteException e) {
> e.printStackTrace();
> }
> }
> }
> JAXWS MR could not load the other dependent classes
--
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-3429) JAXWS classloading issues with annotated class with aar based deployment
[
https://issues.apache.org/jira/browse/AXIS2-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith updated AXIS2-3429:
Attachment: calculator-jaxws-sample.aar
attaching the aar
> JAXWS classloading issues with annotated class with aar based deployment
>
>
> Key: AXIS2-3429
> URL: https://issues.apache.org/jira/browse/AXIS2-3429
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Lahiru Sandakith
> Attachments: calculator-jaxws-sample.aar,
> jaxws_mr_classloading_issue_fix.txt
>
>
> When we create a annotated class and create and service archive with the
> services.xml
>
>
> true
>
> http://www.w3.org/2004/08/wsdl/in-out";
>
> class="org.apache.axis2.jaxws.server.JAXWSMessageReceiver"/>
>
> name="ServiceClass">calculator.service.JAXWSCalculatorService
> http://www.w3.org/2004/08/wsdl/in-out";>
>
>
>
>
> deployed the aar and invoked the client
> public class Client {
> public static void main(String[] args) throws Exception{
> CalculatorServiceStub stub = new CalculatorServiceStub();
> CalculatorServiceStub.Add add = new CalculatorServiceStub.Add();
> add.setValue1(10);
> add.setValue2(20);
> try {
> stub.add(add);
> } catch (RemoteException e) {
> e.printStackTrace();
> }
> }
> }
> JAXWS MR could not load the other dependent classes
--
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-3429) JAXWS classloading issues with annotated class with aar based deployment
JAXWS classloading issues with annotated class with aar based deployment
Key: AXIS2-3429
URL: https://issues.apache.org/jira/browse/AXIS2-3429
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Lahiru Sandakith
When we create a annotated class and create and service archive with the
services.xml
true
http://www.w3.org/2004/08/wsdl/in-out";
class="org.apache.axis2.jaxws.server.JAXWSMessageReceiver"/>
calculator.service.JAXWSCalculatorService
http://www.w3.org/2004/08/wsdl/in-out";>
deployed the aar and invoked the client
public class Client {
public static void main(String[] args) throws Exception{
CalculatorServiceStub stub = new CalculatorServiceStub();
CalculatorServiceStub.Add add = new CalculatorServiceStub.Add();
add.setValue1(10);
add.setValue2(20);
try {
stub.add(add);
} catch (RemoteException e) {
e.printStackTrace();
}
}
}
JAXWS MR could not load the other dependent classes
--
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: svn commit: r601617 - in /webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server: EndpointController.java JAXWSMessageReceiver.java
Hi Nick,
I with my svn commit: r608797 I revert the code change done to the JAXWS
Class Loader, Since the svn commit: r604813 done to the Axis2 trunk resolve
the issue and it existed with the same time that I was doing the fix. So its
OK.
One other thing that I would like to get your feeedback is on
modules/jaxws/src/org/apache/axis2/jaxws/message/impl/XMLPartBase.java
of this part of the code at the rest invocation and on JAXWS side of the XML
part creation.
} else if (protocol == Protocol.rest) {
this.protocol = Protocol.rest;
// Axis2 stores XML/HTTP messages inside a soap11 envelope. We
will mimic this behavior
if (qName.getNamespaceURI().equals(
SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI)) {
// Okay
} else
if (qName.getNamespaceURI().equals(
SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI)) {
** throw ExceptionFactory.
**makeWebServiceException(Messages.getMessage
("restWithSOAPErr"));
} else {
content = _createSpine(Protocol.rest, Style.DOCUMENT, 0,
root);
contentType = SPINE;
}
If you remember the scenatio that I asked about getting a POJO deployed with
the basic annotations and with the current JAXWSMessageReceiver the rest
works if we do not have the SOAP12 restriction above. I have tested this. Is
there a particular reason that JAXWS that is do this SOAP version
restriction. Please give your feedback on this.
Thanks
Lahiru Sandakith
On Dec 12, 2007 2:01 PM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote:
> Hi Nick ,
>
> This is really strange, when I get an update now and run all the build
> with test cases that include my fix, all the test passes and when it was
> removed these two tests fails,
>
> Failed tests:
> testLoadWSDLImpl(
> org.apache.axis2.jaxws.description.AnnotationServiceImplWithDBCTests)
> testLoadWSDLSEI(
> org.apache.axis2.jaxws.description.AnnotationServiceImplWithDBCTests)
>
> I am bit confused now, will look at the latest changes to find out what
> was the reason to happen this.
>
> Thanks
>
> Sandakith
>
>
>
> On Dec 12, 2007 12:06 PM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote:
>
> > Hi Nick,
> >
> > Thanks for the reply.
> >
> > On Dec 11, 2007 8:08 PM, Nicholas L Gallardo <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Hi Sandakith,
> > >
> > > A few more comments based on your responses...
> > >
> > > Actually when I debug the code for this scenario I found
> > > that Actually there is no need for this binding type missmatch check,
> > > since
> > > it was reached correctly upto that point and when this line executes the
> > > mismath check, as I saw it it's creating the same version mismatch faults
> > > as
> > > the existing JAX-WS.
> > >
> > > Can you point me to where in the Axis2 code the mismatch fault is
> > > being generated? This code was added to the JAX-WS impl as a requirement
> > > of
> > > the CTS test suite. Without something concrete that shows a similar
> > > behavioral semantic, we need to revert the change and include this code.
> > > Leaving this as is would most likely break our JAX-WS compliance within
> > > Geronimo, which is a very bad thing as it then puts in jeopardy the
> > > JavaEE 5
> > > certification.
> > >
> > Ok, now got the requirement, I came to conclusion by inspecting the eic
> > and service description. And also found it in the SOAP 1.2 specification
> > under Appendix 'A'. I will fix this.
> >
> > >
> > >
> > > Is the basic problem that this code was blowing up when an HTTP GET
> > > was sent?
> > >
> > Yes it was,
> >
> > > If so, then there's probably a way to fix the code so that it
> > > provides the existing functionality while enabling the HTTP GET.
> > >
> >
> > Before that I attach the fix to this JIRA
> > https://issues.apache.org/jira/browse/AXIS2-3382 to review, I check in
> > the code with full build with tests. Sad that this gone pass those. Anyway
> > I will look more into way that it will handle the scenario inside the Utils
> > where is checks for the missmath. Please send your suggestions on this. Also
> > now we have the confirmation from the users that the sample also works
> > recently,
> > http://www.nabble.com/Re%3A--Axis2--Problem-Axis2-sample---jaxws-calculator-p14211643.html
> >
> > >
> > >
> > >
> > >
> > > Beyond that, it has been our opinion that the JAX-WS POJO
Re: [Axis2] Release plan and road map for Axis2 1.4 release
Hi Nick, On Jan 4, 2008 9:47 PM, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote: > Thanks Deepal for narrowing the list down here. I just wanted to add a > few things. > > In response to Amila's comment: > > > Do we have to run any standard test suite to claim the compliance? I > mean for JAXWS we have to pass the SUNs' TCK. > > Yes, someone with access to the Apache CTS buckets will need to run the > JAXWS TCK. I'm not familiar with what the access restrictions are on this > though. Is anyone aware of how this process works within Apache? > Regardless, I believe the suite must be run by someone not working on the > code. > I did some background search on this and there are some information found in this page. http://www.apache.org/jcp/ . According to that Apache have the JSR 2224 : JAXWS TCK version 2.0 since from the 10th May 2006. .But seems there is a version 2.1 in the Suns web. For the start Nick, lets narrow down infomation on this perticularly about the version of the TCK and basic infomation about the environment of Axis2 that we point against the TCK. But my view is having basic knowledge of the code will be a massive help for the person who will be getting the suit run against the axis2 runtime. +1 for including this in the next release. > > > On Dec 19, 2007 12:02 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> > wrote: > > > Hi Devs and Users, > > > > > > I saw a number of users asking about the next release of Axis2 , so I >... > > > doing a release on end of February ? > > > > > > So in the release I would like to see following list of items > > > - Support for RPC-Encoded > > > - Full support for JAX-WS > > > - Enhance NIO transport support > > > - Discuss and implement dynamic phase rule support > > > - Fix the issues we found at MS PlugFest > > > - Anything else . ?? > > > > > I want to clarify the second item here, Full support for JAX-WS. Beyond > getting the TCK running and complete, what is your expectation for this > work? I would anticipate this to include a better integration of JAX-WS > into the Axis2 deployment model. A preliminary description of this is > included AXIS2-3223. There's work that could be done to further simplify > things after this is complete, but what's described in that JIRA is the > first step. > +1 , I guess for the having a bettter doployment model will help the TCK stuff done easily. So this proposal is about the full AAR based deployment and I saw some code by Deepal which was about POJO based deployment ? > > > Also, I'd like to add Java 6 tolerance (at least for JAX-WS) to the list. > As of today, there are compile errors when running with a Java 6 JDK. I > think we can include Java 6 support first for JAX-WS Apps and can consider > extending that to the other programming models if others feel an immediate > need. I've opened JIRA AXIS2-3425 ( > https://issues.apache.org/jira/browse/AXIS2-3425) with more information. > +1 Thanks Lahiru Sandkith > > > > Thanks, > > -Nick > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: java2wsdl maven2 plugin is broken
]>> > >> > >> > > 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] > > - > 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] > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: svn commit: r601617 - in /webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server: EndpointController.java JAXWSMessageReceiver.java
Hi Nick , This is really strange, when I get an update now and run all the build with test cases that include my fix, all the test passes and when it was removed these two tests fails, Failed tests: testLoadWSDLImpl( org.apache.axis2.jaxws.description.AnnotationServiceImplWithDBCTests) testLoadWSDLSEI( org.apache.axis2.jaxws.description.AnnotationServiceImplWithDBCTests) I am bit confused now, will look at the latest changes to find out what was the reason to happen this. Thanks Sandakith On Dec 12, 2007 12:06 PM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote: > Hi Nick, > > Thanks for the reply. > > On Dec 11, 2007 8:08 PM, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote: > > > Hi Sandakith, > > > > A few more comments based on your responses... > > > > Actually when I debug the code for this scenario I found that > > Actually there is no need for this binding type missmatch check, since it > > was reached correctly upto that point and when this line executes the > > mismath check, as I saw it it's creating the same version mismatch faults as > > the existing JAX-WS. > > > > Can you point me to where in the Axis2 code the mismatch fault is being > > generated? This code was added to the JAX-WS impl as a requirement of the > > CTS test suite. Without something concrete that shows a similar behavioral > > semantic, we need to revert the change and include this code. Leaving this > > as is would most likely break our JAX-WS compliance within Geronimo, which > > is a very bad thing as it then puts in jeopardy the JavaEE 5 certification. > > > Ok, now got the requirement, I came to conclusion by inspecting the eic > and service description. And also found it in the SOAP 1.2 specification > under Appendix 'A'. I will fix this. > > > > > > > Is the basic problem that this code was blowing up when an HTTP GET was > > sent? > > > Yes it was, > > > If so, then there's probably a way to fix the code so that it provides > > the existing functionality while enabling the HTTP GET. > > > > Before that I attach the fix to this JIRA > https://issues.apache.org/jira/browse/AXIS2-3382 to review, I check in > the code with full build with tests. Sad that this gone pass those. Anyway > I will look more into way that it will handle the scenario inside the Utils > where is checks for the missmath. Please send your suggestions on this. Also > now we have the confirmation from the users that the sample also works > recently, > http://www.nabble.com/Re%3A--Axis2--Problem-Axis2-sample---jaxws-calculator-p14211643.html > > > > > > > > > > > Beyond that, it has been our opinion that the JAX-WS POJO style > > endpoints will not support an HTTP get, given the parameter restriction that > > I mentioned below. There are two different styles of endpoints in JAX-WS, > > the POJO style one that you're working with here, and also a Provider style > > endpoint ( javax.xml.ws.Provider) which is a more generic messaging > > endpoint. If JAX-WS is going to support an HTTP GET, I believe it should > > only be for the Provider style endpoint. > > > Please explain a bit more, I am thinking on this as any service that is > exposed is governed by basic service rules no matter how it was deployed > etc. > > > > > > > Given that, these changes are made trying to support a scenario that's > > not intended for JAX-WS. I do understand that this is supported for the base > > Axis2 POJO endpoints, but that is completely different programming model. > > > Ok, but I was in the context that all the services that were deployed in > any kind of deployment will rule with generic rules. > > > > > > > > > > > If you agree with my comments above, my recommendation is that we revert > > the version mismatch changes. I need to look at the TCCL option that you > > mention a little more and see if we need to make other changes in the > > JAXWSMessageReceiver. > > > Yeah, I think my other change was the same thing as setting this param on > Axis2.xml, which fixed the issues on JIRA. Please have a look. > > Thanks > Sandakith > > > > > > > Regards, > > > > -Nick > > > > [image: Inactive hide details for "Lahiru Sandakith" > > <[EMAIL PROTECTED]>]"Lahiru Sandakith" < [EMAIL PROTECTED]> > > > > > > > > *"Lahiru Sandakith" <[EMAIL PROTECTED]>* > > > > 12/11/2007 07:34 AM > > Please respond to > > axis-dev@ws.apache.org > >
Re: svn commit: r601617 - in /webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server: EndpointController.java JAXWSMessageReceiver.java
Hi Nick, Thanks for the reply. On Dec 11, 2007 8:08 PM, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote: > Hi Sandakith, > > A few more comments based on your responses... > > Actually when I debug the code for this scenario I found that > Actually there is no need for this binding type missmatch check, since it > was reached correctly upto that point and when this line executes the > mismath check, as I saw it it's creating the same version mismatch faults as > the existing JAX-WS. > > Can you point me to where in the Axis2 code the mismatch fault is being > generated? This code was added to the JAX-WS impl as a requirement of the > CTS test suite. Without something concrete that shows a similar behavioral > semantic, we need to revert the change and include this code. Leaving this > as is would most likely break our JAX-WS compliance within Geronimo, which > is a very bad thing as it then puts in jeopardy the JavaEE 5 certification. > Ok, now got the requirement, I came to conclusion by inspecting the eic and service description. And also found it in the SOAP 1.2 specification under Appendix 'A'. I will fix this. > > > Is the basic problem that this code was blowing up when an HTTP GET was > sent? > Yes it was, > If so, then there's probably a way to fix the code so that it provides the > existing functionality while enabling the HTTP GET. > Before that I attach the fix to this JIRA https://issues.apache.org/jira/browse/AXIS2-3382 to review, I check in the code with full build with tests. Sad that this gone pass those. Anyway I will look more into way that it will handle the scenario inside the Utils where is checks for the missmath. Please send your suggestions on this. Also now we have the confirmation from the users that the sample also works recently, http://www.nabble.com/Re%3A--Axis2--Problem-Axis2-sample---jaxws-calculator-p14211643.html > > > > > Beyond that, it has been our opinion that the JAX-WS POJO style endpoints > will not support an HTTP get, given the parameter restriction that I > mentioned below. There are two different styles of endpoints in JAX-WS, the > POJO style one that you're working with here, and also a Provider style > endpoint (javax.xml.ws.Provider) which is a more generic messaging > endpoint. If JAX-WS is going to support an HTTP GET, I believe it should > only be for the Provider style endpoint. > Please explain a bit more, I am thinking on this as any service that is exposed is governed by basic service rules no matter how it was deployed etc. > > > Given that, these changes are made trying to support a scenario that's not > intended for JAX-WS. I do understand that this is supported for the base > Axis2 POJO endpoints, but that is completely different programming model. > Ok, but I was in the context that all the services that were deployed in any kind of deployment will rule with generic rules. > > > > > If you agree with my comments above, my recommendation is that we revert > the version mismatch changes. I need to look at the TCCL option that you > mention a little more and see if we need to make other changes in the > JAXWSMessageReceiver. > Yeah, I think my other change was the same thing as setting this param on Axis2.xml, which fixed the issues on JIRA. Please have a look. Thanks Sandakith > > > Regards, > > -Nick > > [image: Inactive hide details for "Lahiru Sandakith" > <[EMAIL PROTECTED]>]"Lahiru Sandakith" <[EMAIL PROTECTED]> > > > > *"Lahiru Sandakith" <[EMAIL PROTECTED]>* > > 12/11/2007 07:34 AM > Please respond to > axis-dev@ws.apache.org > > > To > > axis-dev@ws.apache.org > cc > > [EMAIL PROTECTED] > Subject > > Re: svn commit: r601617 - in > /webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server: > EndpointController.java JAXWSMessageReceiver.java > > Hi Nick, > > I missed the mail also, in my commit mails, so sorry for the late reply > too. > > On Dec 6, 2007 8:45 PM, Nicholas L Gallardo <[EMAIL PROTECTED] *<[EMAIL > PROTECTED]>> > wrote: > >Hi Sandakith, > >Sorry I'm commenting on this a little late. A couple of >points/questions. I'm wondering if what's going on here is still a mix of >the JAX-WS and Axis2/181 POJO support. I know I still owe you my thoughts > on >how to resolve some of that. I'll try to get that out as soon as I can. > > > Ok, Cool Nick, Please forward them to me, > > > >1) You mention in commenting out the code in the EndpointController >that the check for a version mismatch is already happening
Re: svn commit: r601617 - in /webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server: EndpointController.java JAXWSMessageReceiver.java
l)
> +++
> webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server/EndpointController.java
> Wed Dec 5 21:15:52 2007
> @@ -196,12 +196,13 @@
> eic.setHandlers(new HandlerResolverImpl(
> endpointDesc.getServiceDescription()).getHandlerChain(
> endpointDesc.getPortInfo()));
> }
>
> -if (!Utils.bindingTypesMatch(request,
> endpointDesc.getServiceDescription())) {
> -Protocol protocol = request.getMessage().getProtocol();
> -MessageContext faultContext =
> Utils.createVersionMismatchMessage(request, protocol);
> -eic.setResponseMessageContext(faultContext);
> -return false;
> -}
> +//Not needed since this is already handled when eic reaches this
> level
> +//if (!Utils.bindingTypesMatch(request,
> endpointDesc.getServiceDescription())) {
> +//Protocol protocol = request.getMessage().getProtocol();
> +//MessageContext faultContext =
> Utils.createVersionMismatchMessage(request, protocol);
> +//eic.setResponseMessageContext(faultContext);
> +//return false;
> +//}
>
> MessageContext responseMsgContext = null;
>
>
> Modified:
> webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server/JAXWSMessageReceiver.java
> URL:
> http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server/JAXWSMessageReceiver.java?rev=601617&r1=601616&r2=601617&view=diff
>
> ==
> ---
> webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server/JAXWSMessageReceiver.java
> (original)
> +++
> webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server/JAXWSMessageReceiver.java
> Wed Dec 5 21:15:52 2007
> @@ -19,6 +19,9 @@
>
> package org.apache.axis2.jaxws.server;
>
> +import javax.xml.ws.Binding;
> +import javax.xml.ws.WebServiceException;
> +
> import org.apache.axis2.AxisFault;
> import org.apache.axis2.addressing.AddressingConstants;
> import org.apache.axis2.context.OperationContext;
> @@ -43,9 +46,6 @@
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
>
> -import javax.xml.ws.Binding;
> -import javax.xml.ws.WebServiceException;
> -
> /**
> * The JAXWSMessageReceiver is the entry point, from the server's
> perspective, to the JAX-WS code.
> * This will be called by the Axis Engine and is the end of the chain from
> an Axis2 perspective.
> @@ -80,8 +80,12 @@
>
> org.apache.axis2.description.Parameter svcClassParam =
> service.getParameter(PARAM_SERVICE_CLASS);
> -
> + ClassLoader prevCl = Thread.currentThread().getContextClassLoader();
>
> try {
> + //Set the service class loader
> +ClassLoader newCl = service.getClassLoader();
> + Thread.currentThread().setContextClassLoader(newCl);
> +
> if (svcClassParam == null) {
> throw new RuntimeException(
> Messages.getMessage
> ("JAXWSMessageReceiverNoServiceClass"));
> @@ -176,6 +180,8 @@
> ThreadContextMigratorUtil.performContextCleanup(
> Constants.THREAD_CONTEXT_MIGRATOR_LIST_ID,
> axisResponseMsgCtx);
> }
> +//Revert back from service class loader to the previous
> class loader
> + Thread.currentThread().setContextClassLoader(prevCl);
> }
>
> } catch (Exception e) {
> @@ -193,6 +199,9 @@
> // The AxisEngine expects an AxisFault
> throw AxisFault.makeFault(wse);
>
> +} finally {
> + // In a case of exception also swith from service cl to previous
> cl
> + Thread.currentThread().setContextClassLoader(prevCl);
> }
>
> //This assumes that we are on the ultimate execution thread
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
Thanks
Lahiru Sandakith
http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
<><>
[jira] Commented: (AXIS2-3324) Document JSR181 support
[ https://issues.apache.org/jira/browse/AXIS2-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549040 ] Lahiru Sandakith commented on AXIS2-3324: - I have added a README to the jaxws-calculator sample, will add a document on how the JSR-181 support done with pojo deployer. > Document JSR181 support > --- > > Key: AXIS2-3324 > URL: https://issues.apache.org/jira/browse/AXIS2-3324 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Paul Fremantle > Assignee: Lahiru Sandakith > > Although there is JSR181 annotation support there is no documentation. Even > the sample doesn't even have a README! -- 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-3324) Document JSR181 support
[ https://issues.apache.org/jira/browse/AXIS2-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3324: --- Assignee: Lahiru Sandakith (was: Deepal Jayasinghe) > Document JSR181 support > --- > > Key: AXIS2-3324 > URL: https://issues.apache.org/jira/browse/AXIS2-3324 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Paul Fremantle > Assignee: Lahiru Sandakith > > Although there is JSR181 annotation support there is no documentation. Even > the sample doesn't even have a README! -- 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] Problem Axis2 sample - jaxws-calculator
This fix is now committed to the trunk with the latest revision. Thanks Sandakith. On Dec 3, 2007 9:10 PM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote: > Hi , > we found that this was an issue with JAXWS MR could not found the service > impl class, > I have attached a patch to the > https://issues.apache.org/jira/browse/AXIS2-3382 > > And it addresses the class loading issue and now, > With the patch if we build axis2 jaxws-calculator and deploy it in axis2 > > Both code generate stubs with client invocation and rest like invocation > works for me. > Could not commit since there are some test failures in the kernel module > currently in the trunk. > Can someone who is more familiar with JAXWS look more at the issue and the > patch. > The patch address a class loader switch from service to current and vise > versa at the time needed to load the impl service class. > > > Thanks > Sandakith. > > > On Dec 3, 2007 8:42 AM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote: > > > Hi Rick, > > > > On Dec 2, 2007 11:17 PM, Rick Isaacs <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi Charitha, > > > > > > Thank you for your email and that you have reported this problem. > > > > > > I am not familiar with the Axis2 snapshot releases. > > > > > > Where can I find out more about snapshots? > > > > > > If you need the latest snapshot build its available here, > > http://people.apache.org/dist/axis2/nightly/ > > One more thing, if you are building axis2 from the source, it is > > recommended to use latest maven version (I have 2.0.7) > > > > I tried to look at the issue that you have reported against the > > jaxws-calcualter service archive with the axis2 with the latest snapshot > > build. I noticed that the service getting deployed with correct operations, > > and its seems to be an issue with the rest like way of invoking the service. > > Will update you more on this as soon as I have more info. > > Thanks > > Sandakith. > > > > > > > > > > > I noticed that the maven project was using a 1.3-snapshot. > > > > > > Thanks, > > > Rick > > > > > > > > > > > > On Dec 2, 2007 2:37 AM, Charitha Kankanamge < [EMAIL PROTECTED]> > > > wrote: > > > > > > > Rick, > > > > I also experienced some issues with jax-ws sample. That sample did > > > > not > > > > have any document and I had reported a jira sometime back > > > > ( https://issues.apache.org/jira/browse/AXIS2-3091 ). > > > > A seperate jira was reported for the nullpointer exception. > > > > (https://issues.apache.org/jira/browse/AXIS2-3382) > > > > > > > > Hope these issues will be resolved in the snapshot builds ASAP. > > > > > > > > regards > > > > Charitha > > > > > > > > Rick Isaacs wrote: > > > > > > > > > > > > > > Hi, > > > > > > > > > > I am trying to get the axis2-1.3\samples\jaxws-calculator sample > > > > to > > > > > work, but I get > > > > > the error in Tomcat > > > > > > > > > > java.lang.ClassNotFoundException: > > > > > org.apache.axis2.jaxws.calculator.Calculator > > > > > > > > > > > > > > > - downloaded and installed maven > > > > > > > > > > - called maven package for the the sample, but maven could not > > > > > download the necessary files > > > > > > > > > > - changed the pom.xml > > > > > > > > > > axis2-aar-maven-plugin > > > > > 1.3-SNAPSHOT > > > > > > > > > > axis2-jaxws > > > > > 1.3-SNAPSHOT > > > > > > > > > > to > > > > > > > > > > 1.3 > > > > > > > > > > - maven package downloaded many files and built > > > > > samples\jaxws-calculator\target\jaxws-calculator-1.3.aar > > > > > > > > > > - copied aar file to /services to deploy > > > > > > > > > > - service is found by the Axis2 Service servlet along with wsdl > > > > > > > > > > - > > > > > > > > > http://127.0.0.1:8080/axis2/services/CalculatorService/add?value1=1&value2=3 > > > > > <http://127.0.0.1:8080/axis2/service
[jira] Resolved: (AXIS2-3091) No readme for jaxws-calculator sample
[ https://issues.apache.org/jira/browse/AXIS2-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3091. - Resolution: Fixed Resolved the issue with Committed revision 600579. > 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: Lahiru Sandakith > > 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] Assigned: (AXIS2-3091) No readme for jaxws-calculator sample
[ https://issues.apache.org/jira/browse/AXIS2-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3091: --- Assignee: Lahiru Sandakith > 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: Lahiru Sandakith > > 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]
Re: [Axis2] Problem Axis2 sample - jaxws-calculator
Hi , we found that this was an issue with JAXWS MR could not found the service impl class, I have attached a patch to the https://issues.apache.org/jira/browse/AXIS2-3382 And it addresses the class loading issue and now, With the patch if we build axis2 jaxws-calculator and deploy it in axis2 Both code generate stubs with client invocation and rest like invocation works for me. Could not commit since there are some test failures in the kernel module currently in the trunk. Can someone who is more familiar with JAXWS look more at the issue and the patch. The patch address a class loader switch from service to current and vise versa at the time needed to load the impl service class. Thanks Sandakith. On Dec 3, 2007 8:42 AM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote: > Hi Rick, > > On Dec 2, 2007 11:17 PM, Rick Isaacs <[EMAIL PROTECTED]> wrote: > > > > > Hi Charitha, > > > > Thank you for your email and that you have reported this problem. > > > > I am not familiar with the Axis2 snapshot releases. > > > > Where can I find out more about snapshots? > > > If you need the latest snapshot build its available here, > http://people.apache.org/dist/axis2/nightly/ > One more thing, if you are building axis2 from the source, it is > recommended to use latest maven version (I have 2.0.7) > > I tried to look at the issue that you have reported against the > jaxws-calcualter service archive with the axis2 with the latest snapshot > build. I noticed that the service getting deployed with correct operations, > and its seems to be an issue with the rest like way of invoking the service. > Will update you more on this as soon as I have more info. > Thanks > Sandakith. > > > > > > > I noticed that the maven project was using a 1.3-snapshot. > > > > Thanks, > > Rick > > > > > > > > On Dec 2, 2007 2:37 AM, Charitha Kankanamge < [EMAIL PROTECTED]> wrote: > > > > > Rick, > > > I also experienced some issues with jax-ws sample. That sample did not > > > have any document and I had reported a jira sometime back > > > ( https://issues.apache.org/jira/browse/AXIS2-3091 ). > > > A seperate jira was reported for the nullpointer exception. > > > (https://issues.apache.org/jira/browse/AXIS2-3382) > > > > > > Hope these issues will be resolved in the snapshot builds ASAP. > > > > > > regards > > > Charitha > > > > > > Rick Isaacs wrote: > > > > > > > > > > > Hi, > > > > > > > > I am trying to get the axis2-1.3\samples\jaxws-calculator sample to > > > > work, but I get > > > > the error in Tomcat > > > > > > > > java.lang.ClassNotFoundException: > > > > org.apache.axis2.jaxws.calculator.Calculator > > > > > > > > > > > > - downloaded and installed maven > > > > > > > > - called maven package for the the sample, but maven could not > > > > download the necessary files > > > > > > > > - changed the pom.xml > > > > > > > > axis2-aar-maven-plugin > > > > 1.3-SNAPSHOT > > > > > > > > axis2-jaxws > > > > 1.3-SNAPSHOT > > > > > > > > to > > > > > > > > 1.3 > > > > > > > > - maven package downloaded many files and built > > > > samples\jaxws-calculator\target\jaxws-calculator-1.3.aar > > > > > > > > - copied aar file to /services to deploy > > > > > > > > - service is found by the Axis2 Service servlet along with wsdl > > > > > > > > - > > > > > > > http://127.0.0.1:8080/axis2/services/CalculatorService/add?value1=1&value2=3 > > > > <http://127.0.0.1:8080/axis2/services/CalculatorService/add?value1=1&value2=3 > > > > > > > > > > > > response in browser > > > > > > > > java.lang.NullPointerException > > > > > > > > > > > > Tomcat shows > > > > java.lang.NullPointerException > > > > > > > > > > > > I could not find an documentation for this sample, so I am not sure, > > > > how to correctly install this sample. > > > > > > > > Maybe I am missing some jars. > > > > > > > > Thanks, > > > > Rick > > > > > > > > > > > > > -- > > > 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] > > > > > > > > > > > -- > Thanks > Lahiru Sandakith > > http://sandakith.wordpress.com/ > GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Commented: (AXIS2-3382) NPE throws when invoking jax-ws calculator sample service
[ https://issues.apache.org/jira/browse/AXIS2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547872 ] Lahiru Sandakith commented on AXIS2-3382: - Here is what I did Build the axis2 from source.. from trunk extracted the standalone build at module/distribution build the sample jaxws deployed it in axis2 and start the server. 1) invoked with rest like browser invocation as original issue reports -> not working 2) codegen the client stub from the wsdl , wrote client , invoke it - > issues apply the patch.. build again both 1) and 2) works Thanks Sandakith. > 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 > Attachments: Fix_for_Axis2_3382.txt > > > - 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-3382) NPE throws when invoking jax-ws calculator sample service
[ https://issues.apache.org/jira/browse/AXIS2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith updated AXIS2-3382: Attachment: Fix_for_Axis2_3382.txt Attaching the fix for the issue.. since there are some test failing at this time in the trunk. This issue is limited to jaxws module. can someone who more familiar with JAXWS review this one.. > 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 > Attachments: Fix_for_Axis2_3382.txt > > > - 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]
Re: [Axis2] Build break Again
Thanks Rich, full build is working now with the tests. Sandakith. On Dec 1, 2007 4:37 AM, R J Scheuerle Jr <[EMAIL PROTECTED] > wrote: > Rich Scheuerle > IBM Web Services > Apache Axis2 ([EMAIL PROTECTED]) > 512-838-5115 (IBM TL 678-5115) > > R J Scheuerle Jr/Austin/[EMAIL PROTECTED] wrote on 11/30/2007 02:39:42 PM: > > > I am seeing the same problems after updating today. > > > > Does anyone have any ideas yet ? > > > This particular test has an invalid service. The service has a > wsdlLocation but no wsdl. > I disabled the failing tests (67) and I will open a JIRA shortly to > correct the tests. > > > > > > > Rich Scheuerle > > IBM Web Services > > Apache Axis2 ([EMAIL PROTECTED]) > > 512-838-5115 (IBM TL 678-5115) > > > > "Lahiru Sandakith" <[EMAIL PROTECTED]> wrote on 11/30/2007 01:24:55 > AM: > > > > > Hi Devs, > > > With the latest updates that I have received, I am experiencing some > > > jaxws test failures, > > > > > > Tests in error: > > > testSendImageAttachmentAPI11(org.apache.axis2.jaxws.sample. > > MtomSampleTests) > > > testSendImageAttachmentProperty11( org.apache.axis2.jaxws.sample. > > > MtomSampleTests) > > > testSendImageAttachmentAPIProperty11(org.apache.axis2.jaxws. > > > sample.MtomSampleTests) > > > > > > Tests run: 365, Failures: 0, Errors: 3, Skipped: 0 > > > > > > I also try to see what was the cause and trying to figure out a > > fix for this. > > > > > > Thanks > > > Sandakith. > > > > > > > > On Nov 29, 2007 10:12 PM, keith chapman <[EMAIL PROTECTED]> > wrote: > > > Fixed. Yes it was due to a Woden API change. > > > > > > Thanks, > > > Keith. > > > > > > > > On Nov 29, 2007 6:17 PM, David Illsley < [EMAIL PROTECTED]> > wrote: > > > Hi all, > > > The Axis2 nightly build is failing [1], and it seems to be to do with > > > a woden api change. Could someone who know a bit about woden/wsdl2 > > > take a look? > > > Thanks, > > > David > > > > > > [1] http://ws.zones.apache.org: > > > 1/continuum/servlet/continuum/target/ProjectBuild.vm? > > > view=ProjectBuild&buildId=3375&id=131 > > > -- > > > David Illsley - IBM Web Services Development > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > -- > > > Keith Chapman > > > WSO2 Inc. > > > Oxygen for Web Services Developers. > > > http://wso2.org/ > > > > > > > > > > > > -- > > > Thanks > > > Lahiru Sandakith > > > > > > http://sandakith.wordpress.com/ > > > GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 > 9A0F > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] JAX-WS: problems with annotated methods
Hi Nick,
Thanks for the reply.
On Nov 30, 2007 8:31 PM, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote:
> Lahriu,
>
> Thanks for the insights. I agree that there's a gap that needs to be
> closed here. I'll write up the thoughts I've had for a little while on this
> and float them to the list.
>
great,
>
>
> I don't know if I'll have time to affect all of this, but I will at least
> try to lay it out and others can contribute if they'd like to pick pieces of
> it up.
>
sure, lets try to discuss and come up with a list that we all can fill,
Thanks
Sandakith.
>
>
> Thanks,
>
> -Nick
>
>
>
>
> [image: Inactive hide details for "Lahiru Sandakith"
> <[EMAIL PROTECTED]>]"Lahiru Sandakith" <[EMAIL PROTECTED]>
>
>
>
> *"Lahiru Sandakith" <[EMAIL PROTECTED]>*
>
> 11/28/2007 09:35 PM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
>
> axis-dev@ws.apache.org
> cc
>
>
> Subject
>
> Re: [Axis2] JAX-WS: problems with annotated methods
>
> Hi Nick,
>
> Forwarding this with Axis2 lable.
>
> Looking at the issue, we found that in the scenario that we talk about
> POJODeployer being able to deploy a JSR-181 annotated pojo through JAXWS in
> Axis2. I found some issues and with the help of Deepal we fixed them
> yesterday.
>
> 1) Service not exposing with the annotated name correctly , Fixed
> 2) Operation if not exposing with the annotated name correctly , Fixed
> 3) ?wsdl not reflet the service correctly , Fixed
>
> then we tried to invoke the service with a client and in rest way.
> But then we fond that the service that got deployed did not attached with
> the JAXWS Message Receiver and it being exposed with the default RPC Message
> Receiver, with some debuggig we found that in the DiscrptionFactory the
> axisService JAXWS module
>
> public static AxisService createAxisService(Class serviceImplClass) {
> ServiceDescription serviceDescription =
> createServiceDescription(serviceImplClass);
> EndpointDescription[] edArray = serviceDescription.getEndpointDescriptions();
> AxisService axisService = edArray[0].getAxisService();
> return axisService;
> }
>
> did not attached the correct MR to the axisService.
>
> I guess this is an issue, and would like to have your thoughts on this and
> about the overall deployment integration of JAXWS to Axis2 as mentioned in
> the earlier mail.
>
> Thanks
> Sandakith
>
>
>
>
> On Nov 28, 2007 8:16 AM, Lahiru Sandakith <[EMAIL PROTECTED]<[EMAIL
> PROTECTED]>>
> wrote:
>
>Hi Nick,
>
>I was also looking at the possibilities of JSR-181 annotated class
>exposing as a Axis2/JAXWS service.
>
>
>On Nov 28, 2007 2:39 AM, Nicholas L Gallardo < [EMAIL PROTECTED]<[EMAIL
> PROTECTED]>>
>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.
>
>This is about POJO Deployer, Simply we get this class
>
>package jaxws.example;
>
>import javax.jws.WebMethod;
>import javax.jws.WebService;
>
>
>@WebService(name= "WSASJAX_Service2", targetNamespace =
> "*http://www.webtest.org/jaxws
>* <http://www.webtest.org/jaxws>")
>public class JAXWSService1 {
>
>@WebMethod(operationName = "echoMethodString")
>
>public String echoMethod(String s){
>return s;
>}
>}
>
>* make it a jar
>* edit the axis2.xml entry specific on POJODeployer to pick up .jar
>files
>* put the jar into the repository/pojo directory
>* start axis2.
>
>When we do that we see the service with 2 methods echoMethodString
>and echoMethod. This is how to reproduce the issue.
>
>Also I saw that in the POJODeployer class code, If the JAXWS jars
>are present in the classpath then it will try to deploy it as a JAXWS
>endpoint, else it will deploy it as a Axis2 endpoint.*
>**
>
> https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/POJODeployer.java
>
> *<https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/POJODeployer.java>guess
> this maybe the cause to the problem.
>
>
>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.
>
>So actually
Re: [Axis2] Build break Again
Hi Devs, With the latest updates that I have received, I am experiencing some jaxws test failures, Tests in error: testSendImageAttachmentAPI11(org.apache.axis2.jaxws.sample.MtomSampleTests ) testSendImageAttachmentProperty11( org.apache.axis2.jaxws.sample.MtomSampleTests) testSendImageAttachmentAPIProperty11( org.apache.axis2.jaxws.sample.MtomSampleTests) Tests run: 365, Failures: 0, Errors: 3, Skipped: 0 I also try to see what was the cause and trying to figure out a fix for this. Thanks Sandakith. On Nov 29, 2007 10:12 PM, keith chapman <[EMAIL PROTECTED]> wrote: > Fixed. Yes it was due to a Woden API change. > > Thanks, > Keith. > > > On Nov 29, 2007 6:17 PM, David Illsley <[EMAIL PROTECTED]> wrote: > > > Hi all, > > The Axis2 nightly build is failing [1], and it seems to be to do with > > a woden api change. Could someone who know a bit about woden/wsdl2 > > take a look? > > Thanks, > > David > > > > [1] > > http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=3375&id=131 > > > > -- > > David Illsley - IBM Web Services Development > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Keith Chapman > WSO2 Inc. > Oxygen for Web Services Developers. > http://wso2.org/ -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Resolved: (AXIS2-3375) Axis2 webapp throws exception with missing class at startup
[ https://issues.apache.org/jira/browse/AXIS2-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3375. - Resolution: Fixed Fixed in Committed revision 599328. > Axis2 webapp throws exception with missing class at startup > --- > > Key: AXIS2-3375 > URL: https://issues.apache.org/jira/browse/AXIS2-3375 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Reporter: Lahiru Sandakith > > With the current axis2 trunk build webapp this is the stack trace, when we > start webapp inside the tomcat servlet container. > [ERROR] org.apache.axis2.rmi.deploy.RMIServiceDeployer > java.lang.ClassNotFoundException: > org.apache.axis2.rmi.deploy.RMIServiceDeployer > at > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1443) > at > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1289) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at java.lang.Class.forName0(Native Method) -- 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-3375) Axis2 webapp throws exception with missing class at startup
Axis2 webapp throws exception with missing class at startup --- Key: AXIS2-3375 URL: https://issues.apache.org/jira/browse/AXIS2-3375 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Lahiru Sandakith With the current axis2 trunk build webapp this is the stack trace, when we start webapp inside the tomcat servlet container. [ERROR] org.apache.axis2.rmi.deploy.RMIServiceDeployer java.lang.ClassNotFoundException: org.apache.axis2.rmi.deploy.RMIServiceDeployer at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1443) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1289) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) -- 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]: Using Axis2 with Tomcat v4.1.27
Hi, The axis2 webapp is http://java.sun.com/dtd/web-app_2_3.dtd";> I have deployed it recently with both Tomcat 4.1.x and 5.5.x and it working smoothly for me. Thanks Sandakith. On Nov 28, 2007 2:33 PM, Jan Fasula <[EMAIL PROTECTED]> wrote: > > Hi, > > we are going to use Axis2 v1.3 with a Tomcat server v4.1.27 as servlet > container. I was not able to find any detailled information if this version > will work?! So my question is, on which servlet API version is Axis2 > v1.3based? > > Thanks for your response, > Jan > > *Jan Fasula* > Consultant** > > Tel. (direkt) +49 531 23854 958 > *mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]> > > fme AG > Petzvalstraße 38 > 38104 Braunschweig > Germany > *http://www.fme.de* <http://www.fme.de/> > Tel. +49 531 23854 0 > Fax +49 531 23854 70 > > *...it's possible! > * > Vorstand > Dirk Bode (Vorsitzender) > Frank Mittelstaedt (Stellvertreter) > Dr. Ulrich Wiesner > > Aufsichtsrat > Ulrich Poerschke (Vorsitzender) > Frank Umlauf (Stellvertreter) > Stefan H. Tarach > > Handelsregister Braunschweig HRB: 5422 > Sitz der Gesellschaft: Braunschweig > > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Resolved: (AXIS2-3326) Make JAXWS POJODeployer behave the same as AAR files with respect to hot deploy and redeploy
[ https://issues.apache.org/jira/browse/AXIS2-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3326. - Resolution: Fixed with the latest fixes done to the axis2 trunk, this issue was resolved. > Make JAXWS POJODeployer behave the same as AAR files with respect to hot > deploy and redeploy > > > Key: AXIS2-3326 > URL: https://issues.apache.org/jira/browse/AXIS2-3326 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws >Reporter: Paul Fremantle > > If the axis2.xml says hotDeploy is enabled, or hot redeploy, then that should > also apply to JSR181 services loaded by the POJODeployer -- 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-3352) JAX-WS: wsdl11 generation fails if @WebMethod annotation is specified with member values
[
https://issues.apache.org/jira/browse/AXIS2-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith resolved AXIS2-3352.
-
Resolution: Fixed
Charitha,
Please check this with the current trunk, I tested and this is fixed now.
Thanks
Sandakith
> 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] Commented: (AXIS2-3326) Make JAXWS POJODeployer behave the same as AAR files with respect to hot deploy and redeploy
[ https://issues.apache.org/jira/browse/AXIS2-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546559 ] Lahiru Sandakith commented on AXIS2-3326: - as from the fixes that are done recently to the axis2 trunk, the POJODeployer was working accordingly, I have checked and verified this in the current trunk. But the feature is not fully functioning, because there is an issue with the JAXWS module where it does not set the Message Receiver correctly to the axisService comes out of JAXWS. Will look more on to this.. > Make JAXWS POJODeployer behave the same as AAR files with respect to hot > deploy and redeploy > > > Key: AXIS2-3326 > URL: https://issues.apache.org/jira/browse/AXIS2-3326 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws >Reporter: Paul Fremantle > > If the axis2.xml says hotDeploy is enabled, or hot redeploy, then that should > also apply to JSR181 services loaded by the POJODeployer -- 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-3327) When setting the operationName using JSR181 the service fails to show WSDL correctly
[
https://issues.apache.org/jira/browse/AXIS2-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith resolved AXIS2-3327.
-
Resolution: Fixed
This was fixed in current trunk.
> When setting the operationName using JSR181 the service fails to show WSDL
> correctly
>
>
> Key: AXIS2-3327
> URL: https://issues.apache.org/jira/browse/AXIS2-3327
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
>Reporter: Paul Fremantle
>Assignee: Deepal Jayasinghe
>
> If I set
> @WebMethod(operationName="doit")
> public String myMethod(..) {..}
> then try to view the resulting WSDL for the service, I get a SOAP fault:
>
> −
>
> http://www.w3.org/2005/08/addressing/soap/fault
>
> −
>
> −
>
>
> unknown
>
>
>
>
> If I view WSDL2 (?wsdl2) it works, but the resulting WSDL shows two
> operations for each method:
>
> −
>pattern="http://www.w3.org/ns/wsdl/in-out";>
> http://fremantle.org/doit"/>
> wsaw:Action="urn:myMethodResponse"/>
>
> −
> http://www.w3.org/ns/wsdl/in-out";>
> http://fremantle.org/doit"/>
> wsaw:Action="http://fremantle.org/ns/Hello/doitResponse"/>
>
>
--
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] JAX-WS: problems with annotated methods
Hi Nick,
Forwarding this with Axis2 lable.
Looking at the issue, we found that in the scenario that we talk about
POJODeployer being able to deploy a JSR-181 annotated pojo through JAXWS in
Axis2. I found some issues and with the help of Deepal we fixed them
yesterday.
1) Service not exposing with the annotated name correctly , Fixed
2) Operation if not exposing with the annotated name correctly , Fixed
3) ?wsdl not reflet the service correctly , Fixed
then we tried to invoke the service with a client and in rest way.
But then we fond that the service that got deployed did not attached with
the JAXWS Message Receiver and it being exposed with the default RPC Message
Receiver, with some debuggig we found that in the DiscrptionFactory the
axisService JAXWS module
public static AxisService createAxisService(Class serviceImplClass) {
ServiceDescription serviceDescription =
createServiceDescription(serviceImplClass);
EndpointDescription[] edArray =
serviceDescription.getEndpointDescriptions();
AxisService axisService = edArray[0].getAxisService();
return axisService;
}
did not attached the correct MR to the axisService.
I guess this is an issue, and would like to have your thoughts on this and
about the overall deployment integration of JAXWS to Axis2 as mentioned in
the earlier mail.
Thanks
Sandakith
On Nov 28, 2007 8:16 AM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote:
> Hi Nick,
>
> I was also looking at the possibilities of JSR-181 annotated class
> exposing as a Axis2/JAXWS service.
>
>
> On Nov 28, 2007 2:39 AM, Nicholas L Gallardo < [EMAIL PROTECTED]> 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.
> >
> This is about POJO Deployer, Simply we get this class
>
> package jaxws.example;
>
> import javax.jws.WebMethod;
> import javax.jws.WebService;
>
> @WebService(name= "WSASJAX_Service2", targetNamespace =
> "http://www.webtest.org/jaxws
> ")
> public class JAXWSService1 {
>
> @WebMethod(operationName = "echoMethodString")
> public String echoMethod(String s){
> return s;
> }
> }
>
> * make it a jar
> * edit the axis2.xml entry specific on POJODeployer to pick up .jar files
> * put the jar into the repository/pojo directory
> * start axis2.
>
> When we do that we see the service with 2 methods echoMethodString and
> echoMethod. This is how to reproduce the issue.
>
> Also I saw that in the POJODeployer class code, If the JAXWS jars are
> present in the classpath then it will try to deploy it as a JAXWS endpoint,
> else it will deploy it as a Axis2 endpoint.
>
> https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/POJODeployer.javaguess
> this maybe the cause to the problem.
>
> >
> >
> > 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.
> >
> So actually what will be the procedure in the JAXWS module that we have
> in the Axis2, to get a service in to the axis2 deployment? What will be the
> packaging, is it the same as the AAR model, and do we need the wsdl too.
>
> > You're bean is being picked up as a POJO and deployed as such which is
> > where the "echoMethod" entry is coming from.
> >
> True.
>
> >
> >
> > 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?
> >
> No actually the ?wsdl generation fails in this above described scenario.
>
> >
> >
> > 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.
> >
> Yes, Agreed these are issues in the POJODep
Re: JAX-WS: problems with annotated methods
vice jar.
>
>@WebService(name= "WSASJAX_Service2", targetNamespace =
>"*http://www.webtest.org/jaxws* <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*<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]<[EMAIL PROTECTED]>
>For additional commands, e-mail: [EMAIL PROTECTED] *<[EMAIL PROTECTED]>
>
>
>
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.*
> **http://wso2.org/* <http://wso2.org/>
>
--
Thanks
Lahiru Sandakith
http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] excludeOperations against the schema at modeule/kernel/resources/services.xsd
resolved the issue reported on Axis2-3330 in trunk with Committed revision 596524. Thanks On Nov 19, 2007 4:38 PM, Lahiru Sandakith <[EMAIL PROTECTED]> wrote: > Hi Devs, > > I was looking at the services.xsd at location modeule/kernel/resources, > and used this one for the validation of the services.xml files in IDE > Tools. > Seems there is a problem with the excludeOperations. > In the schema it refers to > > > > > > > > > in which the operations are the normal type that comes at the service > level, which does not seems to be complaint with the axis2, So I believe we > need to change it to the actual nature that fits the sequence of > > >getStrings2 >getStrings >. > > > for > > > > > > > > > > Is there are any other place that we use this schema for validation, If no > one against, I will go ahead and do the change. > -- > Thanks > Lahiru Sandakith > > http://sandakith.wordpress.com/ > GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Resolved: (AXIS2-3330) The generated services.xml file is not validate
[ https://issues.apache.org/jira/browse/AXIS2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3330. - Resolution: Fixed Fix Version/s: nightly Fixed in trunk with Committed revision 596524. > The generated services.xml file is not validate > > > Key: AXIS2-3330 > URL: https://issues.apache.org/jira/browse/AXIS2-3330 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools > Environment: Windows NT >Reporter: G.D.N.C.Pathiragoda > Assignee: Lahiru Sandakith > Fix For: nightly > > > I try to deploy a service using Axis2 IDEA plugin.I have make a service and > automatically generating service.xml but when I go to depploy the service > there is a validation error in service.xml the generated code is > > >Please Type your service description here > > >http://www.w3.org/2004/08/wsdl/in-only"; >class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" /> > http://www.w3.org/2004/08/wsdl/in-out"; > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" /> > > locked="false">service.NameService > >getStrings2 >getStrings >setnames >getStrings4 >getStrings5 >getNames >getStrings3 > > > > problem is on > >getStrings2 >getStrings >setnames >getStrings4 >getStrings5 >getNames >getStrings3 > > tags. > I think the problem with operation tags that have created.Whats the purpose > of operatin tags.when i delete operatin tags it validate properly.But i want > to know how to validate it properly with operation tags.Thank you -- 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]
[Axis2] excludeOperations against the schema at modeule/kernel/resources/services.xsd
Hi Devs, I was looking at the services.xsd at location modeule/kernel/resources, and used this one for the validation of the services.xml files in IDE Tools. Seems there is a problem with the excludeOperations. In the schema it refers to in which the operations are the normal type that comes at the service level, which does not seems to be complaint with the axis2, So I believe we need to change it to the actual nature that fits the sequence of getStrings2 getStrings . for Is there are any other place that we use this schema for validation, If no one against, I will go ahead and do the change. -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [VOTE] Bjorn Townsend for committer
+1 Thanks Sandkaith On Nov 14, 2007 10:02 PM, Glen Daniels <[EMAIL PROTECTED]> wrote: > Hi folks! > > As mentioned I'd like us to invite Bjorn Townsend, who's been helping > out on the fringes of Axis for a while now, to become a committer so he > can help us out with the Axis1 1.5 release. He's kindly volunteered to > help pull together the release, and toward that end, we need him to be > able to fix bugs and commit patches. > > Here's my +1. > > Thanks, > --Glen > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [VOTE] Sanjaya Karunasena as an Axis2 commiter
+1 Thanks Sandakith On Nov 13, 2007 12:00 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> 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] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Assigned: (AXIS2-3330) The generated services.xml file is not validate
[ https://issues.apache.org/jira/browse/AXIS2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3330: --- Assignee: Lahiru Sandakith > The generated services.xml file is not validate > > > Key: AXIS2-3330 > URL: https://issues.apache.org/jira/browse/AXIS2-3330 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools > Environment: Windows NT >Reporter: G.D.N.C.Pathiragoda > Assignee: Lahiru Sandakith > > I try to deploy a service using Axis2 IDEA plugin.I have make a service and > automatically generating service.xml but when I go to depploy the service > there is a validation error in service.xml the generated code is > > >Please Type your service description here > > >http://www.w3.org/2004/08/wsdl/in-only"; >class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" /> > http://www.w3.org/2004/08/wsdl/in-out"; > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" /> > > locked="false">service.NameService > >getStrings2 >getStrings >setnames >getStrings4 >getStrings5 >getNames >getStrings3 > > > > problem is on > >getStrings2 >getStrings >setnames >getStrings4 >getStrings5 >getNames >getStrings3 > > tags. > I think the problem with operation tags that have created.Whats the purpose > of operatin tags.when i delete operatin tags it validate properly.But i want > to know how to validate it properly with operation tags.Thank you -- 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-3318) Java2WSDL -p2n command line issue
[ https://issues.apache.org/jira/browse/AXIS2-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541714 ] Lahiru Sandakith commented on AXIS2-3318: - As I ran java2wsdl with out any argument it resulted correctly in Axis2 1.3 -p2n [,, Java2WSDL -p2n command line issue > - > > Key: AXIS2-3318 > URL: https://issues.apache.org/jira/browse/AXIS2-3318 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 > Environment: Windows XP, Eclipse europa >Reporter: Joy Kenneth Harry >Priority: Blocker > Fix For: 1.3 > > > If Java2WSDL's -p2n command line option is used as > -p2n "test.package urn:MyPackage" > Gives exception ***An error occured while generating codeString index out of > range: -2*** > It works fine if used in the following manner i.e COMMA between the pacakge > name and namespace. > -p2n "test.package, urn:MyPackage" > The command line usage text should be updated. -- 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 Release Restructuring
5. Samples ( only for above features) > > > > is this enogh or is there any thing to add or remove? > > > > As I guess here are the jars we need for that, > > > > Axis2 jars > > 1. axis2-adb-codegen-SNAPSHOT.jar > > 2. axis2-adb-SNAPSHOT.jar > > 3. axis2-codegen-SNAPSHOT.jar > > 4. axis2-java2wsdl-SNAPSHOT.jar > > 5. axis2-kernel-SNAPSHOT.jar > > > > ws jars > > 1. axiom-api-20071017.164440-781.jar > > 2. axiom-impl-20071017.164440-780.jar ( > > (do we need axiom-dom-20071017.164440-780.jar?) > > 3. neethi-20071017.164823-761.jar > > 4. woden-api-1.0-incubating-20071018.161106-2.jar > > 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar > > 6. wsdl4j-1.6.2.jar > > 7. XmlSchema-SNAPSHOT.jar > > > > other jars > > 1. activation-1.1.jar > > 2. annogen-0.1.0.jar > > 3. backport-util-concurrent-2.2.jar > > 4. commons-codec-1.3.jar > > 5. commons-fileupload-1.1.1.jar > > 6. commons-httpclient-3.0.1.jar > > 7. commons-io-1.2.jar > > 8. commons-logging-1.1.jar > > 9. geronimo-annotation_1.0_spec-1.1.jar > > 10. geronimo-stax-api_1.0_spec- 1.0.jar > > 11. httpcore-4.0-alpha5.jar > > 12. httpcore-nio-4.0-alpha5.jar > > 13. httpcore-niossl-4.0-alpha5.jar > > 14. jalopy-1.5rc3.jar > > 15. jaxen-1.1.1.jar > > 16. jettison-1.0-RC1.jar > > 17. log4j-1.2.14.jar > > 18. stax-api-1.0.1.jar > > 19. wstx-asl-3.2.1.jar > > 20. xalan-2.7.0.jar > > 21. xercesImpl-2.8.1.jar > > 22. xml-apis-1.3.03.jar > > > > Are there any thing to add or remove? > > Here any way 34 jars are there. and we have left 24 jars. > > > > thanks, > > Amila. > > > > On 10/30/07, Eran Chinthaka < [EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Amila Suriarachchi wrote: > > > > > > > > I have misunderstood the thing. > > > you mean > > > 1. minimal distribution with > > >server,client and kernal > > > 2. full distribution with > > >minmal + optional > > > 3. Tools distribution with > > >tools > > > > Exactly yes. I am not sure whether we need to expand full distro also in > > > > to two. Are we releasing all the modules with our current standard > > distro. > > > > > > > what I want to say is that we need a proper boundry definition about > > > what should goes to minimal distribution. > > > with some logical reasoning. Otherwise we have to discuss this again > > > when implementing. > > > > Agreed. That is why I made this a proposal rather than a vote :). We > > discussed this packaging issues couple of times and changed packaging > > couple of time. When Axis2 evolves and we get more insight in to user > > experience, we might want to change ourselves to cater for this > > requirements. I myself found it bit difficult/confused to use Axis2 once > > as a user. That is why I am proposing sth like this. > > > > Yes, let's discuss about this. And we might also want to revise this > > once the next release manager (Amila will it be you ;) ) try to > > implement this packaging proposal. > > > > So are we agreed to this three level distro? > > > > Thanks, > > Chinthaka > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.4.6 (GNU/Linux) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z > > 6SUmDsDsirjOF6j5WuAu9EA= > > =ZWKs > > -END PGP SIGNATURE- > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > -- > > Amila Suriarachchi, > > WSO2 Inc. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > -- > > Amila Suriarachchi, > > WSO2 Inc. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Amila Suriarachchi, > WSO2 Inc. -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Assigned: (AXIS2-3315) Compile error in generated JUnit
[
https://issues.apache.org/jira/browse/AXIS2-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith reassigned AXIS2-3315:
---
Assignee: Amila Chinthaka Suriarachchi
Amila , can you please look in to this, Assigning to you.
> Compile error in generated JUnit
>
>
> Key: AXIS2-3315
> URL: https://issues.apache.org/jira/browse/AXIS2-3315
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.3
> Environment: Windows XP
>Reporter: Kathy Chan
>Assignee: Amila Chinthaka Suriarachchi
>
> Using Axis2 v1.3, when I issue the following:
> wsdl2java -uri Persondetails.wsdl -t
> to generate JUnit testcase for client,I got a PersondetailsTest.java
> generated with compile error:
> public void testStartgetPersonDetails() throws java.lang.Exception{
> wtp.PersondetailsStub stub = new wtp.PersondetailsStub();
>
> stub.startgetPersonDetails(
> ,
> new tempCallbackN1000C()
> );
>
> }
> Note that there's a "," with no field in the call to
> stub.startgetPersonDetails.
> Here's the Persondetails.wsdl used:
> http://wtp";
> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
> xmlns:ns0="http://wtp/xsd";
> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
> xmlns:ns1="http://org.apache.axis2/xsd";
> xmlns:xs="http://www.w3.org/2001/XMLSchema";
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> targetNamespace="http://wtp";>
>
> Please Type your service description here
>
>
> http://wtp/xsd";
> attributeFormDefault="qualified"
> elementFormDefault="qualified"
> targetNamespace="http://wtp/xsd";>
>
>
>
>nillable="true"
> type="xs:string" />
>
>
>
>
>
>
>nillable="true"
> type="xs:string" />
>nillable="true"
> type="xs:int" />
>nillable="true"
> type="ns:Address" />
>nillable="true"
> type="xs:string" />
>nillable="true"
> type="xs:string" />
>nillable="true"
> type="xs:string" />
>
>
>
>
>
>
>nillable="true"
> type="xs:string" />
> type="xs:string" />
>nillable="true"
> type="xs:string" />
> type="xs:string" />
> type="xs:string" />
>
[jira] Created: (AXIS2-3317) Axis2 Client generation with wsdl2 java with -g option does not generate skema
Axis2 Client generation with wsdl2 java with -g option does not generate skema -- Key: AXIS2-3317 URL: https://issues.apache.org/jira/browse/AXIS2-3317 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.3 Environment: Axis2 1.3 codegen Reporter: Lahiru Sandakith Assignee: Amila Chinthaka Suriarachchi Currently the -g option in axis2 code generation works for server side only. For -g -u it works correctly. Is there a particular reason that we intentionally made that -g option only with service scenario correctly. This is related to Axis2 Eclipse Code generation reported issue, https://bugs.eclipse.org/bugs/show_bug.cgi?id=208054 -- 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-3178) ANT scripts stop working after "Code Generator Wizard - Eclipse Plug-in" installed
[ https://issues.apache.org/jira/browse/AXIS2-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3178: --- Assignee: Lahiru Sandakith > ANT scripts stop working after "Code Generator Wizard - Eclipse Plug-in" > installed > -- > > Key: AXIS2-3178 > URL: https://issues.apache.org/jira/browse/AXIS2-3178 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 > Environment: Eclipse 3.3 (JEE Distro / Europa) >Reporter: Dustin Henson >Assignee: Lahiru Sandakith > > In Eclipse you can run ant scripts using the External Tools toolbar item. > These stop working after the Code Generator Wizard is installed. The two > areas don't seem like they should be related and I don't have any lead as to > the cause, but I can recreate it consistently on my computer. > To recreate: > - Download and install the JEE Distro (Europa) of Eclipse 3.3 > - Create a simple ant script: > > > Test > > > - Set the ant script to run as an External Tools > Ant Build > - Test it and it works > - Download and install the 1.3 version of the "Code Generator Wizard - > Eclipse Plug-in" tool > - Restart Eclipse > - Run the ANT script again and it hangs. Checking the error log via the > Plug-in Development Perspective shows the following error: > Error logged from Ant UI: > java.net.SocketTimeoutException: Accept timed out > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.PlainSocketImpl.accept(Unknown Source) > at java.net.ServerSocket.implAccept(Unknown Source) > at java.net.ServerSocket.accept(Unknown Source) > at > org.eclipse.ant.internal.ui.launchConfigurations.RemoteAntBuildListener$ServerConnection.run(RemoteAntBuildListener.java:95) -- 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-3145) Eclipse codegen plugin namespace error
[ https://issues.apache.org/jira/browse/AXIS2-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3145: --- Assignee: Lahiru Sandakith > Eclipse codegen plugin namespace error > -- > > Key: AXIS2-3145 > URL: https://issues.apache.org/jira/browse/AXIS2-3145 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 > Environment: WindowsXP SP2, Eclipse 3.3.0, > axis2-eclipse-codegen-plugin 1.3 >Reporter: Suran Jayathilaka >Assignee: Lahiru Sandakith > Fix For: nightly > > Attachments: AXIS2-3145-idea.patch, AXIS2-3145.patch > > > WSDL generated by the plugin has schemaTargetNameSpace with a "/xsd" suffix. > Axis2 expects the schemaTargetNameSpace without that suffix. (i.e. the ?wsld > doesn't have the suffix.) -- 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-3163) BUG in service archiver plugin for eclipse of latest version (1.3)
[ https://issues.apache.org/jira/browse/AXIS2-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3163: --- Assignee: Lahiru Sandakith > BUG in service archiver plugin for eclipse of latest version (1.3) > -- > > Key: AXIS2-3163 > URL: https://issues.apache.org/jira/browse/AXIS2-3163 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 >Reporter: Ashok kariyappa > Assignee: Lahiru Sandakith > > Not able to archive the file using this wizard. it is not supporting > properly , > it wont give error or any thing it simply wont work . > > it wont go forward if click on the next button . > when click the second time it will start proceding and once the Generate > service XML screen comes , it wont proceed will stop there. > somebody mention this issue earlier, they said , it is resolved in new > version, but not. > i am having the new version 1.3 of codegen and service archiver . the same > problem with this.. > regards > ashok.k -- 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: Axis problem in eclipse framework - class loading
Hi Maciek, Eclipse WTP 2.0 include both Axis and Axis2 plugins. But Axis dependencies are embedded inside Axis plugins and Axis2 dependencies are not embedded inside Axis2 plugins. Because of the design of the Axis2 plugins it loads the runtime dependencies with the eclipse preferences runtime pointer. So as I know there is no problem at all to have more than 2 versions of Axis2 set of plugins in the same eclipse framework. From the given information from you, its seems like this is Axis runtime that gives problems. So I guess the problem is more likely related to how Axis runtime load its runtime libs when its initiated through eclipse plugin environment causes the problem. These are some information that I though might be helpful to you. Thanks Lahiru On 10/23/07, Maciek Datka <[EMAIL PROTECTED]> wrote: > > > Hello. > I just would like to ask someone to have a look at the eclipse bug report > and possibly comment if > we diagnose problem correctly and confirm the role that axis plays in the > bug. > > The bug report is here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=197819 > > Aternatively please search for bug 197819 on eclipse bugzilla. > > In short - the problem is that axis uses context class loader - and the > JVM > caches classes in native code. > The result is - problems when 2 eclipse plugins contains axis - the axis > doesn't work because of incorrecty loaded, cached classes. > > Please if you find time - have a look at the bug report. Also I can answer > any questions. > > The possible fix mentioned in different eclipse bug report - 127963 is to > change Class.forName(...,contextClassLoader) to > contextClassLoader.loadClass() > I would like to ask you is it possible. > > Best wishes > Maciej Datka > > > -- > View this message in context: > http://www.nabble.com/Axis-problem-in-eclipse-framework---class-loading-tf4677475.html#a13364378 > Sent from the Axis - Dev mailing list archive at Nabble.com. > > > --------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis/Axis2] benchmark with 100 clients?
Hi Srinath, Please have a look http://wso2.org/library/91, This article test each other with - Axis1 WSDL2Java generated code - Axis2 WSDL2Java generated code with ADB data binding (Axis2's simple built-in databinding) - Axis2 WSDL2Java generated code with Apache XMLBeans data binding Thanks Lahiru On 10/26/07, Srinath Perera <[EMAIL PROTECTED]> wrote: > > Hi All; > Does anyone has a Axis1 benchmark numbers (and may be client source) > which tested with 100+ concurrent clients? If you have one and OK with > sharing it, please drop a link. > > Thanks > Srinath > > > -- > > Srinath Perera: >Indiana University, Bloomington >http://www.cs.indiana.edu/~hperera/ >http://www.bloglines.com/blog/hemapani > > Beauty of style and harmony and grace and good rhythm depend on > simplicity -- Plato > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: for jar file
This class is in rmi module in the Axis2, i.e it will be in the axis2-rmi-*.jar src location will be ./modules/rmi/src/org/apache/axis2/rmi/deploy/RMIServiceDeployer.java Thanks Lahiru On 10/17/07, Pradip Sonar <[EMAIL PROTECTED]> wrote: > > Hi, > > I need jar file for *org.apache.axis2.rmi.deploy.RMIServiceDeployer *class > > Can anybody know from where I will get the jar file. > > > > *Thanks & Regards,* > > *Pradip S. Sonar* > > > > P *Think before you print > *CONFIDENTIALITY: This e-mail (including any attachments) may contain > confidential, proprietary and privileged information, and unauthorized > disclosure or use is prohibited. If you receive this e-mail in error, > please notify the sender and delete this e-mail from your system. > > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[Axis2] Axis2 Code generation with Custom JRE's
Hi Devs, This is related to Eclipse WTP Axis2 Integration Issue [1], on Web service client code gen fails with customized JRE. We've been able to fix this with the patch proposed latter on that thread. Its a small fix that we can include in the entry point of the codegenraion code. [1]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=204182 -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Commented: (AXIS2-3250) maven pom.xml build does not create target folders
[ https://issues.apache.org/jira/browse/AXIS2-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533040 ] Lahiru Sandakith commented on AXIS2-3250: - The axis2 build is now on with maven2 (2.0.7) It would be great if you can point us from where you were directed to the maven1 build (I found readme.txt on module/tools need to be updated) > maven pom.xml build does not create target folders > -- > > Key: AXIS2-3250 > URL: https://issues.apache.org/jira/browse/AXIS2-3250 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: modules >Affects Versions: 1.3 > Environment: Wintel > 4GB RAM > 1 Tera Disk > mvn 2.0.7 > java 1.5.0_02-b09 >Reporter: Martin Gainty >Priority: Minor > > download 2-1.3 > mvn --debug > note that all of the modules/artifactId/target > (target folder is not created for modules/artifactId should be > modules/artifactid/target) -- 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: Re:[Axis2] Axis2-Plugin-Bug?
Hi Matthias, can you post us the method signature in your java application that causes the WSDL to break, This will help us quickly to reproduce the problem and fix, if any. Thanks Lahiru On 10/3/07, Jaliya Ekanayake <[EMAIL PROTECTED]> wrote: > > Hi Matthias, > > It is the GregorianCalendar that causes the trouble and the generated wsdl > is not recognized by the plugin. There is an old maling thread regarding > this but could not find any outstanding jira about this. > > http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200401.mbox/[EMAIL > PROTECTED] > Hope someone in the dev list will help you. > > Thanks, > -jaliya > - Original Message - > From: <[EMAIL PROTECTED]> > To: "Jaliya Ekanayake" <[EMAIL PROTECTED]> > Sent: Tuesday, October 02, 2007 9:11 AM > Subject: Re:[Axis2] Axis2-Plugin-Bug? > > > Hi Jaliya, > > for a better understanding of what I did I send you some screenshots of > these steps. Hope this helps. > > Matthias > > > -Ursprüngliche Nachricht- > > Von: "Jaliya Ekanayake" <[EMAIL PROTECTED]> > > Gesendet: 01.10.07 17:46:54 > > An: <[EMAIL PROTECTED]> > > CC: <[EMAIL PROTECTED]> > > Betreff: Re:[Axis2] Axis2-Plugin-Bug? > > > > > > Hi Matthias, > > > > Please let us know which version of Axis2 you are using. > > > > -jaliya > > > > -Original Message- > > From: Matthias Längrich [mailto:[EMAIL PROTECTED] > > Sent: Monday, October 01, 2007 9:25 AM > > To: [EMAIL PROTECTED] > > Subject: Axis2-Plugin-Bug? > > > > Jaliya, > > > > I just created a small Java-application and used the archiver plugin to > > get > > it deployed as a web service. Afterwards, I created a wsdl using the > code > > generator plug in. Everything works fine. Right now I'm trying to > generate > > some client code out of the formerly created wsdl. The wizard asks me to > > point to the file. I'm doing so using the browse button. The path is > > correct. I press "next" and it says me that "Specified WSDL is not > > found!". > > That's unclear to me since the file is definitely there. Here's the path > > (don't mind the German words): C:\Dokumente und > > Einstellungen\laengrich\Eigene Dateien\workspace\WSTest02\time.wsdl > > > > I don't think that the spaces are a problem because some steps before, > > where > > I had to select a class, they didn't make any problems. The same is true > > for > > the backslash. Well, I don't have a clue. How can I get the plugin > > accepting > > this wsdl? > > > > Yours Sincerely > > Matthias > > > _ > > Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle > > Freunde gleichzeitig schicken: > http://freemail.web.de/features/?mc=021179 > > > > > > > > > > > ___ > Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate > kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=00 > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: So Long, and Thanks for All the Fish
Hi Dims, It's been a great pleasure to work with you and thanks for the enormous help provided when in need. Wish you all the best in your future endeavors and Looking forward to seeing you back again soon on all the ws projects. Thanks Lahiru On 10/1/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > > Hi Dims, > > First of all thank you very much for all the hard work you did specially > in Axis2 dev and user list. You helped a lot for both users and > developers. I will never forget the help I got from you when I was stuck > with Axis2 releases. Not only that you helped us lot by fixing issues > very quickly moving the project into the the correct path . Irrespective > of whether I agree with or not with your decision I am will wish you all > the best and hoping to see you active again in the list. > > Thanks > Deepal > > > > >> 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 > >> > >> > >> > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Created: (AXIS2-3236) Axis2 JAVA2WSDL need to convert the javadoc into wsdl documentation.
Axis2 JAVA2WSDL need to convert the javadoc into wsdl documentation. Key: AXIS2-3236 URL: https://issues.apache.org/jira/browse/AXIS2-3236 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: wsdl Affects Versions: 1.3 Reporter: Lahiru Sandakith Assignee: Deepal Jayasinghe This is related to POJO scenario. This would be an nice to have a feature. I am not exactly sure about the possibility of obtaining the javadoc from the compiled source, we need to figure out that (if its possible to compile the source preserving docs). Anyway if we include annotations in the method signature then we can definitely include that in the relevant place in the wsdl as documentation. -- 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 powered by logo
+1 for the "Axis2 Powered" logo. After finalizing we can include it in all plugin wizards. thanks Lahiru On 9/24/07, Afkham Azeez <[EMAIL PROTECTED]> wrote: > > I prefer "powered". Also I think the suggested logo looks a bit "fat". Can > we get a sleeker looking design. May be we could omit the image of the gear, > which will enable us to reduce the image width. > > -- Azeez > > On 9/21/07, Chatra Nakkawita <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I have attached an edited version of the logo, an 'Axis2 Inside' logo. > > Anyone is welcome to make further changes to it. > > > > But I'm in favor of 'Axis2 powered' (first image):-) > > > > -Chatra > > > > On 9/21/07, Srinath Perera < [EMAIL PROTECTED]> wrote: > > > > > > :), has "intel inside" changed to "intel powered"? may be It is time > > > to me to buy a new computer!! > > > thanks > > > Srinath > > > > > > > Beauty? ;-) U r getting soft in your old age .. > > > > > > > > "Powered" is the more normal thing IMO and even Intel Inside has > > > changed now! > > > > > > > > Anyway, either is fine .. we need to run this by PRC before it can > > > be used. > > > > > > > > Sanjiva. > > > > > > > > Srinath Perera wrote: > > > > > +1 .. Axis2 inside has a touch of beauty in it :) > > > > > Thanks > > > > > Srinath > > > > > > > > > > On 9/20/07, Davanum Srinivas <[EMAIL PROTECTED] > wrote: > > > > >> Chatra, > > > > >> > > > > >> How about "Powered -> Inside"? Looks great! > > > > >> > > > > >> thanks, > > > > >> dims > > > > >> > > > > >> On 9/20/07, Chatra Nakkawita < [EMAIL PROTECTED]> wrote: > > > > >>> Hi guys, > > > > >>> > > > > >>> Please find attached a 'powered by Axis2 logo'. > > > > >>> > > > > >>> I felt this will give the opportunity to other products which > > > use Axis2 to > > > > >>> give the desired recognition to Axis2. > > > > >>> > > > > >>> Any ideas or thoughts? > > > > >>> > > > > >>> Thanks & regards, > > > > >>> > > > > >>> Chatra > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > - > > > > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > >>> For additional commands, e-mail: [EMAIL PROTECTED] > > > > >>> > > > > >>> > > > > >> > > > > >> -- > > > > >> Davanum Srinivas :: http://davanum.wordpress.com > > > > >> > > > > >> > > > - > > > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > > >> > > > > >> > > > > > > > > > > > > > > > > > > -- > > > > Sanjiva Weerawarana, Ph.D. > > > > Founder & Director; Lanka Software Foundation; > > > http://www.opensource.lk/ > > > > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ > > > > Member; Apache Software Foundation; http://www.apache.org/ > > > > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > > > > Srinath Perera: > > >Indiana University, Bloomington > > > > > > http://www.cs.indiana.edu/~hperera/<http://www.cs.indiana.edu/%7Ehperera/> > > >http://www.bloglines.com/blog/hemapani > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Thanks > Afkham Azeez > > http://www.wso2.org > GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760 -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Resolved: (AXIS2-3145) Eclipse codegen plugin namespace error
[ https://issues.apache.org/jira/browse/AXIS2-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3145. - Resolution: Fixed Fixed in the Committed revision 570650. Thanks Suran. > Eclipse codegen plugin namespace error > -- > > Key: AXIS2-3145 > URL: https://issues.apache.org/jira/browse/AXIS2-3145 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.3 > Environment: WindowsXP SP2, Eclipse 3.3.0, > axis2-eclipse-codegen-plugin 1.3 >Reporter: Suran Jayathilaka > Fix For: nightly > > Attachments: AXIS2-3145-idea.patch, AXIS2-3145.patch > > > WSDL generated by the plugin has schemaTargetNameSpace with a "/xsd" suffix. > Axis2 expects the schemaTargetNameSpace without that suffix. (i.e. the ?wsld > doesn't have the suffix.) -- 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] Maven2 SNAPSHOT dependencies included with date suffix
Thanks Saminda, I was able to come up with a solution with your suggestions
that we can have both nightly builds with SNAPSHOTs and release builds work.
I have fixed the build and committed the code.
Thank you
Lahiru
On 8/27/07, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> If you are using assembly pluging to build the distribution, try this in
> your assembly xml,
>
> ...
>
>
> ${artifactId}.SNPAHOT.${extension}
>
> /lib
>
> *:SNAPSHOT:jar:*
>
>
>
> ...
>
> Above is just a temporally solution, but I think you get the idea. You
> need the latest assembly pluging to do the prior. Try version 2.2-beta-1and
> above.
>
> Thank you
>
> Saminda
>
>
>
> On 8/27/07, Lahiru Sandakith <[EMAIL PROTECTED]> wrote:
> >
> > Hi devs,
> > When we have SNAPSHOT dependencies for a particular module, maven2 on
> > line build include them in to the module dependencies with a date suffix.
> > What we need is when we do nightly builds maven2 should rename that to
> > SNAPSHOT and include that in to the nightly builds. For example In order for
> > the eclipse plugins nightly builds to work we have to have the exact 3rd
> > party library name to elcipse framework to load it through the
> > plugin.xml. (There is no question about releases , since we are not
> > going with SNAPSHOTs)
> > Is there a way that we can have renamed SNAPSHOT included in the builds.
> > (AFAIK maven2 get the latest from the repos and rename that to SNAPSHOT in
> > local)
> > For example We have the neethi dependency in the eclipse plugin pom.xmlas
> >
> > org.apache.neethi
> > neethi
> > ${neethi.version}
> >
> > the version coming from the parent which is SNAPSHOT. Problem comes when
> > there is a new neethi nightly build available in the repos compare to my
> > local machine, the build include it as neethi-20070825.224622-550.jarnot as
> > neethi-SNAPSHOT.jar with the on-line build.
> > --
> > Thanks
> > Lahiru Sandakith
> >
> > http://sandakith.wordpress.com/
> > GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
> >
>
>
>
>
> --
> Saminda Abeyruwan
>
> Software Engineer
> WSO2 Inc. - www.wso2.org
--
Thanks
Lahiru Sandakith
http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Maven2 SNAPSHOT dependencies included with date suffix
Hi devs,
When we have SNAPSHOT dependencies for a particular module, maven2 on line
build include them in to the module dependencies with a date suffix. What we
need is when we do nightly builds maven2 should rename that to SNAPSHOT and
include that in to the nightly builds. For example In order for the eclipse
plugins nightly builds to work we have to have the exact 3rd party library
name to elcipse framework to load it through the plugin.xml. (There is no
question about releases , since we are not going with SNAPSHOTs)
Is there a way that we can have renamed SNAPSHOT included in the builds.
(AFAIK maven2 get the latest from the repos and rename that to SNAPSHOT in
local)
For example We have the neethi dependency in the eclipse plugin pom.xml as
org.apache.neethi
neethi
${neethi.version}
the version coming from the parent which is SNAPSHOT. Problem comes when
there is a new neethi nightly build available in the repos compare to my
local machine, the build include it as neethi-20070825.224622-550.jar not as
neethi-SNAPSHOT.jar with the on-line build.
--
Thanks
Lahiru Sandakith
http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [AXIS2] Nominate Roy Wood and Dustin Amrhein to COMMITTER
+1 Lahiru On 8/16/07, R J Scheuerle Jr <[EMAIL PROTECTED]> 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) >
Re: [Axis2][VOTE]Axis2 1.3 release artifacts (#take2)
+1 for the release including plugins. On 8/8/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > I have uploaded Axis2 1.3 into my Apache home location [1] . This > release doesn't contain any SNAPSHOT dependencies and we haven't done > any major changes since RC3. Please test this release as much as you > can and help us to make this release stable. > > 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 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-take2/ > [2] : http://people.apache.org/~deepal/axis2/1.3-take2/tools/ > [3] : http://people.apache.org/~deepal/axis2/1.3-take2/m2-repo/ > > > P.S : Please note that I need to have two more PMC vote to go ahead > with the release. > > > Thanks > Deepal > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGuZyhjOGcXNDx0CARAtB+AJ4zj1XbXxv24WRj+axe37reelxZywCguQby > uHxCZTuam5XgtJq+uaP+CF4= > =AbF+ > -END PGP SIGNATURE- > > > ----- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
