Re: handling of xml attributes flawed
Franz, This is an area of code I haven't worked with for a little while now, so my knowledge is a bit rusty, but I shall try and give some responses to your questions below. Are ElementInfos for XML elements and AttributeInfos for XML attributes or is this a misunderstanding on my side? -- While I believe this was the original intent, taking a look at the code it appears these concepts have become clouded as the code has evolved -- although everytime I work in this area I try to improve it a little. In class Type elements maps names to ElementInfos, whereas attributes maps names to Types. Why not map names to AttributeInfos in the latter case? -- I have a suspicion this could be because all (xml) elements are stored in the typemap, so you use the name to lookup the needed type, while attributes are not. This seems to be the principal flaw to me; there is no direct access to the attributes and their properties (isOptional for example) in populateAttribList; only elements can be accessed with their properties. -- It does seem odd that we immediately work with the Type while being able to work with AttributeInfo, that has already been processed to give easy access to the desired properties, would probably make more sense. Now that my email has become enough confusing too, i think i will give it a second try tomorrow. As a last try for today are the following ideas sound? AttributeInfos should be constructed from names and types like ElementInfos (for attributes a simpler type concept than Type would be sufficient). If className (currently constructor argument for AttributeInfo) is needed for source generation, it should be in the base class ParamInfo. -- This does seem odd, particularly as the classname used is actually the one from the parent ParamInfo -- it really isn't obvious to me how this is used. In class Type, the attributes member should be a map from String to AttributeInfo. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] #axisVersion# #today# in generated service descriptor file
I generated C code using the Java WSDL tool. I get a comment like below in the service.xml file. !-- by the Apache Axis2 version: #axisVersion# #today# -- How can I get the correct version and date to appear here? Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXISCPP-982) HTTPTransportException
HTTPTransportException -- Key: AXISCPP-982 URL: http://issues.apache.org/jira/browse/AXISCPP-982 Project: Axis-C++ Type: Bug Components: Client - Engine Versions: 1.6 Final Environment: MS Windows XP; VS 2005 Reporter: Manfred Pauli Hello, I generated C++ code (client stubs) from a .wsdl file and it worked very well. Now I tried to run an application, but it didn't work. It started with an HTTPTransportException (Error code 126). I thought, my firewall could be the problem and turned it off, but it also didn't work. My main application looks like that: versionPortType vpt(http://bladekemper15.informatik.tu-muenchen.de:8080,APTHTTP1_1); vpt.getVersion(); I add the log file generated at the startup of the application. Please help me! Thank you very much, Manfred Start Display Current Environment Axis C++ libraries built on Mar 3 2006 at 01:06:33 Runtime trace produced on Mon Jul 10 13:32:42 2006 PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\Microsoft SQL Server\90\Tools\binn\;C:\Programme\Microsoft Visual Studio 8\SDK\v2.0\Bin\;C:\Xerces\bin\;C:\g++\bin\;C:\Axis\bin;C:\Expat-2.0.0\Libs;C:\Programme\SSH Communications Security\SSH Secure Shell;c:\Programme\Microsoft Visual Studio 8\;c:\Programme\Microsoft Visual Studio 8\VC\bin AXISCPP_DEPLOY=C:\Axis\deploy CLASSPATH=C:\axis\lib\axisjava\wsdl4j.jar;C:\axis\lib\axisjava\axis.jar;C:\axis\lib\axisjava\commons-discovery.jar;C:\axis\lib\axisjava\commons-logging.jar;C:\axis\lib\axisjava\jaxrpc.jar;C:\axis\lib\axisjava\saaj.jar;C:\axis\lib\axis\wsdl2ws.jar OS=Windows_NT COMPUTERNAME=NEUREUTLAPTOP USERNAME=Manfred * End Display Current Environment * [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I -- Config File settings START [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_WSDDFILEPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0100] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_LOGPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0200] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 c:\Axis\client.log [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_CLIENTLOGPATH = c:\Axis\client.log [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0300] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_CLIENTWSDDFILEPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0400] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\deploy [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_AXISHOME = C:\Axis\deploy [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0500] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\bin\HTTPTransport.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_TRANSPORTHTTP = C:\Axis\bin\HTTPTransport.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0600] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_TRANSPORTSMTP = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0700] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\bin\AxisXMLParserXerces.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_XMLPARSER = C:\Axis\bin\AxisXMLParserXerces.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0800] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 server name [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_NODENAME = server name [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty
[jira] Commented: (AXISCPP-982) HTTPTransportException
[ http://issues.apache.org/jira/browse/AXISCPP-982?page=comments#action_12420062 ] John Hawkins commented on AXISCPP-982: -- It's failing to load the ssh channel library - did you want to use ssh ? If not then comment out the securechannel library in the conf file. If you do want ssh then you need to ensure that you have open ssl on your path (which I can't see in your trace) HTTPTransportException -- Key: AXISCPP-982 URL: http://issues.apache.org/jira/browse/AXISCPP-982 Project: Axis-C++ Type: Bug Components: Client - Engine Versions: 1.6 Final Environment: MS Windows XP; VS 2005 Reporter: Manfred Pauli Hello, I generated C++ code (client stubs) from a .wsdl file and it worked very well. Now I tried to run an application, but it didn't work. It started with an HTTPTransportException (Error code 126). I thought, my firewall could be the problem and turned it off, but it also didn't work. My main application looks like that: versionPortType vpt(http://bladekemper15.informatik.tu-muenchen.de:8080,APTHTTP1_1); vpt.getVersion(); I add the log file generated at the startup of the application. Please help me! Thank you very much, Manfred Start Display Current Environment Axis C++ libraries built on Mar 3 2006 at 01:06:33 Runtime trace produced on Mon Jul 10 13:32:42 2006 PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\Microsoft SQL Server\90\Tools\binn\;C:\Programme\Microsoft Visual Studio 8\SDK\v2.0\Bin\;C:\Xerces\bin\;C:\g++\bin\;C:\Axis\bin;C:\Expat-2.0.0\Libs;C:\Programme\SSH Communications Security\SSH Secure Shell;c:\Programme\Microsoft Visual Studio 8\;c:\Programme\Microsoft Visual Studio 8\VC\bin AXISCPP_DEPLOY=C:\Axis\deploy CLASSPATH=C:\axis\lib\axisjava\wsdl4j.jar;C:\axis\lib\axisjava\axis.jar;C:\axis\lib\axisjava\commons-discovery.jar;C:\axis\lib\axisjava\commons-logging.jar;C:\axis\lib\axisjava\jaxrpc.jar;C:\axis\lib\axisjava\saaj.jar;C:\axis\lib\axis\wsdl2ws.jar OS=Windows_NT COMPUTERNAME=NEUREUTLAPTOP USERNAME=Manfred * End Display Current Environment * [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I -- Config File settings START [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_WSDDFILEPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0100] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_LOGPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0200] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 c:\Axis\client.log [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_CLIENTLOGPATH = c:\Axis\client.log [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0300] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_CLIENTWSDDFILEPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0400] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\deploy [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_AXISHOME = C:\Axis\deploy [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0500] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\bin\HTTPTransport.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_TRANSPORTHTTP = C:\Axis\bin\HTTPTransport.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0600] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_TRANSPORTSMTP = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0700] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\bin\AxisXMLParserXerces.dll [10/07/2006 13:32:42:887 Westeuropäische
[jira] Commented: (AXISCPP-982) HTTPTransportException
[ http://issues.apache.org/jira/browse/AXISCPP-982?page=comments#action_12420081 ] Manfred Pauli commented on AXISCPP-982: --- Thanx a lot!! Now it works!! Greetings Manfred HTTPTransportException -- Key: AXISCPP-982 URL: http://issues.apache.org/jira/browse/AXISCPP-982 Project: Axis-C++ Type: Bug Components: Client - Engine Versions: 1.6 Final Environment: MS Windows XP; VS 2005 Reporter: Manfred Pauli Hello, I generated C++ code (client stubs) from a .wsdl file and it worked very well. Now I tried to run an application, but it didn't work. It started with an HTTPTransportException (Error code 126). I thought, my firewall could be the problem and turned it off, but it also didn't work. My main application looks like that: versionPortType vpt(http://bladekemper15.informatik.tu-muenchen.de:8080,APTHTTP1_1); vpt.getVersion(); I add the log file generated at the startup of the application. Please help me! Thank you very much, Manfred Start Display Current Environment Axis C++ libraries built on Mar 3 2006 at 01:06:33 Runtime trace produced on Mon Jul 10 13:32:42 2006 PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\Microsoft SQL Server\90\Tools\binn\;C:\Programme\Microsoft Visual Studio 8\SDK\v2.0\Bin\;C:\Xerces\bin\;C:\g++\bin\;C:\Axis\bin;C:\Expat-2.0.0\Libs;C:\Programme\SSH Communications Security\SSH Secure Shell;c:\Programme\Microsoft Visual Studio 8\;c:\Programme\Microsoft Visual Studio 8\VC\bin AXISCPP_DEPLOY=C:\Axis\deploy CLASSPATH=C:\axis\lib\axisjava\wsdl4j.jar;C:\axis\lib\axisjava\axis.jar;C:\axis\lib\axisjava\commons-discovery.jar;C:\axis\lib\axisjava\commons-logging.jar;C:\axis\lib\axisjava\jaxrpc.jar;C:\axis\lib\axisjava\saaj.jar;C:\axis\lib\axis\wsdl2ws.jar OS=Windows_NT COMPUTERNAME=NEUREUTLAPTOP USERNAME=Manfred * End Display Current Environment * [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I -- Config File settings START [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_WSDDFILEPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0100] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_LOGPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0200] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 c:\Axis\client.log [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_CLIENTLOGPATH = c:\Axis\client.log [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0300] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_CLIENTWSDDFILEPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0400] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\deploy [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_AXISHOME = C:\Axis\deploy [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0500] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\bin\HTTPTransport.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_TRANSPORTHTTP = C:\Axis\bin\HTTPTransport.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0600] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_TRANSPORTSMTP = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0700] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\bin\AxisXMLParserXerces.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_XMLPARSER = C:\Axis\bin\AxisXMLParserXerces.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0800] [10/07/2006
Re: [Axis2] #axisVersion# #today# in generated service descriptor file
Ajith Ranabahu wrote: hi, Hmm these should get replaced automatically in the maven build (using a filter). Are you using a generated binary or are you inside an IDE ? I am using generatd jar with command line; no IDE. Options used: -l c -u -d adb -ss -sd -o service -uri my.wsdl Thanks, Samisa... Ajith On 7/10/06, Samisa Abeysinghe [EMAIL PROTECTED] wrote: I generated C code using the Java WSDL tool. I get a comment like below in the service.xml file. !-- by the Apache Axis2 version: #axisVersion# #today# -- How can I get the correct version and date to appear here? Thanks, Samisa... - 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]
[jira] Closed: (AXISCPP-982) HTTPTransportException
[ http://issues.apache.org/jira/browse/AXISCPP-982?page=all ] John Hawkins closed AXISCPP-982: Resolution: Fixed HTTPTransportException -- Key: AXISCPP-982 URL: http://issues.apache.org/jira/browse/AXISCPP-982 Project: Axis-C++ Type: Bug Components: Client - Engine Versions: 1.6 Final Environment: MS Windows XP; VS 2005 Reporter: Manfred Pauli Hello, I generated C++ code (client stubs) from a .wsdl file and it worked very well. Now I tried to run an application, but it didn't work. It started with an HTTPTransportException (Error code 126). I thought, my firewall could be the problem and turned it off, but it also didn't work. My main application looks like that: versionPortType vpt(http://bladekemper15.informatik.tu-muenchen.de:8080,APTHTTP1_1); vpt.getVersion(); I add the log file generated at the startup of the application. Please help me! Thank you very much, Manfred Start Display Current Environment Axis C++ libraries built on Mar 3 2006 at 01:06:33 Runtime trace produced on Mon Jul 10 13:32:42 2006 PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\Microsoft SQL Server\90\Tools\binn\;C:\Programme\Microsoft Visual Studio 8\SDK\v2.0\Bin\;C:\Xerces\bin\;C:\g++\bin\;C:\Axis\bin;C:\Expat-2.0.0\Libs;C:\Programme\SSH Communications Security\SSH Secure Shell;c:\Programme\Microsoft Visual Studio 8\;c:\Programme\Microsoft Visual Studio 8\VC\bin AXISCPP_DEPLOY=C:\Axis\deploy CLASSPATH=C:\axis\lib\axisjava\wsdl4j.jar;C:\axis\lib\axisjava\axis.jar;C:\axis\lib\axisjava\commons-discovery.jar;C:\axis\lib\axisjava\commons-logging.jar;C:\axis\lib\axisjava\jaxrpc.jar;C:\axis\lib\axisjava\saaj.jar;C:\axis\lib\axis\wsdl2ws.jar OS=Windows_NT COMPUTERNAME=NEUREUTLAPTOP USERNAME=Manfred * End Display Current Environment * [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I -- Config File settings START [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_WSDDFILEPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0100] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_LOGPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0200] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 c:\Axis\client.log [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_CLIENTLOGPATH = c:\Axis\client.log [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0300] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_CLIENTWSDDFILEPATH = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0400] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\deploy [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_AXISHOME = C:\Axis\deploy [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0500] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\bin\HTTPTransport.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_TRANSPORTHTTP = C:\Axis\bin\HTTPTransport.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0600] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@1 null [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_TRANSPORTSMTP = NULL [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0700] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,@2 C:\Axis\bin\AxisXMLParserXerces.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 - I AXCONF_XMLPARSER = C:\Axis\bin\AxisXMLParserXerces.dll [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig getAxisConfProperty @00346398,[0800] [10/07/2006 13:32:42:887 Westeuropäische Normalzeit] 668 AxisConfig
[jira] Created: (AXIS2C-203) Generated code does not compile
Generated code does not compile --- Key: AXIS2C-203 URL: http://issues.apache.org/jira/browse/AXIS2C-203 Project: Axis2-C Type: Bug Components: code generation Versions: Current (Nightly) Reporter: Samisa Abeysinghe There seems to be problems with generated code. I get the following errors: axis2_MySvc_svc_skeleton.c: In function 'axis2_MySvc_svc_skeleton_invoke': axis2_MySvc_svc_skeleton.c:128: error: 'ret_value2' undeclared (first use in this function) axis2_MySvc_svc_skeleton.c:128: error: (Each undeclared identifier is reported only once axis2_MySvc_svc_skeleton.c:128: error: for each function it appears in.) axis2_MySvc_svc_skeleton.c:158: error: 'ns1' undeclared (first use in this function) axis2_MySvc_svc_skeleton.c:168: error: 'attri1' undeclared (first use in this function) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2C-203) Generated code does not compile
[ http://issues.apache.org/jira/browse/AXIS2C-203?page=all ] Samisa Abeysinghe updated AXIS2C-203: - Attachment: proxyMy_generic.wsdl Generated code does not compile --- Key: AXIS2C-203 URL: http://issues.apache.org/jira/browse/AXIS2C-203 Project: Axis2-C Type: Bug Components: code generation Versions: Current (Nightly) Reporter: Samisa Abeysinghe Attachments: proxyMy_generic.wsdl There seems to be problems with generated code. I get the following errors: axis2_MySvc_svc_skeleton.c: In function 'axis2_MySvc_svc_skeleton_invoke': axis2_MySvc_svc_skeleton.c:128: error: 'ret_value2' undeclared (first use in this function) axis2_MySvc_svc_skeleton.c:128: error: (Each undeclared identifier is reported only once axis2_MySvc_svc_skeleton.c:128: error: for each function it appears in.) axis2_MySvc_svc_skeleton.c:158: error: 'ns1' undeclared (first use in this function) axis2_MySvc_svc_skeleton.c:168: error: 'attri1' undeclared (first use in this function) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] JSR 181 support
i need to review the code changes/sample to be able to make up my mind :) -- dims On 7/9/06, Rajith Attapattu [EMAIL PROTECTED] wrote: Hi Dims, I finnaly managed to get an annotated POJO exposed as an axis2 web service. Before I submit the patch I need to clarify a few things. 1. We need to figure out a way to find the classes marked with @WebService. Right now I just have my test POJO hard corded in WSMToAxis2ServiceBuilder to test things. Ideas? suggestions pls? There was a few disscussion, but can we come to an agreement? 2. Generating Annogen beans for meta data (This is more or less a WSM problem, will cross post there as well) The annogen task that generates code based on the annotated classes seems to have bug with inner classes. For example WebParam.Mode gives compilation errors as it cannot the handle the inner class So I eidted the generated source file to get it working. This maybe an option since the javax.jws classes are static and does not need to go through annogen code generation all the time. But it would be nice if this worked so that I can add a task in wsm to compile the javax.jws classes and generate the required AnnoBeans without manual intervention. Regards, Rajith -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: A Axis2 problem!~
fwd to list
-- Forwarded message --
From: 邱家榆 [EMAIL PROTECTED]
Date: Jul 10, 2006 3:09 AM
Subject: A Axis2 problem!~
To: davanum [EMAIL PROTECTED]
There is a Axis2 1.0 Client Code:
public void testRESTClient() {
Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
//
options.setProperty(Constants.Configuration.ENABLE_REST,Constants.VALUE_TRUE);
options.setAction(urn:getQuote);
//options.setUseSeparateListener(true);
try {
ServiceClient sender = new ServiceClient();
sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
sender.setOptions(options);
OMElement payload = this.getOMElement(getQuote, myce);
OMElement result = sender.sendReceive(payload);
XMLStreamWriter writer =
XMLOutputFactory.newInstance().createXMLStreamWriter(System.out);
result.serialize(writer);
writer.flush();
} catch (XMLStreamException e) {
e.printStackTrace();
} catch (FactoryConfigurationError e) {
e.printStackTrace();
} catch (AxisFault e) {
e.printStackTrace();
}
}
Exception:
org.apache.axis2.AxisFault: Incoming message input stream is null
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:64)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:349)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:457)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)
at com.TestStockQuoteService.testRESTClient(TestStockQuoteService.java:314)
at com.TestStockQuoteService.main(TestStockQuoteService.java:400)
邱家榆
2006-07-10
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
[Axis2] Problems with MessageContext
While playing around with implementing my own handler, I found out, that the getProperties() method of the MessageContext is not implemented correctly: MessageContext overrides the property handling of the parent class by setting/getting properties from the Options object. But getProperties() is passed on to the parent class which then always returns an empty map. (Using getOptions().getProperties() of course works). If you need an implementation for getProperties() which uses the Options object I can provide it. In addition it seems that the outgoing MessageContext objects do not contain the servlet context. Is this by mistake or by design? If it's the latter, how can I access the servlet context? Thanks Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-878) JAXWS: Metadata Abstraction Layer
[ http://issues.apache.org/jira/browse/AXIS2-878?page=all ] Rich Scheuerle updated AXIS2-878: - Assign To: Rich Scheuerle JAXWS: Metadata Abstraction Layer - Key: AXIS2-878 URL: http://issues.apache.org/jira/browse/AXIS2-878 Project: Apache Axis 2.0 (Axis2) Type: New Feature Components: jaxws Reporter: Jeff Barrett Assignee: Rich Scheuerle This layer abstracts the various metadata used by JAXWS. That metadata currently consists of WSDL, JSR-181 annotations, and JAXWS-defined annotations. Eventually, JSR-109 1.2 Deployment Descriptors will be another source of metadata. This layer will shield the rest of JAX-WS from this metadata and the complexities involved in merging the various sources into the final effective metadata to be used. The layer will contain a hierachy of description artifacts corresponding to the service, ports, port types, operations, and parameters. These Description classes will delegate to the AxisSerivce, AxisOperation, etc to access WSDL metadata and non-JAXWS-specific annotation information. The Description classes will contain the JAXWS-specific annotation information (and eventually) other JAXWS-specific information (such as JSR-109 DD information). I am currently working on the initial implementation of this layer and the associated tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-882) Endpoint Controller framework
Endpoint Controller framework -- Key: AXIS2-882 URL: http://issues.apache.org/jira/browse/AXIS2-882 Project: Apache Axis 2.0 (Axis2) Type: New Feature Components: jaxws Versions: 1.0 Reporter: Samuel Isokpunwu Started work on cleaning up the JAXWSMessageReciever and the addition of an Endpoint Controller framework for easy service endpoints maintainability and to provide a reliable framework base for future service endpoint(s) enhancements per JAXWS specification. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Asychronous invocation using the generated stub
Hi, How can I specify that I want to use two separate transports connection when I use a stub generated from a WSDL. A+ -- Jean-Michel PATER [EMAIL PROTECTED] Cogenit Tél : +33 (0) 1 40 20 08 43 53 rue Sainte Anne Fax : +33 (0) 1 40 20 08 45 75002 Paris URL:http://www.cogenit.fr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-883) [JAX-WS] JSR 181 support
[JAX-WS] JSR 181 support
Key: AXIS2-883
URL: http://issues.apache.org/jira/browse/AXIS2-883
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter: Rajith Attapattu
Attachments: beehive-jars.tar.gz, jsr181.patch
Dims,
Attached is the scratch code from my sandbox. Note this was done as a proof of
concept.
More work needs to be done, but I need to see if the initial direction is
community approved before I spend more time on it
A) The patch contains WSMToAxisServiceBuilder.java and other related files.
B) Also attached are the WSM jars from my local repo (put them under
{maven.repo}/beehive/jars
C) SampleAnnotatedPOJO, a very simple POJO with 2 public methods and only one
marked with @WebMethod
just bug me if anything is missing
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-883) [JAX-WS] JSR 181 support
[ http://issues.apache.org/jira/browse/AXIS2-883?page=all ]
Rajith Attapattu updated AXIS2-883:
---
Attachment: jsr181.patch
[JAX-WS] JSR 181 support
Key: AXIS2-883
URL: http://issues.apache.org/jira/browse/AXIS2-883
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter: Rajith Attapattu
Attachments: beehive-jars.tar.gz, jsr181.patch
Dims,
Attached is the scratch code from my sandbox. Note this was done as a proof
of concept.
More work needs to be done, but I need to see if the initial direction is
community approved before I spend more time on it
A) The patch contains WSMToAxisServiceBuilder.java and other related files.
B) Also attached are the WSM jars from my local repo (put them under
{maven.repo}/beehive/jars
C) SampleAnnotatedPOJO, a very simple POJO with 2 public methods and only one
marked with @WebMethod
just bug me if anything is missing
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-883) [JAX-WS] JSR 181 support
[ http://issues.apache.org/jira/browse/AXIS2-883?page=all ]
Rajith Attapattu updated AXIS2-883:
---
Attachment: beehive-jars.tar.gz
[JAX-WS] JSR 181 support
Key: AXIS2-883
URL: http://issues.apache.org/jira/browse/AXIS2-883
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter: Rajith Attapattu
Attachments: beehive-jars.tar.gz, jsr181.patch
Dims,
Attached is the scratch code from my sandbox. Note this was done as a proof
of concept.
More work needs to be done, but I need to see if the initial direction is
community approved before I spend more time on it
A) The patch contains WSMToAxisServiceBuilder.java and other related files.
B) Also attached are the WSM jars from my local repo (put them under
{maven.repo}/beehive/jars
C) SampleAnnotatedPOJO, a very simple POJO with 2 public methods and only one
marked with @WebMethod
just bug me if anything is missing
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-883) [JAX-WS] JSR 181 support
[ http://issues.apache.org/jira/browse/AXIS2-883?page=all ]
Rajith Attapattu updated AXIS2-883:
---
Attachment: SampleAnnotatedPOJO.java
[JAX-WS] JSR 181 support
Key: AXIS2-883
URL: http://issues.apache.org/jira/browse/AXIS2-883
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter: Rajith Attapattu
Attachments: SampleAnnotatedPOJO.java, beehive-jars.tar.gz, jsr181.patch
Dims,
Attached is the scratch code from my sandbox. Note this was done as a proof
of concept.
More work needs to be done, but I need to see if the initial direction is
community approved before I spend more time on it
A) The patch contains WSMToAxisServiceBuilder.java and other related files.
B) Also attached are the WSM jars from my local repo (put them under
{maven.repo}/beehive/jars
C) SampleAnnotatedPOJO, a very simple POJO with 2 public methods and only one
marked with @WebMethod
just bug me if anything is missing
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] JSR 181 support
Dims,Everything is attached to http://issues.apache.org/jira/browse/AXIS2-883Let me know what you think.If anything is missing, please ping me. Note: I have hard coded the class name for testing in WSMToAxis2ServiceBuilder with a comment.This is where I mentioned that we need to pass in the classes annotated with @WebServices.Regards,Rajith On 7/10/06, Davanum Srinivas [EMAIL PROTECTED] wrote: i need to review the code changes/sample to be able to make up my mind :)-- dimsOn 7/9/06, Rajith Attapattu [EMAIL PROTECTED] wrote: Hi Dims, I finnaly managed to get an annotated POJO exposed as an axis2 web service. Before I submit the patch I need to clarify a few things. 1. We need to figure out a way to find the classes marked with @WebService. Right now I just have my test POJO hard corded in WSMToAxis2ServiceBuilder to test things.Ideas? suggestions pls? There was a few disscussion, but can we come to an agreement? 2. Generating Annogen beans for meta data (This is more or less a WSM problem, will cross post there as well) The annogen task that generates code based on the annotated classes seems to have bug with inner classes. For example WebParam.Mode gives compilation errors as it cannot the handle the inner class So I eidted the generated source file to get it working. This maybe an option since the javax.jws classes are static and does not need to go through annogen code generation all the time. But it would be nice if this worked so that I can add a task in wsm to compile the javax.jws classes and generate the required AnnoBeans without manual intervention. Regards, Rajith--Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)-To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-878) JAXWS: Metadata Abstraction Layer
[ http://issues.apache.org/jira/browse/AXIS2-878?page=comments#action_12420108 ] Rajith Attapattu commented on AXIS2-878: Rich, I hope you have not started any work on JSR 181 support. Hopefully we are not working on the same thing in isolation :-) I have provided a patch with some very basic support, comments are appreciated. Rajith JAXWS: Metadata Abstraction Layer - Key: AXIS2-878 URL: http://issues.apache.org/jira/browse/AXIS2-878 Project: Apache Axis 2.0 (Axis2) Type: New Feature Components: jaxws Reporter: Jeff Barrett Assignee: Rich Scheuerle This layer abstracts the various metadata used by JAXWS. That metadata currently consists of WSDL, JSR-181 annotations, and JAXWS-defined annotations. Eventually, JSR-109 1.2 Deployment Descriptors will be another source of metadata. This layer will shield the rest of JAX-WS from this metadata and the complexities involved in merging the various sources into the final effective metadata to be used. The layer will contain a hierachy of description artifacts corresponding to the service, ports, port types, operations, and parameters. These Description classes will delegate to the AxisSerivce, AxisOperation, etc to access WSDL metadata and non-JAXWS-specific annotation information. The Description classes will contain the JAXWS-specific annotation information (and eventually) other JAXWS-specific information (such as JSR-109 DD information). I am currently working on the initial implementation of this layer and the associated tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problems with MessageContext
On Mon, 2006-07-10 at 11:33 +0200, Carsten Ziegeler wrote: While playing around with implementing my own handler, I found out, that the getProperties() method of the MessageContext is not implemented correctly: MessageContext overrides the property handling of the parent class by setting/getting properties from the Options object. But getProperties() is passed on to the parent class which then always returns an empty map. (Using getOptions().getProperties() of course works). If you need an implementation for getProperties() which uses the Options object I can provide it. IIRC, the behavior desired was for just the message context to use options' properties instead of using the local hashtable. This has something to do with allowing users to set stuff from outside via options and having them take effect at the various contexts. So if the property is not found via options.getProperty() then we cross over to whatever level of other context is around (operation or service or .. etc.) and ask there. Note that setProperty() too has been overridden to match this behavior. So in effect the properties hashtable inherited from the superclass is not used by the MessageContext class. In addition it seems that the outgoing MessageContext objects do not contain the servlet context. Is this by mistake or by design? If it's the latter, how can I access the servlet context? Its by design- you have to get the operation context from the outgoing MC and then get the incoming MC from that and look there for the servlet context and any other incoming info. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-878) JAXWS: Metadata Abstraction Layer
[ http://issues.apache.org/jira/browse/AXIS2-878?page=comments#action_12420141 ] Jeff Barrett commented on AXIS2-878: Rajith, Actually I am doing this work, not Rich :-). This layer doesn't include any JSR-181 support. It is a wrapper around the various places that JAX-WS metadata can come from. The JSR-181 annotations and WSDL will come from elsewhere in Axis2 (i.e. the AxisService built from WSDL + JSR-181 annotations). The only annotations contained in this layer are the JAX-WS specific ones. Sorry that wasn't clear in my original Description. Jeff JAXWS: Metadata Abstraction Layer - Key: AXIS2-878 URL: http://issues.apache.org/jira/browse/AXIS2-878 Project: Apache Axis 2.0 (Axis2) Type: New Feature Components: jaxws Reporter: Jeff Barrett Assignee: Rich Scheuerle This layer abstracts the various metadata used by JAXWS. That metadata currently consists of WSDL, JSR-181 annotations, and JAXWS-defined annotations. Eventually, JSR-109 1.2 Deployment Descriptors will be another source of metadata. This layer will shield the rest of JAX-WS from this metadata and the complexities involved in merging the various sources into the final effective metadata to be used. The layer will contain a hierachy of description artifacts corresponding to the service, ports, port types, operations, and parameters. These Description classes will delegate to the AxisSerivce, AxisOperation, etc to access WSDL metadata and non-JAXWS-specific annotation information. The Description classes will contain the JAXWS-specific annotation information (and eventually) other JAXWS-specific information (such as JSR-109 DD information). I am currently working on the initial implementation of this layer and the associated tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Requirement of bouncycastle on Java 1.5
Davanum Srinivas wrote: how about this for a start? http://mail-archives.apache.org/mod_mbox/ws-fx-dev/200403.mbox/[EMAIL PROTECTED] Thanks for the link and sorry for the delayed response. Couple of quick questions though: 1) Since that message is a bit dated, is it possible to get an update on this? Since support for RSA-OAEP, and a lot of the signature algorithms has been integrated in JDK 1.5, it seems the only reasons to require any external JCE provider at all would be to support a larger range of key-sizes for symmetric encryption not provided by the JDK. Is this deduction accurate? 2) In addition, there are some inconsistencies in the behaviour of Bouncycastle and other crypto providers (including the JDK) which seem to make the Axis/wss4j code (somewhat accidentally) dependent on Bouncycastle. From my inspection, these are minor things like algorithm transformations/names etc. Are there any deeper issues I have missed in my assessment? If the stumbling blocks are limited to what I mentioned above, then it probably wont require a lot of effort to make Axis more crypto-provider agnostic. Thanks, Vivek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Requirement of bouncycastle on Java 1.5
Can you please drop an email to wss4j-dev (specifically addressed to werner?). Also please look at juice code base (http://svn.apache.org/repos/asf/incubator/juice/). thanks, dims On 7/10/06, Vivek Lakshmanan [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: how about this for a start? http://mail-archives.apache.org/mod_mbox/ws-fx-dev/200403.mbox/[EMAIL PROTECTED] Thanks for the link and sorry for the delayed response. Couple of quick questions though: 1) Since that message is a bit dated, is it possible to get an update on this? Since support for RSA-OAEP, and a lot of the signature algorithms has been integrated in JDK 1.5, it seems the only reasons to require any external JCE provider at all would be to support a larger range of key-sizes for symmetric encryption not provided by the JDK. Is this deduction accurate? 2) In addition, there are some inconsistencies in the behaviour of Bouncycastle and other crypto providers (including the JDK) which seem to make the Axis/wss4j code (somewhat accidentally) dependent on Bouncycastle. From my inspection, these are minor things like algorithm transformations/names etc. Are there any deeper issues I have missed in my assessment? If the stumbling blocks are limited to what I mentioned above, then it probably wont require a lot of effort to make Axis more crypto-provider agnostic. Thanks, Vivek -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Fwd: svn commit: r420634 - /webservices/muse/trunk/modules/muse-platform-axis2/src/org/apache/muse/core/platform/axis2/AxisEnvironment.java
Can we please fix this? -- Forwarded message -- From: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Jul 10, 2006 5:24 PM Subject: svn commit: r420634 - /webservices/muse/trunk/modules/muse-platform-axis2/src/org/apache/muse/core/platform/axis2/AxisEnvironment.java To: [EMAIL PROTECTED] Author: danj Date: Mon Jul 10 14:24:03 2006 New Revision: 420634 URL: http://svn.apache.org/viewvc?rev=420634view=rev Log: Temporary fix for MUSE-30 - when an EPR is read from Axis2's WS-A, we check the wsa:Metadata field, and if there are any elements inside, copy them to wsa:ReferenceParameters. This will allow everyone to use the code with our own client until we can get a real fix with the help of the Axis2 team. Modified: webservices/muse/trunk/modules/muse-platform-axis2/src/org/apache/muse/core/platform/axis2/AxisEnvironment.java Modified: webservices/muse/trunk/modules/muse-platform-axis2/src/org/apache/muse/core/platform/axis2/AxisEnvironment.java URL: http://svn.apache.org/viewvc/webservices/muse/trunk/modules/muse-platform-axis2/src/org/apache/muse/core/platform/axis2/AxisEnvironment.java?rev=420634r1=420633r2=420634view=diff == --- webservices/muse/trunk/modules/muse-platform-axis2/src/org/apache/muse/core/platform/axis2/AxisEnvironment.java (original) +++ webservices/muse/trunk/modules/muse-platform-axis2/src/org/apache/muse/core/platform/axis2/AxisEnvironment.java Mon Jul 10 14:24:03 2006 @@ -214,11 +214,9 @@ // FIXME: for some reason, Axis2 is adding the reference parameters //to the Metadata section of the EPR, even though the //IsReferenceParameter attribute is qualified with the WS-A -//namespace. if this cannot be fixed immediately, a hack to -//swap metadata to parameters should be added here (and it -//should look like the code below). +//namespace. the code below is a temporary hack until we can +//get some help from the Axis2 mailing list. // -/* Element metadata = XmlUtils.getElement(eprXML, WsaConstants.METADATA_QNAME); if (metadata != null) @@ -237,7 +235,10 @@ params.appendChild(children[n]); } } -*/ + +// +// end of glorious hack +// return new EndpointReference(eprXML); } - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-884) SecurityException thrown when run from an applet
SecurityException thrown when run from an applet Key: AXIS2-884 URL: http://issues.apache.org/jira/browse/AXIS2-884 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: deployment Reporter: Shreyes Seshasai Java applets are given fewer security privileges than stand alone applications by default. When trying to run an Axis2 client from a java applet, it may not have all of the privileges required by some of the calls in the Axis2 code, causing SecurityExceptions to be thrown. Examples of these calls are System.getProperty() and File.listFiles(). A suggested fix would be to enclose these calls in try/catch(SecurityException) blocks, and assign default values to the variables which failed to be set. Known affected files: org.apache.axis2.deployment.FileSystemConfigurator.java org.apache.axis2.deployment.RepositoryListener.java Adding the try/catch blocks here allowed the applet to start and function correctly. However, the problem probably exists in other locations in the code too. I was only using limited functionality (no additional modules or databinding). Since applets cannot read files from the file system, I'm unsure how this affects other axis2 functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
