Aaah rite. I see. So, the "destroy" method is not considered a "custom" method and so in code generation it is pre-written in the AbstractXXXService class. So There should be no need to ever have to write this in the Service class? Is this true?
The attached service class doesn't have the "destroy" method.It is defined in the attached "AbstractXXService" class. This is what was generated by apollo. I have tried moving it from the Abstract to the Service class but it doesn't make a difference. I'll double check my wsdl, but I cant see how there can be an error in the wsdl if it managed to generate the correct methods. Thank you Shahzad -----Original Message----- From: Campana Jr., Salvatore J [mailto:[EMAIL PROTECTED] Sent: 25 March 2005 16:42 To: [email protected] Subject: RE: Destroy a resource... Shazad, Let's take a step back.... When we generate code, the spec operations are declared in the Abstract..Service we generate. In the code you sent to list, the destroy method was not defined in the Abstract...Service...It was in the generated Service itself. This tells me you modified that. In moving the operation from the Abstract..Service to the actual Service the package imports were messed up (easy mistake)... I never meant to imply you need to declare it in 2 places. My only point is that you wsdl and the generated code no longer match, and because of this your requests are not understood.... Send the src for the files as you have them now so I can see what you've done and we'll take it from there.... -S -----Original Message----- From: Shahzad Younas [mailto:[EMAIL PROTECTED] Sent: Friday, March 25, 2005 11:18 AM To: [email protected] Subject: Destroy a resource... PLEASE IGNORE PREVIOUS EMAIL....it was sent accidentaly! Hi, I get what you are saying. But a question just popped into my head. If the service extends the "abstractXXservice", and the destroy method is defined correctly in the abstract service, why am I having to "redeclare" it in my service class? I have made the changes you have suggested, but, its still refusing to work! The message I am sending: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Header> <wsa:To soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";>http://loca lhos t:8080/wsrf/services/ShibbolethBrowserSession</wsa:To> <wsa:Action soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";>http://loca lhos t:8080/wsrf/services/ShibbolethBrowserSession/Destroy/Destroy</wsa:Actio n> <shibbw:ResourceID soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="1" xmlns:shibbw="http://ShibbolethBrowserSession/ShibbolethBrowserSession.w sdl" >ShibbolethBrowserSessionResource1</shibbw:ResourceID> </soapenv:Header> <soapenv:Body> <wsrf-rlw:Destroy xmlns:wsrf-rlw="http://docs.oasis-open.org/wsrf/2004/11/wsrf-WS-Resource Life time-1.2-draft-04.wsdl"/> </soapenv:Body> </soapenv:Envelope> I have checked all my namespaces and they all look correct. I have even tried it with the "destroy" method removed in the Service class, so it just uses the one defined in the AbstractXXService. Thanks Shahzad -----Original Message----- From: Campana Jr., Salvatore J [mailto:[EMAIL PROTECTED] Sent: 25 March 2005 15:59 To: [email protected] Subject: RE: Destroy a resource... Shazad, Ok I see what is happening now, I needed another set of eyes to see this, and I've added code to print warning to be more explicit in the future... You have a mish-mosh of stuff..... I sent you an email correcting your request based on your wsdl...The request was correct... Upon looking at you classes I see you modified the generated code in that you moved the destroy operation from the AbstractService to the concrete service....In doing so you must have inadvertantly messed up the imports and got a different version of destroy..... Your request (and wsdl) has the 2004/11 namespace: ttp://docs.oasis-open.org/wsrf/2004/11/wsrf-WS-ResourceLifetime-1.2-draf t-04.wsdl But you imported 2004/06 when you moved the method: import org.oasisOpen.docs.wsrf.x2004.x06.wsrfWSResourceLifetime12Draft01.Destro yDocument; So you can either change your request to reflect the correct WSDL namespace, or fix your imports to point to the version you had in your wsdl (probably the better choice to avoid more confusion).... The reason we generate the AbstractService is to avoid these sorts of issues...Typically there is no need to modify the Abstract source.. That being said, this was a good problem and in the future we will be able to see exactly what is going on due to the new log messages I added. Hope this helps... -S -----Original Message----- From: Shahzad Younas [mailto:[EMAIL PROTECTED] Sent: Friday, March 25, 2005 10:14 AM To: [email protected] Subject: RE: Destroy a resource... Hi, Sorry, I must have sent the Factory class by mistake. I've attached the proper service classes this time! I've checked my xmlbeans source and the build xmlbeans jar file and it DOESN'T contain any org.oasis.... It just contains my specific messages that I created. I have definitely got the wsrf-abeans-SNAPSHOT.jar in my classpath. Shahzad -----Original Message----- From: Campana Jr., Salvatore J [mailto:[EMAIL PROTECTED] Sent: 25 March 2005 15:07 To: [email protected] Subject: RE: Destroy a resource... Apache was having issues earlier this week... I noticed the destroy operation is in your ShibbolethBrowserSessionService....You didn't send AbstractShibbolethBrowserSessionService...I'm guessing you moved the operation from the abstract class over to the concrete...I don't think that would make a difference though...but it would be nice to see the abstract if you could send it also (you sent the abstract factory service).... Aside from something strange there, the only other thing I can think of is how you generated.....What does your build.xml (assuming you copied an included sample) look like? The reason I ask is because when generating services, we generate XmlBeans for the types. XmlBeans will generate code for types it doesn't know about, so if wsrf-xbeans-SNAPSHOT.jar was not in the classpath when generating code, then XmlBeans would have regenerated the code for the spec operations...namely Destroy (and others).... Why would this matter? XmlBeans places a static final SchemaType object in the interfaces it generates...Our codebase is compiled against our set, a new set would probably cause issues.... I'm not saying this is WHAT is happening, I'm just saying its possible.... Easy way to see is to look in your generated directory.-->.xmlbeans-->src and look for org.oasis..... If these packages are in this dir, then you regenerated the spec stuff and that may be why you are having issues....Let me know if that is the case.....If it is, make sure when running wsdl2java that the classpath attribute (ant task) is set to the full classpath (we set it up in the init in the build.xml)...That way it gets the wsrf-abeans-SNAPSHOT.jar Next steps: 1. Look to see if org.oasis stuff was generated 2. If so, then fix build.xml classpath issues 3. If not then we need to take it from there...send the AbstractShibbolethBrowserSessionService (though I'm not sure it will make a difference.) -S -----Original Message----- From: Shahzad Younas [mailto:[EMAIL PROTECTED] Sent: Thursday, March 24, 2005 5:44 PM To: [email protected] Subject: Destroy a resource... Hi, I've tried what Stefan has said, and it still doesn't want to work :( The message I send is: SENT MESSAGE ==================== <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Header> <wsa:To soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";>http://loca lhos t:8080/wsrf/services/ShibbolethBrowserSession</wsa:To> <wsa:Action soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";>http://loca lhos t:8080/wsrf/services/ShibbolethBrowserSessionDestroy/Destroy</wsa:Action > <shibbw:ResourceID soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="1" xmlns:shibbw="http://ShibbolethBrowserSession/ShibbolethBrowserSession.w sdl" >ShibbolethBrowserSessionResource1</shibbw:ResourceID> </soapenv:Header> <soapenv:Body> <wsrf-rlw:Destroy xmlns:wsrf-rlw="http://docs.oasis-open.org/wsrf/2004/11/wsrf-WS-Resource Life time-1.2-draft-04.wsdl"/> </soapenv:Body> </soapenv:Envelope> ==================== Attached is my service and wsdl. Thanks for looking over it guys! By the way, is the apache mail server having problems? I keep getting failed reports :( Shahzad -----Original Message----- From: Campana Jr., Salvatore J [mailto:[EMAIL PROTECTED] Sent: 24 March 2005 15:11 To: [email protected] Subject: RE: Destroy a resource... Shazad, Why don't you just attach ShibbolethBrowserSessionService.java AND AbstractShibbolethBrowserSessionService.java to the email so we can see what is going on... Stefan was partially correct...You should look at AbstractShibbolethBrowserSessionService to see if destroy was defined. We generate all the spec operations "plumming" in the Abstract...Service so you (the implementor) can focus primarily on you custom operations (which are generated in the concrete Service class) Send the files and we'll take a look... -S -----Original Message----- From: Stefan Lischke [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 23, 2005 9:15 PM To: [email protected] Subject: Re: Destroy a resource... Hi Shahzad , Just an idea: Is your Service Implementing the ImmediateResourceTerminationPortType Interface? There is the destroy method defined. So your Service has to implement this Interface and use delegater pattern to call this method on the impl. So your Service code should look like this. -- public DestroyResponseDocument destroy( org.oasisOpen.docs.wsrf.x2004.x06.wsrfWSResourceLifetime12Draft01.Destro yDocument requestDoc ) { return new org.apache.ws.resource.lifetime.v1_2_draft01.porttype.impl.ImmediateReso urceTerminationPortTypeImpl( getResourceContext( ) ).destroy( requestDoc ); } -- hope this helps stefan Shahzad Younas wrote: > Hi, > > I am trying to send a message to destroy a resource. My wsdl is attached. > However, when i send the message below to my service, I get the error > below: > What am i doing wrong? I have looked at the examples and I cant see > anything wrong. > I have even looked in my AbstractXXService and I have a destroy method > already defined there. > > Thanks > Shahzad > > SENT MESSAGE > ==================== > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > <soapenv:Header> > <wsa:To soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; > soapenv:mustUnderstand="1" > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";>http://lo > calhost:8080/wsrf/services/ShibbolethBrowserSession</wsa:To > <http://schemas.xmlsoap.org/ws/2004/03/addressing%22%3Ehttp://localhost: 8080/wsrf/services/ShibbolethBrowserSession%3C/wsa:To>> > <wsa:Action > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; > soapenv:mustUnderstand="1" > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";>http://lo > calhost:8080/wsrf/services/ShibbolethBrowserSessionDestroy/Destroy</ws > a:Action > <http://schemas.xmlsoap.org/ws/2004/03/addressing%22%3Ehttp://localhost: 8080/wsrf/services/ShibbolethBrowserSessionDestroy/Destroy%3C/wsa:Action >> > <shibbw:ResourceID > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; > soapenv:mustUnderstand="1" > xmlns:shibbw="http://ShibbolethBrowserSession/ShibbolethBrowserSession > .wsdl">ShibbolethBrowserSessionResource7</shibbw:ResourceID > <http://ShibbolethBrowserSession/ShibbolethBrowserSession.wsdl%22%3ESh > ibbolethBrowserSessionResource7%3C/shibbw:ResourceID>> > </soapenv:Header> > <soapenv:Body> > <wsrl:Destroy > xmlns:wsrl="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLi > fetime-1.2-draft-01.xsd"/ > <http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2- > draft-01.xsd%22/>> > </soapenv:Body> > </soapenv:Envelope> > ==================== > > > DEBUG 2005-03-23 19:54:13,875 > (org.apache.ws.resource.handler.ResourceHandler:123) - Recieved Request > DEBUG 2005-03-23 19:54:13,875 > (org.apache.ws.resource.handler.ResourceHandler:130) - The request > envelope: > <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Header> > <wsa:To > <http://www.w3.org/2001/XMLSchema-instance%22%3E%3Csoapenv:Header%3E%3 > Cwsa:To> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; > soapenv:mustUnderstand="1" xmlns:wsa="http > ://schemas.xmlsoap.org/ws/2004/03/addressing">http://localhost:8080/ws > rf/services/ShibbolethBrowserSession</wsa:To><wsa:Action > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; > soapenv:mustUnderstand="1" > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";>http://lo > calhost:8080/wsrf > <http://schemas.xmlsoap.org/ws/2004/03/addressing%22%3Ehttp://localhos > t:8080/wsrf> > /services/ShibbolethBrowserSessionDestroy/Destroy</wsa:Action><shibbw: > ResourceID soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; > soapenv:mustUnderstand="1" > xmlns:shibbw="http://ShibbolethBrowserSession/ShibbolethBrowserSession > .wsdl">ShibbolethBrowserSessionResource7</shibbw:ResourceID></s > <http://ShibbolethBrowserSession/ShibbolethBrowserSession.wsdl%22%3ESh > ibbolethBrowserSessionResource7%3C/shibbw:ResourceID%3E%3C/s> > oapenv:Header><soapenv:Body><wsrl:Destroy > xmlns:wsrl="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLi > fetime-1.2-draft-01.xsd"/></soapenv:Body></soapenv:Envelope > <http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-dr aft-01.xsd%22/%3E%3C/soapenv:Body%3E%3C/soapenv:Envelope>> > DEBUG 2005-03-23 19:54:13,875 > (org.apache.ws.resource.handler.ResourceHandler:272) - Retrieved > Service Class name: > shibbolethBrowserSession.shibbolethBrowserSessionWsdl.ShibbolethBrowse > rSessionService > from ResourceHome. > DEBUG 2005-03-23 19:54:13,890 > (org.apache.ws.resource.handler.ResourceHandler:403) - Creating an > instance of service class: class > shibbolethBrowserSession.shibbolethBrowserSessionWsdl.ShibbolethBrowserS essionService > DEBUG 2005-03-23 19:54:13,890 > (org.apache.ws.resource.handler.ResourceHandler:351) - Deriving the > service method name from the request: <wsrl:Destroy > xmlns:wsrl="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLife time-1.2-draft-01.xsd" > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelo > pe/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/ > <http://www.w3.org/2001/XMLSchema-instance%22/>> > > javax.xml.rpc.JAXRPCException: Unable to find method destroy with > valid signature in service class > shibbolethBrowserSession.shibbolethBrowserSessionWsdl.ShibbolethBrowserS essionService. > at > org.apache.ws.resource.handler.ResourceHandler.getServiceMethod(Resource Handler.java:374) > at > org.apache.ws.resource.handler.ResourceHandler.handleRequest(ResourceHan dler.java:151) > at > org.apache.ws.resource.handler.axis.ResourceProvider.invoke(ResourceProv ider.java:203) > at > org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j ava:32) > at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) > at > org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:450) > at org.apache.axis.server.AxisServer.invoke(AxisServer.java:285) > at > org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:653) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at > org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.j ava:301) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:214) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) > at > org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCon textValve.java:198) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:152) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :137) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :118) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:102) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:109) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) > at > org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:79 9) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:705) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:57 7) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:684) > at java.lang.Thread.run(Unknown Source) > DEBUG 2005-03-23 19:54:13,906 > (org.apache.ws.resource.handler.axis.ResourceProvider:219) - Fault: > AxisFault > faultCode: > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException > faultSubcode: > faultString: javax.xml.rpc.JAXRPCException: Unexpected error. Cause: > javax.xml.rpc.JAXRPCException: Unable to find method destroy with > valid signature in service class > shibbolethBrowserSession.shibbolethBrowserSessionWsdl.ShibbolethBrowserS essionService. > faultActor: > faultNode: > faultDetail: > > {http://xml.apache.org/axis/}stackTrace:javax.xml.rpc.JAXRPCException: > Unexpected error. Cause: javax.xml.rpc.JAXRPCException: Unable to find > method destroy with valid signature in service class > shibbolethBrowserSession.shibbolethBrowserSessionWsdl.ShibbolethBrowserS essionService. > at > org.apache.ws.resource.handler.ResourceHandler.handleRequest(ResourceHan dler.java:191) > at > org.apache.ws.resource.handler.axis.ResourceProvider.invoke(ResourceProv ider.java:203) > at > org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j ava:32) > at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) > at > org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:450) > at org.apache.axis.server.AxisServer.invoke(AxisServer.java:285) > at > org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:653) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at > org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.j ava:301) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:214) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) > at > org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCon textValve.java:198) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:152) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :137) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :118) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:102) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:109) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) > at > org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:79 9) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:705) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:57 7) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:684) > at java.lang.Thread.run(Unknown Source) > > > >----------------------------------------------------------------------- >- > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > -- My place : http://user.cs.tu-berlin.de/~lischke --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AbstractShibbolethBrowserSessionService.java
Description: Binary data
ShibbolethBrowserSessionService.java
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
