date:20030124

nmukhi  2003/01/24 02:51:43

  Modified:java/doc build.html samples.html
  Log:
  Changed docs to more clearly list dependencies that we don't redistribute;
  also added JMS JAR file to this list.
  
  Revision  ChangesPath
  1.2   +9 -8  xml-axis-wsif/java/doc/build.html
  
  Index: build.html
  ===
  RCS file: /home/cvs/xml-axis-wsif/java/doc/build.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- build.html14 Jan 2003 14:19:08 -  1.1
  +++ build.html24 Jan 2003 10:51:43 -  1.2
  @@ -51,13 +51,14 @@
   
   Building WSIF by using provided scripts and JAR files
   If you downloaded the source distribution you need to make sure you have all prerequisite jars available under their respective 
subdirectories within the lib directory; the README files in each subdirectory will 
point you to a location where you can download the jar.
  -If you downloaded the binary distribution, most of necessary jar files are 
already included in lib directory. You will 
  -only need to download activation.jar and put it into lib/activation 
  -(see README), mail.jar and put 
  -it into lib/javamail  (see 
  -README) and optionally j2ee.jar or other jar file with J2EE APIs (see 
  -README) to compile EJB and JCA providers (all of those files must be 
  -downloaded separately as they can not be distributed).
  +Most of necessary jar files are already included in lib directory (we 
redistribute what we can). You will only need to download the following and put them 
into the lib/ directory.
  +
  +activation.jar
  +mail.jar
  +jms.jar
  +j2ee.jar; if you plan to download this it includes the above three so 
you won't need to download those separately.
  +
  +The dependency README tells you where you can 
download these from and also how they are used, so you can decide for yourself which 
JARs you really need.
   
   Then use build script (./build.sh on UNIX or build.bat on Windows) to 
   rebuilt WSIF (see list of targets above).
  
  
  
  1.8   +9 -10 xml-axis-wsif/java/doc/samples.html
  
  Index: samples.html
  ===
  RCS file: /home/cvs/xml-axis-wsif/java/doc/samples.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- samples.html  23 Jan 2003 12:40:17 -  1.7
  +++ samples.html  24 Jan 2003 10:51:43 -  1.8
  @@ -15,16 +15,15 @@
   JAR files and set CLASSPATH to contain both WSIF jar files and
   required JAR files. If you use binary distribution of WSIF most of JAR
   files is already provided and classpath script can be used to set
  -CLASSPATH.  You will only need to download activation.jar
  -and put it into lib/ (see README), mail.jar
  -and put it into lib/  (see README) and
  -optionally j2ee.jar or other jar file with J2EE APIs and put it
  -into lib/ (see README). All
  -of those files must be downloaded separately as they can not be
  -distributed. j2ee.jar is required if you would like to compile EJB,
  -JCA or JMS providers or run samples that use those providers.
  +CLASSPATH.  We redistribute as many of the required JARs as we can; you will 
only need to download the following and put them into the lib/ directory.
  +
  +activation.jar
  +mail.jar
  +jms.jar
  +j2ee.jar; if you plan to download this it includes the above three so 
you won't need to download those separately.
  +
  +The dependency README tells you where you can 
download these from and also how they are used, so you can decide for yourself which 
JARs you really need.
  +
   Once you have the necessary jar files, to run samples
   you can simply call classpath script (on Windows use
   classpath.bat on UNIX use source classpath.csh if you use TCSH or

cvs commit: xml-axis-wsif/java/doc build.html samples.html

nmukhi  2003/01/24 02:52:59

  Modified:java/doc build.html samples.html
  Log:
  Fixed minor HTML error
  
  Revision  ChangesPath
  1.3   +2 -2  xml-axis-wsif/java/doc/build.html
  
  Index: build.html
  ===
  RCS file: /home/cvs/xml-axis-wsif/java/doc/build.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- build.html24 Jan 2003 10:51:43 -  1.2
  +++ build.html24 Jan 2003 10:52:59 -  1.3
  @@ -51,7 +51,7 @@
   
   Building WSIF by using provided scripts and JAR files
   If you downloaded the source distribution you need to make sure you have all prerequisite jars available under their respective 
subdirectories within the lib directory; the README files in each subdirectory will 
point you to a location where you can download the jar.
  -Most of necessary jar files are already included in lib directory (we 
redistribute what we can). You will only need to download the following and put them 
into the lib/ directory.
  +Most of necessary jar files are already included in lib directory (we 
redistribute what we can). You will only need to download the following and put them 
into the lib/ directory.
   
   activation.jar
   mail.jar
  
  
  
  1.9   +1 -1  xml-axis-wsif/java/doc/samples.html
  
  Index: samples.html
  ===
  RCS file: /home/cvs/xml-axis-wsif/java/doc/samples.html,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- samples.html  24 Jan 2003 10:51:43 -  1.8
  +++ samples.html  24 Jan 2003 10:52:59 -  1.9
  @@ -15,7 +15,7 @@
   JAR files and set CLASSPATH to contain both WSIF jar files and
   required JAR files. If you use binary distribution of WSIF most of JAR
   files is already provided and classpath script can be used to set
  -CLASSPATH.  We redistribute as many of the required JARs as we can; you will 
only need to download the following and put them into the lib/ directory.
  +CLASSPATH.  We redistribute as many of the required JARs as we can; you will 
only need to download the following and put them into the lib/ directory.
   
   activation.jar
   mail.jar

cvs commit: xml-axis-wsif/java/doc build.html

nmukhi  2003/01/24 02:56:31

  Modified:java/doc build.html
  Log:
  Removed reference to lib subdirectories since we have changed lib structure
  
  Revision  ChangesPath
  1.4   +2 -3  xml-axis-wsif/java/doc/build.html
  
  Index: build.html
  ===
  RCS file: /home/cvs/xml-axis-wsif/java/doc/build.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- build.html24 Jan 2003 10:52:59 -  1.3
  +++ build.html24 Jan 2003 10:56:31 -  1.4
  @@ -50,8 +50,7 @@
 tests: Build tests
   
   Building WSIF by using provided scripts and JAR files
  -If you downloaded the source distribution you need to make sure you have all prerequisite jars available under their respective 
subdirectories within the lib directory; the README files in each subdirectory will 
point you to a location where you can download the jar.
  -Most of necessary jar files are already included in lib directory (we 
redistribute what we can). You will only need to download the following and put them 
into the lib/ directory.
  +If you downloaded the source distribution you need to make sure you have all prerequisite jars available under the lib/ 
directory. Most of the necessary jar files are already included in lib directory (we 
redistribute what we can). You will only need to download the following and put them 
into the lib/ directory.
   
   activation.jar
   mail.jar

Is this a bug ?

2003-01-24 Thread Claus Nyhus Christensen


Hi

I am trying to create a simple handler which alters the content of the
SOPABody of an incoming SOAP message.

The web service I am using is a simple "echo" web service with a single
method called echo. The methods takes a string and just returns it.

The code for the handler is as follows:

package com.trifork.eas.test.webservices.echoservice;

import java.io.*;
import java.io.InputStream;
import java.util.*;
import java.util.Iterator;

import javax.xml.namespace.QName;
import javax.xml.rpc.handler.*;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.*;
import javax.xml.soap.SOAPMessage;
import javax.xml.transform.stream.*;

/**
 * Created: Jan 20, 2003
 *
 * @author Claus Nyhus Christensen <[EMAIL PROTECTED]>
 */
public class EchoServiceServerHandler implements Handler {

  public boolean handleRequest(MessageContext messageContext) {

try {
  SOAPMessageContext soapMsgCtx = (SOAPMessageContext)
messageContext;
  SOAPMessage soapMsg = soapMsgCtx.getMessage();
  SOAPPart soapPart = soapMsg.getSOAPPart();
  SOAPEnvelope soapEnvelope = soapPart.getEnvelope();
  soapEnvelope.getBody().detachNode();
  SOAPBody soapBody = soapEnvelope.addBody();
  SOAPBodyElement echoElement =
soapBody.addBodyElement(soapEnvelope.createName("echo", "ns1",
"http://soapinterop.org/";));
  SOAPElement argElement = echoElement.addChildElement("arg0");
  argElement =
argElement.addAttribute(soapEnvelope.createName("type", "xsi",
"http://www.w3.org/2001/XMLSchema-instance";), "xsd:string");
argElement.addTextNode("a new string");
soapMsg.saveChanges();

} catch (Exception e) {
  e.printStackTrace();
}

return true;
  }

...

}

Now, when my client tries to call the web service, I get the following
exception:

AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: java.lang.Exception: No deserialization context to use in
MessageElement.getValueAsType()!
 faultActor: null
 faultNode: null
 faultDetail: 
stackTrace: java.lang.Exception: No deserialization context to
use in
MessageElement.getValueAsType()!
at
org.apache.axis.message.MessageElement.getValueAsType(MessageElement.java:544)
at
org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:150)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:332)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:469)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:326)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:782)


