Axis2
Locked
 
Administrator
|
Hi Devs,
I have (quickly) tested the Paul Piper's Axis2 component (from a previous work by Alfredo Rueda Unsain) see http://docs.ofbiz.org/pages/viewpageattachments.action?pageId=6090 And it integrates and works well in OFBiz hot-deploy. I'd like now, as question about SOAP complex types come over and over, make it a specialpurpose component (not showing), WDYT ? Thanks Jacques PS : I got only this error about "valid certification path" There was a problem in Axis2 version service , may be the service not available or some thing has gone wrong. But this does not mean system is not working ! Try to upload some other service and check to see whether it is working. and in log 2009-04-26 17:19:01,187 (http-0.0.0.0-18443-1) [ ControlServlet.java:299:INFO ] [[[login] Request Done- total:7.094,since last([login] Request B...):7.094]] 2009-04-26 17:19:39,156 (http-0.0.0.0-18443-2) [ HttpMethodDirector.java:439:INFO ] I/O exception (org.apache.axis2.AxisFault) caught when processing request: sun.security.validator.ValidatorException: PKIX p ath building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target But this does not seem to be a big issue |
|
Inline :
On Sun, Apr 26, 2009 at 9:02 PM, Jacques Le Roux < [hidden email]> wrote: > Hi Devs, > > I have (quickly) tested the Paul Piper's Axis2 component (from a previous > work by Alfredo Rueda Unsain) see > http://docs.ofbiz.org/pages/viewpageattachments.action?pageId=6090 > And it integrates and works well in OFBiz hot-deploy. I'd like now, as > question about SOAP complex types come over and over, make it > a specialpurpose component (not showing), WDYT ? + 1 for adding it in the special purpose (not showing). > > > Thanks > > Jacques > |
|
|
Sorry I missed the earlier message... Shouldn't this be in the framework and refactored to be part of the service or perhaps webtools components? I ask because I think this is more of a core/technical type of functionality. -David On Apr 26, 2009, at 9:53 PM, Ashish Vijaywargiya wrote: > Inline : > > On Sun, Apr 26, 2009 at 9:02 PM, Jacques Le Roux < > [hidden email]> wrote: > >> Hi Devs, >> >> I have (quickly) tested the Paul Piper's Axis2 component (from a >> previous >> work by Alfredo Rueda Unsain) see >> http://docs.ofbiz.org/pages/viewpageattachments.action?pageId=6090 >> And it integrates and works well in OFBiz hot-deploy. I'd like now, >> as >> question about SOAP complex types come over and over, make it >> a specialpurpose component (not showing), WDYT ? > > > + 1 for adding it in the special purpose (not showing). > > >> >> >> Thanks >> >> Jacques >> |
|
|
+1 on David's comment.
Somehow I missed to think like this. -- Ashish David E Jones wrote: > > Sorry I missed the earlier message... > > Shouldn't this be in the framework and refactored to be part of the > service or perhaps webtools components? I ask because I think this is > more of a core/technical type of functionality. > > -David > > > |
smime.p7s (4K) |
Administrator
|
Yes, this sounds like the better place. Webtools with a link seems more accessible. I will do
Jacques From: "Ashish Vijaywargiya" <[hidden email]> > +1 on David's comment. > > Somehow I missed to think like this. > > -- > Ashish > > David E Jones wrote: >> >> Sorry I missed the earlier message... >> >> Shouldn't this be in the framework and refactored to be part of the >> service or perhaps webtools components? I ask because I think this is >> more of a core/technical type of functionality. >> >> -David >> >> >> > |
|
Administrator
|
In my effort to commit the new Axis2 component in framework I wonder about licences issues.
I have added the necessary in NOTICE, it was easy, no problems Currently in the component, at framework/axis2/webapp/axis2/WEB-INF/lib/ precisely, there are a number of libraries which come with their licence files. There are near hundred files (97 exactly), 40 being licence files. I was ready to put the content of these licence files in the LICENCE file and to put also the libraries with them as it's done for the others. But then I wondered if it's a worthwhile (very tedious) task. For 2 reasons : 1) The information is already there, and we could just said that in the LICENCE file 2) If we do so future updates will be far easier (nothing to check but maybe updating the wiki page related to libraries) What do you think ? Do we really need to put these informations in LICENCE file or a simple mention in it would be sufficient ? Something like <<Some extra libraries come with Axis2, their licence files can be found into framework/axis2/webapp/axis2/WEB-INF/lib/>> added after <<Other licenses used by libraries distributed with Apache OFBiz are listed below. This file includes a list of all libraries distributed with Apache OFBiz and the full text of the license used for each.>> Thanks Jacques From: "Jacques Le Roux" <[hidden email]> > Yes, this sounds like the better place. Webtools with a link seems more accessible. I will do > > Jacques > > From: "Ashish Vijaywargiya" <[hidden email]> > > >> +1 on David's comment. >> >> Somehow I missed to think like this. >> >> -- >> Ashish >> >> David E Jones wrote: >>> >>> Sorry I missed the earlier message... >>> >>> Shouldn't this be in the framework and refactored to be part of the service or perhaps webtools components? I ask because I >>> think this is more of a core/technical type of functionality. >>> >>> -David >>> >>> >>> >> > |
|
|
It sounds like that stuff needs a LOT of cleaning up before it goes into the trunk... I don't think this makes sense to put into its own component and should (like the older Axis stuff) go into the service and webtools components. If that's beyond what you want to invest in this, don't worry about it... sooner or later it will be important enough to someone to sit down and do it... and if not then it's a clear sign that no one cares enough! :( -David On May 2, 2009, at 1:42 PM, Jacques Le Roux wrote: > In my effort to commit the new Axis2 component in framework I wonder > about licences issues. > I have added the necessary in NOTICE, it was easy, no problems > Currently in the component, at framework/axis2/webapp/axis2/WEB-INF/ > lib/ precisely, there are a number of libraries which come with > their licence files. There are near hundred files (97 exactly), 40 > being licence files. > I was ready to put the content of these licence files in the LICENCE > file and to put also the libraries with them as it's done for > the others. > But then I wondered if it's a worthwhile (very tedious) task. > For 2 reasons : > 1) The information is already there, and we could just said that in > the LICENCE file > 2) If we do so future updates will be far easier (nothing to check > but maybe updating the wiki page related to libraries) > > What do you think ? Do we really need to put these informations in > LICENCE file or a simple mention in it would be sufficient ? > Something like <<Some extra libraries come with Axis2, their licence > files can be found into > framework/axis2/webapp/axis2/WEB-INF/lib/>> added after > <<Other licenses used by libraries distributed with Apache OFBiz are > listed > below. This file includes a list of all libraries distributed with > Apache > OFBiz and the full text of the license used for each.>> > > Thanks > > Jacques > > > From: "Jacques Le Roux" <[hidden email]> >> Yes, this sounds like the better place. Webtools with a link seems >> more accessible. I will do >> >> Jacques >> >> From: "Ashish Vijaywargiya" <[hidden email]> >> >> >>> +1 on David's comment. >>> >>> Somehow I missed to think like this. >>> >>> -- >>> Ashish >>> >>> David E Jones wrote: >>>> >>>> Sorry I missed the earlier message... >>>> >>>> Shouldn't this be in the framework and refactored to be part of >>>> the service or perhaps webtools components? I ask because I >>>> think this is more of a core/technical type of functionality. >>>> >>>> -David >>>> >>>> >>>> >>> >> > > |
|
Administrator
|
From: "David E Jones" <[hidden email]>
> It sounds like that stuff needs a LOT of cleaning up before it goes into the trunk... Do you say that only from my message below or did you test and review the component ? > I don't think this makes sense to put into its own component and should (like the older Axis stuff) go into the service and > webtools components. I think having Axis2 as a webap embedded in OFBiz is giving OFBiz OOTB more possibilities regarding SOAP Web services. We could let it apart as it's now in a page attachement in wiki. But I'm sure it will need to be updated from time to time and having it in OFBiz will trigger this needs avoiding to forget it. Also I'm sure that having it embedded will allow more contributions than if it's obscured somewhere in wiki. > If that's beyond what you want to invest in this, don't worry about it... sooner or later it will be important enough to someone > to sit down and do it... and if not then it's a clear sign that no one cares enough! :( We had enough recurring demands these last year to not negligt these possiblities. If it's ok to do like I proposed below, it's reday to be commited. Else yes, I will need to work this slowly. But I don't think we need to make it more inbricated with OFBiz. Alfredo's and Paul's recent experience are positive with Axis as a simple component. THis allow also to have the Axis2 Administrator console which adds some nice feature. Axis2 component could be simply accessed from Webtolls Jacques > -David > > > On May 2, 2009, at 1:42 PM, Jacques Le Roux wrote: > >> In my effort to commit the new Axis2 component in framework I wonder about licences issues. >> I have added the necessary in NOTICE, it was easy, no problems >> Currently in the component, at framework/axis2/webapp/axis2/WEB-INF/ lib/ precisely, there are a number of libraries which come >> with >> their licence files. There are near hundred files (97 exactly), 40 being licence files. >> I was ready to put the content of these licence files in the LICENCE file and to put also the libraries with them as it's done >> for >> the others. >> But then I wondered if it's a worthwhile (very tedious) task. >> For 2 reasons : >> 1) The information is already there, and we could just said that in the LICENCE file >> 2) If we do so future updates will be far easier (nothing to check but maybe updating the wiki page related to libraries) >> >> What do you think ? Do we really need to put these informations in LICENCE file or a simple mention in it would be sufficient ? >> Something like <<Some extra libraries come with Axis2, their licence files can be found into >> framework/axis2/webapp/axis2/WEB-INF/lib/>> added after >> <<Other licenses used by libraries distributed with Apache OFBiz are listed >> below. This file includes a list of all libraries distributed with Apache >> OFBiz and the full text of the license used for each.>> >> >> Thanks >> >> Jacques >> >> >> From: "Jacques Le Roux" <[hidden email]> >>> Yes, this sounds like the better place. Webtools with a link seems more accessible. I will do >>> >>> Jacques >>> >>> From: "Ashish Vijaywargiya" <[hidden email]> >>> >>> >>>> +1 on David's comment. >>>> >>>> Somehow I missed to think like this. >>>> >>>> -- >>>> Ashish >>>> >>>> David E Jones wrote: >>>>> >>>>> Sorry I missed the earlier message... >>>>> >>>>> Shouldn't this be in the framework and refactored to be part of the service or perhaps webtools components? I ask because I >>>>> think this is more of a core/technical type of functionality. >>>>> >>>>> -David >>>>> >>>>> >>>>> >>>> >>> >> >> > |
|
|
In reply to this post by David E Jones-3
It looks like there was still some reference to my old Java class (I expected that to happen), but shouldn't be a problem for me to fix and re-upload (I will do that later tonight). I would also argue for it to be a part of the framework itself, since it is of such an importance to anybody who needs to rely on Webservices. I don't exactly understand how the previous AXIS-components were integrated, but if we could accomplish something similar with this one (meaning the neat export=true functionality), I am sure it would be of good use for any developer. Right now the process works as the following: 1) Deploy the folder (leave the build.xml file as is) 2) create a Java Object for the service parameters you want to create 3) create the service itself (also in a java class) 4) use the specific axis2 build file to generate and deploy the service to axis2 (ant generate.service)... You do not need to run the rpc.clienz, that is only for testing-purposes... |
|
|
build.xml
Please do me a favor and replace the included build.xml file located in /webservices/orca with the one attached. I removed the last few references to our own classes and replaced them with the sample WeatherServices one. The WeatherService java source is the basic example provided by the AXIS2 Framework, btw. Oh and as for all other references: BP is the company i am working for, Orca is what we named parts of our software. You can change all that in this package, of course... |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |