HTTPS over proxy?

2008-04-17 Thread Balazs Borbely
Hello All,

The proxy configuration for http requests is working fine; when I switch to
https it is not working.
Is https over proxy supported? Do I need some specific configuration?


Thanks in advance,
Balazs


RE : RE : [Axis2]Apache Axis2/C 1.3.1 RC2 (resolved)

2008-04-17 Thread Lefrancois, Carl
Hi Dushshantha,

This one is my mistake.  I am doing a hack to add xsi:type attributes directly 
in the node serialization code where data is copied into start_input_str, and I 
had neglected to change the malloc call for this buffer.

The axutil_stream_write problem is unrelated and I hope to find out what is 
causing that.

Carl


-Message d'origine-
De : Dushshantha Chandradasa [mailto:[EMAIL PROTECTED] 
Envoyé : jeudi, avril 17, 2008 02:04
À : Apache AXIS C User List
Objet : Re: RE : [Axis2]Apache Axis2/C 1.3.1 RC2


Hi Carl,

I tried generating code from the axis2 java latest nightly build for 
Calculator.wsdl in the \test\resources\wsdl folder.  I got the 
service and client working  fine.  I used RC2 Windows Binary. If you can 
provide a sample wsdl to regenerate your problem, We can test it and see 
whether the problem exists.

regards,
Dushshantha 


On Wed, Apr 16, 2008 at 11:48 PM, Lefrancois, Carl <[EMAIL PROTECTED]> wrote:

Hello,

I did an SVN update today while trying to debug a problem with
axutil_stream_write and my WSDL2C generated stub got an access violation
during the stub create call.

The fault line was the call to free(ptr) in util\src\allocator.c:

void AXIS2_CALL
axutil_allocator_free_impl(
   axutil_allocator_t * allocator,
   void *ptr)
{
   free(ptr);
}

Reverting to version 1.3.0 makes the crash go away.

I'm assuming the latest SVN revision is the same code as 1.3.1 RC2!

HTH
Carl


-Message d'origine-
De : Dinesh Premalal [mailto:[EMAIL PROTECTED] De la part de Dinesh
Premalal
Envoyé : mercredi, avril 16, 2008 09:06
À : axis-c-user@ws.apache.org
Objet : [Axis2]Apache Axis2/C 1.3.1 RC2



Hi All,

  I have packed and uploaded Apache Axis2/C 1.3.1 RC2 here
  [1]. Please test and send your feedback.

thanks,
Dinesh

1.http://people.apache.org/~dinesh/release/Axis2C-1.3.1-RC2/


--
http://nethu.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 _

"Ce message est confidentiel, à l'usage exclusif du destinataire
ci-dessus et son contenu ne représente en aucun cas un engagement de la
part de AXA, sauf en cas de stipulation expresse et par écrit de la part
de AXA. Toute publication, utilisation ou diffusion, même partielle,
doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce
message, merci d'en avertir immédiatement l'expéditeur."

"This e-mail message is confidential, for the exclusive use of the
addressee and its contents shall not constitute a commitment by AXA,
except as otherwise specifically provided in writing by AXA. Any
unauthorized disclosure, use or dissemination, either whole or partial,
is prohibited. If you are not the intended recipient of the message,
please notify the sender immediately."


-
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: RE : RE : problem modifying axutil_stream_t in AXIOM_DATA_SOURCE node

2008-04-17 Thread Dushshantha Chandradasa
Hi Carl,

I tried generating code from the axis2 java latest nightly build for
Calculator.wsdl in the \test\resources\wsdl folder.  I got
the service and client working  fine.  I used RC2 Windows Binary. If you can
provide a sample wsdl to regenerate your problem, We can test it and see
whether the problem exists. And also please attach your .c file which
implements your business logic.

regards
Dushshantha


On Thu, Apr 17, 2008 at 1:58 AM, Lefrancois, Carl <
[EMAIL PROTECTED]> wrote:

> What is the debugger trace?  I am restricted to win32  :*  so if you mean
> some nix thing then I can't.  I will try to get the trace to you tomorrow.
>
> Thanks for your help
>
> Carl
>
> -Message d'origine-
> De : Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi, avril 16, 2008 14:32
> À : Apache AXIS C User List
> Objet : Re: RE : problem modifying axutil_stream_t in AXIOM_DATA_SOURCE
> node
>
>
> Is it possible to get the debugger trace?
>
> Samisa...
>
> Lefrancois, Carl wrote:
> > Here is my latest trace.  The crash location has changed.  Now it is
> > crashing on the memcpy inside the axutil_stream_write function, which
> > seems like the same error as last time, only trapped earlier.
> >
> > To recap, these are the calls causing the crash:
> >
> > readSize = axutil_stream_read (stream, env, buffer, streamSize);
> > readSize = axutil_stream_write (stream, env, buffer, streamSize);
> >
> >
> > Carl
> >
> >
> >
> >
> > [Wed Apr 16 14:06:04 2008] [debug]
> > c:\ws\axis_svn\src\core\engine\phase.c(121) axis2_handler_t
> > *request_uri_based_dispatcher added to the index 0 of the phase
> > Transport [Wed Apr 16 14:06:04 2008] [debug]
> > c:\ws\axis_svn\src\core\engine\phase.c(121) axis2_handler_t
> > *addressing_based_dispatcher added to the index 1 of the phase
> > Transport [Wed Apr 16 14:06:04 2008] [debug]
> > c:\ws\axis_svn\src\core\engine\phase.c(121) axis2_handler_t
> > *rest_dispatcher added to the index 0 of the phase Dispatch [Wed Apr
> > 16 14:06:04 2008] [debug] c:\ws\axis_svn\src\core\engine\phase.c(121)
> > axis2_handler_t *soap_message_body_based_dispatcher added to the index
> > 1 of the phase Dispatch [Wed Apr 16 14:06:04 2008] [debug]
> c:\ws\axis_svn\src\core\engine\phase.c(121) axis2_handler_t
> *soap_action_based_dispatcher added to the index 2 of the phase Dispatch
> [Wed Apr 16 14:06:04 2008] [debug]
> c:\ws\axis_svn\src\core\engine\phase.c(121) axis2_handler_t
> *dispatch_post_conditions_evaluator added to the index 0 of the phase
> PostDispatch [Wed Apr 16 14:06:04 2008] [debug]
> c:\ws\axis_svn\src\core\engine\phase.c(121) axis2_handler_t *context_handler
> added to the index 1 of the phase PostDispatch [Wed Apr 16 14:06:04 2008]
> [debug] c:\ws\axis_svn\src\core\deployment\conf_builder.c(233) no custom
> dispatching order found continue with default dispatching order [Wed Apr 16
> 14:06:04 2008] [debug] c:\ws\axis_svn\util\src\class_loader.c(141) Object
> loaded successfully [Wed Apr 16 14:06:04 2008] [debug]
> c:\ws\axis_svn\util\src\class_loader.c(141) Object loaded successfully [Wed
> Apr 16 14:06:04 2008] [error] c:\ws\axis_svn\util\src\dir_handler.c(220) No
> files in the path H:\Projets\SOA\Axis2c\axis_svn\build\deploy/modules.
> > [Wed Apr 16 14:06:04 2008] [error]
> c:\ws\axis_svn\util\src\dir_handler.c(220) No files in the path
> H:\Projets\SOA\Axis2c\axis_svn\build\deploy/services.
> > [Wed Apr 16 14:06:04 2008] [debug]
> c:\ws\axis_svn\src\core\phaseresolver\phase_resolver.c(117) Service name is
> : __ANONYMOUS_SERVICE__
> >
> >
> >
> >
> >
> >
> >
> >
> > -Message d'origine-
> > De : Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> > Envoyé : mercredi, avril 16, 2008 12:08
> > À : Apache AXIS C User List
> > Objet : Re: problem modifying axutil_stream_t in AXIOM_DATA_SOURCE node
> >
> >
> > Lefrancois, Carl wrote:
> >
> >> Hi list,
> >>
> >> Please help with some unexpected behaviour.  This morning I started
> >> using the functions axutil_stream_read and axutil_stream_write to
> >> modify the contents of an AXIOM_DATA_SOURCE node in my payload, and I
> >> am getting program crashes.
> >>
> >>
> >
> > Can you send in the traces of the crashes?
> >
> > Samisa...
> >
> >
> >> I am using WSDL2C generated code stubs, and modifying the
> >> axis2_stub_xx.c file to make changes to the payload.  I inserted a
> >> function at the top of the file and call this function just after the
> >> payload is generated on the line:
> >>
> >>  payload = adb__serialize(_, env, NULL, NULL,
> AXIS2_TRUE,
> >> NULL, NULL);
> >>   modify_stream_contents(payload, env);
> >>
> >> My function navigates the payload node to find the AXIOM_DATA_SOURCE
> >> node.  It then reads the contents into a buffer and does some
> >> modification, then writes the modified data back into the stream.  I'm
> >> including a minimal version of the function below that only reads the
> >> stream and writes it back again without modification.
> >>
> >> The behaviour is strange: if the axutil_stre