I have been looking into the code, and it seems that the way the
original SOAPBody is build is different from the way it is done when you
use the JAXM methods on the SOAPBody class.

I have tried the same example using the JAXRPC/SAAJ reference
implementations and it works just fine there.

To me it seems that:

1. I am doing something completely wrong in my handler
or
2. The addBodyElement on the SOAPBody class is not working as is should

If you agree with me that number 2 is the case, I would like to help
create a fix. But I cannot figure out how I am going to be able to get a
DeserializationContext in the SOAPBody class.

A related problem occur if you use the addChildElement on SOAPBody
instead of addBodyElement. When you do this a new MessageElement is
added to the SOAPBody. However, this will result in a ClassCastException
in the processMessage of the RPCProvider class. Line 141 and 142 gives
the problem:
if (!(bodies.get(bNum) instanceof RPCElement)) {
SOAPBodyElement bodyEl = (SOAPBodyElement)bodies.get(bNum);

Since the MessageElement is not an instance of RPCElement, it is cast to
a SOAPBodyElement. This will result in the ClassCastException. This case
also works fine on the JAXRPC/SAAJ reference implementation.

The fix seems to be to overwrite the addChildElement methods in SOAPBody
(which it inherits from MessageElement) to make sure that
SOAPBodyElements (or maybe RPCElement) are always added. However, this
fix will have the same problem with the DeserializationContext as stated
above.


I hope this mail was not to long, and was posted to the right
mailinglist :)

Cheers

-- 
Claus Nyhus Christensen
Software Engineer, M. Sc. CS.

Trifork, Margrethepladsen 3, DK-8000 ?rhus C, Denmark
Phone: +45 8732 8787 / Fax: +45 8732 8788 / http://www.trifork.com

Re: code sample: Simple LDAP Authentication.

Alex,

