Hi, Upul,
Thanks for your advice.
It works now!
2007/10/22, Upul Godage <[EMAIL PROTECTED]>:
>
> There is this ServiceLifeCycle interface. When implemented and configured,
> startUp, shutDown will be called at service deployment, undeployment times
> respectively. Deploying services hap
Hi Ruchith,
Yes, I think tha handler should be in the addressing module, and so
yes, I think we should use a property to allow the AxisOperation to be
verified (and easily extracted by the security handlers).
David
On 19/10/2007, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
> Hi David,
>
> I agree
Hi,
I have one javase application and now I need to change it into axis2
webservice and publish it.
While it was javase application, it run fine(certanlly, it could db
connections). But after I change it into axis2 service, when the application
tries to create database connection, there w
java.lang.reflect.InvocationTargetException
---
Key: AXIS-2703
URL: https://issues.apache.org/jira/browse/AXIS-2703
Project: Axis
Issue Type: Bug
Affects Versions: 1.4
Environment: Windows
[
https://issues.apache.org/jira/browse/AXIS-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_1253
]
Javier A. Ortiz commented on AXIS-2703:
---
By the way the offending code is in a Binding stub created by wsdl2java
NPE in AxisEngine when trying to use TCP transport
--
Key: AXIS2-3293
URL: https://issues.apache.org/jira/browse/AXIS2-3293
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: clien
Change default http protocol to 1.0 from 1.1
Key: AXIS2-3294
URL: https://issues.apache.org/jira/browse/AXIS2-3294
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: client-ap
Hi, this sounds good - please see comments inline.
On 19/10/2007, David Illsley <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
> It's not entirely clear to me what you're trying to do... are you
> looking to add client and service samples into the axis2 build which
> you can then run against WebSphere? I
Hi Jeremy,
Thanks for the quick response.
The WebSphere interoperobility tests will be targeted to run against
out-of-the-box Axis2. Furthermore, the developer will have the flexibility
to change the endpoints to a WebSphere server of their own choice. No
downloads, or WebSphere prereqs/softwa
Yes they will be.
On 10/20/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> Andrew
>
> Are these WebSphere endpoints going to be publicly (internet) accessible?
>
> Paul
>
> On 10/19/07, Andrew Das < [EMAIL PROTECTED]> wrote:
> >
> > Hi David,
> > Thanks for the quick response. The samples we int
We prefer to put in an automated process in Axis2 so that we don't have to
manage when and where to run the samples. Any developer, including internal
developers can run our samples against a snapshot or released Axis2 build.
This will free us from managing and maintaining the test cycles, if done
I have no objecting on introducing these samples, and I think it is good
to have such a set of samples. But my only worry is I should be able to
run the build off line. Therefore rather than adding to the build
directly let's have a separate maven option to run those sample ,
something like
mvn cle
[
https://issues.apache.org/jira/browse/AXIS2-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536830
]
Lars Kruse Pedersen commented on AXIS2-3059:
Thanks for the fix, but...
Isn't there supposed to be a colo
[Concerning commons-logging]
> also what would you replace it with ?
I actually think that the JDK 1.4 logging APIs would probably do the
trick, not have "jar hell" problems, and be functional enough for most
everyone.
--
Tom Jordahl
-Original Message-
From: Ajith Ranabahu [mailto:[EMAI
:-) I don't think you want to put the websphere samples in that
directory (modile/integration/manual)... I don't think it actually
builds, and it may not have a long lifespan (see below).
How about you create a module in modules/integration/websphere which
isn't hooked in to the build by default.
Hi Tom,
On 10/22/07, Tom Jordahl <[EMAIL PROTECTED]> wrote:
> [Concerning commons-logging]
> > also what would you replace it with ?
>
> I actually think that the JDK 1.4 logging APIs would probably do the
> trick, not have "jar hell" problems, and be functional enough for most
> everyone.
>
Agre
I've been stuck in classloader hell many times and moving to
commons-logging 1.1 solved a lot of problems for me - there's been a
lot of work put into that area. Also, everything else in apache land
uses commons-logging. +1 for keeping it.
Robert
On 10/22/07, Tom Jordahl <[EMAIL PROTECTED]> wrote
If you really want to have hardcoded endpoints etc. then the solution is
to host those samples somewhere and have some automated execution of those
against Axis2 nightly builds.
Its not acceptable to commit into the ASF repo some code that is only
designed to work against some WebSphere sample
Hi,
Yesterdy I asked Antonio about the db connection creation in a service.
The answer was: Put the db driver .jar in /axis2/WEB-INF/lib, all jars what
you want to use must go here. I followed that and did it, but with a little
change(because I didn't have a web server then), I put the db driv
19 matches
Mail list logo
