file path separators
Right now I am working in Windows but the primary reason for using Axis2/C is to go cross platform sometime next year. Apache C Modules have done a very nice job of making sure that all file file IO functions that take a path are neutral when it comes to file path separators. Well not actually neutral exactly, but expect everything to be forward slashes. Question: Do the functions in axutil_file_handler.h which take a file path work on Windows given Apache style paths (forward slash)? Sam
Re: WSDL2C exception
thanks alot Dimuthu On Sun, Apr 5, 2009 at 6:18 PM, Dimuthu Gamage dimut...@gmail.com wrote: Hi Anil, You wsdl should have external wsdls or/and schemas that are imported or included. In that case you need to be online when running the tool. That is not a requirement of the tool. Thanks Dimuthu On Sun, Apr 5, 2009 at 10:06 AM, Anil anil.pund...@gmail.com wrote: I was trying to generate skelton and stub code from a wsdl file using WSDL2C.(axis2-1.4.1). It works fine when i am connected to internet. But throws exception when i am offline. Is it mandatory to be connected to internet when running WSDL2C? or am i missing any of the option in WSDL2C?? Please guide/coorect me if i am wrong. -- Regards, -Anil -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org -- Cheers, -Anil
WS-Policy support
Hi All, I am working on using axis2/c to built a web service client. I have a few questions regarding WS-policy support in axis2/c. From the manual in axis2/c web site, it seems that the WS-policy support is built in to the axis2/c. I would like to know the following: (1) Are there any documents regarding how to use WS-policy in axis2/c? (2) Are there any examples regarding how to use WS-policy in axis2/c? (3) I have a customer presenting me with a WSDL that contains some policy definitions and then referenced in operation/binding definitions, suppose I can parse the WSDL and extract all the policy information, at runtime, how do I use axis2/c to set the related policy in a operation/binding when I create a web service client (using axis2/c)? Any APIs? The afore mentioned WSDL (shortened to contain only related info) is pasted at the end of the message : Thanks much in advance! Vivian === wsdl:definitions wsp:UsingPolicy wsdl:required=true/ wsp:Policywsu:Id=BN_BN_BatchByIDQueryResponse_Binding wsp:ExactlyOne... /wsp:ExactlyOne /wsp:Policy wsp:Policywsu:Id=IF_IF_BatchByIDQueryResponse_In /wsdl:definitions xyzAdmin:CentralAdministration xmlns:xyzAdmin=http://www.xyz.com/webas/1000/soap/features101/wsp:Optional=true/ /wsp:Policy - wsp:Policywsu:Id=OP_IF_OP_BatchByIDQueryResponse_In xyzcomhnd:enableCommitxmlns:xyzcomhnd=http://www.xyz.com/NW05/soap/features/commit/;false/xyzcomhnd:enableCommit xyzblock:enableBlockingxmlns:xyzblock=http://www.xyz.com/NW05/soap/features/blocking/;true/xyzblock:enableBlocking /wsp:Policy wsdl:types . /wsdl:types ... wsdl:portTypename=BatchByIDQueryResponse_In wsp:Policy wsp:PolicyReference URI=#IF_IF_BatchByIDQueryResponse_In/ /wsp:Policy wsdl:operationname=BatchByIDQueryResponse_In wsp:Policy wsp:PolicyReference URI=#OP_IF_OP_BatchByIDQueryResponse_In/ /wsp:Policy wsdl:input message=tns:BatchByIDQuery_sync/ wsdl:output message=tns:BatchByIDResponse_sync/ wsdl:fault name=StandardMessageFaultmessage=tns:StandardMessageFault/ /wsdl:operation /wsdl:portType wsdl:bindingname=BatchByIDQueryResponse_Bindingtype=tns:BatchByIDQueryResponse_In wsp:Policy wsp:PolicyReference URI=#BN_BN_BatchByIDQueryResponse_Binding/ /wsp:Policy soap:binding transport=http://schemas.xmlsoap.org/soap/httpstyle=document/ wsdl:operationname=BatchByIDQueryResponse_In soap:operation soapAction=style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output wsdl:faultname=StandardMessageFault soap:fault name=StandardMessageFaultuse=literal/ /wsdl:fault /wsdl:operation /wsdl:binding ..
Re: Application scope parameters
Yes, as I have mentioned in a previous mail you can put the info into conf_ctx and retrieve it from the service. Supun On Mon, Apr 6, 2009 at 8:37 AM, Sam Carleton scarle...@gmail.com wrote: On Sun, Apr 5, 2009 at 11:15 PM, Supun Kamburugamuva supu...@gmail.com wrote: On Mon, Apr 6, 2009 at 2:23 AM, Sam Carleton scarle...@miltonstreet.com wrote: Question: From within the services init function, is there any way to get a parameter element from axis2.xml or services.xml? It is not possible to access these parameters from init function. You can access the parameters when the first request comes to the service using the msg_ctx. So the init function call is really only designed to allocate and setup the svc_skeleton, nothing else, correct? For me to use Axis2/C, I really MUST get this setup done during the initialization. My server is Apache and I have already added the mod_axis2 code to another custom Apache module. The setup that needs to be done is already happening in the Apache module. Question: Is there any way to pass the vital information from the Apache module (axis2_module_init or axis2_handler) into the service? Sam -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
Re: resolving relative file paths (mod_axis2)
These links might help you, http://wsaxc.blogspot.com/2008/11/axis2c-handler-parameters.html http://wsaxc.blogspot.com/2008/11/axis2c-modules-and-persistent.html Supun On Mon, Apr 6, 2009 at 8:50 AM, Sam Carleton scarle...@gmail.com wrote: On Sun, Apr 5, 2009 at 11:27 PM, Supun Kamburugamuva supu...@gmail.com wrote: I'm not that clear about your question. Generally if the info is available for mod_axis2 at start-up you can put it to conf_ctx and retrieve it when the service is invoked. Supun, I think that is EXACTLY what I need. Is there any chance there might be some additional details on how exactly to put info into the conf_ctx and how to get the info out in the service? Sam -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
RE: RV: problems with Axis2
Hi Andreas! The complete stacktrace (as attach file) Thanks for your answer Joan -Mensaje original- De: Andreas Veithen [mailto:andreas.veit...@gmail.com] Enviado el: sábado, 04 de abril de 2009 15:06 Para: axis-user@ws.apache.org Asunto: Re: RV: problems with Axis2 Can you post the complete stacktrace of the UnsupportedDataTypeException? Andreas On Fri, Apr 3, 2009 at 15:32, Alcaraz Galofre, Joan Eugeni joaneugeni.alca...@t-systems.es wrote: Sr Developers of Axis2: I have a problem with Axis2 after a couple of days working without success I develop a axis2 webservice client embeded into a web application. The objective is download a binary file using MTOM technology The webservice client generate the following exception Caused by: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type text/xml; charset=UTF-8 at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:851 ) The code of the web service client is like this: EndpointReference targetEPR = new EndpointReference(URLConnexion); Options options = new Options(); options.setTo(targetEPR); options.setAction(urn:+functionName); options.setProperty(Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE); //configure MTOM at client side options.setTransportInfo(Constants.TRANSPORT_HTTP,Constants.TRANSPORT_ HTTP, false); //optimize MTOM at client side options.setSoapVersionURI(SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI) ; options.setProperty(Constants.Configuration.MIME_BOUNDARY, Axis2_MIME_Boundary); //force Axis2 MIME head options.setProperty(HTTPConstants.CHUNKED,Constants.VALUE_TRUE); options.setTimeOutInMilliSeconds(1); //delay a maximum of 10 seconds ServiceClient sender = new ServiceClient(); sender.setOptions(options); OperationClient mepClient = sender.createClient(ServiceClient.ANON_OUT_IN_OP); //use the OperationClient method MessageContext mc = new MessageContext(); SOAPEnvelope env = createEnvelope(XML,functionName); mc.setEnvelope(env); mepClient.addMessageContext(mc); mepClient.execute(true); == GENERATE THE EXCEPTION AT THIS POINT What's it happend? Have anyone any idea? I work with axis2 1.3.jar for MIME support I use activation.jar (1.1v) and mail.jar (1.4v). Both (client and server) uses the same version of activation.jar and mail.jar Compiled with WSAD 5.1.1 (WebSphere v5 JRE) The web application is deployed into a WAS 6.1 Both SO are Windows 2000 SP4 I hope your answers and thanks in advance! Sincerely Joan Alcaraz PD: sorry my poor english This e-mail and any attachments may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited. This e-mail and any attachments may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited.[3/04/09 14:03:26:600 CEST] 0030 SystemErr R org.apache.axiom.om.OMException: Error while writing to the OutputStream. [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.axiom.om.impl.MIMEOutputUtils.complete(MIMEOutputUtils.java:75) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:126) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:422) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:68) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:84) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) [3/04/09 14:03:26:600 CEST] 0030 SystemErr Rat org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:520) [3/04/09
upgrading axis.jar version 1.0 from JDK 4 to 6
Hello, I am emailing about the file axis.jar version 1.0 I wanted to know if this jar will be supported in JDK 6 for the version mentioned (or are there any known bugs). Does it compile under JDK 6? If I pre-compile it in JDK 4, will it run in JDK 6? If the version isn't supported, is there a new one which is supported? Are there any security patches issues in this version? Thanks, Roi Oron Cisco
Extracting attribute values from SAML token in rampart sample 05
Hi all, I was wondering if it's possible to extract the values inside a SAML token. I looked at sample 05 and wanted to list out the values of the attribute statement, I tried this in the password call back handler Element el = pwcb.getCustomToken(); But just got null. What I'm trying to achieve is not just validate that the attributes signed by the sts but also see what attributes the client can give the possessing. How can this be done?? cheers, håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
RE: Extracting attribute values from SAML token in rampart sample 05
//Construct RahasData from MessageContext http://ws.apache.org/rampart/apidocs/org/apache/rahas/RahasData.html //get a default handle SAMLCallbackHandler handler = config.getCallbackHander(); //then construct SAML AttributeCallback to retrieve the RahasData contents http://ws.apache.org/rampart/apidocs/org/apache/rahas/impl/util/SAMLAttributeCallback.html SAMLAttributeCallback cb = new SAMLAttributeCallback(data); SAMLCallbackHandler handler = config.getCallbackHander(); handler.handle(cb); attrs = cb.getAttributes(); en annen svare ? Martin __ Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 6 Apr 2009 17:06:59 +0200 Subject: Extracting attribute values from SAML token in rampart sample 05 From: hakon.sageh...@bccs.uib.no To: axis-user@ws.apache.org; rampart-...@ws.apache.org Hi all, I was wondering if it's possible to extract the values inside a SAML token. I looked at sample 05 and wanted to list out the values of the attribute statement, I tried this in the password call back handler Element el = pwcb.getCustomToken(); But just got null. What I'm trying to achieve is not just validate that the attributes signed by the sts but also see what attributes the client can give the possessing. How can this be done?? cheers, håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) _ Rediscover Hotmail®: Now available on your iPhone or BlackBerry http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Mobile1_042009
RE: weblogic 10g axis - Admin servlet failed to preload on startup
Hi! The stack trace that I get is below. I have cropped a few lines - weblogic.application.ModuleException: [HTTP:101216]Servlet: AdminServlet failed to preload on startup in Web application: SSAxis. java.lang.NullPointerException at org.apache.axis.transport.http.AxisServletBase.getEngineEnvironment(Axis ServletBase.java:273) at org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase .java:172) at org.apache.axis.transport.http.AxisServletBase.getOption(AxisServletBase .java:396) at org.apache.axis.transport.http.AxisServletBase.init(AxisServletBase.java :112) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubS ecurityHelper.java:282) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu bject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityH elper.java:63) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLife cycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.init(StubLifecycleHelper .java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl .java:507) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServ letContext.java:1853) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(Web AppServletContext.java:1830) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe rvletContext.java:1750) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContex t.java:2909) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:9 73) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD river.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv er.java:26) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr iver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModule Driver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleLis tenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD river.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv er.java:26) From: Sirohi, Vivek Sent: Monday, April 06, 2009 10:37 AM To: 'axis-user@ws.apache.org' Subject: weblogic 10g axis - Admin servlet failed to preload on startup Hi All, I have written a web service using axis and have successfully deployed it to weblogic 10g. However I have had to use the prefer-web-inf-classes setting in weblogic.xml to get it to run otherwise it gives me the AdminServlet failed to preload on startup in Web application: error. I don't want to use this setting so was wondering what could be the possible causes of this error and any solutions that you may have to solve this problem. Regards, ViV
weblogic 10g axis - Admin servlet failed to preload on startup
Hi All, I have written a web service using axis and have successfully deployed it to weblogic 10g. However I have had to use the prefer-web-inf-classes setting in weblogic.xml to get it to run otherwise it gives me the AdminServlet failed to preload on startup in Web application: error. I don't want to use this setting so was wondering what could be the possible causes of this error and any solutions that you may have to solve this problem. Regards, ViV Regards, Vivek Sirohi
RE: weblogic 10g axis - Admin servlet failed to preload on startup
which axis version are you using ? Martin __ Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Subject: RE: weblogic 10g axis - Admin servlet failed to preload on startup Date: Mon, 6 Apr 2009 11:01:31 -0700 From: vs3...@att.com To: axis-user@ws.apache.org Hi! The stack trace that I get is below. I have cropped a few lines – weblogic.application.ModuleException: [HTTP:101216]Servlet: AdminServlet failed to preload on startup in Web application: SSAxis. java.lang.NullPointerException at org.apache.axis.transport.http.AxisServletBase.getEngineEnvironment(AxisServletBase.java:273) at org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase.java:172) at org.apache.axis.transport.http.AxisServletBase.getOption(AxisServletBase.java:396) at org.apache.axis.transport.http.AxisServletBase.init(AxisServletBase.java:112) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.init(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1853) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1830) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1750) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) From: Sirohi, Vivek Sent: Monday, April 06, 2009 10:37 AM To: 'axis-user@ws.apache.org' Subject: weblogic 10g axis - Admin servlet failed to preload on startup Hi All, I have written a web service using axis and have successfully deployed it to weblogic 10g. However I have had to use the prefer-web-inf-classes setting in weblogic.xml to get it to run otherwise it gives me the AdminServlet failed to preload on startup in Web application: error. I don't want to use this setting so was wondering what could be the possible causes of this error and any solutions that you may have to solve this problem. Regards, ViV _ Rediscover Hotmail®: Get quick friend updates right in your inbox. http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Updates1_042009
RE: weblogic 10g axis - Admin servlet failed to preload on startup
Hi, I am using Axis 1.4. Thanks for looking into this. Vivek From: Martin Gainty [mailto:mgai...@hotmail.com] Sent: Monday, April 06, 2009 1:04 PM To: axis-user@ws.apache.org Subject: RE: weblogic 10g axis - Admin servlet failed to preload on startup which axis version are you using ? Martin __ Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Subject: RE: weblogic 10g axis - Admin servlet failed to preload on startup Date: Mon, 6 Apr 2009 11:01:31 -0700 From: vs3...@att.com To: axis-user@ws.apache.org Hi! The stack trace that I get is below. I have cropped a few lines - weblogic.application.ModuleException: [HTTP:101216]Servlet: AdminServlet failed to preload on startup in Web application: SSAxis. java.lang.NullPointerException at org.apache.axis.transport.http.AxisServletBase.getEngineEnvironment(AxisServletBase.java:273) at org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase.java:172) at org.apache.axis.transport.http.AxisServletBase.getOption(AxisServletBase.java:396) at org.apache.axis.transport.http.AxisServletBase.init(AxisServletBase.java:112) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.init(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1853) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1830) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1750) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) From: Sirohi, Vivek Sent: Monday, April 06, 2009 10:37 AM To: 'axis-user@ws.apache.org' Subject: weblogic 10g axis - Admin servlet failed to preload on startup Hi All, I have written a web service using axis and have successfully deployed it to weblogic 10g. However I have had to use the prefer-web-inf-classes setting in weblogic.xml to get it to run otherwise it gives me the AdminServlet failed to preload on startup in Web application: error. I don't want to use this setting so was wondering what could be the possible causes of this error and any solutions that
webservice client
I am faily new to Axis. I have a WSDL and I generated client stubs and proxies using WSDL2Java. But my WSDL needs uid and pwd. Classes generated are: CustomerWSLocator CustomerWS_PortType.java CustomerWS.java WebServices_CustomerWS_BinderStub.java Which classes should I used to add my uid/pwd?
Re: WSDL2JAVA created uncompilable Stub
Hi Jacques, I am new to axis. I have to develop an web service I have followed the steps you mentioned and created a wsdl, skeleton and stubs. Could you pls tell me what changes i need to make it in skeleton and stub files Also pls tell me how to deploy this web service. Thanks, Pricilla. On Fri, Apr 3, 2009 at 11:43 AM, Jacques46 jacques.pou...@gmail.com wrote: Just putting in my 2 cents, because a week ago I knew nothing about Axis, and I had to overcome some of the hurdles that have been encountered by other posters in the past... I hope I can avoid other people the same wasted time that I experienced... My environment is Eclipse 3.2.2, with the Codegen Wizard plugin. I have used the wizard in both directions (wsdl2java and java2wsdl) in versions 1.3 and 1.4.1 of Axis2. About the wizard : when you go to the Axis website, you can download the Codegen Wizard plugin for any version of Axis. What's misleading is that when you unzip each version (1.3 and 1.4.1), they both are contained in the Axis2_Codegen_Wizard_1.3.0 directory. Having successfully created my stubs with version 1.3 of the wizard and Axis libraries, I now wanted to compile them with Axis2 1.4.1. My first reaction when I downloaded the 1.4.1 wizard was to say hmmm... seems the wizard hasn't changed since version 1.3, because it's in the same directory name. WRONG ! Upon further inspection, I clearly saw that the libraries in the /lib directory of the plugin were indeed different. So, here are the steps I would recommend for a successful compile : - If you're in Eclipse, EXIT ! - If you have not done so yet, download the Axis2 standard distribution binary for the version you want, unzip it to some directory, and then create an environment variable AXIS2_HOME that points to that directory. - Download the Codegen Wizard for the Axis version you're shooting for (the same version as the standard distribution). Unzip it into your Eclipse's plugins directory. Note that if you had a previous version of the plugin there, you're gonna have to overwrite it with this new one if they both have the same name. - Copy the geronimo-stax-api_1.0_spec-1.0.1.jar and backport-util-concurrent-3.1.jar from the AXIS2_HOME/lib directory to the Wizard's /lib directory. - Edit the plugin.xml file of the Wizard. You'll see in there a bunch of library nodes, add 2 nodes pointing to the jars you just copied. - Start Eclipse - Create a new project - In that project, import the jars from the AXIS2_HOME/lib directory (import them in a new folder you'll call lib) - Refresh the project - Project properties : Add all the jars to the build path - Create some java class that will have the methods you want your web service to have. Save it. - Right-click on the project, New-, Other... - Select Axis2 Wizards - Axis2 Code Generator, Next. - Select Java2WSDL - Type the fully qualified class name, and then add the path for the class file. For example, if you class is com.xyz.TheClass, and your java source is in SomeDir/src/com/xyz/TheClass.java, and the corresponding class file is in SomeDir/bin/com/xyz/TheClass.class, then you'd enter SomeDir/bin. - Click Test Class Loading... If it doesn't work, review previous step. - Click Next, and you can change the options if you want, and then click next again. - Select to send the output to a project in the workspace, and browse to that project. Then give your wsdl a name, and click Finish. - Hopefully, all went well, and if you refresh your project, you'll see the WSDL. Now, if you want to create client and server code for this new WSDL: - Go in the codegen wizard again, this time select WSDL2Java, click Next. - Select the WSDL file you've just created. Next. - In Codegen Option, select Custom. Check Generate both... (last checkbox). Next. - Browse to the project location, and Click Finish. You should have the client and server code generated, along with a nice ant build file. The class you'll want to modify is ClassNameSkeleton.java for the server-side. For a client to use that service, you'd instantiate ClassNameStub.java. I really hope this helps someone in the future. It's been a frustrating week. Jacques. -- View this message in context: http://www.nabble.com/WSDL2JAVA-created-uncompilable-Stub-tp17775033p22872262.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: WSDL2JAVA created uncompilable Stub
On Tue, Apr 7, 2009 at 9:15 AM, pricilla p pricy...@gmail.com wrote: Hi Jacques, I am new to axis. I have to develop an web service I have followed the steps you mentioned and created a wsdl, skeleton and stubs. Could you pls tell me what changes i need to make it in skeleton and stub files Also pls tell me how to deploy this web service. you have to implement your business logic at the skelton. you need to create a .aar file to deploy it as an axis2 service. Please refer to user guide. thanks, Amila. Thanks, Pricilla. On Fri, Apr 3, 2009 at 11:43 AM, Jacques46 jacques.pou...@gmail.comwrote: Just putting in my 2 cents, because a week ago I knew nothing about Axis, and I had to overcome some of the hurdles that have been encountered by other posters in the past... I hope I can avoid other people the same wasted time that I experienced... My environment is Eclipse 3.2.2, with the Codegen Wizard plugin. I have used the wizard in both directions (wsdl2java and java2wsdl) in versions 1.3 and 1.4.1 of Axis2. About the wizard : when you go to the Axis website, you can download the Codegen Wizard plugin for any version of Axis. What's misleading is that when you unzip each version (1.3 and 1.4.1), they both are contained in the Axis2_Codegen_Wizard_1.3.0 directory. Having successfully created my stubs with version 1.3 of the wizard and Axis libraries, I now wanted to compile them with Axis2 1.4.1. My first reaction when I downloaded the 1.4.1 wizard was to say hmmm... seems the wizard hasn't changed since version 1.3, because it's in the same directory name. WRONG ! Upon further inspection, I clearly saw that the libraries in the /lib directory of the plugin were indeed different. So, here are the steps I would recommend for a successful compile : - If you're in Eclipse, EXIT ! - If you have not done so yet, download the Axis2 standard distribution binary for the version you want, unzip it to some directory, and then create an environment variable AXIS2_HOME that points to that directory. - Download the Codegen Wizard for the Axis version you're shooting for (the same version as the standard distribution). Unzip it into your Eclipse's plugins directory. Note that if you had a previous version of the plugin there, you're gonna have to overwrite it with this new one if they both have the same name. - Copy the geronimo-stax-api_1.0_spec-1.0.1.jar and backport-util-concurrent-3.1.jar from the AXIS2_HOME/lib directory to the Wizard's /lib directory. - Edit the plugin.xml file of the Wizard. You'll see in there a bunch of library nodes, add 2 nodes pointing to the jars you just copied. - Start Eclipse - Create a new project - In that project, import the jars from the AXIS2_HOME/lib directory (import them in a new folder you'll call lib) - Refresh the project - Project properties : Add all the jars to the build path - Create some java class that will have the methods you want your web service to have. Save it. - Right-click on the project, New-, Other... - Select Axis2 Wizards - Axis2 Code Generator, Next. - Select Java2WSDL - Type the fully qualified class name, and then add the path for the class file. For example, if you class is com.xyz.TheClass, and your java source is in SomeDir/src/com/xyz/TheClass.java, and the corresponding class file is in SomeDir/bin/com/xyz/TheClass.class, then you'd enter SomeDir/bin. - Click Test Class Loading... If it doesn't work, review previous step. - Click Next, and you can change the options if you want, and then click next again. - Select to send the output to a project in the workspace, and browse to that project. Then give your wsdl a name, and click Finish. - Hopefully, all went well, and if you refresh your project, you'll see the WSDL. Now, if you want to create client and server code for this new WSDL: - Go in the codegen wizard again, this time select WSDL2Java, click Next. - Select the WSDL file you've just created. Next. - In Codegen Option, select Custom. Check Generate both... (last checkbox). Next. - Browse to the project location, and Click Finish. You should have the client and server code generated, along with a nice ant build file. The class you'll want to modify is ClassNameSkeleton.java for the server-side. For a client to use that service, you'd instantiate ClassNameStub.java. I really hope this helps someone in the future. It's been a frustrating week. Jacques. -- View this message in context: http://www.nabble.com/WSDL2JAVA-created-uncompilable-Stub-tp17775033p22872262.html Sent from the Axis - User mailing list archive at Nabble.com. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