Thanks. Any help is welcome. Please follow instructions mentioned here
(http://nagoya.apache.org/wiki/apachewiki.cgi?SubmitPatches) to sumbit an enchancement 
request in
bugzilla. Please consider adding a few html docs to help people use the new code and 
some test
cases to make sure that subsequent check-ins don't break the code.

-- dims

--- SKRZYNIARZ Alexandre <[EMAIL PROTECTED]> wrote:
> Hello.
> 
> I'm a PhD student at ENST Bretagne (france), and I want to thank you for developping 
>axis.
> 
> I have written a LDAP Simple Authentication Handler (and the corresponding LDAP 
>Security
> Provider) based on the SimpleAuthenticationHandler and the SimpleSecurityProvider.
> 
> If you think my handler could be of some use, I would be glad to submit it to
> the axis project.
> 
> Best regards.
> 
> -- 
> Alex.S

=
Davanum Srinivas - http://xml.apache.org/~dims/

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: Is this a bug ?

Claus,

Can you please submit a stripped down test that we can use to recreate the problem and 
log it as a
bug in bugzilla?

Thanks,
dims

--- Claus Nyhus Christensen <[EMAIL PROTECTED]> wrote:
> 
> Hi
> 
> I am trying to create a simple handler which alters the content of the
> SOPABody of an incoming SOAP message.
> 
> The web service I am using is a simple "echo" web service with a single
> method called echo. The methods takes a string and just returns it.
> 
> The code for the handler is as follows:
> 
> package com.trifork.eas.test.webservices.echoservice;
> 
> import java.io.*;
> import java.io.InputStream;
> import java.util.*;
> import java.util.Iterator;
> 
> import javax.xml.namespace.QName;
> import javax.xml.rpc.handler.*;
> import javax.xml.rpc.handler.soap.SOAPMessageContext;
> import javax.xml.soap.*;
> import javax.xml.soap.SOAPMessage;
> import javax.xml.transform.stream.*;
> 
> /**
>  * Created: Jan 20, 2003
>  *
>  * @author Claus Nyhus Christensen <[EMAIL PROTECTED]>
>  */
> public class EchoServiceServerHandler implements Handler {
> 
>   public boolean handleRequest(MessageContext messageContext) {
> 
> try {
>   SOAPMessageContext soapMsgCtx = (SOAPMessageContext)
> messageContext;
>   SOAPMessage soapMsg = soapMsgCtx.getMessage();
>   SOAPPart soapPart = soapMsg.getSOAPPart();
>   SOAPEnvelope soapEnvelope = soapPart.getEnvelope();
>   soapEnvelope.getBody().detachNode();
>   SOAPBody soapBody = soapEnvelope.addBody();
>   SOAPBodyElement echoElement =
> soapBody.addBodyElement(soapEnvelope.createName("echo", "ns1",
> "http://soapinterop.org/";));
>   SOAPElement argElement = echoElement.addChildElement("arg0");
>   argElement =
> argElement.addAttribute(soapEnvelope.createName("type", "xsi",
> "http://www.w3.org/2001/XMLSchema-instance";), "xsd:string");
> argElement.addTextNode("a new string");
> soapMsg.saveChanges();
> 
> } catch (Exception e) {
>   e.printStackTrace();
> }
> 
> return true;
>   }
> 
> ...
> 
> }
> 
> Now, when my client tries to call the web service, I get the following
> exception:
> 
> AxisFault
>  faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>  faultSubcode: 
>  faultString: java.lang.Exception: No deserialization context to use in
> MessageElement.getValueAsType()!
>  faultActor: null
>  faultNode: null
>  faultDetail: 
> stackTrace: java.lang.Exception: No deserialization context to
> use in
> MessageElement.getValueAsType()!
> at
> org.apache.axis.message.MessageElement.getValueAsType(MessageElement.java:544)
> at
> org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:150)
> at
> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:332)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
> at
> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:469)
> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:326)
> at
> org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:782)
> 
> 
> I have been looking into the code, and it seems that the way the
> original SOAPBody is build is different from the way it is done when you
> use the JAXM methods on the SOAPBody class.
> 
> I have tried the same example using the JAXRPC/SAAJ reference
> implementations and it works just fine there.
> 
> To me it seems that:
> 
> 1. I am doing something completely wrong in my handler
> or
> 2. The addBodyElement on the SOAPBody class is not working as is should
> 
> If you agree with me that number 2 is the case, I would like to help
> create a fix. But I cannot figure out how I am going to be able to get a
> DeserializationContext in the SOAPBody class.
> 
> A related problem occur if you use the addChildElement on SOAPBody
> instead of addBodyElement. When you do this a new MessageElement is
> added to the SOAPBody. However, this will result in a ClassCastException
> in the processMessage of the RPCProvider class. Line 141 and 142 gives
> the problem:
> if (!(bodies.get(bNum) instanceof RPCElement)) {
> SOAPBodyElement bodyEl = (SOAPBodyElement)bodies.get(bNum);
> 
> Since the MessageElement is not an instance of RPCElement, it is cast to
> a SOAPBodyElement. This will result in the ClassCastException. This case
> also works fine on the JAXRPC/SAAJ reference implementation.
> 
> The fix seems to be to overwrite the addChildElement methods in SOAPBody
> (which it inherits from MessageElement) to make sure that
> SOAPBodyElements (or maybe RPCElement) are always added. However, this
> fix will have the same problem with the DeserializationContext as stated
> above.
> 
> 
> I hope this mail was not to long, and was posted to the r

cvs commit: xml-axis-wsif/java/samples/jms README.html

2003-01-24 Thread aslom

aslom 2003/01/24 06:20:43

Modified:java/samples/ejb README.html
java/samples/ejb/service/deploy/jboss README.html
java/samples/jms README.html
Log:
updated samples documentation

Revision ChangesPath
1.4 +4 -3 xml-axis-wsif/java/samples/ejb/README.html

Index: README.html
===
RCS file: /home/cvs/xml-axis-wsif/java/samples/ejb/README.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- README.html 16 Jan 2003 18:05:06 - 1.3
+++ README.html 24 Jan 2003 14:20:43 - 1.4
@@ -11,12 +11,13 @@
Web Services Invocation Framework:
EJB Sample
This sample aims to demonstrate the invocation of an EJB through WSIF's API.
This means that an EJB is exposed as a first class WSDL-described service using the EJB binding extensions defined
in WSIF.
-In this particular sample, we describe an AddressBook service, a common example
in various Web services toolkits. For those unfamilar with it, this service offers a
port type with three operations. Two of the operations add an entry to the address
book, using slightly different styles for providing input information. The third
operation queries the address book with a name. The service uses complex schema types
for representing an address and a phone number.
+In this particular sample, we describe an AddressBook service, a common example
in various Web services toolkits. For those
+unfamiliar with it, this service offers a port type with three operations. Two of
the operations add an entry to the address book, using slightly different styles for
providing input information. The third operation queries the address book with a name.
The service uses complex schema types for representing an address and a phone
number.
The abstract functionality is tied to an EJB binding that describes how a
stateful session bean supports the abstract port type defined. It is worth emphasizing
that this isn't a standard WSDL binding, instead it exploits WSDL's extensibility to
describe how to access the abstract functionality when it is deployed and available on
an EJB. You will notice that the element in the AddressBook WSDL refers to an initial context factory that
gets used by WSIF's EJB provider. The classpath specified here is vendor specific and
will need to be changed depending on your particular deployment, we have provided
instructions in the service deployment documentation we link to below.
The WSDL file is in this sample directory; this
has the EJB binding.
Here's how this service is implemented. We
also describe how to deploy the EJB on a J2EE platform of your choice.
Here's how to invoke this service
dynamically using WSIF's dynamic invocation interface (DII).
Here's how to invoke this service by first
generating the stub interface and using this directly through WSIF's dynamic proxy,
thus hiding all WSIF specifics from the client code. Note that the stub interface used
is the the service interface as defined by the JAX-RPC specification.
-Deployment of an EJB as well as acessing and using it is vendor-specific. We
have included instructions for deploying and using this sample in particular app
server environments; even if your favorite app server isn't part of our list, we have
provided enough documentation so that it should not be hard to run this sample in a
different environment.
+Deployment of an EJB as well as accessing and using it is vendor-specific. We
have included instructions for deploying and using this sample in particular app
server environments; even if your favorite app server isn't part of our list, we have
provided enough documentation so that it should not be hard to run this sample in a
different environment.

-
+
\ No newline at end of file

1.2 +3 -3 xml-axis-wsif/java/samples/ejb/service/deploy/jboss/README.html

Index: README.html
===
RCS file: /home/cvs/xml-axis-wsif/java/samples/ejb/service/deploy/jboss/README.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.html 16 Jan 2003 18:06:17 - 1.1
+++ README.html 24 Jan 2003 14:20:43 - 1.2
@@ -13,9 +13,9 @@

Deploying the sample:
We have included in this directory a pre-packaged jar that contains the compiled
beans and the configuration files required by JBoss. All you need to deploy to JBoss
is to drop this addressbook JAR file for JBoss (assuming
you use the default server configuration) into server/default/deploy under
your JBoss server installation, and start your server. This has been tested with JBoss
version 3.0.4 running on Windows 2000, with the sample client running on Windows 2000
and using WSIF in a Java 1.4.1 environment.
-Conf

update requested on security alert

2003-01-24 Thread Kari Whitcomb

Back in November a security alert was posted on this list.  I'm looking 
for an update on the status of this problem.  The description of the 
problem was posted as:

Summary: Using the DTD part of the XML document, it is possible to cause 
the XML parser to consume 100% CPU and/or a lot of  memory, therefore 
resulting in a denial of service condition.

A link to the previous thread on this topic: 
http://marc.theaimsgroup.com/?l=axis-dev&m=103838167718099&w=2

Has there been any work done to correct this vulnerability?  Is there an 
expected release which will have the fix (if it is not currently available)?

Thanks,
Kari Whitcomb

cvs commit: xml-axis-wsif/java/doc release_notes_2_0.html

nmukhi  2003/01/24 06:42:59

  Added:   java/doc release_notes_2_0.html
  Log:
  Release notes for 2.0
  
  Revision  ChangesPath
  1.1  xml-axis-wsif/java/doc/release_notes_2_0.html
  
  Index: release_notes_2_0.html
  ===
  
  
  Apache WSIF 2.0 Release Notes
  
 
 
  
  
  Release Notes
  These are the release notes for Apache WSIF 2.0.
  
  WSIF (the "Web Services Invocation Framework") is a WSDL-based API for invoking 
WSDL-described services. It has a pluggable architecture with protocol-specific 
"providers" to handle invocations according to a specific protocol.
  
  Apache WSIF 2.0 comes bundled with providers for SOAP (using Apache SOAP or 
Axis), local java classes, EJBs, JMS services and applications accessible via Java 
Connectors. WSIF also describes the specific WSDL extensions used to make these kinds 
of applications accessible as WSDL-described services.
  
  Here is a list of *recent* changes to Apache WSIF (note that this is the first 
release, so this list of changes is not particularly illuminating).
  
  
  Changes to Apache WSIF
  
  
  
  1/24/04: built RC4 release (tagged as WSIF_2_0_RC4)
  1/23/04: built RC3 release (tagged as WSIF_2_0_RC3)
  
  added JCA sample
  
  fixed bugs:
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13646";>13646 
WSIFOperation_ApacheAxis fails to set up Call's Parameter list
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15134";>15134  AXIS 
provider requires mail.jar and acivation.jar even when not using attachements
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15578";>15578  WSIF 
incorrectly handles returned attachment from service
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15691";>15691  errors 
in docs
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15780";>15780  WSIF 
stub invocation for doc style with unwrapped parts don't work
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15837";>15837  
Attachments fail if in the wrong order
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16041";>16041  There 
is no way to override the default (de)serializers used by the WSIF AXIS provider
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16196";>16196  WSIF 
AXIS provider performance unacceptable
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16197";>16197  axis 
provider messaging with attachments don't work
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16199";>16199  
response soap headers not passed to WSIF client
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16199";>16199  WSIF 
AXIS provider no longer supports jms:property parts in the input message
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16256";>16256  WSIF 
AXIS Operation uses incorrect encoding style
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16271";>16271  
WSIFUtils method initializeProviders should be public
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16334";>16334  WSIF 
NPE for a document style service which is not wrapped
  
  
  updated FAQ
  added DSL provider sample to demonstrate how WSIF
  can be used ot interact with many services each potentially implemented with
  different protocol (EJB, JMS, SOAP, ...).
  added JMS sample to demonstrate how WSIF
  can be used to interacts with software accessible through the JMS API.
  
  12/20/02: built RC1 release (tagged as WSIF_2_0_RC1): new samples 
(multibinding,
  customfactory),
  misc. updates to documentation and samples
  
  built BETA1 release (tagged as WSIF_2_0_BETA1):
  improvements to documentation that is now split in smaller pieces that
  are better fitting into http://xml.apache.org/axis/wsif/";>
  http://xml.apache.org/axis/wsif/ websiteadded EJB sample with documentation 
and pre-packaged jar
  for deployment in JBoss 
  
  built ALPHA2 release (tagged as WSIF_2_0_ALPHA2)
  
  changed release packaging: there are now three different release builds:
  
  
  src: only source file (no binaries) - essentially all that is needed
  to compile WSIF if you downloaded all required jar files
  bin: only binaries: just download few jar files that can not be 
distributed
  and you are ready to run WSIF (no source code except for samples)
  all = bin + src
  
  
  included samples to demonstrate invocation of SOAP service, local java and 
service with complex types and documentation for samples.
  
  
  documentation changes
  factored out readme.htm1 into smaller pieces that are 
put in doc/ (like cvs and requirements)
  updated doc/ with factored out info about cvs and requirements and improved build 
instructions,
  moved wsdl_extensions to doc/ from README_files,
  simplified wsif.css (much less colors, easier to read ...)
  
  preparing first official release: added 
  RELEASE_TASKS.txtwork on first alpha release
  
  
  
  
  
  
  
  
   
  
  Nirmal Mukhi,
  http://www.extreme.indiana.edu/~aslom/";>Aleksander Slominski
  Last modified: $Id: release_not

cvs commit: xml-axis-wsif/java build.xml

nmukhi  2003/01/24 07:00:13

  Modified:java build.xml
  Log:
  Changed release tag to RC4
  
  Revision  ChangesPath
  1.30  +1 -1  xml-axis-wsif/java/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/xml-axis-wsif/java/build.xml,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- build.xml 22 Jan 2003 21:18:47 -  1.29
  +++ build.xml 24 Jan 2003 15:00:13 -  1.30
  @@ -48,7 +48,7 @@
   
   
   
  -
  +

[wsif] testing RC3

hi,

i have tested all samples on windows 2000 and what i could on solaris (i 
did not have JBoss or other app server installed on Solaris so i did not 
check JMS and EJB samples) and i have checked in small updates to 
documentation

i could get JCA sample to work on windows (after adding one directory to 
CLASSPATH) but not on solaris and even on windows it produced lot of 
output with stack traces but printed expected result (below).

thanks,

alek

ps. here is how to run JCA sample: with normal classpath it does not work:

C:\tmp\WSIF\wsif-2.0rc3>classpath
build\lib\wsif.jar;build\lib\wsif-j2c.jar;build\classes;build\samples;build\tests;lib\xmlParserAPIs-
2_2_1.jar;lib\xercesImpl-2_2_1.jar;lib\wsdl4j-20021124.jar;lib\soaprmi-1_1.jar;lib\servlet-2_2.jar;l
ib\saaj-1_1.jar;lib\qname-from-wsdl4j-20021124.jar;lib\optional-1_5_1.jar;lib\myeis.jar;lib\log4j-1_
2_4.jar;lib\junit-3_8_1.jar;lib\jms-1_1.jar;lib\jaxrpc-1_1.jar;lib\j2ee-1_3_1.jar;lib\commons-loggin
g.jar;lib\commons-discovery.jar;lib\axis-1_0.jar;lib\axis-1_0-ant.jar;lib\apache_soap-2_3_1.jar;lib\
ant-1_5_1.jar;

C:\tmp\WSIF\wsif-2.0rc3>java com.myeis.customer.J2C_MyEIS_CustomerInfoProxy
Exception in thread "main" java.lang.NoClassDefFoundError:
com/myeis/customer/J2C_MyEIS_CustomerInfoProxy



to fix it it is necessary to add build\samples\jca\customer 
(which is a bit strange to do - why it is not compiled into build/samples?) 
and then after lot of stack traces it prints expected output 

C:\tmp\WSIF\wsif-2.0rc3>set
CLASSPATH=%CLASSPATH%;build\samples\jca\customer

C:\tmp\WSIF\wsif-2.0rc3>java com.myeis.customer.J2C_MyEIS_CustomerInfoProxy
java.io.FileNotFoundException:
C:\tmp\WSIF\wsif-2.0rc3\config\security.properties (The system cannot
find the path specified)
   at java.io.FileInputStream.open(Native Method)
   at java.io.FileInputStream.(FileInputStream.java:103)
   at
com.sun.enterprise.util.Utility.getPropertiesFromFile(Utility.java:42)
   at com.sun.enterprise.iiop.POAEJBORB.(POAEJBORB.java:78)
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:207)
   at org.omg.CORBA.ORB.create_impl(ORB.java:306)
   at org.omg.CORBA.ORB.init(ORB.java:345)
   at
