Re: [vote] XBean donation
+1 On 2/14/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote: Just to tie this up so it won't be left hanging - since Dain has already started moving forward with the ip document in incubator and declared his intention to commit the code tomorrow ... My point was that this should have been presented before the vote on the dev list (So here's why I want to bring XBean to Geronimo and why it's appropriate for Geronimo), rather than it be assumed that everyone is familiar with whatever off-list or historical conversations have taken place around this. I'm not against this - I was the one trying to get Dain to bring it back to Geronimo last summer when he first took it to Codehaus - but I think that the motivations for bringing in code that is out of main scope of the project deserves some illumination. geir James Strachan wrote: On 1 Feb 2006, at 15:53, Geir Magnusson Jr wrote: I asked a while ago and I think my question was never answered - why bring XBean into Geronimo? ActiveMQ, Jetty, OpenEJB, ServiceMix are all using it as an optional lightweight kernel for efficient and concise configuration and deployment in Spring-ish ways. It is a very useful core piece of technology and quite a lot of us are pretty excited to work with it in Geronimo James --- http://radio.weblogs.com/0112098/ -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani
Re: [Vote] Installer: Default Web Container Selection
[ ] Make Jetty the default Web Container install selection [X] Make Tomcat the default web container install selection Thanks Srinath Erik Daughtrey wrote: The installer should make either Tomcat or Jetty the default selection. The operator can always override and select the other. Vote: [ ] Make Jetty the default Web Container install selection [X] Make Tomcat the default web container install selection Regards, Stefan Schmidt We may run out of time before the votes can be tallied. For that reason, I'm making the default Jetty unless someone can provide a good reason why it shouldn't be. FYI - it's been decided that installation of both web containers via the installer will not be allowed. Manual configuration of both is possible though.
Re: Vote - move to Axis 1.4 SNAPSHOTS for Geronimo in anticipation of 1.0 release
+1 On 11/29/05, Davanum Srinivas [EMAIL PROTECTED] wrote: +1 from me On 11/29/05, Matt Hogstrom [EMAIL PROTECTED] wrote: AXIS is in the throws of releasing their 1.4 version. This includes a set of defects that were identified by Kevan as containing memory leaks. I would like to move to the 1.4 SNAPSHOTs if there are no objections. I'm going to move my private build to it today and do some testing. Matt -- Davanum Srinivas : http://wso2.com/blogs/
Re: [VOTE] M4 release
+1 On 8/4/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: +1 Gianny David Blevins [EMAIL PROTECTED] wrote: The tests are still running on David J's machine and should finish sometime tomorrow. Since voting takes a day or so anyway, let's get started and do them in parallel. Vote: Let's Release these binaries when the tests successfully complete. (http://cvs.apache.org/dist/geronimo/unstable/1.0-M4) Here is my +1. -David
Re: VOTE: IBM web console donation
[+1] Add to geronimo/incubator/ibm-web-console; add full committers [+1] Add to geronimo/incubator/ibm-web-console; restricted committers [+1] Add to geronimo/trunk/applications/web-console; full committers Thanks Srinath
Re: Why are gbeans not serialized but the gbean attributes are?
Hi Hiram; I will try to give a possible reason .. Not all the attributes in the GBeans are serializable, e.g. ClassLoader, kernel attributes in a GBean are not serializable, and have a special meaning in the enviorment it runs. those so called magic attributes get the values from the enviorment .. so serializing them do not make sense. I belive this is a reason making attributes Serializable (only the persitant ones), but not the GBeans, Thanks Srinath On 5/21/05, Hiram Chirino [EMAIL PROTECTED] wrote: I've been trying to analyze the reason why gbean attributes HAVE to be serializable. The facts are that: 1. A gbean itself does not need to be serializable. 2. Only the gbean attributes are serialized. 3. The de-serialized attributes are injected at runtime to construct the gbean. My question is why does a gbean get different treatment than attribute? I've got a feeling it's this way because gbeans are complex objects while most gbean attributes are simple types. But we are starting to see gbean objects that have complex attribute types. Why not also give gbean attributes the kind of runtime construction support that is given to gbeans? If this was done, then you don't force complex attributes to implement the Serializable interfaces. This could go a long way in helping solve some of the serialization issues that are being discussed in other threads. Regards, Hiram Chirino
Re: Change to AxisWebServiceContainer class in axis module?
Yap, Dims and David .. I will move the TestCase to the axis-builder Just a random thought .. the AxisWebServiceContainer not work with just any SOAPService and expect certain value to be set. Since the normal user do not see this details it is not critical. but it does not live up to the expecations one get whn he look at the method signatures. And when I tried with the most natural way to get a SOAPService (by parsing axis DD, deploy.wsdd) and run the AxisWebServiceContainer with that SOAP service it failed with NullPointers Any chance to fix it ? thanks Srinath On Wed, 16 Mar 2005 10:35:49 -0600, David Blevins [EMAIL PROTECTED] wrote: On Wed, Mar 16, 2005 at 08:14:47PM +0600, Srinath Perera wrote: Hi All; I wrote a TestCase for axis module and checked it in. But the soap invocation fails and send back a SOAPFault. This can be fixed by changing the line 63 of AxisWebServiceContainer org.apache.axis.MessageContext context = new org.apache.axis.MessageContext(null); to org.apache.axis.MessageContext context = new org.apache.axis.MessageContext(new AxisServer()); I do not do the change yet .. I remeber David Blevins mentioned he do the code without AxisEngine, not sure will it couse trouble thoughts? Hi Srinath, Thanks for the test case, looks like a great start. Your problem with the axis engine will go away if you use the AxisServiceBuilder to build the JavaServiceDesc instead of building it by hand in the test case. Since maven doesn't like circular dependencies, you'll probably have to move the test case to the axis-builder module to get that to compile. -David
Re: Change to AxisWebServiceContainer class in axis module?
I have some pending changes, so it may fail in the meantime. If it does, just hang tight till I can get things checked in. cool And when I tried with the most natural way to get a SOAPService (by parsing axis DD, deploy.wsdd) and run the AxisWebServiceContainer with that SOAP service it failed with NullPointers Any chance to fix it ? Well, we are purposely not letting Axis do some of the things it likes to do at runtime, like fill in extra data into your FooDesc objects. The WSDD file isn't as detailed as a jaxrpc mapping file and Axis will typically fill in the required detail at runtime using fairly intuitive algorithms. One example is that the WSDD file isn't able to say what method goes with an operation, so Axis will fill that in at runtime in a synchronized block the first time the service is invoked. After that, you still hit the synchronized block on every call, albeit just long enough to see that the initialized flag is true and return. We have all this detail up front and configure our JavaServiceDesc objects with more information than the WSDD stuff does and we very intentionally do not want Axis changing anything at runtime. We actually have code to stop Axis from doing some of it's usual guess work. cool, that mean we are working on the WSDL and mapping files direct. understood the problem and why you give that solution :) Thanks Srinath
[jira] Updated: (GERONIMO-269) webservice deployment with ews
[ http://issues.apache.org/jira/browse/GERONIMO-269?page=history ] Srinath Perera updated GERONIMO-269: Attachment: testcase.patch I add a test case for the axis module, but the test case need a aternation to AxisWebServiceContainer. I would like it to be reviwed before check in. webservice deployment with ews -- Key: GERONIMO-269 URL: http://issues.apache.org/jira/browse/GERONIMO-269 Project: Geronimo Type: New Feature Components: webservices Versions: 1.0-M1 Environment: all Reporter: Srinath Perera Attachments: 2004_11_02.txt, deploy-patch-re.txt, patch-fix.txt, patch.txt, patch.txt, patch_10_18_2004.txt, patch_27_08_2004.txt, samples.zip, testcase.patch this patch has code to deploy the webservice in the geronimo. there is a 1) WebServiceDeployerGbean and by calling deploy GBean method one can deploy a webservice. right now Axis service keep a seperate config-store but that can be changed when we decide on the final thing 2)the Deployer accept a webservice jar file and generate the required code using ews and deploy them. for time been the Axis GBean need to restart to get the new deploymnet. 3)the complete senario is shown in the WebServiceTest.java test. But to run this code need the JAVA_HOME/lib/tools.jar in the classpth. Since still can not get it in the classpath of maven I exclude the tests. If somebody using IDE and add the tools.jar in the classpath they should work fine :) 4) let me add some doc to the wiki about how this works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Change to AxisWebServiceContainer class in axis module?
Hi All; I wrote a TestCase for axis module and checked it in. But the soap invocation fails and send back a SOAPFault. This can be fixed by changing the line 63 of AxisWebServiceContainer org.apache.axis.MessageContext context = new org.apache.axis.MessageContext(null); to org.apache.axis.MessageContext context = new org.apache.axis.MessageContext(new AxisServer()); I do not do the change yet .. I remeber David Blevins mentioned he do the code without AxisEngine, not sure will it couse trouble thoughts? Thanks Srinath
Re: [Axis2][Revisit]How about making Message context executable?
Opps sorry this supose to go to axis dev! On Wed, 9 Mar 2005 21:03:41 +0600, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: Um, Srinath wrong list? ;-) Sanjiva. - Original Message - From: Srinath Perera [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 07, 2005 3:49 PM Subject: [Axis2][Revisit]How about making Message context executable? Hi All; I put this Q about making the MessageContext executable? I do not get a clear response .. May be it does not call for enough attention? But I feel this is bit too bigger change to do without enough community input .. So I feel we should hold it back for the F2F. But then pause the engine execution at some state should wait too thoughts? Srinath -- Forwarded message -- From: Ajith Ranabahu [EMAIL PROTECTED] Date: Fri, 4 Mar 2005 16:49:43 +0600 Subject: Re: [Axis2]How about making Message context executable? To: axis-dev@ws.apache.org, Srinath Perera [EMAIL PROTECTED] Hi there Srinath and all, This is probably a complete 180 degree turn from where we were heading (well not exactly a backward leap, but a drastic change in direction). The Message Context (MC) was pursued only as a property bag. Now we are trying to put executable actions there! So the role of the MC is changed now. I am not sure what this means to the structure of axis. I guess this needs to be thought out carefully. BTW if we are to do such a change this is the best time to tackle such a change. It will be impossible on later stage. On Thu, 3 Mar 2005 17:54:59 +0600, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; This is regarding the invoke, pausing and resuming the the invocation! To this point this is implemented with an ExecutionChain kept in the MessageContext ..calling the invoke on the MessageContext. But more I look at the code more I convinced the way the Glen has done it in EngineToy by putting the invoke(), resume() and pause() in the MessageContext would yield simpler and better code. Only catch is that it will make the MessageContext executable .. making it bit away from what we percive about it! thoughts? I have a bit more revolutionary proposal to add (hope I will not killed for saying this :D ) that is to get rid of the AxisEngine and put the send and receive in to the MessageContext. Making it our approach is to create the information bag, messageContext and ask it to send(), recive(), pause() .. I just want to know what people think about this? Thanks Srinath -- Ajith Ranabahu
[Axis2][Revisit]How about making Message context executable?
Hi All; I put this Q about making the MessageContext executable? I do not get a clear response .. May be it does not call for enough attention? But I feel this is bit too bigger change to do without enough community input .. So I feel we should hold it back for the F2F. But then pause the engine execution at some state should wait too thoughts? Srinath -- Forwarded message -- From: Ajith Ranabahu [EMAIL PROTECTED] Date: Fri, 4 Mar 2005 16:49:43 +0600 Subject: Re: [Axis2]How about making Message context executable? To: axis-dev@ws.apache.org, Srinath Perera [EMAIL PROTECTED] Hi there Srinath and all, This is probably a complete 180 degree turn from where we were heading (well not exactly a backward leap, but a drastic change in direction). The Message Context (MC) was pursued only as a property bag. Now we are trying to put executable actions there! So the role of the MC is changed now. I am not sure what this means to the structure of axis. I guess this needs to be thought out carefully. BTW if we are to do such a change this is the best time to tackle such a change. It will be impossible on later stage. On Thu, 3 Mar 2005 17:54:59 +0600, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; This is regarding the invoke, pausing and resuming the the invocation! To this point this is implemented with an ExecutionChain kept in the MessageContext ..calling the invoke on the MessageContext. But more I look at the code more I convinced the way the Glen has done it in EngineToy by putting the invoke(), resume() and pause() in the MessageContext would yield simpler and better code. Only catch is that it will make the MessageContext executable .. making it bit away from what we percive about it! thoughts? I have a bit more revolutionary proposal to add (hope I will not killed for saying this :D ) that is to get rid of the AxisEngine and put the send and receive in to the MessageContext. Making it our approach is to create the information bag, messageContext and ask it to send(), recive(), pause() .. I just want to know what people think about this? Thanks Srinath -- Ajith Ranabahu
Re: Axis GBean is deployable?
Sorry for the late answer, David Blevins say he will move some ews code in to the geronimo (I think that is the commit David's mention). Thanks David for clarification as I too trying to catch up the things Venket If you can lend a hand I will also try to help if I can to get around the things Thanks Srinath On Tue, 1 Mar 2005 12:00:29 -0800, David Jencks [EMAIL PROTECTED] wrote: On Mar 1, 2005, at 4:42 AM, Venkat Reddy wrote: David, Thanks for the valuable clarification ! I thought Geronimo will use Axis core for its SOAP stack and EWS code for JSR-921 support. When I looked at EWS it looked to me as if it did 2 things: 1) code generation of stubs 2) partial translation of jaxrpc-mapping file to wsdd xml file. As far as I can tell this mapping translation is completely ignoring the javabean property to xml element name mapping and the exception mapping. After examing the generated code it looked to me as if it would be easier to use a cglib proxy solution than to compile the generated code from EWS. One of the basic principles behind geronimo is that we compile all xml deployment descriptors into binary gbean configurations ready to be loaded and started at runtime. Following this principle, if we were to use wsdd, we would have to preprocess it during deployment into the actual objects that configure axis, and serialize those. AFAICT this would involve major surgery on the axis deployment system. I believe it is much simpler simply to process the j2ee deployment descriptors directly into the appropriate axis configuration objects, entirely skipping the wsdd file format. We've done this, and I don't see anything else in EWS that we can use. In particular we have some code that, using the XmlBeans schema type model, completely analyzes the jaxrpc mapping and attempts to set up the correct TypeDesc and exception mapping for axis. The exception mapping in particular is not quite complete for simple types. Lets consider our use of Axis. We are attempting to set up each service reference and web service (POJO or EJB) as an independent entity. I think this is more or less required by the independent lifecycles of j2ee components. For instance, a service reference gets compiled during deployment into a Service instance that is serialized to be bound into jndi. This serialized object includes all the axis configuration objects needed to run the service reference, and some setup code to build the non-serializable parts of axis. In particular it includes the type mapping info and the TypeDesc objects. The service-reference code is fairly far along and I think deals with pretty much everything required. I'm sure there are plenty of bugs but these are not yet too evident without much working on the server side. For the server-side, we have some code to dispatch from jetty to POJO and EJB web services, and some wiring in place to deploy this properly, but the actual code to configure axis is not yet committed: David Blevins is IIUC progressing rapidly and we may see something in the next few days. I believe he is following the same path of setting up an independent entity for each web service, configured for exactly the needs of that web service. POJO web services, being part of a web app, get deployed as a gbean similar to the servlet gbean. For jetty, the servlet gbean is JettyServletHolder, and we have a JettyAxisPOJOWebService gbean subclass that is (or, more accurately, will be) specialized to hold the axis ws stack and the actual web service object. Deployment of a POJO ws proceeds from the web app deployer (JettyModuleBuilder) which recognizes that a servlet is not a servlet but a POJO ws, copies a template of this JettyAxisPOJOWebService gbean, and hands the resulting GBeanData to the AxisBuilder together with the relevant info from the webservices.xml deployment descriptor. AxisBuilder is expected to configure this GBeanData with whatever is necessary to construct the fully functional axis stack when the gbean is started. EJB web services are not part of a web app. Therefore we have an adapter, JettyWebServiceHandler, that plugs into jetty and forwards calls to the web service to the EJB container. To jetty, this looks like a web app, but the important point is that it gets only calls to the specific ejb. Currently the xfire implementation is hooked up to use this, although the architecture there with a ws gbean separate from the ejb container gbean is not compatible with the JACC security requirements. To meet the JACC requirements that the security be checked before the handler chain is entered, we think we will have to install the ws stack inside the EJBContainer, and use a partially separate interceptor chain for ws invocations from that for regular ejb invocations. In any case I anticipate deployment proceeding by the OpenejbModuleBuilder handing the partially configured EJBContainer
[ANN]AXIS2-M1 released
The Apache Axis2 Team is pleased to announce the first milestone release of Apache Axis2 and the release is available at http://ws.apache.org/axis2 Downloads: http://cvs.apache.org/dist/axis/v2.0-M1/axis2-M1-src.zip http://cvs.apache.org/dist/axis/v2.0-M1/axis2-M1-bin.zip Release Notes: http://cvs.apache.org/dist/axis/v2.0-M1/release-notes.html Overview of Apache Axis2 === Axis2 is an effort to re-design and totally re-implement both Axis/Java and (eventually) Axis/C++ on a new architecture. Evolving from the now standard handler chain model which Axis1 pioneered, Axis2 is developing a more flexible pipeline architecture which can yet be managed and packaged in a more organized manner. This new design acknowledges the maturing of the Web services space in terms of new protocols such as WS-ReliableMessaging, WS-Security and WS-Addressing that are built on top of the base SOAP system. At the time Axis1 was designed, while it was fully expected that other protocols such as WS-ReliableMessaging would be built on top of it, there was no proper extension architecture defined to enable clean composition of such layers. Thus, one of the key motivations for Axis2 is to provide a clean and simple environment for extensions like Apache Sandesha and Apache WSS4J to layer on top of the base SOAP system. Another driving force for Axis2 is to move away from RPC oriented Web services towards more document-oriented, message style asynchronous service interactions. The Axis2 project is centered on a new representation for SOAP messages called AXIOM (AXIs Object Model). AXIOM consists of two parts: a complete XML Infoset representation and a SOAP Infoset representation on top of that. The XML Infoset representation provides a JDOM-like simple API but is built on a deferred model via a StAX-based (Streaming API for XML) pull parsing API. A key feature of AXIOM is that it allows one to stop building the XML tree and just access the pull stream directly; thus enabling both maximum flexibility and maximum performance. This approach allows us to support multiple levels of abstraction for consuming and offering Web services: using plain AXIOM, using generated code and statically data-bound data types and so on. At the time of Axis1's design, RPC-style, synchronous, request-response interactions were the order of the day for Web services. Today service interactions are much more message-oriented and exploit many different message exchange patterns. The Axis2 engine architecture is careful to not build in any assumptions of request-response patterns to ensure that it can be used easily to support arbitrary message exchange patterns. --The Apache Axis2 Team
Re: Runtime and deployment time web services architecture -- please comment
On Sat, 5 Feb 2005 16:25:33 -0800, David Jencks [EMAIL PROTECTED] wrote: I've been talking with David Blevins a bit about web services runtime and deployment time architecture and am belatedly moving to the list. I'm mostly thinking about ejb ws right now. Goals: support both Jetty and Tomcat (and possibly a standalone non-servlet-container for OpenEJB standalone), and both Axis and XFire. or, more generally, support multiple web containers, multiple web service stacks, and multiple ejb containers. Minimize the number of gbeans that need to be created. Non goal at this time: support more than one of these at once in a running geronimo instance. E.g., not possible to have both axis and xfire feeding ws requests to the same ejb. - So, for ejb ws, we need interfaces between the web container and the web service stack, and between the web service stack and the ejb. yes there should be a some way to direct the Web Service call from the servlet to EJB, I was using the ContinerIndex to call EJBs (see org.apache.geronimo.axis.AxisGeronimoUtils), but there may be a better way to do it. For POJO ws, we need at least an interface between the web container and the web service stack: the ws stack might or might not need an interface to the pojo: I think both Axis and XFire provide this themselves. yes - web container -- ws stack interface: I implemented a first draft proposal, WebServiceInvoker, which is probably wrong in all details. It provides a name for the concept however. I think no deployment time support for this is needed except for supplying the object name of the web container (e.g. JettyContainer) to the gbean supplying this interface for the ejb. At runtime, this gbean related to the ejb will register the WebServiceInvoker with the web container, and the web container will do something to forward requests to this url to the WebServiceInvoker. This appears to be moderately easy to implement in jetty using HttpContext subclasses, and quite easy to implement in tomcat using a container level valve. This is different from my first draft implementation, which requires a gbean in the web container for each web service, and deploy time web container support. - ws stack -- ejb interface Assumptions: -- the ws stack involves configuring an object or stack for each ws ejb, rather than funneling all requests through a single object. -- each ejb only needs to be hooked up to one web service stack at a time (noted in non-goals) -- the ws stack works with invocation type objects rather than first splitting up into separate code for each method being called. This seems more or less implied by the handler architecture. The first of these means we can have the ejb builder delegate construction of the ws stack to a separate web service builder. This stack object could be placed either inside the ejb container or as a separate gbean. The second means that there will be only one of these stack objects per ejb container, so we can include the stack inside the ejb container. In the interests of minimizing gbean count I think this is a good idea. Now there is the question of the interface between the web service stack and the ejb interceptor stack. Assuming that the ws stack works with invocation type objects, we can most easily convert these directly into EjbInvocation objects and send them down the ejb interceptor stack, without converting them into method calls to the ServiceEndpointInterface and then back into ejbInvocations. My conclusion is that the ejb container should implement the WebServiceInvoker interface so the web server calls it directly, and the ws stack should be an object inside the ejb container that gets the WebServiceInvoker calls and eventually calls the interceptor stack directly. yes - ws stack -- pojo interfaces At least Axis currently provides a servlet that can call pojo web services. I haven't looked at it very hard yet. If we do not use the axis servlet, I think we could use a similar strategy for POJO web services as for ejbs. We can, for each web container, write a ServletHolder-like gbean that delegates to a configured ws stack, and gets the invocation object at the other end and feeds it to the POJO. Presumably we can use cglib here to avoid reflection. If the Axis Servlet is used, all the WS calls go through a one servlet, and it is bit tricky to enable the configurations that are defined for each WS via the web.xml file. there was a thread that talk about theis more or less on the list Subject of thread [Writing dummy Servlet to redirect HTTP/SOAP requests] - Builder support. For ejb ws, the web module builder doesn't have to do anything. The ejbs will register themselves with the container to receive requests at their url. The ejb builder needs call the ws builder to
Re: Runtime and deployment time web services architecture -- please comment
My picture for the EJB Ws are that the WS stack do the XML-java conversion of the invocation and then hand java representatons over to the EJB Continaer to do the invocation and return the result to WS stack. [I know in thoery the Invocation object should be added to the intercepter stack]. Then WS-stack will do the Java -XML conversion and send it back. I hope what I am saying fits here, I too belive that the SOAP/HTTP(XML)- java conversion should not be put inside EJB class as it is the WS-Stack's job Thanks Srinath On Mon, 7 Feb 2005 17:22:01 -0800, David Blevins [EMAIL PROTECTED] wrote: On Feb 7, 2005, at 4:15 PM, David Jencks wrote: From another reply David wrote: I should state more clearly what I mean by this. CMP/BMP EntityBeans or Stateful SessionBeans will not have a Web Service Stack, neither will Stateless SessionBeans that only have Local or Remote interfaces. In fact, in the case where people are just chatting from Servlets to EJB's through Local interfaces, we don't need any protocol stacks at all, e.g. no CORBA, no EJBd, no HTTP/SOAP. This is partly why it weirds me out to add protocol specific things into the GenericEJBContainer class. now that you put it that way I agree. I might change my mind at any time... but this seems like a very strong argument. If you think of anything neat to add/remove, I'm all ears. -David
Re: Writing dummy Servlet to redirect HTTP/SOAP requests
Hi All; To plan for how to continue I will look in to writing a GBean based EngineRgsitry as I explained and get geronimo webservices to work to calls coming to SimpleAxisServer (based on sockets). Once that is working let us talk finer details how the SimpleAxisServer can be replaced by the DummyServlet I wrote a EngineRegistry based on GBeans that works on the simple Axis Server. I will look more in to David Jencks comments on the thread and try to do it for the Servlet. code is at http://www.apache.org/~hemapani/projects/axis-geronimo-branch.zip. Shall I create a branch for the Axis module till it is stable, what should be the naming convention? Thanks Srinath On Wed, 15 Dec 2004 14:59:01 +0600, Srinath Perera [EMAIL PROTECTED] wrote: On Wed, 15 Dec 2004 00:37:55 -0800, David Jencks [EMAIL PROTECTED] wrote: On Dec 14, 2004, at 10:24 PM, Srinath Perera wrote: Hi David; I don't think exactly this will work. I have two related ideas that will work; 1. Supply the kernel name and axis gbean object name as init params for the servlet. The init method can then get the actual kernel using the kernel name Kernel kernel = Kernel.getKernel(kernelName); and get a proxy to the axis gbean using its object name (don't remember the code). This could be done with the current web deployment framework. there is a minus point as we need to user kernel to invoke the methods that we do not like to do unless absolutly necessary You can get a proxy implementing axis[GBean]. While calls do go through some CGLib machinery, they go through just as much with proposal (2). (1) can be implemented without writing a special builder, just generating web.xml. 2. I think an even better approach is to extend JettyServletHolder to include a reference to the AxisGBean and to construct the servlet instance with the reference. Since we would control the construction of the servlet, it could have a non-default constructor. This would require writing some web services deployment code that would process the web services dd and add gbeans to the context directly. that would be nice :) if I got the idea correct it is if Servlet has constructor with AxisGBean the kernel injected refernace to AxisGBean for us! hope that is not unfair requirment from the web container point of view we won't be deploying a normal servlet, but a servlet with a non-default constructor. This would depend on quite a few details of the jetty-geronimo integration. To plan for how to continue I will look in to writing a GBean based EngineRgsitry as I explained and get geronimo webservices to work to calls coming to SimpleAxisServer (based on sockets). Once that is working let us talk finer details how the SimpleAxisServer can be replaced by the DummyServlet (based on #1 or #2. I might be able to do #2 by myself) Thanks for the help :) Srinath
Re: Few words about GBeans
On Sat, 18 Dec 2004 21:22:40 +0600, Srinath Perera [EMAIL PROTECTED] wrote: I haven't yet read it, but at the glimpse the doc looks interesting. Absolutely must read for everybody. Could you publish it in Geronimo Wiki. Thanks Jacek :) , I will publish it wiki with in first fewdays of the next week It is on the WIKI @ http://wiki.apache.org/geronimo/GBeansArticle1 Cheers Srinath
Few words about GBeans
Hi All; I have been digging in to GBean stuff write up some of the things I come across. The doc is at http://www.apache.org/~hemapani/docs/gbeans.pdf If someone got a chance to read, comments are welcome :) . I gather the information from the code, mailing list quiries, articles ect. Cheers Srinath
[jira] Resolved: (GERONIMO-490) Axis creates config store in trunk root
[ http://nagoya.apache.org/jira/browse/GERONIMO-490?page=history ] Srinath Perera resolved GERONIMO-490: - Resolution: Fixed EWS and the axis-geronimo module is updated to not creating anyhting in the target directory. Please cross check Axis creates config store in trunk root --- Key: GERONIMO-490 URL: http://nagoya.apache.org/jira/browse/GERONIMO-490 Project: Apache Geronimo Type: Bug Components: webservices Reporter: Alan Cabrera Assignee: Srianth Perera Axis creates config store in trunk root, i.e. trunk/target. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: Writing dummy Servlet to redirect HTTP/SOAP requests
Hi David; I don't think exactly this will work. I have two related ideas that will work; 1. Supply the kernel name and axis gbean object name as init params for the servlet. The init method can then get the actual kernel using the kernel name Kernel kernel = Kernel.getKernel(kernelName); and get a proxy to the axis gbean using its object name (don't remember the code). This could be done with the current web deployment framework. there is a minus point as we need to user kernel to invoke the methods that we do not like to do unless absolutly necessary 2. I think an even better approach is to extend JettyServletHolder to include a reference to the AxisGBean and to construct the servlet instance with the reference. Since we would control the construction of the servlet, it could have a non-default constructor. This would require writing some web services deployment code that would process the web services dd and add gbeans to the context directly. that would be nice :) if I got the idea correct it is if Servlet has constructor with AxisGBean the kernel injected refernace to AxisGBean for us! hope that is not unfair requirment from the web container point of view Thanks Srinath
Re: Axis build question
Hi Hari;
EWS build.xml generation is first writen without the knowladge about
geronimo axis module and when it try to acomadate later and get the
build working things get messy (there is a problem of finding the
maven repository in all the machines)
I will have a look at the both build to improve the things and get
back .. there must be a way to make the things more simple!
Thanks
Srinath
On Tue, 14 Dec 2004 22:20:45 -0800, Hari Kodungallur
[EMAIL PROTECTED] wrote:
I have a build related question (in axis module) that could be related
to this JIRA entry.
The EWS code generation currently assumes that the directory structure
for axis looks like geronimo/modules/axis. Geronimo build runs into
problems if I either rename geronimo to, say, trunk (i.e.,
trunk/modules/axis), or if I do not start the build at the geronimo
level (say I have mywork/geronimo/... and I have another build file at
mywork level and I call geronimo build from mywork).
Actually the code generation is okay, but the test:test of axis fails
when it tries to build the generated files. (Because the generated
build.xml file does not have the correct class path to the geronimo-axis
classes)
The classpath for the generated build.xml in this case looks like
path id=classpath
pathelement location={basedir}/target/classes/
pathelement location={basedir}/target/test-classes/
pathelement
location={basedir}/modules/axis/target/samples/echo.jar/
fileset dir=${maven.repo.local}
(snip)
/fileset
/path
whereas the geronimo-axis classes are in
{basedir}/modules/axis/target/classes.
I am curious whether there is there any reason why the first pathelement
is dependent on the location of ws4j2ee.properties file? Can the Build
File Generation file just put the {basedir}/modules/axis/target/classes
irrespective of where the config file is found?
Thanks much!
-Hari
On Tue, 2004-12-14 at 20:13, Srinath Perera (JIRA) wrote:
[ http://nagoya.apache.org/jira/browse/GERONIMO-490?page=history ]
Srinath Perera resolved GERONIMO-490:
-
Resolution: Fixed
EWS and the axis-geronimo module is updated to not creating anyhting in the
target directory. Please cross check
Axis creates config store in trunk root
---
Key: GERONIMO-490
URL: http://nagoya.apache.org/jira/browse/GERONIMO-490
Project: Apache Geronimo
Type: Bug
Components: webservices
Reporter: Alan Cabrera
Assignee: Srianth Perera
Axis creates config store in trunk root, i.e. trunk/target.
Re: Writing dummy Servlet to redirect HTTP/SOAP requests
On Wed, 15 Dec 2004 00:37:55 -0800, David Jencks [EMAIL PROTECTED] wrote: On Dec 14, 2004, at 10:24 PM, Srinath Perera wrote: Hi David; I don't think exactly this will work. I have two related ideas that will work; 1. Supply the kernel name and axis gbean object name as init params for the servlet. The init method can then get the actual kernel using the kernel name Kernel kernel = Kernel.getKernel(kernelName); and get a proxy to the axis gbean using its object name (don't remember the code). This could be done with the current web deployment framework. there is a minus point as we need to user kernel to invoke the methods that we do not like to do unless absolutly necessary You can get a proxy implementing axis[GBean]. While calls do go through some CGLib machinery, they go through just as much with proposal (2). (1) can be implemented without writing a special builder, just generating web.xml. 2. I think an even better approach is to extend JettyServletHolder to include a reference to the AxisGBean and to construct the servlet instance with the reference. Since we would control the construction of the servlet, it could have a non-default constructor. This would require writing some web services deployment code that would process the web services dd and add gbeans to the context directly. that would be nice :) if I got the idea correct it is if Servlet has constructor with AxisGBean the kernel injected refernace to AxisGBean for us! hope that is not unfair requirment from the web container point of view we won't be deploying a normal servlet, but a servlet with a non-default constructor. This would depend on quite a few details of the jetty-geronimo integration. To plan for how to continue I will look in to writing a GBean based EngineRgsitry as I explained and get geronimo webservices to work to calls coming to SimpleAxisServer (based on sockets). Once that is working let us talk finer details how the SimpleAxisServer can be replaced by the DummyServlet (based on #1 or #2. I might be able to do #2 by myself) Thanks for the help :) Srinath
Re: How to start a plan from the Code
hi All;
follow up from the itest module for axis, I look in to the itest
modules and have finds some patterns. I have few questions and need to
verify what I see is correct!
Q1)How to run the itest from the maven build .. is there something
like m:itests ...
Q2) itests have itest and java dirs what does they mean ..please check
my hypothesis
java - have the application (e.g. web services )
itest - test cases
what happen when the modules runs
a) compile and create web services using the files in java dir and
package them to a module
b) itest:setup start the geronimo and axis and deployed the modules created
c) test cases in the itests run automatically
d) itest:shutdown shut down the server
Q3) What is the format I should be given in the module at
/geronimo-itests-axis-${pom.currentVersion}.jar
deploy:distribute
uri=deployer:geronimo:jmx:rmi://localhost/jndi/rmi:/JMXConnector
username=system
password=manager
module=${basedir}/target/geronimo-itests-axis-${pom.currentVersion}.jar
/
Thanks
Srinath
On Fri, 3 Dec 2004 07:40:27 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote:
Srinath,
Any progress on this?
Thanks,
dims
On Sat, 20 Nov 2004 09:25:43 +0600, Srinath Perera [EMAIL PROTECTED] wrote:
I think what you want to do is use the itest plugin together with the
geronimo maven deploy plugin. You will have to add a new module to do
this: I suggest itests/webservices. The good example of how to use
this is openejb itests. These tests will run only after assembly;
however if you are starting jetty and openejb, what you have is
definitely not a unit test but an integration test.
Thanks Daivd; yap it is more like integeration :), .
what I want is to start system plan , j2ee-server plan, (with jetty
and openejb) some axis configuration plan and then send SOAP calls.
(there is long way to go it seems.) will look at the plugin!
Thanks
Srinath
On Nov 19, 2004, at 12:45 AM, Srinath Perera wrote:
I am trying to bring up few Gbeans from plan; I am trying to use
following code.
ReadOnlyRepository repository = new ReadOnlyRepository(new
File(temp));
ServiceConfigBuilder scb = new
ServiceConfigBuilder(null,repository);
File plan = new File(plan1.xml);
ConfigurationDocument configurationDoc =
ConfigurationDocument.Factory.parse(plan.toURL());
File temp = new File(new);
ConfigurationType conf = configurationDoc.getConfiguration();
List confs = scb.buildConfiguration(conf,null,temp);
URI uri = new URI(conf.getConfigId());
-- Point A
kernel.startConfiguration(temp.toURI());
kernel.stopConfiguration(temp.toURI());
1) when I run the code the kernel not seem to know about the
configuration I created at point A, Is there something missing and any
way to improve this code?
2) Actually I need to get up J2EE continer, OpenEJB and Jetty
Contianers up using plans from the code. I think there are plans
created already (I think it is in assembly) what are the plans I
should load to get that three contianers up and in what order.
Thanks
Srinath
p.s. my plan
?xml version=1.0 encoding=UTF-8?
configuration
xmlns=http://geronimo.apache.org/xml/ns/deployment;
configId=test/plan1
!-- Use the default deployer --
gbean name=test:axis=gb1 class=GBean1
attribute name=attribute1Hi/attribute
attribute name=attribute2
type=java.lang.Stringgeronimo.server:
j2eeType=J2EEServer,name=geronimo/attribute
/gbean
/configuration
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: How to start a plan from the Code
I do not did anything concreate yet .. will have a try at the next week and get back Thanks Srinath On Fri, 3 Dec 2004 07:40:27 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote: Srinath, Any progress on this? Thanks, dims On Sat, 20 Nov 2004 09:25:43 +0600, Srinath Perera [EMAIL PROTECTED] wrote: I think what you want to do is use the itest plugin together with the geronimo maven deploy plugin. You will have to add a new module to do this: I suggest itests/webservices. The good example of how to use this is openejb itests. These tests will run only after assembly; however if you are starting jetty and openejb, what you have is definitely not a unit test but an integration test. Thanks Daivd; yap it is more like integeration :), . what I want is to start system plan , j2ee-server plan, (with jetty and openejb) some axis configuration plan and then send SOAP calls. (there is long way to go it seems.) will look at the plugin! Thanks Srinath On Nov 19, 2004, at 12:45 AM, Srinath Perera wrote: I am trying to bring up few Gbeans from plan; I am trying to use following code. ReadOnlyRepository repository = new ReadOnlyRepository(new File(temp)); ServiceConfigBuilder scb = new ServiceConfigBuilder(null,repository); File plan = new File(plan1.xml); ConfigurationDocument configurationDoc = ConfigurationDocument.Factory.parse(plan.toURL()); File temp = new File(new); ConfigurationType conf = configurationDoc.getConfiguration(); List confs = scb.buildConfiguration(conf,null,temp); URI uri = new URI(conf.getConfigId()); -- Point A kernel.startConfiguration(temp.toURI()); kernel.stopConfiguration(temp.toURI()); 1) when I run the code the kernel not seem to know about the configuration I created at point A, Is there something missing and any way to improve this code? 2) Actually I need to get up J2EE continer, OpenEJB and Jetty Contianers up using plans from the code. I think there are plans created already (I think it is in assembly) what are the plans I should load to get that three contianers up and in what order. Thanks Srinath p.s. my plan ?xml version=1.0 encoding=UTF-8? configuration xmlns=http://geronimo.apache.org/xml/ns/deployment; configId=test/plan1 !-- Use the default deployer -- gbean name=test:axis=gb1 class=GBean1 attribute name=attribute1Hi/attribute attribute name=attribute2 type=java.lang.Stringgeronimo.server: j2eeType=J2EEServer,name=geronimo/attribute /gbean /configuration -- Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Build failure in Axis module
seems the ews build fail for soem reason and the old ews jar is out of
sync .. Will look in to it now. shall I make the ews depend on axis
rc2?
On Mon, 29 Nov 2004 18:55:01 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote:
That was my nightly build script causing problemsplease try
maven under modules/axis now and let me know if you still have
problems. Sorry for the delay.
-- dims
On Mon, 29 Nov 2004 17:45:22 -0500, Davanum Srinivas [EMAIL PROTECTED]
wrote:
[17:40] dims folks: this is completely weird...i did not change
anything but running maven under modules\axis works fine (after i blow
up .maven/repository/axis and build ews)
[17:41] dims can someone verify this for me? (blow up
.maven/repository/axis and run maven under modules/axis)
-- dims
On Mon, 29 Nov 2004 09:41:14 -0800, Jeremy Boynes [EMAIL PROTECTED] wrote:
Is this an issue or just that EWS is out of sync?
java:compile:
[depend] Deleted 0 out of date files in 0 seconds
[echo] Compiling to
C:\apache\geronimo\trunk\modules\axis/target/classes
[javac] Compiling 10 source files to
C:\apache\geronimo\trunk\modules\axis\t
arget\classes
[javac]
C:\apache\geronimo\trunk\modules\axis\src\java\org\apache\geronimo\a
xis\GeronimoWsDeployContext.java:21: cannot find symbol
[javac] symbol : class Ws4J2eeDeployContextImpl
[javac] location: package org.apache.geronimo.ews.ws4j2ee.toWs.impl
[javac] import
org.apache.geronimo.ews.ws4j2ee.toWs.impl.Ws4J2eeDeployContex
tImpl;
[javac] ^
[javac]
C:\apache\geronimo\trunk\modules\axis\src\java\org\apache\geronimo\a
xis\GeronimoWsDeployContext.java:26: cannot find symbol
[javac] symbol: class Ws4J2eeDeployContextImpl
[javac] public class GeronimoWsDeployContext extends
Ws4J2eeDeployContextImp
l implements Ws4J2eeDeployContext {
[javac] ^
[javac]
C:\apache\geronimo\trunk\modules\axis\src\java\org\apache\geronimo\a
xis\GeronimoWsDeployContext.java:26:
org.apache.geronimo.axis.GeronimoWsDeployCo
ntext is not abstract and does not override abstract method
getModuleLocation()
in org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeDeployContext
[javac] public class GeronimoWsDeployContext extends
Ws4J2eeDeployContextImp
l implements Ws4J2eeDeployContext {
[javac]^
[javac]
C:\apache\geronimo\trunk\modules\axis\src\java\org\apache\geronimo\a
xis\GeronimoWsDeployContext.java:81: cannot find symbol
[javac] symbol : variable outputLocation
[javac] location: class
org.apache.geronimo.axis.GeronimoWsDeployContext
[javac] return outputLocation;
[javac]^
[javac] Note: * uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 4 errors
--
Davanum Srinivas - http://webservices.apache.org/~dims/
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Build failure in Axis module
I sync the axis jars versons in the geronimo axis module and the ews,
please cross check the does that fix the build
On Mon, 29 Nov 2004 16:56:39 -0800, Jeremy Boynes [EMAIL PROTECTED] wrote:
It now builds for me - thanks all.
--
Jeremy
Srinath Perera wrote:
seems the ews build fail for soem reason and the old ews jar is out of
sync .. Will look in to it now. shall I make the ews depend on axis
rc2?
On Mon, 29 Nov 2004 18:55:01 -0500, Davanum Srinivas [EMAIL PROTECTED]
wrote:
That was my nightly build script causing problemsplease try
maven under modules/axis now and let me know if you still have
problems. Sorry for the delay.
-- dims
On Mon, 29 Nov 2004 17:45:22 -0500, Davanum Srinivas [EMAIL PROTECTED]
wrote:
[17:40] dims folks: this is completely weird...i did not change
anything but running maven under modules\axis works fine (after i blow
up .maven/repository/axis and build ews)
[17:41] dims can someone verify this for me? (blow up
.maven/repository/axis and run maven under modules/axis)
-- dims
On Mon, 29 Nov 2004 09:41:14 -0800, Jeremy Boynes [EMAIL PROTECTED]
wrote:
Is this an issue or just that EWS is out of sync?
java:compile:
[depend] Deleted 0 out of date files in 0 seconds
[echo] Compiling to
C:\apache\geronimo\trunk\modules\axis/target/classes
[javac] Compiling 10 source files to
C:\apache\geronimo\trunk\modules\axis\t
arget\classes
[javac]
C:\apache\geronimo\trunk\modules\axis\src\java\org\apache\geronimo\a
xis\GeronimoWsDeployContext.java:21: cannot find symbol
[javac] symbol : class Ws4J2eeDeployContextImpl
[javac] location: package org.apache.geronimo.ews.ws4j2ee.toWs.impl
[javac] import
org.apache.geronimo.ews.ws4j2ee.toWs.impl.Ws4J2eeDeployContex
tImpl;
[javac] ^
[javac]
C:\apache\geronimo\trunk\modules\axis\src\java\org\apache\geronimo\a
xis\GeronimoWsDeployContext.java:26: cannot find symbol
[javac] symbol: class Ws4J2eeDeployContextImpl
[javac] public class GeronimoWsDeployContext extends
Ws4J2eeDeployContextImp
l implements Ws4J2eeDeployContext {
[javac] ^
[javac]
C:\apache\geronimo\trunk\modules\axis\src\java\org\apache\geronimo\a
xis\GeronimoWsDeployContext.java:26:
org.apache.geronimo.axis.GeronimoWsDeployCo
ntext is not abstract and does not override abstract method
getModuleLocation()
in org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeDeployContext
[javac] public class GeronimoWsDeployContext extends
Ws4J2eeDeployContextImp
l implements Ws4J2eeDeployContext {
[javac]^
[javac]
C:\apache\geronimo\trunk\modules\axis\src\java\org\apache\geronimo\a
xis\GeronimoWsDeployContext.java:81: cannot find symbol
[javac] symbol : variable outputLocation
[javac] location: class
org.apache.geronimo.axis.GeronimoWsDeployContext
[javac] return outputLocation;
[javac]^
[javac] Note: * uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 4 errors
--
Davanum Srinivas - http://webservices.apache.org/~dims/
--
Davanum Srinivas - http://webservices.apache.org/~dims/
How to make changes of EWS propergate to Geronimo
Hi All,Dims; I got a commit to do on EWS, that would break geronimo axis build for about (ews builds 4 times a day) MAX 6 hours. Is there any way I can go and rebuild build the ews jar once I check it in and fix geronimo. (other wise we are having checken and egg problem for 6Hours :) ) Thanks Srinath
Re: How to make changes of EWS propergate to Geronimo
:) will commit both together .. worse case will be a hour Thanks Srinath On Sun, 28 Nov 2004 22:51:18 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote: runnig the cron every hour for a day or two :) -- dims On Mon, 29 Nov 2004 09:24:16 +0600, Srinath Perera [EMAIL PROTECTED] wrote: Hi All,Dims; I got a commit to do on EWS, that would break geronimo axis build for about (ews builds 4 times a day) MAX 6 hours. Is there any way I can go and rebuild build the ews jar once I check it in and fix geronimo. (other wise we are having checken and egg problem for 6Hours :) ) Thanks Srinath -- Davanum Srinivas - http://webservices.apache.org/~dims/
Re: net.sf.cglib.core.CodeGenerationException: what does usually mean
thanks everybody :) .. for the time been I will create my interface to match with configuration GBean and put a referance to it. Thanks Srinath On Tue, 23 Nov 2004 12:29:16 -0800, Dain Sundstrom [EMAIL PROTECTED] wrote: On Nov 23, 2004, at 10:48 AM, Aaron Mulder wrote: We might as well poll to see if anyone's using it, but it just seems dangerous to keep around in principle. I'd rather make people implement the interface and have some methods throw an UnsupportedOperationException instead of getting some kind of method doesn't exist error out of CGlib... It's not clear in that case that it's the callee's fault not the caller (or builder's) fault. I would never go as far as to require the target to implement the interface, as this creates all sorts of classloader issues, and it does not allow us to reference gbeans that implement no interfaces. I was suggesting that when we create a reference proxy we assure that the target exposes all of the necessary operations and attributes. -dain
Re: net.sf.cglib.core.CodeGenerationException: what does usually mean
Judging from the stack trace, you have a reference from one gbean to another and that reference is a java class type (not a interface). In geronimo, we always proxy references, which means that we treat the reference type as an interface. When a class type is used instead of an interface, it must have a default no-arg constructor because we generate a subclass of the reference type, and override all public methods, effectively making it an interface. Most of the time it is better to use an interface, but sometimes it is not possible due to an implementation. Thanks everbody :) for the pointers .. Is there any way to get more error messages? or may be should write a Gbean verifier to check for the conditions and give better error There is currently no way to get better (any :) error messages. A GBeanInfo verifier would be nice. let us keep it in the TODO .. will have a go at first opportunity Thanks Srinath
Re: net.sf.cglib.core.CodeGenerationException: what does usually mean
I am trying to add a raferance to a configuration object ... it does not have a default constructer ...what should be I do? (the case is ws like it keep a referancs to EJB that is behind the WS in the WS) Thanks Srinath On Mon, 22 Nov 2004 08:44:31 -0800, David Jencks [EMAIL PROTECTED] wrote: This one is fairly well explained by the message if you know what is expected. It's saying there is no default constructor. You are trying to construct a proxy to a gbean, using the gbean class itself as the class the proxy exposes. The class a proxy exposes must either be an interface or be a class with a default constructor. thanks david jencks On Nov 22, 2004, at 3:38 AM, Srinath Perera wrote: Hi All; Am getting this net.sf.cglib.core.CodeGenerationException: quite regulerly. I know that means something wrong with the GBean I am trying to start! but spending long times to find where is the error. Is there any way to get more error messages? or may be should write a Gbean verifier to check for the conditions and give better error messages! Thought? Srinath Caused by: net.sf.cglib.core.CodeGenerationException: java.lang.NoSuchMethodException-- org.apache.geronimo.kernel.config.Configuration$$EnhancerByCGLIB$$8021 e1df.init() at net.sf.cglib.core.ReflectUtils.getConstructor(ReflectUtils.java:281) at net.sf.cglib.core.ReflectUtils.newInstance(ReflectUtils.java:255) at net.sf.cglib.proxy.Enhancer.createUsingReflection(Enhancer.java:386) at net.sf.cglib.proxy.Enhancer.nextInstance(Enhancer.java:366) at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator. java:200) at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:330) at net.sf.cglib.proxy.Enhancer.create(Enhancer.java:265) at org.apache.geronimo.gbean.jmx.CGLibProxyFactory.create(CGLibProxyFactor y.java:53) at org.apache.geronimo.gbean.jmx.CGLibProxyFactory.create(CGLibProxyFactor y.java:47) at org.apache.geronimo.gbean.jmx.SingleProxy.init(SingleProxy.java:78) at org.apache.geronimo.gbean.jmx.GBeanMBeanReference.online(GBeanMBeanRefe rence.java:165) at org.apache.geronimo.gbean.jmx.GBeanMBean.preRegister(GBeanMBean.java: 534) at mx4j.server.interceptor.InvokerMBeanServerInterceptor.registration(Invo kerMBeanServerInterceptor.java:158) at mx4j.server.interceptor.DefaultMBeanServerInterceptor.registration(Defa ultMBeanServerInterceptor.java:111) at mx4j.server.interceptor.SecurityMBeanServerInterceptor.registration(Sec urityMBeanServerInterceptor.java:135) at mx4j.server.interceptor.DefaultMBeanServerInterceptor.registration(Defa ultMBeanServerInterceptor.java:111) at mx4j.server.interceptor.DefaultMBeanServerInterceptor.registration(Defa ultMBeanServerInterceptor.java:111) at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.regist ration(ContextClassLoaderMBeanServerInterceptor.java:161) at mx4j.server.MX4JMBeanServer.registerImpl(MX4JMBeanServer.java:801) at mx4j.server.MX4JMBeanServer.registerMBeanImpl(MX4JMBeanServer.java: 745) at mx4j.server.MX4JMBeanServer.registerMBean(MX4JMBeanServer.java:729) at org.apache.geronimo.kernel.Kernel.loadGBean(Kernel.java:355) ... 16 more Caused by: java.lang.NoSuchMethodException: org.apache.geronimo.kernel.config.Configuration$$EnhancerByCGLIB$$8021e 1df.init() at java.lang.Class.getConstructor0(Class.java:1937) at java.lang.Class.getConstructor(Class.java:1027) at net.sf.cglib.core.ReflectUtils.getConstructor(ReflectUtils.java:279) ... 37 more
[jira] Commented: (GERONIMO-490) Axis creates config store in trunk root
[ http://nagoya.apache.org/jira/browse/GERONIMO-490?page=comments#action_55782 ] Srinath Perera commented on GERONIMO-490: - I removed the folder creation done by the geronimo module; there is folder created by ews. (will check in once I verify the build). There is a folder generated by EWS, it is hack on my part.. I will clear the ews code in the weekend anyway and will address this isuue too. Axis creates config store in trunk root --- Key: GERONIMO-490 URL: http://nagoya.apache.org/jira/browse/GERONIMO-490 Project: Apache Geronimo Type: Bug Components: webservices Reporter: Alan Cabrera Assignee: Srianth Perera Axis creates config store in trunk root, i.e. trunk/target. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: How to start a plan from the Code
I think what you want to do is use the itest plugin together with the geronimo maven deploy plugin. You will have to add a new module to do this: I suggest itests/webservices. The good example of how to use this is openejb itests. These tests will run only after assembly; however if you are starting jetty and openejb, what you have is definitely not a unit test but an integration test. Thanks Daivd; yap it is more like integeration :), . what I want is to start system plan , j2ee-server plan, (with jetty and openejb) some axis configuration plan and then send SOAP calls. (there is long way to go it seems.) will look at the plugin! Thanks Srinath On Nov 19, 2004, at 12:45 AM, Srinath Perera wrote: I am trying to bring up few Gbeans from plan; I am trying to use following code. ReadOnlyRepository repository = new ReadOnlyRepository(new File(temp)); ServiceConfigBuilder scb = new ServiceConfigBuilder(null,repository); File plan = new File(plan1.xml); ConfigurationDocument configurationDoc = ConfigurationDocument.Factory.parse(plan.toURL()); File temp = new File(new); ConfigurationType conf = configurationDoc.getConfiguration(); List confs = scb.buildConfiguration(conf,null,temp); URI uri = new URI(conf.getConfigId()); -- Point A kernel.startConfiguration(temp.toURI()); kernel.stopConfiguration(temp.toURI()); 1) when I run the code the kernel not seem to know about the configuration I created at point A, Is there something missing and any way to improve this code? 2) Actually I need to get up J2EE continer, OpenEJB and Jetty Contianers up using plans from the code. I think there are plans created already (I think it is in assembly) what are the plans I should load to get that three contianers up and in what order. Thanks Srinath p.s. my plan ?xml version=1.0 encoding=UTF-8? configuration xmlns=http://geronimo.apache.org/xml/ns/deployment; configId=test/plan1 !-- Use the default deployer -- gbean name=test:axis=gb1 class=GBean1 attribute name=attribute1Hi/attribute attribute name=attribute2 type=java.lang.Stringgeronimo.server: j2eeType=J2EEServer,name=geronimo/attribute /gbean /configuration
Re: Can GBean get its configuration ClassLoader?
Just two quick question, 1) is there anyway one can add/register magic attributes form code or plan? (Just for INFO have not find for use case for it yet :) ) 2) Does GBean constrcters support injecting magic attributes only? Thanks Srinath On Thu, 18 Nov 2004 13:54:28 -0500 (EST), Aaron Mulder [EMAIL PROTECTED] wrote: Right, you helped me out with this in person a few days ago... Thanks. BTW, as a note for anyone else who's interested, GBeanMBean has a section at the bottom defining all the available magic attributes, and there are a lot of them. Dain pointed me to that, too. :) Aaron On Thu, 18 Nov 2004, Dain Sundstrom wrote: You simply declare an attribute of type ClassLoader, named classLoader, which is not persistent, and the framework will automatically inject the correct class loader. -dain -- Dain Sundstrom Chief Architect Gluecode Software 310.536.8355, ext. 26 On Nov 18, 2004, at 7:49 AM, Alan D. Cabrera wrote: -Original Message- From: Aaron Mulder [mailto:[EMAIL PROTECTED] Sent: Sunday, November 14, 2004 10:56 PM To: [EMAIL PROTECTED] Subject: Can GBean get its configuration ClassLoader? I wonder if there's a way for a GBean to get the ClassLoader for the configuration it's a part of -- in other words, the GBeanMBean.getClassLoader(), which includes the dependencies in the deployment plan, etc. I want the SQLSecurityRealm to be able to load a driver class. However, the SQLSecurityRealm itself was loaded in the Server configuration, and the JDBC driver is included as a dependency of the service deployment plan that declares the realm (but gets the SQLSecurityRealm class from its parent). So the SQLSecurityRealm can't see the driver classes in a child of it's own CL, and the ThreadContextClassLoader does not appear to be set to something useful when doStart is called on the GBean. I basically want to be able to call some static method to get the GBeanMBean for the current GBean implementation class, becasue then I could get the ClassLoader from it. But any other suggestions would be appreciated too. :) Why not declare the driver in the same plan as the SQLSecurityRealm and use the magic attribute classLoader? Regards, Alan
How to start a plan from the Code
I am trying to bring up few Gbeans from plan; I am trying to use following code. ReadOnlyRepository repository = new ReadOnlyRepository(new File(temp)); ServiceConfigBuilder scb = new ServiceConfigBuilder(null,repository); File plan = new File(plan1.xml); ConfigurationDocument configurationDoc = ConfigurationDocument.Factory.parse(plan.toURL()); File temp = new File(new); ConfigurationType conf = configurationDoc.getConfiguration(); List confs = scb.buildConfiguration(conf,null,temp); URI uri = new URI(conf.getConfigId()); -- Point A kernel.startConfiguration(temp.toURI()); kernel.stopConfiguration(temp.toURI()); 1) when I run the code the kernel not seem to know about the configuration I created at point A, Is there something missing and any way to improve this code? 2) Actually I need to get up J2EE continer, OpenEJB and Jetty Contianers up using plans from the code. I think there are plans created already (I think it is in assembly) what are the plans I should load to get that three contianers up and in what order. Thanks Srinath p.s. my plan ?xml version=1.0 encoding=UTF-8? configuration xmlns=http://geronimo.apache.org/xml/ns/deployment; configId=test/plan1 !-- Use the default deployer -- gbean name=test:axis=gb1 class=GBean1 attribute name=attribute1Hi/attribute attribute name=attribute2 type=java.lang.Stringgeronimo.server:j2eeType=J2EEServer,name=geronimo/attribute /gbean /configuration
[Axis modules]Should I commit in directly?
Hi All; I have few more excluded test cases up for the axis geronimo module! Should I check them in directly? BTW Is there way to verify I have not broke the build (something more than get it work in my machine!) How it usually done? Unfortunately am 12 hours behind US time and had I break something and when the complains come I am sleeping :(. cheers Srinath
Re: [Axis modules]Should I commit in directly?
Apache SVN seem to down (https://svn.apache.org/repos/asf/webservices/axis/) will try tommarow. Thanks Srinath On Tue, 16 Nov 2004 06:57:02 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote: +1 from. I'll cover your back :) thanks, dims On Mon, 15 Nov 2004 18:23:45 -0800, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; I have few more excluded test cases up for the axis geronimo module! Should I check them in directly? BTW Is there way to verify I have not broke the build (something more than get it work in my machine!) How it usually done? Unfortunately am 12 hours behind US time and had I break something and when the complains come I am sleeping :(. cheers Srinath -- Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Axis module review
Hi All; As I promise I have send a patch that fix the basic problems (hardcoded obj names ..ect ) in the Axis geronimo module and get the POJO case up and runing :). The patch is checked in; I am looking foward to the comments to know am I heading in the right direction. (I am busy with a exam and might not write codes for about two weeks on the module.) but I will be online and will happy if I can communicate in the mean time and understand the expectation of the EWS from the Geronimo point of view throughly. Thanks Srinath On Fri, 29 Oct 2004 15:17:14 +0600, Srinath Perera [EMAIL PROTECTED] wrote: Thanks everybody for the help :) :)... I think I got the big picure and hopfully should be able to get the Web Services working(which do not have EJB) behind them with out kernel. (There is a classloader issue when the EJB involved. I will try to get the code up removing all referances to kernel for POJO based WS.) I think over all the stuff over the weekend get back. My view about the Web Service is follows. There are two types of web services A) EJB based B) POJO based (servlet based one .. actually both has a servlet at the front so I dont see any sense in the name Servlet based : ) ) Web Service(HTTP one we concern about) is a Servlet that accepts SOAP over HTTP. Axis basically 1) get the request XML (SOAP) and converts them to the java objects 2) call the java class (POJO) or EJB that provide the implementation 3) get what ever the result and send them back as SOAP Only deferance between the EJB based and POJO based one is 1) Axis call a EJB instead of POJO at step #2 2) We have to make sure EJB is up when the webservice is called I think we should be able to do it with one WSBuilder. To be the steps is like follows 1. Geronimo Deployer find that the WAR/EAR is a ws module by looking at exsistance of the webservices.xml file in the module 2. The WSBuilder will create the confiuration and start it a. there should be a one GBean for each WS (we have to sort out how to do this) b. there should be a GBean for each EJB that referanced 3. when the confiuration started web services are avalible AxisGBean will keep track of the things and manage Axis Thanks Srinath On Fri, 29 Oct 2004 01:24:19 -0700, David Blevins [EMAIL PROTECTED] wrote: On Oct 28, 2004, at 11:52 PM, David Jencks wrote: My understanding of web services is that messages can be sent to either servlets or ejbs. (Apparently the servlets aren't Servlet implementations, but are usually wrapped in one). We need a gbean to be deployed for each such servlet and each such ejb. At the moment I think the best approach is to have a WSServletBuilder and a WSEJBBuilder that will actually build the gbeans. These, especially the WSEJBBuilder, would be similar to the openejb SessionConfigBuilder. Not just similar to but the same as--one session bean can have all of the following interfaces: - Local - Remote - ServiceEndpoint All of which can have transaction attributes associated with them. The ServiceEndpoint interface can even be invoked directly by EJBs, Servlets, or App Clients through declaring it as a service-ref and looking a it up through JNDI. Any invocations on the ServiceEndpoint interface go through JAX-RPC. Aside from JAX-RPC/ServiceEndpoint invocations, people can invoke the session bean through SOAP/WSDL over HTTP or HTTPS. In this case there is a mapping from WSDL to the ServiceEndpoint interface. All in all, this is not very different from the CORBA integration which also supports Java and non-Java clients through IIOP. In this case we use SOAP instead of IIOP, ServiceEndpoint/JAX-RPC instead of Remote/RMI-IIOP, WSDL-to-Java mapping instead of IDL-to-Java mapping, and Axis instead of an ORB. -David
Re: Axis module review
Thanks David :) I am listing what might helpful for you to review. (no hurry . even I like to have about two weeks time to get the real thing started). 1) new code has removed alll the hardcoded obj names. 2)At the test cases I do manually initaite the GBeans that would started by the plan in real case. 3) I think I got the basic of the plans. It is XML file explans the set of GBeans and there referances. . If I need GBean A referd by GBean B I should specify poth GBeans at the plan and put a referance in B to A's obj name. then the B will get a refrance to A. 4) WSConFig Builder .. (it does not implement the interface properly yet) build a GBean (s) for the WS, Store the GBeans in a confguration and write the configuration to a store. Using the URI return anyone can load the configuration. 5) I am not sure How the Axis GBean should find the deployed Configurations. I look at the referance patterns but do not get the real hang on it yet. Cheers Srinath On Wed, 3 Nov 2004 20:50:39 -0800, David Jencks [EMAIL PROTECTED] wrote: I am looking forward to looking at the new code very much and hope that I can quickly finish up what I've been working on so I can concentrate on the new code properly. Many thanks, david jencks On Nov 3, 2004, at 8:39 PM, Srinath Perera wrote: Hi All; As I promise I have send a patch that fix the basic problems (hardcoded obj names ..ect ) in the Axis geronimo module and get the POJO case up and runing :). The patch is checked in; I am looking foward to the comments to know am I heading in the right direction. (I am busy with a exam and might not write codes for about two weeks on the module.) but I will be online and will happy if I can communicate in the mean time and understand the expectation of the EWS from the Geronimo point of view throughly. Thanks Srinath On Fri, 29 Oct 2004 15:17:14 +0600, Srinath Perera [EMAIL PROTECTED] wrote: Thanks everybody for the help :) :)... I think I got the big picure and hopfully should be able to get the Web Services working(which do not have EJB) behind them with out kernel. (There is a classloader issue when the EJB involved. I will try to get the code up removing all referances to kernel for POJO based WS.) I think over all the stuff over the weekend get back. My view about the Web Service is follows. There are two types of web services A) EJB based B) POJO based (servlet based one .. actually both has a servlet at the front so I dont see any sense in the name Servlet based : ) ) Web Service(HTTP one we concern about) is a Servlet that accepts SOAP over HTTP. Axis basically 1) get the request XML (SOAP) and converts them to the java objects 2) call the java class (POJO) or EJB that provide the implementation 3) get what ever the result and send them back as SOAP Only deferance between the EJB based and POJO based one is 1) Axis call a EJB instead of POJO at step #2 2) We have to make sure EJB is up when the webservice is called I think we should be able to do it with one WSBuilder. To be the steps is like follows 1. Geronimo Deployer find that the WAR/EAR is a ws module by looking at exsistance of the webservices.xml file in the module 2. The WSBuilder will create the confiuration and start it a. there should be a one GBean for each WS (we have to sort out how to do this) b. there should be a GBean for each EJB that referanced 3. when the confiuration started web services are avalible AxisGBean will keep track of the things and manage Axis Thanks Srinath On Fri, 29 Oct 2004 01:24:19 -0700, David Blevins [EMAIL PROTECTED] wrote: On Oct 28, 2004, at 11:52 PM, David Jencks wrote: My understanding of web services is that messages can be sent to either servlets or ejbs. (Apparently the servlets aren't Servlet implementations, but are usually wrapped in one). We need a gbean to be deployed for each such servlet and each such ejb. At the moment I think the best approach is to have a WSServletBuilder and a WSEJBBuilder that will actually build the gbeans. These, especially the WSEJBBuilder, would be similar to the openejb SessionConfigBuilder. Not just similar to but the same as--one session bean can have all of the following interfaces: - Local - Remote - ServiceEndpoint All of which can have transaction attributes associated with them. The ServiceEndpoint interface can even be invoked directly by EJBs, Servlets, or App Clients through declaring it as a service-ref and looking a it up through JNDI. Any invocations on the ServiceEndpoint interface go through JAX-RPC. Aside from JAX-RPC/ServiceEndpoint invocations, people can invoke the session bean through SOAP/WSDL over HTTP or HTTPS. In this case there is a mapping from WSDL to the ServiceEndpoint interface. All in all, this is not very different from
Re: Getting started on Web Services Stuff
Hi John; the PATCH according to the review by community change the the structrue of the Axis module quite drastically. But if you get the test working for the old ... I will help to get it FIX in the new one :) Cheers Srinath On Mon, 1 Nov 2004 16:29:50 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote: John, Please take a look at the following thread for more info on what needs to be done. - http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=9605 - http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=9607 - http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=9608 - http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=9609 thanks, dims On Wed, 27 Oct 2004 11:16:15 -0400 (EDT), John Childs [EMAIL PROTECTED] wrote: Thanks dims, I'll take a look at it. John John, Here's something you can start on...ComplexTypeWebServiceTest.java junit test case has be excluded explicitly in geronimo\trunk\modules\axis\project.xml because of some class loader issues. Can you dig into it and get it working? This will give you something to start with. Thanks, dims -- Davanum Srinivas - http://webservices.apache.org/~dims/ __ Post your free ad now! http://personals.yahoo.ca -- Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Getting started on Web Services Stuff
John there is a one test case up that check complete POJO case. I exclude others becouse do not get time to get them working. ComplexType test now completly outdated with new code. I get it done from the both. (there is a maven plugins to generate eclipse/IDE proj from maven build us it. But we get to test it in maven at the end). Thanks Srinath On Wed, 3 Nov 2004 10:05:03 -0500 (EST), John Childs [EMAIL PROTECTED] wrote: Hi Srinath, With the current code that I have it looks like none of the axis tests are included. Should I just get the new codeline and work from there? I've tried removing the ComplexWebServiceTest from the exclude list in project.xml and that doesn't seem to be enough to run the test. Is there something I am missing? I had the test running (and failing) with last weeks codeline, but I decided to update my code Monday morning and now I can't seem to get those tests to run at all. When you run them, do you run them from Maven, set them up manually, or from an IDE? John Srinath Perera wrote: Hi John; the PATCH according to the review by community change the the structrue of the Axis module quite drastically. But if you get the test working for the old ... I will help to get it FIX in the new one :) Cheers Srinath On Mon, 1 Nov 2004 16:29:50 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote: John, Please take a look at the following thread for more info on what needs to be done. - http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=9605 - http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=9607 - http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=9608 - http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=9609 thanks, dims On Wed, 27 Oct 2004 11:16:15 -0400 (EDT), John Childs [EMAIL PROTECTED] wrote: Thanks dims, I'll take a look at it. John John, Here's something you can start on...ComplexTypeWebServiceTest.java junit test case has be excluded explicitly in geronimo\trunk\modules\axis\project.xml because of some class loader issues. Can you dig into it and get it working? This will give you something to start with. Thanks, dims -- Davanum Srinivas - http://webservices.apache.org/~dims/ __ Post your free ad now! http://personals.yahoo.ca -- Davanum Srinivas - http://webservices.apache.org/~dims/ __ Post your free ad now! http://personals.yahoo.ca
[jira] Updated: (GERONIMO-269) webservice deployment with ews
[ http://issues.apache.org/jira/browse/GERONIMO-269?page=history ] Srinath Perera updated GERONIMO-269: Attachment: patch_27_08_2004.txt The current EWS will broke the Axis Geronimo module. I check in the code and when it is updated the build will fail. the patch will fix it. Please somebody chek it in. webservice deployment with ews -- Key: GERONIMO-269 URL: http://issues.apache.org/jira/browse/GERONIMO-269 Project: Apache Geronimo Type: New Feature Environment: all Reporter: Srinath Perera Attachments: deploy-patch-re.txt, patch-fix.txt, patch.txt, patch.txt, patch_10_18_2004.txt, patch_27_08_2004.txt, samples.zip this patch has code to deploy the webservice in the geronimo. there is a 1) WebServiceDeployerGbean and by calling deploy GBean method one can deploy a webservice. right now Axis service keep a seperate config-store but that can be changed when we decide on the final thing 2)the Deployer accept a webservice jar file and generate the required code using ews and deploy them. for time been the Axis GBean need to restart to get the new deploymnet. 3)the complete senario is shown in the WebServiceTest.java test. But to run this code need the JAVA_HOME/lib/tools.jar in the classpth. Since still can not get it in the classpath of maven I exclude the tests. If somebody using IDE and add the tools.jar in the classpath they should work fine :) 4) let me add some doc to the wiki about how this works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: [PATCH]FIX for AXIS geronimo module
forget to mention this fix all the testcases :) Thanks Srinath On Mon, 18 Oct 2004 14:37:32 +0600, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; the patch http://nagoya.apache.org/jira/secure/attachment/17935/patch_10_18_2004.txt fix the broken axis-geronimo build :). Can somebody please check this in. Thanks Srinath NOTE: rebuild the ews jar before apply the patch
Re: Web Services and Portlet deployment
The current web services deployment code does not appear at first glance to fit well into either jsr-88 deployment or the geronimo architecture. yap for the time been it is a hack. I was worried about getting it working. I talk with the Dims there is bit of clean up to done. I am explaining what happen at the WS deployment with should happen list? Here's what I think should happen: --jsr-88 client tells geronimo to deploy package, as a standard j2ee package. --geronimo deployer sorts it as a standard package and hands it to the web or ejb deployer --web or ejb deployer recognizes the extra deployment descriptor and hands it to the web services or portlet deployer if it is ws deployer * deployer generate a ejb and a wrapper to accpet the income SOAP and call the ejb/POJO. * if there a EJB it is deployed and started in the openejb * Axis do not directly support start/stop each web services.So the webservice is registerd inside the Axis .. * But there is no GBean for each Web servicehaving a GBean for eah WS would be nicer. But Axis is just a Servlet as far as the J2EE Continaer's point of view. So am not sure how to expose a Admin interface to the J2EE continer so that GBeans can use them. (any sugesstions are welcome) * if we get that GBean for each WS working then when they refer EJB's we can make ejb GBean put there as a WS GBean as a dependancy thoughts Thanks Srinath
Re: Web Services and Portlet deployment
Can webservices be unregistered from axis? yes .. undeploy support in the Axis geronimo module is not written yet. it is matter of writing code. (I do not get a chance to look in to those things due to Axis2 ..) I will implement that shortly. I'm not sure I understand exactly what a web service is:-) We need (even without web services or portlets) to have a gbean for each servlet. Therefore axis itself, since it is a servlet, will be represented by a gbean. this is already done .. it is load as a jetty cotiner as a web application. problem is gain access to the Axis Admin API since jetty know it as a servlet only. we had to use some Static things (I do not like it much ..but the classloaing inside Axis use atatic things too ...) For web services that talk to ejbs, we can either use the standard openejb container gbean or if necessary write and extension gbean. yes right now they use standard openejb container gbean though the ContainerIndex. it work well for Simple Types. there was a security manager issue loading the complex type class when I go though the ContainerIndex. I will check it agien and report to dev list. I don't understand yet about web services that talk to POJOs. Is each POJO wrapped in an individual servlet? Or does axis handle all of these itself without interaction with the rest of the j2ee framework? Axis is a servlet. It convert parameters in SOAP(XML)-java objects. then it call the impl with parameters. Impl is a POJO/EJB. if it is POJO axis simply load the class, create instance and call it. if it is EJB axis call it though ContinerIndex (inside OpnEJB)/or Remote Interface. What ever results will convert to SOAP(XML) and send back. So As far as POJO is concerned axis handle all of these itself without interaction with the rest of the j2ee framework Thanks Srinath
RE: [EWS]fix the Axis module
yes please .. I was waiting for correct them to find what is wrong. Srinath Hi Srinath, I failed to build EWS with the following message: [javac] Compiling 583 source files to C:\java\project\ws-axis\contrib\ews\target\classes C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ews\jaxrpcmappin g\J2eeBeanWriter.java:225: cannot resolve symbol symbol : method getLocalPart () location: class java.lang.String String elemName = elem.getName().getLocalPart(); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ews\jaxrpcmappin g\J2eeBeanWriter.java:400: cannot resolve symbol symbol : method getLocalPart () location: class java.lang.String Utils.xmlNameToJava(elem.getName().getLocalPart())); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ews\jaxrpcmappin g\J2eeBeanHelperWriter.java:295: cannot resolve symbol symbol : method getLocalPart () location: class java.lang.String String elemLocalName = elem.getName().getLocalPart(); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ews\jaxrpcmappin g\J2eeBeanHelperWriter.java:298: incompatible types found : java.lang.String required: javax.xml.namespace.QName QName xmlName = elem.getName(); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ews\jaxrpcmappin g\J2eeGeneratorFactory.java:1019: cannot resolve symbo l symbol : method holder (org.apache.axis.wsdl.symbolTable.MimeInfo,org.apache.axis.wsdl.symbolTable. TypeEntry,org.apache.geronimo. ews.jaxrpcmapping.J2eeEmitter) location: class org.apache.axis.wsdl.toJava.Utils signature = signature + Utils.holder(p.getMIMEInfo(), p.getType(), emitter) + ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ews\jaxrpcmappin g\J2eeHolderWriter.java:77: cannot resolve symbol symbol : method holder (nulltype,org.apache.axis.wsdl.symbolTable.TypeEntry,org.apache.geronimo.e ws.jaxrpcmapping.J2eeEmitter) location: class org.apache.axis.wsdl.toJava.Utils super(emitter, Utils.holder(null, type, emitter), holder); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ews\jaxrpcmappin g\J2eeTestCaseWriter.java:236: cannot resolve symbol symbol : method holder (org.apache.axis.wsdl.symbolTable.MimeInfo,org.apache.axis.wsdl.symbolTable. TypeEntry,org.apache.axis.wsdl toJava.Emitter) location: class org.apache.axis.wsdl.toJava.Utils pw.print(new + Utils.holder(param.getMIMEInfo(), param.getType(), emitter) ^ Note: Some input files use or override a deprecated API. Note: Recompile with -deprecation for details. 7 errors One thing I'm curious of is Utils.holder usage, which is wrong and should be corrected by Utils.holder(param, emitter) If you don't mind, I'll commit those corrections :-) Regards, Ias -Original Message- From: Srinath Perera [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:50 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Jongjin Choi' Subject: RE: [EWS]fix the Axis module Choi. Anyway, how can elem.getName() be null? Could you tell me which test case causes this error? org.apache.geronimo.ews.jaxrpcmapper.MapperTest, org.apache.geronimo.ews.ws4j2ee.JaxRpcMappingTest form ews test cases failed when I try. The trace I refering is to do with sameple/ejb/echo in the ews repository. Thanks Srinath Lanka Sofware Foundation
RE: [EWS]fix the Axis module
Thanks very much .. I will test the state with geronimo and get back. Thanks Srinath Hi all, Now EWS works fine as it passes all the tests. I updated J2eeGeneratorFactory and J2eeXxxWriters to catch up the latest Axis' refactoring on toJava package. Thanks for your patience, Ias -Original Message- From: Ias [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 5:17 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [EWS]fix the Axis module Hi Srinath, I failed to build EWS with the following message: [javac] Compiling 583 source files to C:\java\project\ws-axis\contrib\ews\target\classes C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ew s\jaxrpcmappin g\J2eeBeanWriter.java:225: cannot resolve symbol symbol : method getLocalPart () location: class java.lang.String String elemName = elem.getName().getLocalPart(); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ew s\jaxrpcmappin g\J2eeBeanWriter.java:400: cannot resolve symbol symbol : method getLocalPart () location: class java.lang.String Utils.xmlNameToJava(elem.getName().getLocalPart())); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ew s\jaxrpcmappin g\J2eeBeanHelperWriter.java:295: cannot resolve symbol symbol : method getLocalPart () location: class java.lang.String String elemLocalName = elem.getName().getLocalPart(); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ew s\jaxrpcmappin g\J2eeBeanHelperWriter.java:298: incompatible types found : java.lang.String required: javax.xml.namespace.QName QName xmlName = elem.getName(); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ew s\jaxrpcmappin g\J2eeGeneratorFactory.java:1019: cannot resolve symbo l symbol : method holder (org.apache.axis.wsdl.symbolTable.MimeInfo,org.apache.axis.wsd l.symbolTable. TypeEntry,org.apache.geronimo. ews.jaxrpcmapping.J2eeEmitter) location: class org.apache.axis.wsdl.toJava.Utils signature = signature + Utils.holder(p.getMIMEInfo(), p.getType(), emitter) + ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ew s\jaxrpcmappin g\J2eeHolderWriter.java:77: cannot resolve symbol symbol : method holder (nulltype,org.apache.axis.wsdl.symbolTable.TypeEntry,org.apa che.geronimo.e ws.jaxrpcmapping.J2eeEmitter) location: class org.apache.axis.wsdl.toJava.Utils super(emitter, Utils.holder(null, type, emitter), holder); ^ C:\java\project\ws-axis\contrib\ews\src\org\apache\geronimo\ew s\jaxrpcmappin g\J2eeTestCaseWriter.java:236: cannot resolve symbol symbol : method holder (org.apache.axis.wsdl.symbolTable.MimeInfo,org.apache.axis.wsd l.symbolTable. TypeEntry,org.apache.axis.wsdl toJava.Emitter) location: class org.apache.axis.wsdl.toJava.Utils pw.print(new + Utils.holder(param.getMIMEInfo(), param.getType(), emitter) ^ Note: Some input files use or override a deprecated API. Note: Recompile with -deprecation for details. 7 errors One thing I'm curious of is Utils.holder usage, which is wrong and should be corrected by Utils.holder(param, emitter) If you don't mind, I'll commit those corrections :-) Regards, Ias -Original Message- From: Srinath Perera [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:50 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Jongjin Choi' Subject: RE: [EWS]fix the Axis module Choi. Anyway, how can elem.getName() be null? Could you tell me which test case causes this error? org.apache.geronimo.ews.jaxrpcmapper.MapperTest, org.apache.geronimo.ews.ws4j2ee.JaxRpcMappingTest form ews test cases failed when I try. The trace I refering is to do with sameple/ejb/echo in the ews repository. Thanks Srinath Lanka Sofware Foundation
RE: Build error in Axis?
Sorry just see the error .. I will look in to it I will sent a patch if I fixt it, plesae somebody commit it. Thanks Srinath I get the same thing. Regards, Alan -Original Message- From: Aaron Mulder [mailto:[EMAIL PROTECTED] Sent: Monday, August 30, 2004 9:17 AM To: [EMAIL PROTECTED] Subject: Build error in Axis? When I try to build, I'm getting a NullPointerException from ews in the Axis module. I tried to rebuild, didn't make a difference. Any thoughts? (Maven 1.0, JDK 1.4.2_05) Thanks, Aaron Unable to obtain goal [default] -- geronimo/modules/axis/maven.xml:30:97: ews java.lang.NullPointerException Lanka Sofware Foundation
[EWS]fix the Axis module
Concerning the failure of the EWS on the Axis snap shot it is happen at the jaxrpc mapper inside axis code. I check the wsdl file with Axis WSDL2Java tool and it works ok. That means there is something assumned in the jaxrpc mapper that is broken. Still I do not get what it is. Ias do you have any idea what would be wrong? Thanks Srinath p.s. stac the NUllPointer come at here becouse name variable is null String fieldName = getAsFieldName(elem.getName()); // jongjin. java.lang.NullPointerException at org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.getAsFieldName(JavaBeanHelperWriter.java:403) at org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.writeMetaData(JavaBeanHelperWriter.java:318) at org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.writeFileBody(JavaBeanHelperWriter.java:175) at org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:130) at org.apache.axis.wsdl.toJava.JavaBeanWriter.writeFileBody(JavaBeanWriter.java:243) at org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:130) at org.apache.axis.wsdl.toJava.JavaTypeWriter.generate(JavaTypeWriter.java:112) at org.apache.geronimo.ews.jaxrpcmapping.J2eeGeneratorFactory$Writers.generate(J2eeGeneratorFactory.java:303) at org.apache.geronimo.ews.jaxrpcmapping.J2eeEmitter.generateTypes(J2eeEmitter.java:516) at org.apache.geronimo.ews.jaxrpcmapping.J2eeEmitter.generate(J2eeEmitter.java:417) at org.apache.geronimo.ews.jaxrpcmapping.J2eeEmitter.runServerSide(J2eeEmitter.java:175) at org.apache.geronimo.ews.ws4j2ee.toWs.ws.ServerSideWsGenerator.generate(ServerSideWsGenerator.java:129) at org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeEmitter.generatedSEIandtypes(Ws4J2eeEmitter.java:53) at org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeEmitter.emmit(Ws4J2eeEmitter.java:112) at org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2ee.generate(Ws4J2ee.java:129) at org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2ee.main(Ws4J2ee.java:360) at org.apache.geronimo.ews.ws4j2ee.GenerateWithoutWSDLTest.testEchoJar(GenerateWithoutWSDLTest.java:147) 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:324) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:392) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:276) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:167) Lanka Sofware Foundation
RE: [EWS]fix the Axis module
Choi. Anyway, how can elem.getName() be null? Could you tell me which test case causes this error? org.apache.geronimo.ews.jaxrpcmapper.MapperTest, org.apache.geronimo.ews.ws4j2ee.JaxRpcMappingTest form ews test cases failed when I try. The trace I refering is to do with sameple/ejb/echo in the ews repository. Thanks Srinath
Re: Axis dependencies
+1 .. that has a additional advantage as when the OpenEJB code changes the this cade break and by putting it at openEJB and add a test it can handle easily as well. Let me think how it should be done. a thought; I will hide the what expected by open EJB behind a interface. the real implemetation of the interface let us put inside OpenEJB cvs. let us load the impl class in runtime (same way JAXB/JNDI load the impls) using property file or a hard coded class name. This make the axis can compile without openejb jars (yap it will fail at runing) thoughts .. may be we should do the same to jetty as well .. then we can switch between tomcat and jetty easily. Thanks Srinath +1 from me to move the relevant code...Alan, do you want to take a stab at it? -- dims - Original Message - From: Alan D. Cabrera [EMAIL PROTECTED] Date: Sun, 8 Aug 2004 19:51:55 -0400 Subject: Axis dependencies To: [EMAIL PROTECTED], dev@openejb.org There are parts of the Axis code that rely on OpenEJB. This seems to introduce a circular dependence as OpenEJB relies on Geronimo. IIUC, this code may be better placed in OpenEJB. Thoughts? Regards, Alan -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation
Re: Axis module fails
that code generation done (where the error occurs) inside preGoal name=test:test isn't the the Compiled class avalible by that time. The AxisGeronimoUtils moved from EWS to here becouse it is more natural to have it here. Should we move that code .. can we fix the build while it is here. Thanks Srinath On Sun, Aug 08, 2004 at 08:29:44AM -0400, Alan D. Cabrera wrote: I figured out the problem, geronimo-axis-1.0-SNAPSHOT.jar was not in my repository, a chicken and the egg thing. I just hand copied the jar into my local maven repository. This makes me wonder, should we be updating a maven repository w/ snapshots? I post them here nightly: http://cvs.apache.org/repository/geronimo/jars/ -David Regards, Alan -Original Message- From: Alan D. Cabrera Sent: Saturday, August 07, 2004 4:46 PM To: [EMAIL PROTECTED] Subject: Axis module fails Here's the output: test:test: truetruetruetruetruetruetruetruetruetruetruetruetruetruetruetruetruetrue truetruetruetruetruetruetruetruetruetruetruetruetruetruetruetruetruetrue truetruetruetruetr geronimo\modules\axis\target\lib C:\dev\incubator-geronimo\.\target\ws4j2ee.properties created .. [echo] the files are up to date = true EchoPortSoapBindingImpl.java already exists, WSDL2Java will not overwrite it. [delete] Deleting 16 files from C:\dev\incubator-geronimo\modules\axis\target\generated\samples\build\cl asses [javac] Compiling 10 source files to C:\dev\incubator-geronimo\modules\axis\target\generated\samples\build\cl asses C:\dev\incubator-geronimo\modules\axis\target\generated\samples\org\apac he\ws\echosample\EchoPortSoapBindingImpl.java:2: package org.apache.geronimo.axis does not import org.apache.geronimo.axis.AxisGeronimoUtils; ^ C:\dev\incubator-geronimo\modules\axis\target\generated\samples\org\apac he\ws\echosample\EchoPortSoapBindingImpl.java:18: cannot resolve symbol symbol : variable AxisGeronimoUtils location: class org.apache.ws.echosample.EchoPortSoapBindingImpl return (java.lang.String)AxisGeronimoUtils.invokeEJB(echo,methodName,classes, arguments); ^ C:\dev\incubator-geronimo\modules\axis\target\generated\samples\org\apac he\ws\echosample\EchoPortSoapBindingImpl.java:25: cannot resolve symbol symbol : variable AxisGeronimoUtils location: class org.apache.ws.echosample.EchoPortSoapBindingImpl AxisGeronimoUtils.invokeEJB(echo,methodName,classes,arguments); ^ C:\dev\incubator-geronimo\modules\axis\target\generated\samples\org\apac he\ws\echosample\EchoPortSoapBindingImpl.java:32: cannot resolve symbol symbol : variable AxisGeronimoUtils location: class org.apache.ws.echosample.EchoPortSoapBindingImpl return ((java.lang.Integer)AxisGeronimoUtils.invokeEJB(echo,methodName,classe s,arguments)).intValue(); ^ C:\dev\incubator-geronimo\modules\axis\target\generated\samples\org\apac he\ws\echosample\EchoPortSoapBindingImpl.java:39: cannot resolve symbol symbol : variable AxisGeronimoUtils location: class org.apache.ws.echosample.EchoPortSoapBindingImpl return ((java.lang.Double)AxisGeronimoUtils.invokeEJB(echo,methodName,classes ,arguments)).doubleValue(); ^ C:\dev\incubator-geronimo\modules\axis\target\generated\samples\org\apac he\ws\echosample\EchoPortSoapBindingImpl.java:46: cannot resolve symbol symbol : variable AxisGeronimoUtils location: class org.apache.ws.echosample.EchoPortSoapBindingImpl return ((java.lang.Float)AxisGeronimoUtils.invokeEJB(echo,methodName,classes, arguments)).floatValue(); ^ C:\dev\incubator-geronimo\modules\axis\target\generated\samples\org\apac he\ws\echosample\EchoPortSoapBindingImpl.java:53: cannot resolve symbol symbol : variable AxisGeronimoUtils location: class org.apache.ws.echosample.EchoPortSoapBindingImpl return ((java.lang.Boolean)AxisGeronimoUtils.invokeEJB(echo,methodName,classe s,arguments)).booleanValue(); ^ C:\dev\incubator-geronimo\modules\axis\target\generated\samples\org\apac he\ws\echosample\EchoPortSoapBindingImpl.java:60: cannot resolve symbol symbol : variable AxisGeronimoUtils location: class org.apache.ws.echosample.EchoPortSoapBindingImpl return ((java.lang.Short)AxisGeronimoUtils.invokeEJB(echo,methodName,classes, arguments)).shortValue(); ^
Re: EWS and Geronimo
We were wondering should ews go to ws-fx (to a webservice project ) or in to the geronimo. It is still not decided. I accept the fact that it should use the geronimo group ID if it continue to use the Geronimo package space. Or else that should replace with ws and put the geronimo specific code in to geronimo axis module. To me there are good reasons to both and do not mind either. Thanks Srinath Why doesn't EWS use the Geronimo maven group id? Its code is in the Geronimo package-space. Just wondering. Regards, Alan - Visit our Internet site at http://www.reuters.com Get closer to the financial markets with Reuters Messaging - for more information and to register, visit http://www.reuters.com/messaging Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd. Lanka Sofware Foundation
Re: [PATCH]webservice deployment in geronimo
I do not commit the EWS task becouse there was a problem. If I have not remove it from the patch It mean I have mess it up some how. I download the your check in of the patch(do not look at it yet). basically I will try my best to get the test cases run and get back to you :). Thanks for your help Srinath Srinath, org.apache.geronimo.ews.ws4j2ee.utils.EWSTask is missing as well in the EWS project -- dims On Thu, 22 Jul 2004 11:01:46 -0700, Dain Sundstrom [EMAIL PROTECTED] wrote: On Jul 21, 2004, at 7:22 PM, Srinath Perera wrote: the patch is posted to JIRA @ http://nagoya.apache.org/jira/secure/ManageAttachments.jspa?id=22172 :) So ews generates java source code and compiles it? Is there any way to skip the Java source generation and thus the need for a compiler? -dain I think code generation is a must as the axis stub/skeltons need to be generated anyway. but there may be a way out. We can provide the ews as a tools and ask user to run it(in here the ews can find the tools.jar in the same way ant/maven find it, via shell script) and then geronimo can deploy the generated code. (If I am right sun RI ask use to run the generater ws* before deploy code). To me it is better if we can say to the user give us the bundle the J2EE spec talk about and we will do the rest!!!, but if there practical problems I think it is ok to ask user to run EWS themselves and then deploy. If we need to generate Java source code and compile it, then I would rather have the deployment process simply do that. What I was really getting at is can we simply generate the byte code directly and skip the Java source generation and compile steps? -dain -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation
Re: [PATCH]webservice deployment in geronimo
Thanks Dims,
I have done a stupid mistake :(... in the project.properties file the my
profile url is misspelled. It should be
http://ws.apache.org/~hemapani/maven
I attached the patch, but I think easist thing to you is to change the
properties file by hand it is the only change.
hope I have not create a mess.
Thanks
Srinath
Am reviewing this now...more details tomorrow.
thanks,
dims
Index: maven.xml
===
RCS file: maven.xml
diff -N maven.xml
--- /dev/null 1 Jan 1970 00:00:00 -
+++ maven.xml 22 Jul 2004 01:47:01 -
@@ -0,0 +1,27 @@
+?xml version=1.0 encoding=UTF-8?
+
+project default=jar
+xmlns:j=jelly:core
+xmlns:maven=jelly:maven
+xmlns:deploy=deploy
+xmlns:ant=jelly:ant
+goal name=setclasspath
+path id=test.classpath
+path refid=maven.dependency.classpath/
+pathelement location=${tools.jar}/
+/path
+/goal
+
+preGoal name=test:test
+ ant:java classname=org.apache.geronimo.ews.ws4j2ee.utils.PropertyStore fork=no
+ ant:arg value=${maven.repo.local}/
+ ant:classpath refid=maven.dependency.classpath/
+ /ant:java
+j:jelly xmlns=jelly:ant
+ ant:ant antfile=build.xml inheritall=true inheritrefs=true dir=src/samples/echo/
+ taskdef name=ews classname=org.apache.geronimo.ews.ws4j2ee.utils.EWSTask
+classpath refid=maven.dependency.classpath/
+/taskdef
+/j:jelly
+/preGoal
+/project
Index: project.properties
===
RCS file: /home/cvs/incubator-geronimo/modules/axis/project.properties,v
retrieving revision 1.1
diff -u -r1.1 project.properties
--- project.properties 13 Jul 2004 17:21:55 - 1.1
+++ project.properties 22 Jul 2004 01:47:01 -
@@ -4,6 +4,7 @@
# the directory containing the geronimo website in CVS
-maven.repo.remote=http://dist.codehaus.org, http://www.ibiblio.org/maven, http://ws.apache.org/~dims/maven
+maven.repo.remote=http://dist.codehaus.org, http://www.ibiblio.org/maven, http://ws.apache.org/~dims/maven, http://ws.apache.org/~hemapani/maven
+
+maven.junit.jvmargs=-Djava.security.auth.login.config=src/test-resources/data/login.config
-maven.junit.jvmargs=-Djava.security.auth.login.config=src/test-resources/data/login.config
\ No newline at end of file
Index: project.xml
===
RCS file: /home/cvs/incubator-geronimo/modules/axis/project.xml,v
retrieving revision 1.2
diff -u -r1.2 project.xml
--- project.xml 18 Jul 2004 21:50:39 - 1.2
+++ project.xml 22 Jul 2004 01:47:02 -
@@ -6,16 +6,16 @@
Licensed under the Apache License, Version 2.0 (the License);
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
-
+
http://www.apache.org/licenses/LICENSE-2.0
-
+
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an AS IS BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--
-
+
!-- $Revision: 1.2 $ $Date: 2004/07/18 21:50:39 $ --
@@ -61,6 +61,14 @@
artifactIdgeronimo-kernel/artifactId
version${pom.currentVersion}/version
/dependency
+dependency
+groupIdgeronimo/groupId
+artifactIdgeronimo-core/artifactId
+version1.0-M1/version
+properties
+moduletrue/module
+/properties
+/dependency
dependency
groupIdgeronimo/groupId
artifactIdgeronimo-jetty/artifactId
@@ -153,6 +161,11 @@
xmlbeanstrue/xmlbeans
/properties
/dependency
+dependency
+groupIdgeronimo-spec/groupId
+artifactIdgeronimo-spec-ejb/artifactId
+version2.1-rc2/version
+/dependency
dependency
groupIdjetty/groupId
@@ -171,6 +184,15 @@
artifactIdmx4j/artifactId
version2.0.1/version
/dependency
+
+ dependency
+groupIddom4j/groupId
+artifactIddom4j/artifactId
+version1.4/version
+properties
+moduletrue/module
+/properties
+/dependency
!-- these are just needed to run the unit tests --
dependency
@@ -263,6 +285,62 @@
!-- Module Dependencies --
dependency
+groupIdews/groupId
+artifactIdews/artifactId
+version1.0/version
+properties
+moduletrue/module
+/properties
+/dependency
+dependency
+groupIdjaxb-ri/groupId
+artifactIdjaxb-api/artifactId
+
Re: [PATCH]webservice deployment in geronimo
the patch is posted to JIRA @ http://nagoya.apache.org/jira/secure/ManageAttachments.jspa?id=22172 :) So ews generates java source code and compiles it? Is there any way to skip the Java source generation and thus the need for a compiler? -dain I think code generation is a must as the axis stub/skeltons need to be generated anyway. but there may be a way out. We can provide the ews as a tools and ask user to run it(in here the ews can find the tools.jar in the same way ant/maven find it, via shell script) and then geronimo can deploy the generated code. (If I am right sun RI ask use to run the generater ws* before deploy code). To me it is better if we can say to the user give us the bundle the J2EE spec talk about and we will do the rest!!!, but if there practical problems I think it is ok to ask user to run EWS themselves and then deploy. Thanks Srinath
Re: [PATCH]webservice deployment in geronimo
I will check it and get back to you. hopefully fix it right now.
Srinath
will do. right now i am seeing a failure in EWS
C:\APACHE\ws-axis\contrib\ews\target\generated\samples\withoutWSDL\math\server\DefaultNamespace\MathSoapBindingStub.java:10:
DefaultNamespace.MathSoapBindingStub is not abstract and does not
override abstract method remove() in javax.ejb.EJBObject
public class MathSoapBindingStub extends org.apache.axis.client.Stub
implements testData.math.MathFace {
^
1 error
file:C:/APACHE/ws-axis/contrib/ews/target/generated/samples/withoutWSDL/math/server/build.xml:26:
Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:844)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at
org.apache.geronimo.ews.ws4j2ee.utils.AntExecuter.execute(AntExecuter.java:47)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeEmitter.executeAnt(Ws4J2eeEmitter.java:99)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeEmitter.emmit(Ws4J2eeEmitter.java:112)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2ee.generate(Ws4J2ee.java:128)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2ee.main(Ws4J2ee.java:359)
at
org.apache.geronimo.ews.ws4j2ee.GenerateWithoutWSDLTest.testMathSample(GenerateWithoutWSDLTest.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
-- dims
On Wed, 21 Jul 2004 21:59:27 -0400 (EDT), Srinath Perera
[EMAIL PROTECTED] wrote:
Thanks Dims,
I have done a stupid mistake :(... in the project.properties file the my
profile url is misspelled. It should be
http://ws.apache.org/~hemapani/maven
I attached the patch, but I think easist thing to you is to change the
properties file by hand it is the only change.
hope I have not create a mess.
Thanks
Srinath
Am reviewing this now...more details tomorrow.
thanks,
dims
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Lanka Sofware Foundation
Re: [PATCH]webservice deployment in geronimo
it is fixed, check the latest, cvs hope it works :).
the error was actually at the test case
Thanks
Srinath
will do. right now i am seeing a failure in EWS
C:\APACHE\ws-axis\contrib\ews\target\generated\samples\withoutWSDL\math\server\DefaultNamespace\MathSoapBindingStub.java:10:
DefaultNamespace.MathSoapBindingStub is not abstract and does not
override abstract method remove() in javax.ejb.EJBObject
public class MathSoapBindingStub extends org.apache.axis.client.Stub
implements testData.math.MathFace {
^
1 error
file:C:/APACHE/ws-axis/contrib/ews/target/generated/samples/withoutWSDL/math/server/build.xml:26:
Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:844)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at
org.apache.geronimo.ews.ws4j2ee.utils.AntExecuter.execute(AntExecuter.java:47)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeEmitter.executeAnt(Ws4J2eeEmitter.java:99)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeEmitter.emmit(Ws4J2eeEmitter.java:112)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2ee.generate(Ws4J2ee.java:128)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2ee.main(Ws4J2ee.java:359)
at
org.apache.geronimo.ews.ws4j2ee.GenerateWithoutWSDLTest.testMathSample(GenerateWithoutWSDLTest.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
-- dims
On Wed, 21 Jul 2004 21:59:27 -0400 (EDT), Srinath Perera
[EMAIL PROTECTED] wrote:
Thanks Dims,
I have done a stupid mistake :(... in the project.properties file the my
profile url is misspelled. It should be
http://ws.apache.org/~hemapani/maven
I attached the patch, but I think easist thing to you is to change the
properties file by hand it is the only change.
hope I have not create a mess.
Thanks
Srinath
Am reviewing this now...more details tomorrow.
thanks,
dims
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Lanka Sofware Foundation
Re: [PATCH]webservice deployment in geronimo
it is fixed, check the latest cvs, hope it works :).
the error was actually at the test case
Thanks
Srinath
will do. right now i am seeing a failure in EWS
C:\APACHE\ws-axis\contrib\ews\target\generated\samples\withoutWSDL\math\server\DefaultNamespace\MathSoapBindingStub.java:10:
DefaultNamespace.MathSoapBindingStub is not abstract and does not
override abstract method remove() in javax.ejb.EJBObject
public class MathSoapBindingStub extends org.apache.axis.client.Stub
implements testData.math.MathFace {
^
1 error
file:C:/APACHE/ws-axis/contrib/ews/target/generated/samples/withoutWSDL/math/server/build.xml:26:
Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:844)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at
org.apache.geronimo.ews.ws4j2ee.utils.AntExecuter.execute(AntExecuter.java:47)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeEmitter.executeAnt(Ws4J2eeEmitter.java:99)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2eeEmitter.emmit(Ws4J2eeEmitter.java:112)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2ee.generate(Ws4J2ee.java:128)
at
org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2ee.main(Ws4J2ee.java:359)
at
org.apache.geronimo.ews.ws4j2ee.GenerateWithoutWSDLTest.testMathSample(GenerateWithoutWSDLTest.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
-- dims
On Wed, 21 Jul 2004 21:59:27 -0400 (EDT), Srinath Perera
[EMAIL PROTECTED] wrote:
Thanks Dims,
I have done a stupid mistake :(... in the project.properties file the my
profile url is misspelled. It should be
http://ws.apache.org/~hemapani/maven
I attached the patch, but I think easist thing to you is to change the
properties file by hand it is the only change.
hope I have not create a mess.
Thanks
Srinath
Am reviewing this now...more details tomorrow.
thanks,
dims
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Lanka Sofware Foundation
[PATCH]webservice deployment in geronimo
Hi All;
this patch has code to deploy the webservice in the geronimo.
there is a
1) WebServiceDeployerGbean and by calling deploy GBean method one can
deploy a webservice. right now Axis service keep a seperate config-store
but that can be changed when we decide on the final thing
2)the Deployer accept a webservice jar file and generate the required code
using ews and deploy them. for time been the Axis GBean need to restart to
get the new deploymnet.
3)the complete senario is shown in the WebServiceTest.java test. But to
run this code need the JAVA_HOME/lib/tools.jar in the classpth. Since
still can not get it in the classpath of maven I exclude the tests. If
somebody using IDE and add the tools.jar in the classpath they should work
fine :)
4) let me add some doc to the wiki about how this works.
Can somebody verify this and check it in for me.
Thanks
Srinath
Lanka Sofware Foundation
Index: maven.xml
===
RCS file: maven.xml
diff -N maven.xml
--- /dev/null 1 Jan 1970 00:00:00 -
+++ maven.xml 21 Jul 2004 12:10:55 -
@@ -0,0 +1,27 @@
+?xml version=1.0 encoding=UTF-8?
+
+project default=jar
+xmlns:j=jelly:core
+xmlns:maven=jelly:maven
+xmlns:deploy=deploy
+xmlns:ant=jelly:ant
+goal name=setclasspath
+path id=test.classpath
+path refid=maven.dependency.classpath/
+pathelement location=${tools.jar}/
+/path
+/goal
+
+preGoal name=test:test
+ ant:java classname=org.apache.geronimo.ews.ws4j2ee.utils.PropertyStore fork=no
+ ant:arg value=${maven.repo.local}/
+ ant:classpath refid=maven.dependency.classpath/
+ /ant:java
+j:jelly xmlns=jelly:ant
+ ant:ant antfile=build.xml inheritall=true inheritrefs=true dir=src/samples/echo/
+ taskdef name=ews classname=org.apache.geronimo.ews.ws4j2ee.utils.EWSTask
+classpath refid=maven.dependency.classpath/
+/taskdef
+/j:jelly
+/preGoal
+/project
Index: project.properties
===
RCS file: /home/cvs/incubator-geronimo/modules/axis/project.properties,v
retrieving revision 1.1
diff -u -r1.1 project.properties
--- project.properties 13 Jul 2004 17:21:55 - 1.1
+++ project.properties 21 Jul 2004 12:10:55 -
@@ -4,6 +4,7 @@
# the directory containing the geronimo website in CVS
-maven.repo.remote=http://dist.codehaus.org, http://www.ibiblio.org/maven, http://ws.apache.org/~dims/maven
+maven.repo.remote=http://dist.codehaus.org, http://www.ibiblio.org/maven, http://ws.apache.org/~dims/maven,http://ws.apache.org/~dims/hemapani
-maven.junit.jvmargs=-Djava.security.auth.login.config=src/test-resources/data/login.config
\ No newline at end of file
+maven.junit.jvmargs=-Djava.security.auth.login.config=src/test-resources/data/login.config
+maven.compile.optimize=false
\ No newline at end of file
Index: project.xml
===
RCS file: /home/cvs/incubator-geronimo/modules/axis/project.xml,v
retrieving revision 1.2
diff -u -r1.2 project.xml
--- project.xml 18 Jul 2004 21:50:39 - 1.2
+++ project.xml 21 Jul 2004 12:10:56 -
@@ -6,16 +6,16 @@
Licensed under the Apache License, Version 2.0 (the License);
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
-
+
http://www.apache.org/licenses/LICENSE-2.0
-
+
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an AS IS BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--
-
+
!-- $Revision: 1.2 $ $Date: 2004/07/18 21:50:39 $ --
@@ -61,6 +61,14 @@
artifactIdgeronimo-kernel/artifactId
version${pom.currentVersion}/version
/dependency
+dependency
+groupIdgeronimo/groupId
+artifactIdgeronimo-core/artifactId
+version1.0-M1/version
+properties
+moduletrue/module
+/properties
+/dependency
dependency
groupIdgeronimo/groupId
artifactIdgeronimo-jetty/artifactId
@@ -153,6 +161,11 @@
xmlbeanstrue/xmlbeans
/properties
/dependency
+dependency
+groupIdgeronimo-spec/groupId
+artifactIdgeronimo-spec-ejb/artifactId
+version2.1-rc2/version
+/dependency
dependency
groupIdjetty/groupId
@@ -171,6 +184,15 @@
artifactIdmx4j/artifactId
version2.0.1/version
/dependency
+
+ dependency
+groupIddom4j/groupId
+
making the tools.jar avalible at the unit tests in geronimo maven build
Hi All; to run the webservice deployment tests I need the tools.jar in the classpath. Usually it is in the maven test classpath .. but in this case it is not in the geronmo case. how can I make it avalible. Thanks Srinath Lanka Sofware Foundation
Re: making the tools.jar avalible at the unit tests in geronimo maven build
No .. I have integrated the EWS and have simple code that acepts webservice modules generate the webservice , ejb then deploy both in the geronimo via a new DeployGBean. it need a restart of the axis service. to compile the generated code I need the tools.jar. I have few test cases and to get them running I need the tools.jar. I am trying get the test cases works in geronimo before send the patch :) If I get the that axis code I may be make the module find the tools.jar by ews it self. Thanks Srinath BTW - is it ok if I make avalible the latest ews jar in my profile and make the maven download them in the build. Srinath, Are u trying JWS deployment? Please use latest Axis from CVS. It automatically finds tools.jar -- dims On Tue, 20 Jul 2004 08:28:19 -0400 (EDT), Srinath Perera [EMAIL PROTECTED] wrote: Hi All; to run the webservice deployment tests I need the tools.jar in the classpath. Usually it is in the maven test classpath .. but in this case it is not in the geronmo case. how can I make it avalible. Thanks Srinath Lanka Sofware Foundation -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation
Re: problem starting jetty as GBean stanalone
In the future can you start with a fresh email message instead of replying to an existing message on the mailing list. On most email clients if you reply to a message and change the subject it still groups the response with the original thread. BTW this is called thread hijacking. thanks for let me know. will make sure that wan't happen agien :) Anyway, I took a peek at the HTTPConnector code an what you have should work. Can you try hooking up a debugger to see what is in GBeanMBean attributes map? I will try (not still sure how yet , but will find out) any way if there is a bug as I claimed the other peoples build of the maven should failed inside axis module tests. It seems it is not the case. may be I have messs up something, any way plese let me check it, try to debug it and get back to you. Thanks Srinath On Jul 14, 2004, at 1:29 AM, Srinath Perera wrote: The code I was using to start jetty stand alone in AaxisGBean failing. It works just few days ago. in the HTTPConnector GBean the port is defined in the super class sp they are not inherited?? may be this has something to done with this but I am still not sure Then I try code to start the Jetty from ApplicationTest and it also fails saying port is a attribute. If what I saying is true the test should be failing in number of occasions. Thanks Srinath trace = javax.management.AttributeNotFoundException: Unknown attribute port at org.apache.geronimo.gbean.jmx.GBeanMBean.getAttributeByName(GBeanMBean. java:736) at org.apache.geronimo.gbean.jmx.GBeanMBean.setAttribute(GBeanMBean.java: 674) at org.apache.geronimo.axis.AxisGBeanTest.setUp(AxisGBeanTest.java:112) containerName = new ObjectName(geronimo.jetty:role=Container); containerPatterns = Collections.singleton(containerName); connectorName = new ObjectName(geronimo.jetty:role=Connector); appName = new ObjectName(geronimo.jetty:app=test); tmName = new ObjectName(geronimo.test:role=TransactionManager); tcaName = new ObjectName(geronimo.test:role=ConnectionTrackingCoordinator); kernel = new Kernel(test.kernel, test); kernel.boot(); mbServer = kernel.getMBeanServer(); container = new GBeanMBean(JettyContainerImpl.GBEAN_INFO); connector = new GBeanMBean(HTTPConnector.GBEAN_INFO); connector.setAttribute(port, new Integer(5678)); connector.setReferencePatterns(JettyContainer, containerPatterns); start(containerName, container); start(connectorName, connector); tm = new GBeanMBean(GeronimoTransactionManager.GBEAN_INFO); Set patterns = new HashSet(); patterns.add(ObjectName.getInstance(geronimo.server: j2eeType=JCAManagedConnectionFactory,*)); tm.setReferencePatterns(resourceManagers, patterns); start(tmName, tm); ctc = new GBeanMBean(ConnectionTrackingCoordinator.GBEAN_INFO); start(tcaName, ctc); Lanka Sofware Foundation
Re: problem starting jetty as GBean stanalone
Anyway, I took a peek at the HTTPConnector code an what you have should work. Can you try hooking up a debugger to see what is in GBeanMBean attributes map? I will try (not still sure how yet , but will find out) any way if there is a bug as I claimed the other peoples build of the maven should failed inside axis module tests. It seems it is not the case. may be I have messs up something, any way plese let me check it, try to debug it and get back to you. Thanks Srinath yes when I build all geronimo with tests off and then build the axis module back and in that case it works ok. Srinath On Jul 14, 2004, at 1:29 AM, Srinath Perera wrote: The code I was using to start jetty stand alone in AaxisGBean failing. It works just few days ago. in the HTTPConnector GBean the port is defined in the super class sp they are not inherited?? may be this has something to done with this but I am still not sure Then I try code to start the Jetty from ApplicationTest and it also fails saying port is a attribute. If what I saying is true the test should be failing in number of occasions. Thanks Srinath trace = javax.management.AttributeNotFoundException: Unknown attribute port at org.apache.geronimo.gbean.jmx.GBeanMBean.getAttributeByName(GBeanMBean. java:736) at org.apache.geronimo.gbean.jmx.GBeanMBean.setAttribute(GBeanMBean.java: 674) at org.apache.geronimo.axis.AxisGBeanTest.setUp(AxisGBeanTest.java:112) containerName = new ObjectName(geronimo.jetty:role=Container); containerPatterns = Collections.singleton(containerName); connectorName = new ObjectName(geronimo.jetty:role=Connector); appName = new ObjectName(geronimo.jetty:app=test); tmName = new ObjectName(geronimo.test:role=TransactionManager); tcaName = new ObjectName(geronimo.test:role=ConnectionTrackingCoordinator); kernel = new Kernel(test.kernel, test); kernel.boot(); mbServer = kernel.getMBeanServer(); container = new GBeanMBean(JettyContainerImpl.GBEAN_INFO); connector = new GBeanMBean(HTTPConnector.GBEAN_INFO); connector.setAttribute(port, new Integer(5678)); connector.setReferencePatterns(JettyContainer, containerPatterns); start(containerName, container); start(connectorName, connector); tm = new GBeanMBean(GeronimoTransactionManager.GBEAN_INFO); Set patterns = new HashSet(); patterns.add(ObjectName.getInstance(geronimo.server: j2eeType=JCAManagedConnectionFactory,*)); tm.setReferencePatterns(resourceManagers, patterns); start(tmName, tm); ctc = new GBeanMBean(ConnectionTrackingCoordinator.GBEAN_INFO); start(tcaName, ctc); Lanka Sofware Foundation Lanka Sofware Foundation
Re: where to put the axis-geronimo module
Thanks dims, I was worried about hard coded string ... you have fix it :) Srinath Srinath, I have added a incubator-geronimo\modules\axis. Please try the latest CVS and submit patch against CVS from now on :) thanks, dims On Tue, 13 Jul 2004 08:45:09 -0700, David Jencks [EMAIL PROTECTED] wrote: +1 david jencks On Tuesday, July 13, 2004, at 03:40 AM, Davanum Srinivas wrote: +1 to creating axis module in geronimo. It's time to get this into the mainstream. -- dims On Mon, 12 Jul 2004 21:48:13 -0700, Jeremy Boynes [EMAIL PROTECTED] wrote: How about just as the axis module in Geronimo? -- Jeremy -- Davanum Srinivas - http://webservices.apache.org/~dims/ -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation
problem starting jetty as GBean stanalone
The code I was using to start jetty stand alone in AaxisGBean failing. It works just few days ago. in the HTTPConnector GBean the port is defined in the super class sp they are not inherited?? may be this has something to done with this but I am still not sure Then I try code to start the Jetty from ApplicationTest and it also fails saying port is a attribute. If what I saying is true the test should be failing in number of occasions. Thanks Srinath trace = javax.management.AttributeNotFoundException: Unknown attribute port at org.apache.geronimo.gbean.jmx.GBeanMBean.getAttributeByName(GBeanMBean.java:736) at org.apache.geronimo.gbean.jmx.GBeanMBean.setAttribute(GBeanMBean.java:674) at org.apache.geronimo.axis.AxisGBeanTest.setUp(AxisGBeanTest.java:112) containerName = new ObjectName(geronimo.jetty:role=Container); containerPatterns = Collections.singleton(containerName); connectorName = new ObjectName(geronimo.jetty:role=Connector); appName = new ObjectName(geronimo.jetty:app=test); tmName = new ObjectName(geronimo.test:role=TransactionManager); tcaName = new ObjectName(geronimo.test:role=ConnectionTrackingCoordinator); kernel = new Kernel(test.kernel, test); kernel.boot(); mbServer = kernel.getMBeanServer(); container = new GBeanMBean(JettyContainerImpl.GBEAN_INFO); connector = new GBeanMBean(HTTPConnector.GBEAN_INFO); connector.setAttribute(port, new Integer(5678)); connector.setReferencePatterns(JettyContainer, containerPatterns); start(containerName, container); start(connectorName, connector); tm = new GBeanMBean(GeronimoTransactionManager.GBEAN_INFO); Set patterns = new HashSet(); patterns.add(ObjectName.getInstance(geronimo.server:j2eeType=JCAManagedConnectionFactory,*)); tm.setReferencePatterns(resourceManagers, patterns); start(tmName, tm); ctc = new GBeanMBean(ConnectionTrackingCoordinator.GBEAN_INFO); start(tcaName, ctc);
where to put the axis-geronimo module
Hi Dims; to where should I commit the axis-geronimo module (AxisGbean + axis geronimo integration classes) http://www.cse.mrt.ac.lk/~hemapani/JSR109/axis-geronimo.zip 1) I can put it in to the EWS but then EWS need about half of the geronimo Jar's to build. So I like to keep it separate as does in the Spring. But the ews dir stucture does not allow to add new module indside? 2) I can commit it in to something like contirb/axis-gronimo so we ca put it to right place when the time comes. Thanks Srinath Original Message Subject: Re: Web Services items for J2EE 1.4 From:Srinath Perera [EMAIL PROTECTED] Date:Thu, July 8, 2004 9:27 am To: [EMAIL PROTECTED] Jeremy Boynes [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] -- Hi Dims, Jeremy and all; in the http://www.cse.mrt.ac.lk/~hemapani/JSR109/axis-geronimo.zip I got a simple AxisGbean .. I start it and invoke a webservice and it works :) I am just put it there as it is. I am not yet thought about the parameter AxisGBean should have . and it still start with the geronimo test kernel I just want to know am going in right path. Couple of Q's = 1) how to get that GBean started when the Geronimo starts up 2) I think when it start up the jetty should be up .. here i did it explicitly but how to put a dependany .. I do not found how yet ? I am build this based on the Geronimo test classes there may be way to make the code look good pls let me know. Thanks Srinath (make sure you point the varibale to the webapps dir in your mechine. - Read Below). How to build it == 1)copy the axis folder to the geronimo module dir and it can be build as a geronimo module. 2) before build it make sure that In the WebserviceContiner class public String WEB_APPS = D:/servers/jboss-3.2.3/server/default/deploy/axis; points to your webapps/axis dir of your local axis :) Srinath, Check out the spring support being added to Geronimo. Axis needs to be seamlessly integrated into Geronimo. This means adding a AxisGBean that allows: - No need for custom AxisServlet/AdminServlet entries in web.xml - No need to use AdminClient for deploy. Things get automatically deployed. - Automatic deployment for JSR 109 type descriptor and native axis wsdd descriptor - All functionality currently in AdminServlet (start/stop/enable/disable) available via JMX (or) however Geronimo exposes these things. Thanks, dims On Fri, 25 Jun 2004 11:47:09 -0400 (EDT), Srinath Perera [EMAIL PROTECTED] wrote: the ews http://cvs.apache.org/viewcvs.cgi/ws-axis/contrib/ews/ can accepts JAR/WAR/EAR packaged Interfaces + Impl Beans + DD and generate implementations (as by spec ). The docs have most info. security is there to some extents as well. This may be time to talk with Jeremy and Luis about finer details how axis comes inside geronimo and how the above explained generated classes are deployed in. Regards Srinath Here's the last mail from Srinath regarding EWS: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=7438 -- dims On Thu, 24 Jun 2004 10:13:52 -0700, Dain Sundstrom [EMAIL PROTECTED] wrote: Where are we on integrating these into geronimo? -dain On Jun 24, 2004, at 7:41 AM, Davanum Srinivas wrote: FYI, List of items from J2EE 1.4 spec (http://java.sun.com/j2ee/1.4/download.html) and where/how they are being implemented: # J2EE.6.12 Web Services for J2EE 1.1 Requirements See http://cvs.apache.org/viewcvs.cgi/ws-axis/contrib/ews/ # J2EE.6.13 Java™ API for XML-based RPC (JAX-RPC) 1.1 Requirements Will be part of Axis 1.2 Final # J2EE.6.14 SOAP with Attachments API for Java™ (SAAJ) 1.2 Will be part of Axis 1.2 Final # J2EE.6.15 Java™ API for XML Registries (JAXR) 1.0 Requirements See http://cvs.apache.org/viewcvs.cgi/ws-juddi/extras/jaxr/ Thanks, dims -- Davanum Srinivas - http://webservices.apache.org/~dims/ -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation Lanka Sofware Foundation
Re: where to put the axis-geronimo module
sure Jeremy that is better... I was thinking how to put the ews jar .. may be we kept the ews jar in a profile and get maven to downlod it when building. (I have to keep the jar upto date). Srinath How about just as the axis module in Geronimo? -- Jeremy Lanka Sofware Foundation
Re: Web Services items for J2EE 1.4
Hi Dims, Jeremy and all; in the http://www.cse.mrt.ac.lk/~hemapani/JSR109/axis-geronimo.zip I got a simple AxisGbean .. I start it and invoke a webservice and it works :) I am just put it there as it is. I am not yet thought about the parameter AxisGBean should have . and it still start with the geronimo test kernel I just want to know am going in right path. Couple of Q's = 1) how to get that GBean started when the Geronimo starts up 2) I think when it start up the jetty should be up .. here i did it explicitly but how to put a dependany .. I do not found how yet ? I am build this based on the Geronimo test classes there may be way to make the code look good pls let me know. Thanks Srinath (make sure you point the varibale to the webapps dir in your mechine. - Read Below). How to build it == 1)copy the axis folder to the geronimo module dir and it can be build as a geronimo module. 2) before build it make sure that In the WebserviceContiner class public String WEB_APPS = D:/servers/jboss-3.2.3/server/default/deploy/axis; points to your webapps/axis dir of your local axis :) Srinath, Check out the spring support being added to Geronimo. Axis needs to be seamlessly integrated into Geronimo. This means adding a AxisGBean that allows: - No need for custom AxisServlet/AdminServlet entries in web.xml - No need to use AdminClient for deploy. Things get automatically deployed. - Automatic deployment for JSR 109 type descriptor and native axis wsdd descriptor - All functionality currently in AdminServlet (start/stop/enable/disable) available via JMX (or) however Geronimo exposes these things. Thanks, dims On Fri, 25 Jun 2004 11:47:09 -0400 (EDT), Srinath Perera [EMAIL PROTECTED] wrote: the ews http://cvs.apache.org/viewcvs.cgi/ws-axis/contrib/ews/ can accepts JAR/WAR/EAR packaged Interfaces + Impl Beans + DD and generate implementations (as by spec ). The docs have most info. security is there to some extents as well. This may be time to talk with Jeremy and Luis about finer details how axis comes inside geronimo and how the above explained generated classes are deployed in. Regards Srinath Here's the last mail from Srinath regarding EWS: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=7438 -- dims On Thu, 24 Jun 2004 10:13:52 -0700, Dain Sundstrom [EMAIL PROTECTED] wrote: Where are we on integrating these into geronimo? -dain On Jun 24, 2004, at 7:41 AM, Davanum Srinivas wrote: FYI, List of items from J2EE 1.4 spec (http://java.sun.com/j2ee/1.4/download.html) and where/how they are being implemented: # J2EE.6.12 Web Services for J2EE 1.1 Requirements See http://cvs.apache.org/viewcvs.cgi/ws-axis/contrib/ews/ # J2EE.6.13 Java™ API for XML-based RPC (JAX-RPC) 1.1 Requirements Will be part of Axis 1.2 Final # J2EE.6.14 SOAP with Attachments API for Java™ (SAAJ) 1.2 Will be part of Axis 1.2 Final # J2EE.6.15 Java™ API for XML Registries (JAXR) 1.0 Requirements See http://cvs.apache.org/viewcvs.cgi/ws-juddi/extras/jaxr/ Thanks, dims -- Davanum Srinivas - http://webservices.apache.org/~dims/ -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation
Re: Web Services items for J2EE 1.4
Thanks dims .. I would look in to them and come back geronimo dev if help is needed. Srinath Srinath, Check out the spring support being added to Geronimo. Axis needs to be seamlessly integrated into Geronimo. This means adding a AxisGBean that allows: - No need for custom AxisServlet/AdminServlet entries in web.xml - No need to use AdminClient for deploy. Things get automatically deployed. - Automatic deployment for JSR 109 type descriptor and native axis wsdd descriptor - All functionality currently in AdminServlet (start/stop/enable/disable) available via JMX (or) however Geronimo exposes these things. Thanks, dims On Fri, 25 Jun 2004 11:47:09 -0400 (EDT), Srinath Perera [EMAIL PROTECTED] wrote: the ews http://cvs.apache.org/viewcvs.cgi/ws-axis/contrib/ews/ can accepts JAR/WAR/EAR packaged Interfaces + Impl Beans + DD and generate implementations (as by spec ). The docs have most info. security is there to some extents as well. This may be time to talk with Jeremy and Luis about finer details how axis comes inside geronimo and how the above explained generated classes are deployed in. Regards Srinath Here's the last mail from Srinath regarding EWS: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=7438 -- dims On Thu, 24 Jun 2004 10:13:52 -0700, Dain Sundstrom [EMAIL PROTECTED] wrote: Where are we on integrating these into geronimo? -dain On Jun 24, 2004, at 7:41 AM, Davanum Srinivas wrote: FYI, List of items from J2EE 1.4 spec (http://java.sun.com/j2ee/1.4/download.html) and where/how they are being implemented: # J2EE.6.12 Web Services for J2EE 1.1 Requirements See http://cvs.apache.org/viewcvs.cgi/ws-axis/contrib/ews/ # J2EE.6.13 Java™ API for XML-based RPC (JAX-RPC) 1.1 Requirements Will be part of Axis 1.2 Final # J2EE.6.14 SOAP with Attachments API for Java™ (SAAJ) 1.2 Will be part of Axis 1.2 Final # J2EE.6.15 Java™ API for XML Registries (JAXR) 1.0 Requirements See http://cvs.apache.org/viewcvs.cgi/ws-juddi/extras/jaxr/ Thanks, dims -- Davanum Srinivas - http://webservices.apache.org/~dims/ -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation -- Davanum Srinivas - http://webservices.apache.org/~dims/ Lanka Sofware Foundation
