Unsubscribe me
-Original Message- From: Dilova, Tereza (BG) [mailto:[EMAIL PROTECTED]] Sent: 25 April 2002 06:56 To: [EMAIL PROTECTED] Subject: Unsubscribe me Unsubscribe me This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: Mutliple Soap-Containers
What context have you set the rpcrouter servlet to ?? is it the same for all of them? -Original Message- From: David Hirst [mailto:[EMAIL PROTECTED]] Sent: 22 March 2002 12:20 To: [EMAIL PROTECTED] Subject: Mutliple Soap-Containers Is it possible to have multiple applications (ear file) that have a seperate soap-container associated with it. So app1 has it's own soap.war file and app2 has it's own. What I'm running into seems to be that despite adding init parms to the web.xml file and creating a soap.xml file, both application still seem to be using the same underlying registry (each application is also using a different configuration manager) Is this behavior possible? Has anyone accomplished what I'm looking for? Thanks, Dave This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: Mutliple Soap-Containers
Within the ear files meta directory you will have an application.xml file...The soap webapp will be listing in here with a context-root element...Most likely they will all have the same context, guessing that it is set to 'soap' for all of them!! These will need to be different for each ear so that they do not goto the same context -Original Message- From: David Hirst [mailto:[EMAIL PROTECTED]] Sent: 22 March 2002 12:48 To: [EMAIL PROTECTED] Subject: Re: Mutliple Soap-Containers I'm not sure what you mean, so the answer is probably that the context is the same for all of them. How would I go abotu changing this? Colin Saxton wrote: What context have you set the rpcrouter servlet to ?? is it the same for all of them? -Original Message- From: David Hirst [mailto:[EMAIL PROTECTED]] Sent: 22 March 2002 12:20 To: [EMAIL PROTECTED] Subject: Mutliple Soap-Containers Is it possible to have multiple applications (ear file) that have a seperate soap-container associated with it. So app1 has it's own soap.war file and app2 has it's own. What I'm running into seems to be that despite adding init parms to the web.xml file and creating a soap.xml file, both application still seem to be using the same underlying registry (each application is also using a different configuration manager) Is this behavior possible? Has anyone accomplished what I'm looking for? Thanks, Dave This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: HELP : xsi:null=true
Its xsi:nil and not xsi:null for specifying that an element value holds a null value... -Original Message- From: dovle [mailto:[EMAIL PROTECTED]] Sent: 12 March 2002 20:12 To: [EMAIL PROTECTED] Subject: Re: HELP : xsi:null=true Not mentioned: using orion 5.2 apache soap 2.2 And the TestSerializable is registered to the BeanSerializer Please help !!! Problems encontered and don't know if this is apache's fault or I am doing something wrong. I send the message as xml schema 1999 . I have a bean that contains some null values and is serialized like this item xsi:type=n1:test.TestSerializable number xsi:type=xsd:int0/number name xsi:null=true / valid xsi:null=true / testVector xsi:null=true / /item (is part of a Vector, of course) On serverside I get the following exception : faultstringNo mapping found for ':name' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'./faultstring When I send a TestSerizable with a name but with valid == null then I get the same exception, but for :valid . And so on. Does apache soap 2.2 knows to use xsi:null (even if using schema 1999) ? I have tried with schema 2000 and still the same . Or else, what is wrong inhere ? I have no idea. Please , need quick help, deadline comming :o( dovle This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: EJB SOAP
One thing Ihave notice when calling EJBs directlyis that theyare slow compared to using an AccessBean which in-turn calls the EJB...you may want to try it... -Original Message-From: Nortje, Andrew [mailto:[EMAIL PROTECTED]]Sent: 13 March 2002 14:19To: '[EMAIL PROTECTED]'Subject: RE: EJB SOAP Thanks that did it! -Original Message-From: Gayatri Irani [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 5:26 PMTo: [EMAIL PROTECTED]Subject: RE: EJB SOAP Hi... The deployment descriptor looks ok other than the following one line: isd:java class="com.jazzman.contact.ContactManagementBean"/ should be replaced by isd:option key="JNDIName" value="your JNDI name"/ Hope this works, all the best! --- Gayatri IraniPrincipal Software DeveloperCimetrics Inc.www.cimetrics.com [EMAIL PROTECTED] Work: 617.350.7550, Cell:508.740.2888 -Original Message-From: Nortje, Andrew [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 3:55 PMTo: '[EMAIL PROTECTED]'Subject: EJB SOAP Hi SOAP Users I'm real new to Apache SOAP and SOAP/XML in general so forgive the basic questions. I have installed Apache SOAP and run some of the demo's, all working fine. I am now trying to setup a SOAP rpc service for an existing EJB installation I have running under JBoss and Tomcat. What is somewhat confusing is: - The deployment descriptor for the sample ejb has only one create method defined, what about the hello() 'business' method, why is it not in the descriptor? - Where does one define the JNDI name of your EJB, there's place to define the URL and factory for the JNDI but no place for the JNDI name of the EJB. Anyway I deployed my SAOP service fine knowing there are probably some errors in the deployment descriptor and get the following error: [ERROR,Default] = [ERROR,Default] In TemplateProvider.locate() [ERROR,Default] URI: urn:ContactManagement [ERROR,Default] DD.ServiceClass: org.apache.soap.providers.StatelessEJBProvider [ERROR,Default] DD.ProviderClass: com.jazzman.contact.ContactManagementBean [ERROR,Default] Call.MethodName: getContacts [INFO,Default] Exception caught: javax.naming.ServiceUnavailableException: http [Root exception is java.net.UnknownHostException: http] Here is my deployment descriptor ?xml version="1.0"? isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:ContactManagement" isd:provider type="org.apache.soap.providers.StatelessEJBProvider" scope="Application" methods="create getContacts addContact" isd:java class="com.jazzman.contact.ContactManagementBean"/ isd:option key="FullHomeInterfaceName" value="com.jazzman.contact.ContactManagementHome"/ isd:option key="ContextProviderURL" value="http://localhost:1099"/ isd:option key="FullContextFactoryName" value="org.jnp.interfaces.NamingContextFactory"/ /isd:provider isd:faultListenerorg.apache.soap.server.DOMFaultListener/isd:faultListener /isd:service Any ideas what I'm doing wrong or where I can look for answers. Thanks in advance. Andrew This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: Performance problems
I have had these problems with SOAP2.2...I think that it is to do with the way the message is parsed in memory...To get round the problem we moved to using Axis which has all of the functionality that we are using in the Alpha version. -Original Message- From: Juan Gargiulo [mailto:[EMAIL PROTECTED]] Sent: 08 March 2002 02:53 To: [EMAIL PROTECTED] Subject: Performance problems Hi, I'm using the Apache SOAP server under Weblogic 5.1 (sp10), with a stateless SessionEjb service. On the client side I'm using the SOAP client side API. My client loads and sends a string to the server, and the server processes this string. But I'm finding that this is dexterously slow with big strings (20 bytes). According to some measures that I took, the bottleneck is happening on the SOAP server, there is a huge gap between when the client sends the call to the RPC servlet, and the actual method in the EJB is called. 1. Did any of you experienced performance problems with this configuration? 2. Can somebody explain briefly what is going on since the rpcrouter servlet receives the request and the actual method in the EJB is called? Thanks in advance!! juan This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: Soap client threads
Title: Soap client threads Each client thread should create a new instance of the client side SOAPobject...you should have no problems here... (Make sure that you are not using the same SOAP object across threads...that would cause synchronization problems). Java does allow you to have multiple sockets open on multiple threads...(How many depends on how much memory and the OS) -Original Message-From: Beer, Christian [mailto:[EMAIL PROTECTED]]Sent: 06 March 2002 09:43To: '[EMAIL PROTECTED]'Subject: AW: Soap client threads I think for the SOAP toolkit that's no problem. But does Java allow many sockets open from many threads? -Ursprüngliche Nachricht-Von: Michael Weir (Transform Research) [mailto:[EMAIL PROTECTED]]Gesendet: Dienstag, 5. März 2002 22:04An: '[EMAIL PROTECTED]'Betreff: Soap client threads Does the Apache SOAP toolkit allow many client-side threads to concurrently send SOAP messages? I'm trying to build a stress-tester for a server, and want to bash it as hard as possible. Thanks, Michael Weir This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: porting from socket to SOAP
I think you can setup HTTPS with minimal problems using java (jdk1.4 has direct support for https) but I would encourage you to think stateless with your design...once you open a connection to the server you are taking up a valuable resource...if you make it persistant then it is no longer a shared resource making your application less scalable. Your server load would begin to become unmanagible the more users logged in...If it is an intranet application then you should be OK, in some respects. If it is an Internet application then your server is going to die... Unless, I am guessing here, you are leaving the server to manage the backend connections which are swapped from client to client?? Anyway...you could set this up yourself with a servlet. You could connect to the servlet from a java client using the URL.openConnection which would return a URLConnection object...This object would allow you to send input and receive output from the servlet which in turn could sit in a loop retreiving and writing data back to the client... If you would like a sample peice of code showing you how this is done then drop me a mail and I can supply a zip... This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: porting from socket to SOAP
Most implementations of SOAP use HTTP which means the connection is closed after each client request (or possibly closed). This means that any data sent from the server must first come from a client request. It also depends on the nodes that are communicating. To implement effecient communication along the lines of what you want would mean having 2 J2EEcommunicating using message driven beans, a bit like B2B. 1. [A] sends a SOAP request to [B] which is then forwarded to a Message Driven Bean. 2. The bean then periodically sends SOAP updates to [A], you can catch this using any method you like on node [A]. The hard part is once you have received the message on server [A] then you would need to forward this message to the client application a. One way of doing that would be to have the client application become a SocketServer. you could then connect to this from within the J2EE server on node [A] using an EJB as a socketClient (which is permitted in the specifications) and forward the data down the socket... You may ask what you gain from the above setup since you are aready using SOAP?? The biggest advantage would be that you can communicate across the internet with the above example through any fire wall. Another example is that you never have to have a continuous connection. You could make your client application server socket a pooled resource making the code more scalable... Although it does seem overkill and probably harder to setup at first there would be advantages. The reason you have not found anyone doing this yet is because it is only really just being developed to its potential by individual companies...you would be a first! -Original Message-From: Mike Brown [mailto:[EMAIL PROTECTED]]Sent: 28 February 2002 06:36To: [EMAIL PROTECTED]Subject: porting from socket to SOAP Hi, I am currently researching the use of XML based protocols for messaging in an application we currently have that uses TCP/IP sockets. In the application, two programs A and B communicate using sockets. A connects to B and asks B to send asyncronous data updates over the socket. If B terminates, A is notified (uses a select() behavior) and marks the data from B as stale (so it won't be displayed to a user, etc...). I need to keep the functionality of the existing application, but would like to use SOAP if possible as it seems to be the upcoming standard. Any ideas? I know I'm not the first to try to solve this problem, but I can't seem to find the solution posted anywhere. I'm not really sure that sessions or cookies can solve my problem. Thanks! Mike This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: porting from socket to SOAP
With comments like this "This means that any data sent from the server must first come from a client request." (SEEBELOW) you would think that it was Monday morning!! (doh...)my apologies but you get what I mean...(I hope!!) -Original Message-From: Colin Saxton [mailto:[EMAIL PROTECTED]]Sent: 28 February 2002 09:39To: '[EMAIL PROTECTED]'Subject: RE: porting from socket to SOAP Most implementations of SOAP use HTTP which means the connection is closed after each client request (or possibly closed). This means that any data sent from the server must first come from a client request. It also depends on the nodes that are communicating. To implement effecient communication along the lines of what you want would mean having 2 J2EEcommunicating using message driven beans, a bit like B2B. 1. [A] sends a SOAP request to [B] which is then forwarded to a Message Driven Bean. 2. The bean then periodically sends SOAP updates to [A], you can catch this using any method you like on node [A]. The hard part is once you have received the message on server [A] then you would need to forward this message to the client application a. One way of doing that would be to have the client application become a SocketServer. you could then connect to this from within the J2EE server on node [A] using an EJB as a socketClient (which is permitted in the specifications) and forward the data down the socket... You may ask what you gain from the above setup since you are aready using SOAP?? The biggest advantage would be that you can communicate across the internet with the above example through any fire wall. Another example is that you never have to have a continuous connection. You could make your client application server socket a pooled resource making the code more scalable... Although it does seem overkill and probably harder to setup at first there would be advantages. The reason you have not found anyone doing this yet is because it is only really just being developed to its potential by individual companies...you would be a first! -Original Message-From: Mike Brown [mailto:[EMAIL PROTECTED]]Sent: 28 February 2002 06:36To: [EMAIL PROTECTED]Subject: porting from socket to SOAP Hi, I am currently researching the use of XML based protocols for messaging in an application we currently have that uses TCP/IP sockets. In the application, two programs A and B communicate using sockets. A connects to B and asks B to send asyncronous data updates over the socket. If B terminates, A is notified (uses a select() behavior) and marks the data from B as stale (so it won't be displayed to a user, etc...). I need to keep the functionality of the existing application, but would like to use SOAP if possible as it seems to be the upcoming standard. Any ideas? I know I'm not the first to try to solve this problem, but I can't seem to find the solution posted anywhere. I'm not really sure that sessions or cookies can solve my problem. Thanks! MikeThis email and any files transmitted with it are confidential andintended solely for the use of the individual or entity to whomthey are addressed. Any views or opinions are solely those ofthe author and do not necessarily represent those of ExelComputer Systems plc. If you have received this email in errorplease notify Customer Services on 0115 946 0101.
DOM or SAX??
I have had a quick look at the open-source code and have found that it relys mainly on the DOM for the SOAP request and SOAP response... Is there any plans to write an all singing SAX version of the libraries? DOM works fine for small SOAP messages but once you get above 50k you will start to see it slowdown...(especially if one of your passes strings contains XML?!). This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
Carriage returns
Title: RE: compatibility with weblogic 6.1 beta One problem I have noticed with Apache SOAP is that it translates CRLF to just LF when receiving Strings from a Client!! Is this correct?...it does no happen with MS SOAP..it leaves them well alone... You will need to code for this if you are comparing 2 strings to see if they have changed...even though the client does not touch the string it is updated by apache?!?
RE: Exception! java2wsdl tool
It probably cannot see the class you are trying to generate the WSDL against. With most object to wsdl converters you need to put the package name in before the Class name so that it can resolve the class...so... MyClass.class would be mypackage.another.MyClass If you are also asked for a path then you will need to enter the path name to the top package ONLY. so instead of doing the following c:/temp/mypackage/another you would type c:/temp From there it would find the class...I hope this helps -Original Message- From: Joseph George [mailto:[EMAIL PROTECTED]] Sent: 13 June 2001 15:20 To: [EMAIL PROTECTED] Subject: Exception! java2wsdl tool James, i get this exception when i try to run your tool: java org.apache.axis.utils.wsdl.Java2WSDL -c exampleTry.class -e http://localhost:8080/soap/servlet/rpcrouter -n urn:try:exampleTry Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/utils/Options at org.apache.axis.utils.wsdl.Java2WSDL.java2wsdl(Java2WSDL.java) at org.apache.axis.utils.wsdl.Java2WSDL.init(Java2WSDL.java) at org.apache.axis.utils.wsdl.Java2WSDL.main(Java2WSDL.java) there's no class named Options... -Joseph. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, June 13, 2001 3:33 PM Subject: Re: Apache SOAP webservice .NET client I uploaded a pre-pre-alpha version of a java2wsdl tool to the axis-dev mailing list. You can find the jar in the archives... James Birchfield Ironmax maximizing your construction equipment assets 5 Corporate Center 9960 Corporate Campus Drive, Suite 2000 Louisville, KY 40223 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] _ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call 01285 884400. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
IIS and Apache SOAP Client
Apache SOAP client does not work on IIS. IIS sends: ... Content-Type:text/xml; charset=utf-8 ... Where as Apache sends ... Content-Type: text/xml; charset=utf-8 ... Notice the extra space after Content-Type:. An Exception is thrown in the SOAP client (GetAddress example) that states the content type should be text/xml but it is read as ext/xml?? I think this is because of the extra space...has anyone had this problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Advantage of SOAP against RMI ???
I think that the problem lies deeply in the way that developers, in general, program for distributed computing...We should not rely on the top down command running after command approach. We should program using an event model...what I would like to see is applications that fire off a request and then wait for the response/responses which are sent back through another protocol...say for instance SMTP...the responses can then be collated and passed to the client as an event...this event would then signal that the program can continue... I think that the Java Spaces technology is on the brink of a revolution here since it could easily extend the Space interface to include spaces that handled soap requests...you would 1. Place your requests in the space... 2. You would have a soap service that would sit on the space waiting for soap tasks...these would be taken from the space and distributed to a server 3. The soap service would then look at the space once more waiting for tasks that needed to be processed... 4. Meanwhile...SOAP tasks would be processed and then posted back to the soap service which is monitoring the space...all finished tasks would then be placed back in the space when they are received in the finished queue, so to speak... 5. While all this is happening the client can be waiting for the finished tasks to be placed back in the queue...where they would be extracted and processed...the whole process then starts again... The is a better way of handling distributed computing...The technologies that are available for java now could implement this solution with minimal problems. I can not understand why sun haven't already released a toolkit that sits round this implementation??...(if they have then ignore me!) -Original Message- From: Peter Govind [mailto:[EMAIL PROTECTED]] Sent: 05 June 2001 14:35 To: [EMAIL PROTECTED] Subject: RE: Advantage of SOAP against RMI ??? Agree. If you look at the web services articles around at the mo' they seem to paint a picture whereby a client app can access a multitude of web services. Sure that's nice. Then again, in reality the call/invocation is a bit on the expensive side (ie take time) - even on one web service only. Things will definitely get worse once a particular client's 'request' (I use the term loosely here) requires invocation of methods from several different web services spread throughout the inter/intranet. Imagine the time the user has to wait before getting a response! Let's not forget that XML processing does require some CPU cycle (ie waiting time) - this couple with Java (after 6 years and with availability of higher CPU power, still a bit on the slow side) does put a hefty baggage on the concept of one client using several web services. Don't get me wrong, I think SOAP is a great idea. Just make sure you get as many stuff done for one single invocation and have a very patient target audience. From: Colin Saxton [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Subject: RE: Advantage of SOAP against RMI ??? Date: Tue, 5 Jun 2001 11:56:16 +0100 One disadvantage that I have found with SOAP depends on the time taken to execute the SOAP envelope on the server!! You could have a call that could take some time and client will more than likely timeout! Keep in mind when performing tasks that could take over a minute to do them as part of a queuing algorithm. The server can then notify the client using a different protocol to HTTP... To summarise...SOAP over HTTP does not work well when time taken to execute the server process is lengthy...You can extend the client timeout but that in itself can lead to problems... -Original Message- From: Ralf Bierig [mailto:[EMAIL PROTECTED]] Sent: 05 June 2001 10:57 To: [EMAIL PROTECTED] Subject: Advantage of SOAP against RMI ??? Which advantages does SOAP provide compared with RMI? Whats with SOAP - CORBA ?? Whats are the advantages of SOAP against RMI and whats are the disadvantages? Discuss! Thanks, in advance! Ralf __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] _ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call 01285 884400. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] _ Get Your Private, Free E-mail from MSN
