[Axis2/Core] Proposal for Error Logging
Hi all, While inspecting the error logging mechanism in Axis2/C, AXIS2_ERROR_SET, according to the implementation, is used to log only the last error that was reported. By doing so, all other error messages that sometimes do have significant importance are lost. We could use an alternative approach using AXIS2_LOG_ERROR where each and every error reported would in fact be logged. AXIS2_ERROR_SET, has been the popular choice of reporting errors in the core. Therefore, we have two alternatives. 1. Use an array to store errors reported using AXIS2_ERROR_SET, and handle them (do some error handling and logging) one after the other. 2. Use AXIS2_LOG_ERROR, to log all errors of importance, as they occur. I would rather suggest alternative 1, to be a better approach in the long run. But, for the moment it is better to focus on alternative 2. Senaka. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What Type of SSL BIO is used in HTTP Transport?
What Type of SSL BIO is used in SSL enabled HTTP Transport? I'm referring to the files, axis2/c/src/core/transport/http/sender/ssl/ssl_*.* What I'm interested in knowing is whether it is blocking or non-blocking or whether it may vary according to the scenario. Thanks in advance, Senaka - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What Type of SSL BIO is used in HTTP Transport?
[EMAIL PROTECTED] wrote: What Type of SSL BIO is used in SSL enabled HTTP Transport? It should depend on the socket that is in use by Axis2/C. Please refer to the axis2_ssl_utils_initialize_ssl() function in ssl_utils.c. I'm referring to the files, axis2/c/src/core/transport/http/sender/ssl/ssl_*.* What I'm interested in knowing is whether it is blocking or non-blocking or whether it may vary according to the scenario. That (i.e., the behavior of Axis2/C sockets) I'm uncertain of. However, it seems that SSL client's function depends much on this fact! HTH, Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
[jira] Created: (AXIS2C-733) Validating the server certificate should not be mandatory
Validating the server certificate should not be mandatory -- Key: AXIS2C-733 URL: https://issues.apache.org/jira/browse/AXIS2C-733 Project: Axis2-C Issue Type: Improvement Components: core/transport Affects Versions: 1.1.0 Reporter: Dumindu Pallewela Assignee: Dumindu Pallewela Current SSL client implementation validates the server certificate at all times. We need some means of allowing the user to disable this validation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-734) Enabling Service Level Custom Logs
Enabling Service Level Custom Logs
--
Key: AXIS2C-734
URL: https://issues.apache.org/jira/browse/AXIS2C-734
Project: Axis2-C
Issue Type: New Feature
Reporter: Damitha Kumarage
A service developer may be interested only in the debug messages he put in his
service. He don't need all the debug messages from within the core/transport of
the axis2c engine. Currently what happen is when the axis2c engine is started
with log enabled all the log messages core/transport are printed to the log
file so that service developers log messages are obscured.
To avoid that I propose another log level called AXIS2_LOG_LEVEL_SERVICE.
When the axis2c engine is started with this log level only the critical and
error logs are printed from the core/ trasport.
All the log messages written by the service developer with the logging function
AXIS2_LOG_SERVICE( ) are also be printed.
Also If we start the axis2c engine with the log level debug, the messages
written using AXIS2_LOG_SERVICE( ) are printed. If we start the axis2c engine
with the log level critical or error only the error/critical log messages are
printed.
The function that I have added to the log.c to implement this is
AXIS2_EXTERN void AXIS2_CALL
axutil_log_impl_log_service(
axutil_log_t * log,
const axis2_char_t * filename,
const int linenumber,
const axis2_char_t * format,
...)
{
FILE *fd = NULL;
axutil_thread_mutex_t *mutex = NULL;
if (log format)
{
if (!(fd = AXIS2_INTF_TO_IMPL(log)-stream))
{
fprintf(stderr, Stream is not found\n);
}
if (!(mutex = AXIS2_INTF_TO_IMPL(log)-mutex))
{
fprintf(stderr, Log mutex is not found\n);
}
if (AXIS2_LOG_LEVEL_DEBUG = log-level)
{
char value[AXIS2_LEN_VALUE + 1];
va_list ap;
va_start(ap, format);
AXIS2_VSNPRINTF(value, AXIS2_LEN_VALUE, format, ap);
va_end(ap);
axutil_log_impl_write_to_file(log, mutex, AXIS2_LOG_LEVEL_DEBUG,
filename, linenumber, value);
}
}
else
fprintf(stderr, please check your log and buffer);
}
Also in the other log functions I have changed this line
if (AXIS2_LOG_LEVEL_DEBUG = log-level)
to
if (AXIS2_LOG_LEVEL_DEBUG = log-level
log-level != AXIS2_LOG_LEVEL_SERVICE)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: What Type of SSL BIO is used in HTTP Transport?
Senaka, Do you have a specific usage scenario for the NIO sockets ? Right now we use blocking sockets in Axis2/C. The code is much simpler and since we are using threads to distribute the workload no need to over complicate stuff by adding NIO sockets unless there is a specific need :). Thanks sahan On 10/25/07, Dumindu Pallewela [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: What Type of SSL BIO is used in SSL enabled HTTP Transport? It should depend on the socket that is in use by Axis2/C. Please refer to the axis2_ssl_utils_initialize_ssl() function in ssl_utils.c. I'm referring to the files, axis2/c/src/core/transport/http/sender/ssl/ssl_*.* What I'm interested in knowing is whether it is blocking or non-blocking or whether it may vary according to the scenario. That (i.e., the behavior of Axis2/C sockets) I'm uncertain of. However, it seems that SSL client's function depends much on this fact! HTH, Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2/Core] Proposal for Error Logging
[EMAIL PROTECTED] wrote: Hi all, While inspecting the error logging mechanism in Axis2/C, AXIS2_ERROR_SET, according to the implementation, is used to log only the last error that was reported. By doing so, all other error messages that sometimes do have significant importance are lost. We could use an alternative approach using AXIS2_LOG_ERROR where each and every error reported would in fact be logged. AXIS2_ERROR_SET, has been the popular choice of reporting errors in the core. Therefore, we have two alternatives. 1. Use an array to store errors reported using AXIS2_ERROR_SET, and handle them (do some error handling and logging) one after the other. +1 Damitha 2. Use AXIS2_LOG_ERROR, to log all errors of importance, as they occur. I would rather suggest alternative 1, to be a better approach in the long run. But, for the moment it is better to focus on alternative 2. Senaka. - 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]
Re: [jira] Commented: (AXIS2C-732) Log file size increasing with no upper limit
Senaka Fernando (JIRA) wrote: [ https://issues.apache.org/jira/browse/AXIS2C-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537558 ] Senaka Fernando commented on AXIS2C-732: Yes, this is a good improvement. But, I have few suggestions to make it better. 1. We will not start from scratch, instead, the new file will have an entry saying that the log file was backed up to the respective location, before starting with the logging procedure. This well help the potential user of the log file identify what is going on. 2. Need to find mechanisms to handle situations such as, if log entries are needed to be made during the process of backing up the log file. (Because, renaming and creating a new file takes some time) This is handled in a thread mutex. 3. The user must be able to define the maximum size of the log file during installation. And, this value must lie between a pre-defined range, or else the default must be assumed. Yes it is good to have the maximum size set during deployment. There are two options 1. Put an param entry in axis2.xml. 2. Give as server argument when starting. Damitha Regards, Senaka Log file size increasing with no upper limit Key: AXIS2C-732 URL: https://issues.apache.org/jira/browse/AXIS2C-732 Project: Axis2-C Issue Type: Improvement Reporter: Damitha Kumarage Currently log file size increase with no upper limit. In a production environment this is not acceptable. To solve it I have provided a simple solution of after the file size exceeds a certain limit it automatically is backed up to a x.log.old file and log is written to from scratch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN]VTD-XML 2.2
XimpleWare is proud to announce the the release of version 2.2 of VTD-XML, the next generation XML parsers/indexer/slicer/editor. This release significantly expands VTD-XML's ability to slice, split, edit and incrementally update the XML documents. To this end, we introduce the concept of namespace-compensated element fragment. This release also adds VTD+XML index writing capability to the VTD Navigator class. Other enhancements in this release include index size pre-computation, support for HTTP get, and some bug fixes. To download the latest release, please go to http://sourceforge.net/project/showfiles.php?group_id=110612. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What Type of SSL BIO is used in HTTP Transport?
On Thu, 2007-10-25 at 20:19 -0400, Sahan Gamage wrote: Senaka, Do you have a specific usage scenario for the NIO sockets ? Well, I was trying to patch a bug, and the reporter mentioned about the error, SSL_ERROR_WANT_READ which can be avoided in a blocking BIO, and wanted to make sure before commenting. https://issues.apache.org/jira/browse/AXIS2C-728 Right now we use blocking sockets in Axis2/C. The code is much simpler and since we are using threads to distribute the workload no need to over complicate stuff by adding NIO sockets unless there is a specific need :). Thanks sahan On 10/25/07, Dumindu Pallewela [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: What Type of SSL BIO is used in SSL enabled HTTP Transport? It should depend on the socket that is in use by Axis2/C. Please refer to the axis2_ssl_utils_initialize_ssl() function in ssl_utils.c. I'm referring to the files, axis2/c/src/core/transport/http/sender/ssl/ssl_*.* What I'm interested in knowing is whether it is blocking or non-blocking or whether it may vary according to the scenario. That (i.e., the behavior of Axis2/C sockets) I'm uncertain of. However, it seems that SSL client's function depends much on this fact! HTH, Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform - 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]
Re: [jira] Commented: (AXIS2C-728) SSL client authenticate failed
Hi, I believe that this document would provide a possible insight to
what might have happened.
http://www.openssl.org/docs/ssl/SSL_accept.html#NOTES
Regards,
Senaka
On Thu, 2007-10-25 at 15:19 -0700, Dumindu Pallewela (JIRA) wrote:
[
https://issues.apache.org/jira/browse/AXIS2C-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537749
]
Dumindu Pallewela commented on AXIS2C-728:
--
I couldn't look in to this in detail, but going through the description, I
sense that this is potentially a bug (Last time I tested it worked!). Could
you please provide some more details on how this bug can be reproduced? Were
you using Apache2 as your server? And the rest of the configuration?
(mod_ssl, openssl, etc version)
SSL client authenticate failed
--
Key: AXIS2C-728
URL: https://issues.apache.org/jira/browse/AXIS2C-728
Project: Axis2-C
Issue Type: Bug
Components: core/transport
Affects Versions: 1.1.0
Environment: OS:RedHar Linux v5
Reporter: tsunoda norihiko
Fix For: 1.1.0
I make a client program to perform SSL client authentication/server
authentication using Axis2/C.
In the environment only for the server authentication, the program worked
normally.
But I cannot receive the response message in the client authentication
environment and detected error code 82 - Input stream is NULL in msg_ctx.
When I confirm server side.
SSL handshake and message transmission to the client worked normally.
I found that an error occurred in axis2_ssl_stream_read() when I debugged a
client program.
${axis2c_src}/src/core/transport/http/sender/ssl/ssl_stream.c
146 int AXIS2_CALL
147 axis2_ssl_stream_read(
148 axutil_stream_t *stream,
149 const axutil_env_t *env,
150 void *buffer,
151 size_t count
152 )
153 {
154 ssl_stream_impl_t *stream_impl = NULL;
155 int read = -1;
156 int len = -1;
157
158 AXIS2_ENV_CHECK(env, AXIS2_CRITICAL_FAILURE);
159
160 stream_impl = AXIS2_INTF_TO_IMPL(stream);
161
162 read = SSL_read(stream_impl-ssl , buffer, count);
163 switch (SSL_get_error(stream_impl-ssl , read))
164 {
165 case SSL_ERROR_NONE:
166 len = read;
167 break;
168 case SSL_ERROR_ZERO_RETURN:
169 len = -1;
170 break;
171 case SSL_ERROR_SYSCALL:
172 AXIS2_LOG_ERROR(env-log, AXIS2_LOG_SI,
173 SSL Error: Premature close);
174 len = -1;
175 break;
176 default:
177 len = -1;
178 break;
179 }
180 return len;
181 }
At the default case in the switch online 176, the value of len should not
be -1.
SSL_get_error() return SSL_ERROR_WANT_READ.
The specifications of SSL_read() seem to be as follows.
In this case a call to SSL_get_error(3) with the return value of SSL_read()
will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE.
As at any time a re-negotiation is possible, a call to SSL_read() can also
cause write operations!
The calling process then must repeat the call after taking appropriate
action to satisfy the needs of SSL_read().
(http://www.openssl.org/docs/ssl/SSL_read.html#NOTES)
I could get a response message when I debug as follows.
${axis2c_src}/src/core/transport/http/sender/http_client.c
413 /* read the status line */
414 do
415 {
416 memset(str_status_line, 0, 512);
417 while ((read = axutil_stream_read(client-data_stream,
env, tmp_buf,
418 1)) 0)
419 {
420 tmp_buf[read] = '\0';
421 strcat(str_status_line, tmp_buf);
422 if (0 != strstr(str_status_line, AXIS2_HTTP_CRLF))
423 {
424 end_of_line = AXIS2_TRUE;
425 break;
426 }
427 }
+428 /* debug */
+429 #if 0
430 if (read 0)
431 {
432 AXIS2_LOG_DEBUG(env-log, AXIS2_LOG_SI, [axis2c] http
client , response timed out);
433 AXIS2_ERROR_SET(env-error,
434 AXIS2_ERROR_RESPONSE_TIMED_OUT,
435 AXIS2_FAILURE);
436 return -1;
437 }
438 else if (read == 0)
+439 #endif
+440 if(read == 0)
441 {
442 AXIS2_ERROR_SET(env-error,
443
[jira] Commented: (AXIS2C-728) SSL client authenticate failed
[
https://issues.apache.org/jira/browse/AXIS2C-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537834
]
Senaka Fernando commented on AXIS2C-728:
Hi Tsunoda,
It seems that a blocking BIO is used in here.
I suggest you try this modification, which would solve your problem according
the the OpenSSL man pages. But, since I couldn't tryout your scenario, I'm not
quite sure whether it solves your problem.
${axis2c_src}/src/core/transport/http/sender/ssl/ssl_stream.c
158 AXIS2_ENV_CHECK(env, AXIS2_CRITICAL_FAILURE);
159
160 stream_impl = AXIS2_INTF_TO_IMPL(stream);
+ 161
+ 162 SSL_CTX_set_mode(stream_impl-ctx, SSL_MODE_AUTO_RETRY);
+ 163
164 read = SSL_read(stream_impl-ssl , buffer, count);
165 switch (SSL_get_error(stream_impl-ssl , read))
166 {
167 case SSL_ERROR_NONE:
168 len = read;
167 break;
Please be kind enough to let us know if your problem was solved.
And, it would be better if you could provide us with info on how this bug can
be reproduced, as Dumindu mentioned before.
Regards,
Senaka.
SSL client authenticate failed
--
Key: AXIS2C-728
URL: https://issues.apache.org/jira/browse/AXIS2C-728
Project: Axis2-C
Issue Type: Bug
Components: core/transport
Affects Versions: 1.1.0
Environment: OS:RedHar Linux v5
Reporter: tsunoda norihiko
Fix For: 1.1.0
I make a client program to perform SSL client authentication/server
authentication using Axis2/C.
In the environment only for the server authentication, the program worked
normally.
But I cannot receive the response message in the client authentication
environment and detected error code 82 - Input stream is NULL in msg_ctx.
When I confirm server side.
SSL handshake and message transmission to the client worked normally.
I found that an error occurred in axis2_ssl_stream_read() when I debugged a
client program.
${axis2c_src}/src/core/transport/http/sender/ssl/ssl_stream.c
146 int AXIS2_CALL
147 axis2_ssl_stream_read(
148 axutil_stream_t *stream,
149 const axutil_env_t *env,
150 void *buffer,
151 size_t count
152 )
153 {
154 ssl_stream_impl_t *stream_impl = NULL;
155 int read = -1;
156 int len = -1;
157
158 AXIS2_ENV_CHECK(env, AXIS2_CRITICAL_FAILURE);
159
160 stream_impl = AXIS2_INTF_TO_IMPL(stream);
161
162 read = SSL_read(stream_impl-ssl , buffer, count);
163 switch (SSL_get_error(stream_impl-ssl , read))
164 {
165 case SSL_ERROR_NONE:
166 len = read;
167 break;
168 case SSL_ERROR_ZERO_RETURN:
169 len = -1;
170 break;
171 case SSL_ERROR_SYSCALL:
172 AXIS2_LOG_ERROR(env-log, AXIS2_LOG_SI,
173 SSL Error: Premature close);
174 len = -1;
175 break;
176 default:
177 len = -1;
178 break;
179 }
180 return len;
181 }
At the default case in the switch online 176, the value of len should not be
-1.
SSL_get_error() return SSL_ERROR_WANT_READ.
The specifications of SSL_read() seem to be as follows.
In this case a call to SSL_get_error(3) with the return value of SSL_read()
will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE.
As at any time a re-negotiation is possible, a call to SSL_read() can also
cause write operations!
The calling process then must repeat the call after taking appropriate action
to satisfy the needs of SSL_read().
(http://www.openssl.org/docs/ssl/SSL_read.html#NOTES)
I could get a response message when I debug as follows.
${axis2c_src}/src/core/transport/http/sender/http_client.c
413 /* read the status line */
414 do
415 {
416 memset(str_status_line, 0, 512);
417 while ((read = axutil_stream_read(client-data_stream, env,
tmp_buf,
418 1)) 0)
419 {
420 tmp_buf[read] = '\0';
421 strcat(str_status_line, tmp_buf);
422 if (0 != strstr(str_status_line, AXIS2_HTTP_CRLF))
423 {
424 end_of_line = AXIS2_TRUE;
425 break;
426 }
427 }
+428 /* debug */
+429 #if 0
430 if (read 0)
431 {
432 AXIS2_LOG_DEBUG(env-log, AXIS2_LOG_SI, [axis2c] http
client , response timed out);
433 AXIS2_ERROR_SET(env-error,
434 AXIS2_ERROR_RESPONSE_TIMED_OUT,
435 AXIS2_FAILURE);
436
Re: [jira] Created: (AXIS2C-734) Enabling Service Level Custom Logs
Here's my +1
Regards,
Senaka
On Thu, 2007-10-25 at 16:16 -0700, Damitha Kumarage (JIRA) wrote:
Enabling Service Level Custom Logs
--
Key: AXIS2C-734
URL: https://issues.apache.org/jira/browse/AXIS2C-734
Project: Axis2-C
Issue Type: New Feature
Reporter: Damitha Kumarage
A service developer may be interested only in the debug messages he put in
his service. He don't need all the debug messages from within the
core/transport of the axis2c engine. Currently what happen is when the axis2c
engine is started
with log enabled all the log messages core/transport are printed to the log
file so that service developers log messages are obscured.
To avoid that I propose another log level called AXIS2_LOG_LEVEL_SERVICE.
When the axis2c engine is started with this log level only the critical and
error logs are printed from the core/ trasport.
All the log messages written by the service developer with the logging
function AXIS2_LOG_SERVICE( ) are also be printed.
Also If we start the axis2c engine with the log level debug, the messages
written using AXIS2_LOG_SERVICE( ) are printed. If we start the axis2c engine
with the log level critical or error only the error/critical log messages are
printed.
The function that I have added to the log.c to implement this is
AXIS2_EXTERN void AXIS2_CALL
axutil_log_impl_log_service(
axutil_log_t * log,
const axis2_char_t * filename,
const int linenumber,
const axis2_char_t * format,
...)
{
FILE *fd = NULL;
axutil_thread_mutex_t *mutex = NULL;
if (log format)
{
if (!(fd = AXIS2_INTF_TO_IMPL(log)-stream))
{
fprintf(stderr, Stream is not found\n);
}
if (!(mutex = AXIS2_INTF_TO_IMPL(log)-mutex))
{
fprintf(stderr, Log mutex is not found\n);
}
if (AXIS2_LOG_LEVEL_DEBUG = log-level)
{
char value[AXIS2_LEN_VALUE + 1];
va_list ap;
va_start(ap, format);
AXIS2_VSNPRINTF(value, AXIS2_LEN_VALUE, format, ap);
va_end(ap);
axutil_log_impl_write_to_file(log, mutex, AXIS2_LOG_LEVEL_DEBUG,
filename, linenumber, value);
}
}
else
fprintf(stderr, please check your log and buffer);
}
Also in the other log functions I have changed this line
if (AXIS2_LOG_LEVEL_DEBUG = log-level)
to
if (AXIS2_LOG_LEVEL_DEBUG = log-level
log-level != AXIS2_LOG_LEVEL_SERVICE)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2]Unsupported type http://www.w3.org/2001/XMLSchema string
Hi, all, there is a problem when axis2 parsing the returned soap message, what's the problem here ? Thanks a lot! Exception in thread main java.lang.RuntimeException: java.lang.RuntimeException: Unsupported type http://www.w3.org/2001/XMLSchema string at localhost.echoserver.EchoServerStub.fromOM(EchoServerStub.java:1096) at localhost.echoserver.EchoServerStub.Echo(EchoServerStub.java:160) at TClient.main(TClient.java:15) Caused by: java.lang.RuntimeException: Unsupported type http://www.w3.org/2001/XMLSchema string at localhost.echoserver.EchoServerStub$ExtensionMapper.getTypeObject( EchoServerStub.java:336) at localhost.echoserver.EchoServerStub$EchoResponse$Factory.parse( EchoServerStub.java:672) at localhost.echoserver.EchoServerStub.fromOM(EchoServerStub.java:1090) ... 2 more The returned soap message is: SOAP-ENV:Envelope xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:ZSI=http://www.zolera.com/schemas/ZSI/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;http://www.w3.org/2001/XMLSchema-instance%22%3E SOAP-ENV:Header/SOAP-ENV:Header SOAP-ENV:Body EchoResponse id=o4b33f48 xsi:type=xsd:stringf/EchoResponse /SOAP-ENV:Body /SOAP-ENV:Envelope
[jira] Commented: (AXIS-2664) Axis generate invalid soap when using RPC/encoded where exists omittable fields (minOccurs=0) and nillable=false
[
https://issues.apache.org/jira/browse/AXIS-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537566
]
Marinó A. Jónsson commented on AXIS-2664:
-
I just hit this snag. My first google hit was issue AXIS-2054, which really
explains in detail my problem. The resolution for that issue, however, is
too superficial and doesn't work for me.
The key point Patrick makes here is that when a field _is not_ nillable but
_is_ omittable it should indeed be omitted.
So - a compromise might look something like this:
// if meta data says minOccurs=0, then we should skip
// it if its value is null and either it's not nillable or we
// aren't doing SOAP encoding.
if (isOmittable (!isNillable || !isEncoded)) {
continue;
}
Axis generate invalid soap when using RPC/encoded where exists omittable
fields (minOccurs=0) and nillable=false
Key: AXIS-2664
URL: https://issues.apache.org/jira/browse/AXIS-2664
Project: Axis
Issue Type: Bug
Components: Serialization/Deserialization
Affects Versions: 1.4
Reporter: Patrick Di Loreto
While using axis 1.4 with webMethods EAI system I have encountered the
following problem :
Axis generate an invalid soap message in RPC/encoded WS where exists
omittable (minOccurs=0) fields and nillable = false.
Axis don't omit the field when null but put it in soap message with nill
value.
Exploring source code I have found the following check in
org.apache.axis.encoding.ser.BeanSerializer.java class at row : 222
// if meta data says minOccurs=0, then we can skip
// it if its value is null and we aren't doing
SOAP
// encoding.
if (isOmittable !isEncoded) {
continue;
}
It seams a choice to not apply omittable behavior while using soap/encoding.
Is it correct ? Is it a standard ? WebMethods aspect that this field was
omitted and not nill.
I fixed it just as follow :
// if meta data says minOccurs=0, then we can skip
// it if its value is null and we aren't doing
SOAP
// encoding.
if (isOmittable){ // !isEncoded) {
continue;
}
What can I aspect on next version of Axis ?
Thx
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3243) Invalid content-type on http header. missed and
[ https://issues.apache.org/jira/browse/AXIS2-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537590 ] Kevin Huber commented on AXIS2-3243: I tracked this down to a regression in Axiom 1.2.5. There is a fix in their source code base, but there hasn't been a new release with the fix yet. Invalid content-type on http header. missed and --- Key: AXIS2-3243 URL: https://issues.apache.org/jira/browse/AXIS2-3243 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.3 Environment: Windows XP Professional JDK 1.5.0_12 Reporter: jun sato i tried to send SOAP message to server by using Axis2 1.3. but server couldn't parse SOAP request message. soap client program is sample program that is provided by Axis2 1.3. i found that and were missed at value of start in Content-Type. --Axis2 1.3-- Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_B4170274BA716AED8C1191484266445; type=text/xml; start=0.urn:uuid:[EMAIL PROTECTED]; charset=UTF-8 i believe that correct content-type is --Axis2 1.2-- Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_B4170274BA716AED8C1191484266445; type=text/xml; start=0.urn:uuid:[EMAIL PROTECTED]; charset=UTF-8 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation
minOccurs=0 always generated by Java2WSDL - problems with .NET client generation -- Key: AXIS2-3300 URL: https://issues.apache.org/jira/browse/AXIS2-3300 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.3 Reporter: Mauro Molinari When you try to expose a POJO as a webservice, suppose you have two Java methods with the following signatures: public Integer a(String, Integer) public String b(Integer, String) Java2WSDL adds the minOccurs=0 for each element of each complex type, both for the input parameters and for the output parameters. When generating clients using .NET WebService Studio 2.0, the result is the following: - all the generated C# methods input parameters are doubled, except for the string ones: the doubled parameters are booleans whose meaning is: is the previous parameter specified or not? - all the generated C# methods return parameters are void, except for the string ones The actual result are clients with methods like these: public void a(string, int, bool); public string b(int, bool, string); This is obviously a problem, particularly for the void return type. If I remove minOccurs=0, clients are generated correctly by .NET WebService Studio 2.0. The issue is this: why does Java2WSDL always adds minOccurs=0? If its meaning were it can be null, I think nillable=true attribute should be more appropriate... Moreover, if I substitute Integer with int in the original Java class methods, minOccurs=0 is still added by Java2WSDL, even if an int cannot be null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Build break....
Glen and all, We (Synapse) also has faced the same problem, I am happy to take the nightly build script management of Synapse. Can I host the build under my account @ apache as a cron? if so will I be able to copy the artifacts to the following location [1] (Synapse nightly path) [EMAIL PROTECTED] /www/people.apache.org/dist/synapse]$ ls -al total 6 drwxrwxr-x 3 dimsapsite 512 Aug 27 03:46 . drwxrwxr-x 30 apsite apsite 512 Aug 27 03:46 .. drwxrwxr-x 2 dimsapsite 512 Aug 28 03:31 nightly [EMAIL PROTECTED] /www/people.apache.org/dist/synapse]$ I think you will have to change the permissions in here. [1] - http://people.apache.org/dist/synapse/nightly/ Thanks, Ruwan On 10/24/07, David Illsley [EMAIL PROTECTED] wrote: On 24/10/2007, Glen Daniels [EMAIL PROTECTED] wrote: Sanjiva Weerawarana wrote: Its not a PMC chair thing as much as someone needs to run the scripts under their ID. I believe the script is simply to do a build and copy the file to the right place. That's correct. Is there any way to make this user independent? It would be great if we could do that, but I'm not sure exactly how it'd happen. I'll make some inquiries on infra, though! In any case, thanks David for taking care of it. David, were you in fact volunteering? :) If so please feel free, but I'm also happy to look into it if you can't. Yeah, I think I was volunteering. ;-) I'll see what I can do to get things going tonight and get back to you with any problems! David -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ruwan Linton http://www.wso2.org - Oxygenating the Web Services Platform
[jira] Created: (AXIS2-3301) Generated WSDL has validation errors when methods launch exceptions
Generated WSDL has validation errors when methods launch exceptions
---
Key: AXIS2-3301
URL: https://issues.apache.org/jira/browse/AXIS2-3301
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Affects Versions: 1.3
Reporter: Mauro Molinari
Priority: Critical
Suppose you have the following class:
package test;
public class TestService
{
public String login(String username, String password) throws MyException,
MyException2
{
return ticket;
}
public void logout(String ticket) throws MyException, MyException2
{
}
}
and two simple extensions of java.lang.Exception called test.MyException and
test.MyException2.
When running java2wsdl with the following options:
java2wsdl -o output-path -of TestService.wsdl -cp classpah -cn
test.TestService
I get a WSDL (attached as TestService.wsdl) for which Eclipse gives two
validation errors:
src-resolve.4.2: Error resolving component 'ns1:Exception'. It was detected
that 'ns1:Exception' is in namespace 'http://test', but components from this
namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns1:Exception'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
TestService.wsdlline 4
src-resolve.4.2: Error resolving component 'ns0:MyException'. It was detected
that 'ns0:MyException' is in namespace 'http://test/xsd', but components from
this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns0:MyException'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
TestService.wsdlline 8
As suggested by some users in Eclipse WTP newsgroup, I tried the following:
java2wsdl -o output-path -of TestService_Exception.wsdl -cp classpah -xc
java.lang.Exception -cn test.TestService
The result is a WSDL (attached as TestService_Exception.wsdl) for which Eclipse
gives three validation errors:
src-resolve.4.2: Error resolving component 'ns1:Exception'. It was detected
that 'ns1:Exception' is in namespace 'http://test', but components from this
namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns1:Exception'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
TestService_Exception.wsdl line 4
src-resolve.4.2: Error resolving component 'xs:Throwable'. It was detected that
'xs:Throwable' is in namespace 'http://www.w3.org/2001/XMLSchema', but
components from this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'xs:Throwable' needs
to be changed. If this is the correct namespace, then an appropriate 'import'
tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
TestService_Exception.wsdl line 4
src-resolve.4.2: Error resolving component 'ns0:MyException'. It was detected
that 'ns0:MyException' is in namespace 'http://test/xsd', but components from
this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns0:MyException'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
TestService_Exception.wsdl line 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[jira] Updated: (AXIS2-3301) Generated WSDL has validation errors when methods launch exceptions
[
https://issues.apache.org/jira/browse/AXIS2-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Molinari updated AXIS2-3301:
--
Attachment: src.zip
Java source files
Generated WSDL has validation errors when methods launch exceptions
---
Key: AXIS2-3301
URL: https://issues.apache.org/jira/browse/AXIS2-3301
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Affects Versions: 1.3
Reporter: Mauro Molinari
Priority: Critical
Attachments: src.zip
Suppose you have the following class:
package test;
public class TestService
{
public String login(String username, String password) throws MyException,
MyException2
{
return ticket;
}
public void logout(String ticket) throws MyException, MyException2
{
}
}
and two simple extensions of java.lang.Exception called test.MyException and
test.MyException2.
When running java2wsdl with the following options:
java2wsdl -o output-path -of TestService.wsdl -cp classpah -cn
test.TestService
I get a WSDL (attached as TestService.wsdl) for which Eclipse gives two
validation errors:
src-resolve.4.2: Error resolving component 'ns1:Exception'. It was detected
that 'ns1:Exception' is in namespace 'http://test', but components from this
namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns1:Exception'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
TestService.wsdlline 4
src-resolve.4.2: Error resolving component 'ns0:MyException'. It was detected
that 'ns0:MyException' is in namespace 'http://test/xsd', but components from
this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns0:MyException'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
TestService.wsdlline 8
As suggested by some users in Eclipse WTP newsgroup, I tried the following:
java2wsdl -o output-path -of TestService_Exception.wsdl -cp classpah -xc
java.lang.Exception -cn test.TestService
The result is a WSDL (attached as TestService_Exception.wsdl) for which
Eclipse gives three validation errors:
src-resolve.4.2: Error resolving component 'ns1:Exception'. It was detected
that 'ns1:Exception' is in namespace 'http://test', but components from this
namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns1:Exception'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
TestService_Exception.wsdl line 4
src-resolve.4.2: Error resolving component 'xs:Throwable'. It was detected
that 'xs:Throwable' is in namespace 'http://www.w3.org/2001/XMLSchema', but
components from this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'xs:Throwable'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
TestService_Exception.wsdl line 4
src-resolve.4.2: Error resolving component 'ns0:MyException'. It was detected
that 'ns0:MyException' is in namespace 'http://test/xsd', but components from
this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns0:MyException'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
[jira] Updated: (AXIS2-3301) Generated WSDL has validation errors when methods launch exceptions
[
https://issues.apache.org/jira/browse/AXIS2-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Molinari updated AXIS2-3301:
--
Attachment: wsdl.zip
Generated WSDL files
Generated WSDL has validation errors when methods launch exceptions
---
Key: AXIS2-3301
URL: https://issues.apache.org/jira/browse/AXIS2-3301
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Affects Versions: 1.3
Reporter: Mauro Molinari
Priority: Critical
Attachments: src.zip, wsdl.zip
Suppose you have the following class:
package test;
public class TestService
{
public String login(String username, String password) throws MyException,
MyException2
{
return ticket;
}
public void logout(String ticket) throws MyException, MyException2
{
}
}
and two simple extensions of java.lang.Exception called test.MyException and
test.MyException2.
When running java2wsdl with the following options:
java2wsdl -o output-path -of TestService.wsdl -cp classpah -cn
test.TestService
I get a WSDL (attached as TestService.wsdl) for which Eclipse gives two
validation errors:
src-resolve.4.2: Error resolving component 'ns1:Exception'. It was detected
that 'ns1:Exception' is in namespace 'http://test', but components from this
namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns1:Exception'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
TestService.wsdlline 4
src-resolve.4.2: Error resolving component 'ns0:MyException'. It was detected
that 'ns0:MyException' is in namespace 'http://test/xsd', but components from
this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns0:MyException'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService.wsdl'.
TestService.wsdlline 8
As suggested by some users in Eclipse WTP newsgroup, I tried the following:
java2wsdl -o output-path -of TestService_Exception.wsdl -cp classpah -xc
java.lang.Exception -cn test.TestService
The result is a WSDL (attached as TestService_Exception.wsdl) for which
Eclipse gives three validation errors:
src-resolve.4.2: Error resolving component 'ns1:Exception'. It was detected
that 'ns1:Exception' is in namespace 'http://test', but components from this
namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns1:Exception'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
TestService_Exception.wsdl line 4
src-resolve.4.2: Error resolving component 'xs:Throwable'. It was detected
that 'xs:Throwable' is in namespace 'http://www.w3.org/2001/XMLSchema', but
components from this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'xs:Throwable'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
TestService_Exception.wsdl line 4
src-resolve.4.2: Error resolving component 'ns0:MyException'. It was detected
that 'ns0:MyException' is in namespace 'http://test/xsd', but components from
this namespace are not referenceable from schema document
'file:///C:/Documents%20and%20Settings/mauro/Documenti/Eclipse33%20workspace/Problema%20Axis2/TestService_Exception.wsdl'.
If this is the incorrect namespace, perhaps the prefix of 'ns0:MyException'
needs to be changed. If this is the correct namespace, then an appropriate
'import' tag should be added to
Re: [Axis2] Build break....
Hi Ruwan! Ruwan Linton wrote: We (Synapse) also has faced the same problem, I am happy to take the nightly build script management of Synapse. Can I host the build under my account @ apache as a cron? if so will I be able to copy the artifacts to the following location [1] (Synapse nightly path) To do this, you'll need to be in the apsite group to write those directories. I'll ask infra to add you. --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Build break....
Thanks Glen. Ruwan On 10/25/07, Glen Daniels [EMAIL PROTECTED] wrote: Hi Ruwan! Ruwan Linton wrote: We (Synapse) also has faced the same problem, I am happy to take the nightly build script management of Synapse. Can I host the build under my account @ apache as a cron? if so will I be able to copy the artifacts to the following location [1] (Synapse nightly path) To do this, you'll need to be in the apsite group to write those directories. I'll ask infra to add you. --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ruwan Linton http://www.wso2.org - Oxygenating the Web Services Platform
RE: Web application and Axis2 deployment issue...
Hi Robert, Thanks for your response. I already have required configuration for web logic server for axis2. I am able to deploy my webservice using axis2 on Weblogic server 9.2. The problem I am facing when I trying to create stubs to access these webservice which are deployed in axis2 war on Weblogic. I am creating stubs in separate web application. Here I am making mistake is that I am copying all axis2 jar into my we applications WEB-INF/lib folder and then I arching it as war and trying to deploy it along with Web service war on Weblogic. So in my Ear I have axis2 war and web application war now. I am getting following error when I am trying to deploy them together. My question is where should keep all axis2 jars in web application war so that it can be accessible at run time? Or What is standard procedure to create stub in web application and refer those to required axis2 war? Thanks and Regards Dinesh Ghutake 302-636-5401 *3640 -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 5:43 PM To: axis-dev@ws.apache.org Subject: Re: Web application and Axis2 deployment issue... Weblogic apparently has stax there somewhere. Try reading this link to see if that helps: http://ws.apache.org/axis2/1_3/app_server.html Robert On 10/24/07, Dinesh Ghutake [EMAIL PROTECTED] wrote: Hi, I am involved into the development of web service application using axis2, hibernate etc. Our front end application is built using struts. My project ear structure is as below: MYProjEAR: - APP-INF - classes -lib - axis2 (all web services deployed in this project) - ejbs - META-INF(application.xml and Weblogic-application.xml) - WEBAPP-WAR WEB-INF Lib (I have copied all axis2 jar here along with webapplication jars ) Struts classes Home -jsp Etc... In Web application I have stubs created to call web services. I am getting this exception when I am try to deploy My Proj. ear on Weblogic 9.2 server. Oct 24, 2007 2:26:56 PM EDT Error Console BEA-240003 Console encountered the followin g error weblogic.application.ModuleException: at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:292) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModu leDriver.ja va:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleL istenerInvo ker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Deploym entCallback Flow.java:360) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv er.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Deploy mentCallbac kFlow.java:56) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Deploy mentCallbac kFlow.java:46) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java: 615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv er.java:26) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java :191) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentS tateChecker .java:147) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppCon tainerInvok er.java:61) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.creat eAndPrepare Container(ActivateOperation.java:189) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPre pare(Activa teOperation.java:87) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepa re(Abstract Operation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeployment Prepare(Dep loymentManager.java:718) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymen tList(Deplo ymentManager.java:1185) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(De ploymentMan ager.java:247) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepar e(Deploymen tServiceDispatcher.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallback Deliverer.d oPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at
[jira] Created: (AXIS2-3302) JAXWS: Performance: Remove Synchronization in JAXBUtils
JAXWS: Performance: Remove Synchronization in JAXBUtils --- Key: AXIS2-3302 URL: https://issues.apache.org/jira/browse/AXIS2-3302 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Problem: The following method(s) in JAXBUtils have an undesireable side effect: public static JAXBContext getJAXBContext(TreeSetString contextPackages, ...) On input, the contextPackages set contains package values. On output, the contextPackages set contains package values, but the invalid package values are removed. The contextPackages object is used by multiple threads. Currently we use some flawed synchronization logic to avoid ConcurrentModificationExceptions. Proposal: The above side effect is really a legacy artifact of the development of JAXBUtils. Axis2 does not depend on the side effect. I am removing the side effect (and thus removing unnecessary synchronization) After the change: On input, the contextPackages set contains package values. On output, the contextPackages set contains the same package values. No one should be depending on this side effect, so this should be a safe change. I will commit a fix later today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3302) JAXWS: Performance: Remove Synchronization in JAXBUtils
[ https://issues.apache.org/jira/browse/AXIS2-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-3302. --- Resolution: Fixed Revision = 588288 JAXWS: Performance: Remove Synchronization in JAXBUtils --- Key: AXIS2-3302 URL: https://issues.apache.org/jira/browse/AXIS2-3302 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Assignee: Rich Scheuerle Problem: The following method(s) in JAXBUtils have an undesireable side effect: public static JAXBContext getJAXBContext(TreeSetString contextPackages, ...) On input, the contextPackages set contains package values. On output, the contextPackages set contains package values, but the invalid package values are removed. The contextPackages object is used by multiple threads. Currently we use some flawed synchronization logic to avoid ConcurrentModificationExceptions. Proposal: The above side effect is really a legacy artifact of the development of JAXBUtils. Axis2 does not depend on the side effect. I am removing the side effect (and thus removing unnecessary synchronization) After the change: On input, the contextPackages set contains package values. On output, the contextPackages set contains the same package values. No one should be depending on this side effect, so this should be a safe change. I will commit a fix later today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3303) Provide getter/setters on DescriptionBuilderComposite for InputStream to handler chain config file
Provide getter/setters on DescriptionBuilderComposite for InputStream to handler chain config file -- Key: AXIS2-3303 URL: https://issues.apache.org/jira/browse/AXIS2-3303 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Affects Versions: nightly Reporter: Dustin Amrhein Assignee: Dustin Amrhein Fix For: nightly Provide getters/setters on the DescriptionBuilderComposite for an InputStream to a handler chain configuration file. Also, the EndpointDescriptionImpl will look for the InputStream if it did not find an @HandlerChain annotation when marshalling in the handler chain information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3303) Provide getter/setters on DescriptionBuilderComposite for InputStream to handler chain config file
[ https://issues.apache.org/jira/browse/AXIS2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Amrhein updated AXIS2-3303: -- Attachment: patch.txt Provide getter/setters on DescriptionBuilderComposite for InputStream to handler chain config file -- Key: AXIS2-3303 URL: https://issues.apache.org/jira/browse/AXIS2-3303 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Affects Versions: nightly Reporter: Dustin Amrhein Assignee: Dustin Amrhein Fix For: nightly Attachments: patch.txt Provide getters/setters on the DescriptionBuilderComposite for an InputStream to a handler chain configuration file. Also, the EndpointDescriptionImpl will look for the InputStream if it did not find an @HandlerChain annotation when marshalling in the handler chain information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3304) NPE when demarshalling a fault response
NPE when demarshalling a fault response --- Key: AXIS2-3304 URL: https://issues.apache.org/jira/browse/AXIS2-3304 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Priority: Minor When demarshalling a fault response, the faultBeanDescriptor cannot be found in some cases. This occurs when there are more than one EndpointDescription for a ServiceDescription. The runtime description is never regenerated after the first endpoint...adding changes to set a dirty bit as well as changes to not throw the NPE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2675) maven java2wsdl and wsdl2code plugins do not work
[ https://issues.apache.org/jira/browse/AXIS2-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537761 ] Hellmut Adolphs commented on AXIS2-2675: Anders, see my comment in the linked issue... maven java2wsdl and wsdl2code plugins do not work - Key: AXIS2-2675 URL: https://issues.apache.org/jira/browse/AXIS2-2675 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.3, 1.2, 1.1 Reporter: Michael Lake Assignee: Deepal Jayasinghe Priority: Critical HERE IS THE ERROR: [EMAIL PROTECTED]:~/service$ mvn wsdl2code:wsdl2code [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'wsdl2code'. [INFO] artifact org.apache.axis2.maven2:axis2-wsdl2code-maven-plugin: checking for updates from maven.snapshots [INFO] artifact org.apache.axis2.maven2:axis2-wsdl2code-maven-plugin: checking for updates from central Downloading: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/axis2/maven2/axis2-wsdl2code-maven-plugin/1.1/axis2-wsdl2code-maven-plugin-1.1.pom 2K downloaded Downloading: http://people.apache.org/maven-snapshot-repository/org/apache/axis2/maven2/axis2-maven-tools/1.1/axis2-maven-tools-1.1.pom [WARNING] Unable to get resource 'org.apache.axis2.maven2:axis2-maven-tools:pom:1.1' from repository maven.snapshots (http://people.apache.org/maven-snapshot-repository) Downloading: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/axis2/maven2/axis2-maven-tools/1.1/axis2-maven-tools-1.1.pom 3K downloaded Downloading: http://repo1.maven.org/maven//org.apache.axis2/poms/axis2-parent-1.1.pom 16K downloaded Downloading: http://people.apache.org/maven-snapshot-repository/org/apache/axis2/maven2/axis2-wsdl2code-maven-plugin/1.1/axis2-wsdl2code-maven-plugin-1.1.jar [WARNING] Unable to get resource 'org.apache.axis2.maven2:axis2-wsdl2code-maven-plugin:maven-plugin:1.1' from repository maven.snapshots (http://people.apache.org/maven-snapshot-repository) Downloading: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/axis2/maven2/axis2-wsdl2code-maven-plugin/1.1/axis2-wsdl2code-maven-plugin-1.1.jar 10K downloaded [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-wsdl2code-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 6 seconds [INFO] Finished at: Tue May 15 11:29:42 EDT 2007 [INFO] Final Memory: 1M/3M [INFO] THIS IS IN MY POM.XML: build plugins plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-java2wsdl-maven-plugin/artifactId configuration classNamecom.example.service.StockQuoteService/className /configuration executions execution goals goaljava2wsdl/goal /goals /execution /executions /plugin plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId configuration packageNamecom.example.gen/packageName /configuration executions execution goals goalwsdl2code/goal /goals /execution /executions /plugin /plugins /build -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-3304) NPE when demarshalling a fault response
[ https://issues.apache.org/jira/browse/AXIS2-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roy A. Wood Jr. reassigned AXIS2-3304: -- Assignee: Roy A. Wood Jr. It appears a similar fix was made as part of rev. 554712 by 'gawor'. That fix basically resets the runtime description each time an endpoint is added to the service description. Added additional changes to prevent the NPE. NPE when demarshalling a fault response --- Key: AXIS2-3304 URL: https://issues.apache.org/jira/browse/AXIS2-3304 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Roy A. Wood Jr. Priority: Minor When demarshalling a fault response, the faultBeanDescriptor cannot be found in some cases. This occurs when there are more than one EndpointDescription for a ServiceDescription. The runtime description is never regenerated after the first endpoint...adding changes to set a dirty bit as well as changes to not throw the NPE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3305) When WSDL exists, set wsdl properties for provider
When WSDL exists, set wsdl properties for provider -- Key: AXIS2-3305 URL: https://issues.apache.org/jira/browse/AXIS2-3305 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Roy A. Wood Jr. Priority: Minor To support WS-Notification, add functionality to supply provider-based endpoints with a context property for wsdl operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-3304) NPE when demarshalling a fault response
[ https://issues.apache.org/jira/browse/AXIS2-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roy A. Wood Jr. closed AXIS2-3304. -- NPE when demarshalling a fault response --- Key: AXIS2-3304 URL: https://issues.apache.org/jira/browse/AXIS2-3304 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Roy A. Wood Jr. Priority: Minor When demarshalling a fault response, the faultBeanDescriptor cannot be found in some cases. This occurs when there are more than one EndpointDescription for a ServiceDescription. The runtime description is never regenerated after the first endpoint...adding changes to set a dirty bit as well as changes to not throw the NPE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3304) NPE when demarshalling a fault response
[ https://issues.apache.org/jira/browse/AXIS2-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roy A. Wood Jr. resolved AXIS2-3304. Resolution: Fixed In addition to the posted comment and another change in MethodMarshallerUtils (rev. 588377) . This is now complete. NPE when demarshalling a fault response --- Key: AXIS2-3304 URL: https://issues.apache.org/jira/browse/AXIS2-3304 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Roy A. Wood Jr. Priority: Minor When demarshalling a fault response, the faultBeanDescriptor cannot be found in some cases. This occurs when there are more than one EndpointDescription for a ServiceDescription. The runtime description is never regenerated after the first endpoint...adding changes to set a dirty bit as well as changes to not throw the NPE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-3243) Invalid content-type on http header. missed and
[ https://issues.apache.org/jira/browse/AXIS2-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jun sato closed AXIS2-3243. --- Resolution: Fixed Invalid content-type on http header. missed and --- Key: AXIS2-3243 URL: https://issues.apache.org/jira/browse/AXIS2-3243 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.3 Environment: Windows XP Professional JDK 1.5.0_12 Reporter: jun sato i tried to send SOAP message to server by using Axis2 1.3. but server couldn't parse SOAP request message. soap client program is sample program that is provided by Axis2 1.3. i found that and were missed at value of start in Content-Type. --Axis2 1.3-- Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_B4170274BA716AED8C1191484266445; type=text/xml; start=0.urn:uuid:[EMAIL PROTECTED]; charset=UTF-8 i believe that correct content-type is --Axis2 1.2-- Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_B4170274BA716AED8C1191484266445; type=text/xml; start=0.urn:uuid:[EMAIL PROTECTED]; charset=UTF-8 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis/Axis2] benchmark with 100 clients?
Hi All; Does anyone has a Axis1 benchmark numbers (and may be client source) which tested with 100+ concurrent clients? If you have one and OK with sharing it, please drop a link. Thanks Srinath -- Srinath Perera: Indiana University, Bloomington http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani Beauty of style and harmony and grace and good rhythm depend on simplicity -- Plato - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Proposal to chage the method signature of set/get documentation
Hi Devs, Currently the method signature for det/get documentation in AxisDescriptio is as follows. public String getDocumentation(); public void setDocumentation(String documentation); As you can see it treats the documentation as a string. There are occasions where the documentation can be XML though. If the documentation is XML what we do currently is wrap it in CDATA tags. This works, but its not the best sollution. I propose deprecating the above methods and introducing the following methods which that documentation as an OMNode. public OMNode getDocumentation(); public void setDocumentation(OMNode documentation); This will enable us to set the documentation as an OMText or OMElement. If needed we can retain the old methods without deprecating them (Just leave them as a convenience method), where they will call into the new method. The above proposal is targeted at improving the wsdl served by Axis2. With what we have currently documentation which is XML is wrapped in CDATA tags in the WSDL. Thanks, Keith. -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: [Axis2] Proposal to chage the method signature of set/get documentation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 from me. If some one calls the earlier methods, you can serialize the OMNode and return, which i think is the easier to do. Chinthaka keith chapman wrote: Hi Devs, Currently the method signature for det/get documentation in AxisDescriptio is as follows. public String getDocumentation(); public void setDocumentation(String documentation); As you can see it treats the documentation as a string. There are occasions where the documentation can be XML though. If the documentation is XML what we do currently is wrap it in CDATA tags. This works, but its not the best sollution. I propose deprecating the above methods and introducing the following methods which that documentation as an OMNode. public OMNode getDocumentation(); public void setDocumentation(OMNode documentation); This will enable us to set the documentation as an OMText or OMElement. If needed we can retain the old methods without deprecating them (Just leave them as a convenience method), where they will call into the new method. The above proposal is targeted at improving the wsdl served by Axis2. With what we have currently documentation which is XML is wrapped in CDATA tags in the WSDL. Thanks, Keith. -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHIWucjON2uBzUhh8RAtmCAKCabVIEiPB/qtLSnzhw2PvW5Jj+GwCaA17r xWy2A3una8h4LSgppYDjGYM= =2Dyf -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Proposal to chage the method signature of set/get documentation
On 10/26/07, Eran Chinthaka [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 from me. If some one calls the earlier methods, you can serialize the OMNode and return, which i think is the easier to do. Sure. Thanks, Keith. Chinthaka keith chapman wrote: Hi Devs, Currently the method signature for det/get documentation in AxisDescriptio is as follows. public String getDocumentation(); public void setDocumentation(String documentation); As you can see it treats the documentation as a string. There are occasions where the documentation can be XML though. If the documentation is XML what we do currently is wrap it in CDATA tags. This works, but its not the best sollution. I propose deprecating the above methods and introducing the following methods which that documentation as an OMNode. public OMNode getDocumentation(); public void setDocumentation(OMNode documentation); This will enable us to set the documentation as an OMText or OMElement. If needed we can retain the old methods without deprecating them (Just leave them as a convenience method), where they will call into the new method. The above proposal is targeted at improving the wsdl served by Axis2. With what we have currently documentation which is XML is wrapped in CDATA tags in the WSDL. Thanks, Keith. -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHIWucjON2uBzUhh8RAtmCAKCabVIEiPB/qtLSnzhw2PvW5Jj+GwCaA17r xWy2A3una8h4LSgppYDjGYM= =2Dyf -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