com.sun.enterprise.util.ORBManager.createORB(ORBManager.java:138)
   at com.sun.enterprise.util.ORBManager.init(ORBManager.java:65)
   at
com.sun.enterprise.naming.SerialInitContextFactory.(SerialInitContextFactory.java:3

1)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
   at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:

39)
   at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorIm

pl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
   at java.lang.Class.newInstance0(Class.java:296)
   at java.lang.Class.newInstance(Class.java:249)
   at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
   at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
   at javax.naming.InitialContext.init(InitialContext.java:219)
   at javax.naming.InitialContext.(InitialContext.java:175)
   at
org.apache.wsif.providers.jca.WSIFUtils_JCA.lookupConnectionFactory(Unknown

Source)
   at
com.myeis.wsif.providers.j2c.myeis.WSIFProvider_MyEIS.createDynamicWSIFPort(Unknown

Sourc
e)
   at
org.apache.wsif.base.WSIFServiceImpl.createDynamicWSIFPort(Unknown Source)
   at org.apache.wsif.base.WSIFServiceImpl.getPort(Unknown Source)
   at
com.myeis.customer.J2C_MyEIS_CustomerInfoProxy.execute(Unknown Source)
   at
com.myeis.customer.J2C_MyEIS_CustomerInfoProxy.getCustomer(Unknown Source)
   at com.myeis.customer.J2C_MyEIS_CustomerInfoProxy.main(Unknown
Source)
java.io.FileNotFoundException:
C:\tmp\WSIF\wsif-2.0rc3\config\ejb.properties (The system cannot find
the path specified)
   at java.io.FileInputStream.open(Native Method)
   at java.io.FileInputStream.(FileInputStream.java:103)
   at
