You can add your third part jars inside the service archive file as an
example if service foo require some third party lib called "a.jar" then
you can add a.jar into foo.aar as follows
foo.aar
MATA-INF
services.xml
lib
a.jar
David Boyer wrote:
> Hey,
>
> New user to axis. I’ve been unable to find any in depth documentation
> or discussion of the code generation engine. I’m digging through the
> codegen module trying to figure out how to plug into the code
> generation to add stuff specific to our project. In this project the
> WSDL is going to be dynamic for some time. My current plan is to use a
> simple name matching pattern that would be easy to dynamically
> generate code for. The idea is to create one class per service (Class
> name = Service name) and one method per action in the service (method
> name = action name). In those external classes I would implement the
> necessary business functionality. Which, though volatile, we wish to
> manage it through standard source control mechanisms.
>
> So the ideal body of a generated function would look like this:
>
> public class DocumentServicePortTypeSkeleton {
>
> *import mypackage.DocumentService;*
>
> public OMElement getDocument () throws Exception {
>
> return DocumentService.getDocument();
>
> }
>
> }
>
> I’ve found the SkeletonTemplate.xsl file. Obviously I could pull this
> out and modify it to suit my needs, rejar and run with it. However, my
> impression is that you’ve designed to allow me to point the
> CodeGenerator at other instances of something like SkeletonTemplate.xsl.
>
> Is there a solution of the second type? (write my own .xsl and
> register it somehow with codegen) If so, is there any documentation on
> this method of interaction? (Mailing list posts, design documents,
> tutorial)
>
> Thanks,
>
> P.S. I’m also wanting to do something similar to the build.xml file
> generated for Ant, to include our class files in the generated aar. If
> there is an alternative location within the exploded axis2 webapp for
> dumping a jar-file for access by a specific aar, that would meet our
> purposes as well. But I haven’t done all of the research yet on this
> issue.
>
> -----------------------------------------------------------------
>
> Deliver Higher Quality, Easier to Maintain Code
>
> with TAU/Logiscope - www.telelogic.com <http://www.telelogic.com/>
>
> -----------------------------------------------------------------
>
> David S. Boyer
>
> Sr. S/W Developer
>
> Telelogic North America
>
> Business: +1 (703) 944-9289
>
> Mobile: +1 (703) 944-9289
>
> mailto:[EMAIL PROTECTED]
>
> -----------------------------------------------------------------
>
> Telelogic - Requirements Driven Innovation
>
> --------------------------------------------------------------------------------
> *Telelogic Lifecycle Solutions:
> Helping You Define, Design & Deliver Advanced Systems & Software
> Learn More at www.telelogic.com <http://www.telelogic.com/>
>
> *David Boyer
> Sr. Software Developer
> Telelogic North America Inc.
> 11911 Freedom Drive,
> Suite 1180
> Reston
> VA 20190
> United States
>
> Phone: +1 (703) 944-9289
> Fax:
> Mobile phone: +1 (703) 944-9289
>
> _
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> http://www.telelogic.com <http://www.telelogic.com/>
>
> ** *Telelogic - Requirements-Driven Innovation!
> ------------------------------------------------------------- *
>
>
> The information contained in this e-mail, including any attachment or
> enclosure, is intended only for the person or entity to which it is
> addressed and may contain confidential material. Any unauthorized use,
> review, retransmissions, dissemination, copying or other use of this
> information by persons or entities other than the intended recipient
> is prohibited.
>
--
Thanks,
Deepal
................................................................
~Future is Open~
