Re: [Axis2] : axis2-java2wsdl.jar NIGHTLY BUILD too small
Hi Deepal, Are those changes commited in the HEAD revision of trunk? Regards On 6/6/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: Hi Vasil , We have move a set of classes from java2wsdl to kernal module , that may be the case jar size. Thanks Deepal > Hi all, > > If I build the axi2-java2wsdl jar from the HEAD revision i get a jar > file which is approx. 58K > and the jar from the nightly build is around 28K > > Regards, Vasil > > -- > Vasil Benov, > Mobile: +359(0)889/202682 > @-mail: benovv at gmail dot com > ICQ: 140269988 > > GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 > Public Key URL: > *) http://random.sks.keyserver.penguin.de/ -- Thanks, Deepal "The highest tower is built one brick at a time" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
[Axis2] : axis2-java2wsdl.jar NIGHTLY BUILD too small
Hi all, If I build the axi2-java2wsdl jar from the HEAD revision i get a jar file which is approx. 58K and the jar from the nightly build is around 28K Regards, Vasil -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
[AXIS2] : maven2 - axis2 war distribution
Hi all, Is it possible to build axis2 war distribution with maven2 Regards, Vasil -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
Re: Axis2 and Maven
Hi it depends, what parts of axis2 you need in your project. A lot of things are already implemented in the 1.2 branch. I have tested and used so far: axis2-kernel * eclipse integration works * build (compile, package etc.) works axis2-java2wsdl * eclipse integration works * build (compile, package etc.) works Regards, Vasil On 4/13/07, lightbulb432 <[EMAIL PROTECTED]> wrote: Thanks for the responses. Is Maven2 support expected to be added anytime soon? If no, is there any way for this to be compatible with the rest of my project that uses Maven2? How would you go about making it work - I can't seem to think of any good way to organize the way I approach my project but keeping all the benefits of Maven-based management. Thanks. Peter Gylling Jørgensen wrote: > > For the record and benifit for newcommers, I think it would be appropriate > also to point to the official help: > > http://ws.apache.org/axis2/svn.html > > From this page you can also uptain instructions for setting up the needed > environment. > > \pgj > >> -Original Message- >> From: Alistair Young [mailto:[EMAIL PROTECTED] >> Sent: Thursday, April 12, 2007 9:27 PM >> To: [EMAIL PROTECTED] >> Subject: Re: Axis2 and Maven >> >> >> svn co >> http://svn.apache.org/repos/asf/webservices/axis2/trunk/java trunk >> >> then for a quick build >> >> maven -Dskip.enterprise.tests=true -Dmaven.test.skip=true >> clean release dist >> >> Alistair >> >> >> -- >> mov eax,1 >> mov ebx,0 >> int 80h >> >> > >> > Could somebody point me to the source repository for Axis2 >> using Maven1 or >> > Maven2? I can't seem to find it, but only what someone on >> the Maven forum >> > called a "binary repository" at this URL: >> > >> > >> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/ > apache/axis2/ >> >> I've also download the zip file of Axis2 but don't see any pom.xml or >> anything like that in there. As I'm fairly new to Maven, if you could >> please >> point me in the right direction, it'd be really appreciated. >> >> Thanks. >> -- >> View this message in context: >> http://www.nabble.com/Axis2-and-Maven-tf3567687.html#a9966535 >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> - >> 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] > > > -- View this message in context: http://www.nabble.com/Axis2-and-Maven-tf3567687.html#a9968595 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
[Axis2]: Namespaces and service names
Hi all, My question is, does Axis2 uses namespaces in addition to service name to register/identify services? If the answer is "yes", I would appreciate if someone can explain how this exactly works. Regards, Vasil -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
Re: [AXIS2] Using OperationContext in a web services implementation class
Thanks Deepal, Regards, Vasil On 1/29/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: Yes you can do the following; MessageContext msgCtx = MessageContext.getCurrentMessageContext(); msgCtx.getOperationContext(); Thanks Deepal > Hi all, > > Is it possible to access the OperationContext in a services > implementation class? > > Thanks in advance > > Regards, Vasil > > -- > Vasil Benov, > Mobile: +359(0)889/202682 > @-mail: benovv at gmail dot com > ICQ: 140269988 > > GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 > Public Key URL: > *) http://random.sks.keyserver.penguin.de/ -- Thanks, Deepal "The highest tower is built one brick at a time" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
[AXIS2] Using OperationContext in a web services implementation class
Hi all, Is it possible to access the OperationContext in a services implementation class? Thanks in advance Regards, Vasil -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
Solved: [AXIS2] How to get available services in a fully programmatic way
Hi all, The right way to go is: ConfigurationContext confCtx = ConfigurationContextFactory.createConfigurationContextFromFileSystem(repo, axis2xml); AxisConfiguration axisConfig = confCtx.getAxisConfiguration(); HashMap serviceMap = axisConfig.getServices(); What has confused me, is that in the javadoc the first parameter of the createConfigurationContextFromFileSystem(path, axis2xml) is said to be the path to the repository. It is actually the absolute path to the WEB-INF directory (Don't know if repository is really what it is meant there) Regards -- Forwarded message -- From: Vasil Benov <[EMAIL PROTECTED]> Date: Jan 23, 2007 12:29 PM Subject: [AXIS2] How to get available services in a fully programmatic way To: axis-user@ws.apache.org Hi all, How do i get a list of all available services on Axis2 in a fully programmatic way? For example with a servlet which uses the same Axis2 runtime. Regards Vasil -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/ -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
[AXIS2] two versions of the same library
Hi all, I am considering the following use case. I have a service which needs external .jar file. I have two versions of this jar. If I put one version in the directory of my .aar and the other one in the directory of the Axis2 web application, then the one in the Axis2 directory loads always first. Is it possible either in a programmatic way or through configuration(e.g. services.xml, axis2.xml) to change this behavior. I would like the .jar that comes with my .aar to be loaded first. Regards, Vasil -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
[AXIS2] How to get available services in a fully programmatic way
Hi all, How do i get a list of all available services on Axis2 in a fully programmatic way? For example with a servlet which uses the same Axis2 runtime. Regards Vasil -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
Re: services.xml
Hi Deepal, The schama does not define a attribute of the element from the file, although the documentation ( http://ws.apache.org/axis2/1_1/axis2config.html#Service_Configuration) mentions the attribute as optional Best regards, Vasil On 1/2/07, Vasil Benov <[EMAIL PROTECTED]> wrote: Hi Deepal, Thank you very much for the e-mail. I'll take a look at the svn repo. Best regards, Vasil On 1/1/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > > Hi Vasil ; > > We have a schema file for services.xml in the xdoc directory in the svn > (xdocs\1_1\resources\schemas) , but it is not up to date with the recent > changes. I will make those changes and commit them. > > Thanks > Deepal > > > Hi Yamini, > > > > Thank You for the reply. > > > > What I am looking for is a really complete services.xml spec or a > > schema definition. > > > > Best regards, > > Vasil > > > > On 12/28/06, * Hemanth, Yamini (MSAS Sys Dev IBD)* > > <[EMAIL PROTECTED] > > > wrote: > > > > > > Hi Vasil, > > > > > > Please find below the description of services.xml file. > > > > > > > > > > * Writing services.xml > > > > The description of services are specified using services.xml. Each > > service archive file needs to have a services.xml in order to be a > > valid service and it should be available in the META-INF directory > > > of the archive file. A very simple services.xml is shown below: > > > > class="full qualifide name the service lifecycle class" > targetNamespace="target namespase for the service"> > > > > The description of the service > > > > > > HTTP > > > > > > > > > > > > > >http://www.w3.org/2004/08/wsdl/in-out > > <http://www.w3.org/2004/08/wsdl/in-out>" > > class=" > org.apache.axis2.rpc.receivers.RPCMessageReceiver "/> > > > > > > > >org.apache.axis2.sample.echo.EchoImpl > > > > > >Mapping to action > > > > > > > > > > > > > > *name*: The service name will be the name of the archive file, if > > the .aar file contains only one service, or else the name of the > > service will be the name given by the name attribute. > > > > *scope*: (Optional Attribute) The time period in which runtime > > information of deployed services will be available. Scope is of > > several types- "Application", "SOAPSession", "TransportSession", > > "Request". The default value (if you dont put any value) will be > > "Request" > > > > *class*: (Optional attribute) To specify the full qualified name > > of the service lifecycle implementation class. ServiceLifeCycle > > class is usefull when you want to do some tasks when the system > > start and when it shutdowns. > > > > *targetNamespace*: (Optional Attribute) Target name space of the > > service, and this value will be used when generating the wsdl , if > > you do not specify this value , then the value will be calculated > > from the package name of the service impl class > > > > *description*: This is an optional element if you want to display > > any description about the service via Axis2 web-admin module, then > > > the description can be specified here. > > > > *transports* : The transports that the service is going to be > > exposed to. This is an optional element. If the transport element > > is not present then the service will be exposed in all the > > transports available in the system. The transport child element is > > there to specify the transport prefix (the name of the transport > > specified in axis2.xml). > > > > *parameters:* A services.xml can have any number of top level > > parameters and all the specified parameters will be transformed > > into service properties in the corresponding AxisService. There is > > a compulsory parameter in a services.xml called ServiceClass which > > specifies the java class which really does the job and the class > > will be loaded by the MessageReceiver. > > > > *operations :* If the service impl class is java, then all the > > public methods in that service will be exposed and if the user > > wants t
Re: services.xml
Hi Deepal, Thank you very much for the e-mail. I'll take a look at the svn repo. Best regards, Vasil On 1/1/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: Hi Vasil ; We have a schema file for services.xml in the xdoc directory in the svn (xdocs\1_1\resources\schemas) , but it is not up to date with the recent changes. I will make those changes and commit them. Thanks Deepal > Hi Yamini, > > Thank You for the reply. > > What I am looking for is a really complete services.xml spec or a > schema definition. > > Best regards, > Vasil > > On 12/28/06, * Hemanth, Yamini (MSAS Sys Dev IBD)* > <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Hi Vasil, > > > Please find below the description of services.xml file. > > > > > * Writing services.xml > > The description of services are specified using services.xml. Each > service archive file needs to have a services.xml in order to be a > valid service and it should be available in the META-INF directory > of the archive file. A very simple services.xml is shown below: > > > > The description of the service > > > HTTP > > > > > > >http://www.w3.org/2004/08/wsdl/in-out > <http://www.w3.org/2004/08/wsdl/in-out>" > class=" org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> > > > >org.apache.axis2.sample.echo.EchoImpl > > >Mapping to action > > > > > > > *name*: The service name will be the name of the archive file, if > the .aar file contains only one service, or else the name of the > service will be the name given by the name attribute. > > *scope*: (Optional Attribute) The time period in which runtime > information of deployed services will be available. Scope is of > several types- "Application", "SOAPSession", "TransportSession", > "Request". The default value (if you dont put any value) will be > "Request" > > *class*: (Optional attribute) To specify the full qualified name > of the service lifecycle implementation class. ServiceLifeCycle > class is usefull when you want to do some tasks when the system > start and when it shutdowns. > > *targetNamespace*: (Optional Attribute) Target name space of the > service, and this value will be used when generating the wsdl , if > you do not specify this value , then the value will be calculated > from the package name of the service impl class > > *description*: This is an optional element if you want to display > any description about the service via Axis2 web-admin module, then > the description can be specified here. > > *transports* : The transports that the service is going to be > exposed to. This is an optional element. If the transport element > is not present then the service will be exposed in all the > transports available in the system. The transport child element is > there to specify the transport prefix (the name of the transport > specified in axis2.xml). > > *parameters:* A services.xml can have any number of top level > parameters and all the specified parameters will be transformed > into service properties in the corresponding AxisService. There is > a compulsory parameter in a services.xml called ServiceClass which > specifies the java class which really does the job and the class > will be loaded by the MessageReceiver. > > *operations :* If the service impl class is java, then all the > public methods in that service will be exposed and if the user > wants to override it then he has to add the "operation" tag and > override it. In the case of non-Java or if you do not have a > service class, then all the operations the user wants to expose by > the service has to be indicated in the services.xml and the > correct way of specifying is as follows: > > > > > > > The only compulsory attribute here is "name", which represents the > operation name that is going to be exposed. Any operation can > contain module references as well as any number of parameters. The > most interesting thing is that one can register custom message > receivers per operation, then the registered message receiver will > be the message receiver for the corresponding operation. If one > does not specify the message receiver, then the default message > receiver will do the job. > > >
Re: services.xml
Hi Yamini, Thank You for the reply. What I am looking for is a really complete services.xml spec or a schema definition. Best regards, Vasil On 12/28/06, Hemanth, Yamini (MSAS Sys Dev IBD) < [EMAIL PROTECTED]> wrote: Hi Vasil, Please find below the description of services.xml file. - Writing services.xml The description of services are specified using services.xml. Each service archive file needs to have a services.xml in order to be a valid service and it should be available in the META-INF directory of the archive file. A very simple services.xml is shown below: The description of the service HTTP http://www.w3.org/2004/08/wsdl/in-out"; class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> org.apache.axis2.sample.echo.EchoImpl Mapping to action *name*: The service name will be the name of the archive file, if the .aar file contains only one service, or else the name of the service will be the name given by the name attribute. *scope*: (Optional Attribute) The time period in which runtime information of deployed services will be available. Scope is of several types- "Application", "SOAPSession", "TransportSession", "Request". The default value (if you dont put any value) will be "Request" *class*: (Optional attribute) To specify the full qualified name of the service lifecycle implementation class. ServiceLifeCycle class is usefull when you want to do some tasks when the system start and when it shutdowns. *targetNamespace*: (Optional Attribute) Target name space of the service, and this value will be used when generating the wsdl , if you do not specify this value , then the value will be calculated from the package name of the service impl class *description*: This is an optional element if you want to display any description about the service via Axis2 web-admin module, then the description can be specified here. *transports* : The transports that the service is going to be exposed to. This is an optional element. If the transport element is not present then the service will be exposed in all the transports available in the system. The transport child element is there to specify the transport prefix (the name of the transport specified in axis2.xml). *parameters:* A services.xml can have any number of top level parameters and all the specified parameters will be transformed into service properties in the corresponding AxisService. There is a compulsory parameter in a services.xml called ServiceClass which specifies the java class which really does the job and the class will be loaded by the MessageReceiver. *operations :* If the service impl class is java, then all the public methods in that service will be exposed and if the user wants to override it then he has to add the "operation" tag and override it. In the case of non-Java or if you do not have a service class, then all the operations the user wants to expose by the service has to be indicated in the services.xml and the correct way of specifying is as follows: The only compulsory attribute here is "name", which represents the operation name that is going to be exposed. Any operation can contain module references as well as any number of parameters. The most interesting thing is that one can register custom message receivers per operation, then the registered message receiver will be the message receiver for the corresponding operation. If one does not specify the message receiver, then the default message receiver will do the job. Regards, ** *Yamini Hemanth * <[EMAIL PROTECTED]> -- *From:* Vasil Benov [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 27, 2006 2:41 PM *To:* axis-user@ws.apache.org *Subject:* services.xml Hello, is there a thorough description of the file. Best regards -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: 1) http://www.student-zw.fh-kl.de/~vabe0001/misc/key.asc<http://www.student-zw.fh-kl.de/%7Evabe0001/misc/key.asc> 2) http://sks.keyserver.penguin.de/ -- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: 1) http://www.student-zw.fh-kl.de/~vabe0001/misc/key.asc 2) http://sks.keyserver.penguin.de/
services.xml
Hello, is there a thorough description of the file. Best regards -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: 1) http://www.student-zw.fh-kl.de/~vabe0001/misc/key.asc 2) http://sks.keyserver.penguin.de/