com.sun.enterprise.util.Utility.getPropertiesFromFile(Utility.java:42)
   at
com.sun.enterprise.iiop.J2EEInitializer.(J2EEInitializer.java:54)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
   at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:

39)
   at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorIm

pl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
   at java.lang.Class.newInstance0(Class.java:296)
   at java.lang.Class.newInstance(Class.java:249)
   at
com.sun.corba.ee.internal.Interceptors.PIORB.registerORBInitializers(PIORB.java:377)

   at
com.sun.corba.ee.internal.Interceptors.PIORB.parseProperties(PIORB.java:347)

   at
com.sun.corba.ee.internal.TxPOA.TxPIORB.parseProperties(TxPIORB.java:116)
   at com.sun.corb

[wsif] running JCA sample

[EMAIL PROTECTED] wrote:


sorry I could not attend the chat, had an emergency. It looks really good,
hopefully will be done shortly. One clarification about JCA sample -
the connector is _not_ intended to be run inside J2EE server as a managed
component. It can only be run in so called
non managed environment (on purpose, this is not a Connector Architecture
sample) where it needs only j2ee.jar, a library from Sun, therefore
WebSphere or JBoss environment is a moot point and should not be mentioned
anywhere.
Also, the statement to that effect is already the jca sample's readme: ("
Because of the minimal implementation, the Resource Adapter cannot be
deployed in the managed environment of the J2EE Application Server, only
the non-managed use is supported.").
 

hi Piotr,

i have done exactly this (no app server such as JBoss) but had some 
errors and it did work on windows 2000 but not on solaris.

could you take look on what i have got when i ran JCA sample (i have 
posted it in separate email)?  i do not understand much from sample 
description in samples/jca/README.html as it does not include enough 
details how to set classpath and i am not sure if maybe i should have 
set something more to get it to run smoothly?

thanks,

alek

--
"Mr. Pauli, we in the audience are all agreed that your theory is crazy. 
What divides us is whether it is crazy enough to be true." Niels H. D. Bohr

[wsif] Unit tests run against an Axis server

2003-01-24 Thread Mark Whitlock

I have enabled the WSIF unit tests to run against an Axis server.

To run the tests against an axis server, find the deploy.wsdd file for each
backend service in the test subdirectories. Deploy it using
org.apache.axis.client.AdminClient deploy.wsdd. Then in
wsif.test.properties set wsif.soapserver=axis. If not set, wsif.soapserver
defaults to soap. Also set
wsif.jms2httpbridge.httpurl=http://localhost:8080/axis/services and the
JMS2HTTPBridge will send requests to this URL appended with the service
name.

Of the approx 300 tests, currently 11 fail against an axis server. Of
these, 9 are in the InoutTest and 2 are in the MessagingAttachmentsTest.
These failures will be investigated.

When writing tests, every SOAPPort needs to have a corresponding AXISPort,
which can be chosen depending on the value of TestUtilities.getSoapServer
(). SOAPJMSPorts are driven for both soap and axis servers.

Enjoy!
Mark
Mark Whitlock, WSIF development, IBM Hursley

DO NOT REPLY [Bug 16396] New: - Calendar serializer has incorrect functionality

2003-01-24 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16396

Calendar serializer has incorrect functionality

   Summary: Calendar serializer has incorrect functionality
   Product: Axis
   Version: 1.0
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Critical
  Priority: Other
 Component: Serialization/Deserialization
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Calendar serializer has incorrect functionality:

It always serialize a Calendar instance to a string with UTC time zone.
Why the concrete time zone value from calendar instance is not serialized?

DO NOT REPLY [Bug 16396] - Calendar serializer has incorrect functionality

2003-01-24 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16396

Calendar serializer has incorrect functionality

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-01-24 16:20 ---
This is working as intended, the time is always serialized in UTC.
Please search previous bugzilla reports and the mailing list for historical 
discussion on this topic.

WSIF to get its own mailing list?

2003-01-24 Thread Tom Jordahl


Since the WSIF project is increasingly active, isn't it time for you guys to get your 
own mailing list?  That would decrease the "noise" on axis-dev.

Hey, we love you, but its time to leave the nest! :-)

--
Tom Jordahl
Macromedia Server Development

RE: update requested on security alert

2003-01-24 Thread Tom Jordahl


This was fixed in the Axis source code and is available in the latest CVS tree or the 
Axis 1.1 beta release.

--
Tom Jordahl
Macromedia Server Development



-Original Message-
From: Kari Whitcomb [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 9:20 AM
To: [EMAIL PROTECTED]
Subject: update requested on security alert


Back in November a security alert was posted on this list.  I'm looking 
for an update on the status of this problem.  The description of the 
problem was posted as:

Summary: Using the DTD part of the XML document, it is possible to cause 
the XML parser to consume 100% CPU and/or a lot of  memory, therefore 
resulting in a denial of service condition.

A link to the previous thread on this topic: 
http://marc.theaimsgroup.com/?l=axis-dev&m=103838167718099&w=2

Has there been any work done to correct this vulnerability?  Is there an 
expected release which will have the fix (if it is not currently available)?

Thanks,
Kari Whitcomb

[wsif] mailing list for WSIF [Re: WSIF to get its own mailing list?]

Tom Jordahl wrote:


Since the WSIF project is increasingly active, isn't it time for you guys to get your own mailing list?  That would decrease the "noise" on axis-dev.

Hey, we love you, but its time to leave the nest! :-)


hi Tom,

i agree with you. i think that what we need for WSIF is: (following 
guidelines described in http://ws.apache.org/mail.html):

[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

i wonder also if we could move WSIF to http://ws.apache.org/wsif?

did i miss anything?

thanks,

alek

--
"Mr. Pauli, we in the audience are all agreed that your theory is crazy. 
What divides us is whether it is crazy enough to be true." Niels H. D. Bohr

Re: [wsif] mailing list for WSIF

2003-01-24 Thread Owen D Burroughs

Hi,

I also agree, wsif mailing lists would be good. As for the web site, you
get my vote for http://ws.apache.org/wsif (even if we're not yet voting :
-)), and have just asked Dims on the new [EMAIL PROTECTED] mailing list
about the  idea of having wsif pages stored under the new ws-site project.

Owen



|-+>
| |   Aleksander   |
| |   Slominski|
| |   <[EMAIL PROTECTED]|
| |   .edu>|
| ||
| |   24/01/2003 16:58 |
| |   Please respond to|
| |   axis-dev |
| ||
|-+>
  
>--|
  |
  |
  |   To:   [EMAIL PROTECTED]
  |
  |   cc:   [EMAIL PROTECTED]  
  |
  |   Subject:  [wsif] mailing list for WSIF [Re: WSIF to get its own mailing 
list?] |
  |
  |
  |
  |
  
>--|



Tom Jordahl wrote:

>Since the WSIF project is increasingly active, isn't it time for you guys
to get your own mailing list?  That would decrease the "noise" on axis-dev.
>
>Hey, we love you, but its time to leave the nest! :-)
>
hi Tom,

i agree with you. i think that what we need for WSIF is: (following
guidelines described in http://ws.apache.org/mail.html):

[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

i wonder also if we could move WSIF to http://ws.apache.org/wsif?

did i miss anything?

thanks,

alek

--
"Mr. Pauli, we in the audience are all agreed that your theory is crazy.
What divides us is whether it is crazy enough to be true." Niels H. D. Bohr

Re: [wsif] mailing list for WSIF [Re: WSIF to get its own mailinglist?]

2003-01-24 Thread Sam Ruby

Aleksander Slominski wrote:

hi Tom,

i agree with you. i think that what we need for WSIF is: (following 
guidelines described in http://ws.apache.org/mail.html):

[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

i wonder also if we could move WSIF to http://ws.apache.org/wsif?

did i miss anything?

I have a strong preference for cvs messages to be redirected to the 
appropriate dev list.  This has two benefits:

1) ensures that there are more eyes reviewing every commit (or at least, 
eliminates an excuse).

2) sends users fleeing to -user.  ;-)

- Sam Ruby

Re: Project pages on the new Web Services site

hi Owen,

i think that if possible we should synchronize making 2.0 release and 
making official ws.apache.org/wsif location (by putting redirect to new 
location in  http://xml.apache.org/axis/wsif/)

thanks,

alek

Owen D Burroughs wrote:

Hi Dims,

I think the short term option would be good enough from the wsif point of
view at the moment, so I'll look to add content soon. There are some other
issues to resolve around the use of Forrest for WSIF documentation before
the long term approach is viable.

Thanks,
Owen

|-+>
| |   Davanum Srinivas |
| |   <[EMAIL PROTECTED]> |
| ||
| |   24/01/2003 17:40 |
| |   Please respond to|
| |   general  |
| ||
|-+>
 >--|
 |  |
 |   To:   [EMAIL PROTECTED]|
 |   cc:|
 |   Subject:  Re: Project pages on the new Web Services site   |
 |  |
 |  |
 >--|

Owen,

Short-Term: Feel free to create a wsif directory under targets for the
html/images in ws-site cvs
module. This will be pushed every 6 hours to web site.

Long-Term: Finish conversion of the WSIF using forrest (any look & feel),
send me the zip, i will
integrate into existing ws-site with new look & feel and generate
everything from there.

Do you want to do Short-Term? or just do Long-Term? or both? Let me know.

Thanks,
dims

--- Owen D Burroughs <[EMAIL PROTECTED]> wrote:

Hi Dims,

Is it possible to have a wsif directory somewhere under ws-site to put

the

html for the WSIF site? It would be good to move them from the xml-site
project and access them from a URL such as http://ws.apache.org/wsif

I've been working on converting the current WSIF pages to use Forrest and
it would be great to apply the new ws look and feel to them and have them
hosted on the new site. In the short term it would be easiest for us to
simply commit generated html for the WSIF pages but in the longer term,
having the ws-site build automatically pick up the source xml files from
the WSIF cvs directories and then build them, would be neat.

Thanks,
Owen

=
Davanum Srinivas - http://xml.apache.org/~dims/

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

--
"Mr. Pauli, we in the audience are all agreed that your theory is crazy. 
What divides us is whether it is crazy enough to be true." Niels H. D. Bohr

Re: [wsif] mailing list for WSIF [Re: WSIF to get its own mailinglist?]



Sam Ruby wrote:


Aleksander Slominski wrote:


hi Tom,

i agree with you. i think that what we need for WSIF is: (following 
guidelines described in http://ws.apache.org/mail.html):

[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

i wonder also if we could move WSIF to http://ws.apache.org/wsif?

did i miss anything?


I have a strong preference for cvs messages to be redirected to the 
appropriate dev list.  This has two benefits:

1) ensures that there are more eyes reviewing every commit (or at 
least, eliminates an excuse).

2) sends users fleeing to -user.  ;-)

it makes sense :-)

maybe guidelines at http://ws.apache.org/mail.html could be annotated to 
point that using -dev may be preferred over separate -cvs?

thanks,

alek

--
"Mr. Pauli, we in the audience are all agreed that your theory is crazy. 
What divides us is whether it is crazy enough to be true." Niels H. D. Bohr

Re: [wsif] testing RC3

2003-01-24 Thread piotrp

Alek,
My omission with the classpath, what you listed perfect.  The problem of
seeing exceptions though is the incorrect initialization
of the JNDI inital context by Sun's implementation of j2ee.jar. To get rid
of it, the user should remove " jndi.properties" file from the
class path. If Sun's j2ee implementation is used, this file is in j2ee.jar
and its deletion fixes the problem.
I think I should add this to the readme, along with the classpath - is it
still ok or would it delay the release?
If so, we can just post the steps on the mailing list (wsif list, I hope -
that is an excellent idea).



Piotr


Regards,

Piotr Przybylski, IBM
Internet: [EMAIL PROTECTED]




   
  
  Aleksander   
  
  SlominskiTo:   "[EMAIL PROTECTED]" 
<[EMAIL PROTECTED]> 
  <[EMAIL PROTECTED]cc: 
  
  .edu>Subject:  [wsif] testing RC3
  
   
  
  01/24/2003 10:15 
  
  AM   
  
  Please respond to
  
  axis-dev 
  
   
  
   
  



hi,

i have tested all samples on windows 2000 and what i could on solaris (i
did not have JBoss or other app server installed on Solaris so i did not
check JMS and EJB samples) and i have checked in small updates to
documentation

i could get JCA sample to work on windows (after adding one directory to
CLASSPATH) but not on solaris and even on windows it produced lot of
output with stack traces but printed expected result (below).

thanks,

alek

ps. here is how to run JCA sample: with normal classpath it does not work:

C:\tmp\WSIF\wsif-2.0rc3>classpath
build\lib\wsif.jar;build\lib\wsif-j2c.jar;build\classes;build\samples;build\tests;lib\xmlParserAPIs-

2_2_1.jar;lib\xercesImpl-2_2_1.jar;lib\wsdl4j-20021124.jar;lib\soaprmi-1_1.jar;lib\servlet-2_2.jar;l

ib\saaj-1_1.jar;lib\qname-from-wsdl4j-20021124.jar;lib\optional-1_5_1.jar;lib\myeis.jar;lib\log4j-1_

2_4.jar;lib\junit-3_8_1.jar;lib\jms-1_1.jar;lib\jaxrpc-1_1.jar;lib\j2ee-1_3_1.jar;lib\commons-loggin

g.jar;lib\commons-discovery.jar;lib\axis-1_0.jar;lib\axis-1_0-ant.jar;lib\apache_soap-2_3_1.jar;lib\

ant-1_5_1.jar;

C:\tmp\WSIF\wsif-2.0rc3>java com.myeis.customer.J2C_MyEIS_CustomerInfoProxy
Exception in thread "main" java.lang.NoClassDefFoundError:
com/myeis/customer/J2C_MyEIS_CustomerInfoProxy



to fix it it is necessary to add build\samples\jca\customer
(which is a bit strange to do - why it is not compiled into build/samples?)

and then after lot of stack traces it prints expected output

C:\tmp\WSIF\wsif-2.0rc3>set
CLASSPATH=%CLASSPATH%;build\samples\jca\customer

C:\tmp\WSIF\wsif-2.0rc3>java com.myeis.customer.J2C_MyEIS_CustomerInfoProxy
java.io.FileNotFoundException:
C:\tmp\WSIF\wsif-2.0rc3\config\security.properties (The system cannot
 find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:103)
at
com.sun.enterprise.util.Utility.getPropertiesFromFile(Utility.java:42)
at com.sun.enterprise.iiop.POAEJBORB.(POAEJBORB.java:78)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:207)
at org.omg.CORBA.ORB.create_impl(ORB.java:306)
at org.omg.CORBA.ORB.init(ORB.java:345)
at
com.sun.enterprise.util.ORBManager.createORB(ORBManager.java:138)
at com.sun.enterprise.util.ORBManager.init(ORBManager.java:65)
at
com.sun.enterprise.naming.SerialInitContextFactory.(SerialInitContextFactory.java:3


1)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:


39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorIm


pl.java:27)
at java.lang.reflect.Cons

WSIF 2.0 RC4 available

2003-01-24 Thread Nirmal Mukhi





Hi,

WSIF version 2.0 RC4 is now available off http://xml.apache.org/axis/wsif.

This is likely to be the final release candidate and promoted to the 2.0
release shortly.

Thanks,
WSIF development team.

cvs commit: xml-axis/proposals/jabber/src/com/snellspace/axis/jabber JabberSender.java JabberTransport.java

2003-01-24 Thread jmsnell

jmsnell 2003/01/24 15:05:21

  Modified:proposals/jabber/src/com/snellspace/axis/jabber
JabberSender.java JabberTransport.java
  Log:
  Adding support for one-way only operations.  In the old code, the JabberSender would 
block until a response was received.  Now, a flag on the JabberTransport indicates 
whether or not the Sender should wait.
  
  Revision  ChangesPath
  1.3   +17 -11
xml-axis/proposals/jabber/src/com/snellspace/axis/jabber/JabberSender.java
  
  Index: JabberSender.java
  ===
  RCS file: 
/home/cvs//xml-axis/proposals/jabber/src/com/snellspace/axis/jabber/JabberSender.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- JabberSender.java 16 Jan 2003 06:24:05 -  1.2
  +++ JabberSender.java 24 Jan 2003 23:05:20 -  1.3
  @@ -37,19 +37,25 @@
 createRequestPacketFromMessage(
   context.getRequestMessage(), 
   context);
  +boolean waitForResponse = 
  +  ((Boolean)context.getProperty(
  +JabberTransport.JABBER_WAIT_FOR_RESPONSE))
  +  .booleanValue();
   connection.send(request, this);
  -try {
  -  synchronized(this) {
  -while (packet == null) {
  -  wait(1000);
  +if (waitForResponse) {
  +  try {
  +synchronized(this) {
  +  while (packet == null) {
  +wait(1000);
  +  }
   }
  -  }
  -} catch (InterruptedException e) {}
  -Packet response = packet;
  -context.setResponseMessage(
  -  createResponseMessageFromPacket(
  -response, 
  -context));
  +  } catch (InterruptedException e) {}
  +  Packet response = packet;
  +  context.setResponseMessage(
  +createResponseMessageFromPacket(
  +  response, 
  +  context));
  +}
   connection.disconnect();
   connection = null;
 }
  
  
  
  1.2   +14 -0 
xml-axis/proposals/jabber/src/com/snellspace/axis/jabber/JabberTransport.java
  
  Index: JabberTransport.java
  ===
  RCS file: 
/home/cvs//xml-axis/proposals/jabber/src/com/snellspace/axis/jabber/JabberTransport.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- JabberTransport.java  31 Dec 2002 20:38:34 -  1.1
  +++ JabberTransport.java  24 Jan 2003 23:05:20 -  1.2
  @@ -13,8 +13,11 @@
 extends Transport {
   
 public static final String DEFAULT_TRANSPORT_NAME = "JabberSender";
  +  public static final String JABBER_WAIT_FOR_RESPONSE = 
  +"com.snellspace.axis.jabber.JabberSender.WaitForResponse";
   
 private String to;
  +  private boolean waitForResponse = true;
   
 public JabberTransport() {
   transportName = DEFAULT_TRANSPORT_NAME;
  @@ -25,6 +28,14 @@
 this.transportName = transportName;
 }
   
  +  public boolean getWaitForResponse() {
  +return waitForResponse;
  +  }
  +  
  +  public void setWaitForResponse(boolean waitForResponse) {
  +this.waitForResponse = waitForResponse;
  +  }
  +
 public String getTo() {
   return to;
 }
  @@ -42,6 +53,9 @@
   context.setProperty(
 MessageContext.TRANS_URL,
 getTo());
  +context.setProperty(
  +JABBER_WAIT_FOR_RESPONSE,
  +new Boolean(waitForResponse));
 }
   
   }

cvs commit: xml-axis/proposals/jabber Axis1.0_JabberTransport.zip

2003-01-24 Thread jmsnell

jmsnell 2003/01/24 15:05:42

  Removed: proposals/jabber Axis1.0_JabberTransport.zip
  Log:
  Removing the old zip file

Web Services project - open for business

Folks,

Please visit http://ws.apache.org. Subscribe to general mailing list. Let's start 
rockin'...

Thanks,
dims

=
Davanum Srinivas - http://xml.apache.org/~dims/

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: Web Services project - open for business

2003-01-24 Thread Kevin . Bedell



Sorry for the cross post!

This announcement is now on the O'Reilly Weblog page -
http://www.oreillynet.com/weblogs/

Kevin




   

   

 Davanum Srinivas  To: [EMAIL PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED], 
 <[EMAIL PROTECTED]>[EMAIL PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED],   
 01/24/2003 10:53 AM [EMAIL PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED]  
 Please respond to axis-devcc: (bcc: Kevin 
Bedell/Systems/USHO/SunLife)
   Subject:  Web Services project - open 
for business  
   





Folks,

Please visit http://ws.apache.org. Subscribe to general mailing list. Let's
start rockin'...

Thanks,
dims

=
Davanum Srinivas - http://xml.apache.org/~dims/

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com




---
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure.  If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---

Re: Web Services project - open for business