Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Wed, 28 Jul 2004 11:07:55 -0400
From: Alan Cabrera <Alan.Cabrera@reuters.com>
Subject: RE: [Fwd: FW: EWS and Geronimo (THANKS)]
To: dev@geronimo.apache.org, dims@apache.org, hemapani@opensource.lk
Message-id: <T6b11d9a803840a276b654@ritig7a.amers.ime.reuters.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Thread-Topic: [Fwd: FW: EWS and Geronimo (THANKS)]
Thread-Index: AcR0skO+JjdL/Pc0TgijEBh2tsDepgAAl4MA
Content-Class: urn:content-classes:message

Works great.  Thanks guys!

-----Original Message-----
From: Davanum Srinivas [mailto:davanum@gmail.com]=20
Sent: Wednesday, July 28, 2004 10:52 AM
To: dev@geronimo.apache.org; hemapani@opensource.lk
Cc: dims@apache.org
Subject: Re: [Fwd: FW: EWS and Geronimo (THANKS)]

"maven test" under modules/axis works fine now. Am building
ews-SNAPSHOT.jar every 6 hours now :)

thanks,
dims

On Wed, 28 Jul 2004 08:44:56 -0400 (EDT), Srinath Perera
<hemapani@opensource.lk> wrote:
> Thanks dims, I have put the patch in to the JIRA, issue I creatrd
earlier
> @ http://nagoya.apache.org/jira/browse/GERONIMO-269 also more info is
at
> the mail [Fwd: [NEW PATCH-FIX FOR TESTS]webservice deployment in
geronimo]
> in the geronimo dev and as a comment in the issue.
>=20
> Basically patch has two parts
> 1) patch for cvs manage folders
> 2) cvs not managed sample Dir is zipped as sample.zip please put it in
to
> the modules/axis/src before build (that is how in my last patch
samples
> are missing)
>=20
> Thanks for help
> Srinath
>=20
>=20
>=20
>=20
> > Srinath,
> >
> > - don't undo, If there are any changes in EWS, go ahead and apply it
> > and i will rebuild the ews-SNAPSHOT.jar
> > - Submit a JIRA for the patch to geronimo-axis module and i'll take
care
> > of it.
> >
> > thanks,
> > dims
> >
> > On Wed, 28 Jul 2004 03:39:57 -0400 (EDT), Srinath Perera
> > <hemapani@opensource.lk> wrote:
> >> Sorry I have meesed it up .. it works well in the morning with the
> >> updated
> >> code :(. If the Patch I sent is checked in this is fixed.. But I
belive
> >> it
> >> would take some time.
> >>
> >> 1) Shall I undo the changes in the EWS
> >> 2) I can sent a patch to update the axis module to fix this and
later
> >> submit a new patch based on new code to the patch I sent erlier
(fixing
> >> test cases)
> >>
> >> Opps that is tough .. I got to update the ews so that the when dims
> >> looking at the patch it works with the ews-SNAPSHOT.jar he is is
> >> downloading and doing so will breaks the current code by the
updated
> >> jar.
> >> Is there a way to protect the both ends.
> >>
> >> pls help me to sort this out
> >> Thanks
> >> Srianth
> >>
> >>
> >>
> >> > Forwarded on behalf of Alan who is having mailer problems
> >> >
> >> > -------- Original Message --------
> >> > Subject: FW: EWS and Geronimo (THANKS)
> >> > Date: Wed, 28 Jul 2004 00:28:14 -0400
> >> > From: Alan D. Cabrera <adc@toolazydogs.com>
> >> > To: <jboynes@gluecode.com>
> >> >
> >> >
> >> > Ok.  Two more questions.
> >> >
> >> > First, it seems that a change in EWS has not been propagated to
> >> Geronimo
> >> > and we're getting this error:
> >> >
> >> >
C:\dev\geronimo\modules\axis\src\java\org\apache\geronimo\axis\GeronimoW
> >> > sDeployContext.java:27:
> >> org.apache.geronimo.axis.GeronimoWsDeployContext
> >> > is not abstract and does not override abstract method isCompile()
in
> >> > org.apache.geronimo.ews.ws4j2ee.toWs.Ws4J2
> >> > eeDeployContext
> >> > public class GeronimoWsDeployContext implements
Ws4J2eeDeployContext {
> >> >         ^
> >> > 1 error
> >> >
> >> >
> >> > Second, you have a jndi.properties file in your jar with the
following
> >> > contents:
> >> >
> >> >
java.naming.factory.initial=3Dorg.jnp.interfaces.NamingContextFactory
> >> > java.naming.provider.url=3Djnp://localhost:1099
> >> > java.naming.factory.url.pkgs=3Dorg.jboss.naming:org.jnp.interfaces
> >> >
> >> >
> >> > Not sure if this is kosher, use wise and ASF policy wise.  As for
the
> >> > former, the Geronimo server barfs when it can't find
> >> > org.jnp.interfaces.NamingContextFactory when it loads up the
remote
> >> JMX
> >> > server.  Can we remove it?
> >> >
> >> >
> >> > Regards,
> >> > Alan
> >> >
> >> >> -----Original Message-----
> >> >> From: Srinath Perera [mailto:hemapani@opensource.lk]
> >> >> Sent: Tuesday, July 27, 2004 8:42 PM
> >> >> To: dev@geronimo.apache.org
> >> >> Subject: Re: EWS and Geronimo
> >> >>
> >> >> We were wondering should ews go to ws-fx (to a webservice
project )
> >> or
> >> > in
> >> >> to the geronimo. It is still not decided. I accept the fact that
it
> >> > should
> >> >> use the geronimo group ID if it continue to use the Geronimo
package
> >> >> space.
> >> >> Or else that should replace with "ws" and put the geronimo
specific
> >> > code
> >> >> in to geronimo axis module. To me there are good reasons to both
and
> >> > do
> >> >> not mind either.
> >> >>
> >> >> Thanks
> >> >> Srinath
> >> >>
> >> >> > Why doesn't EWS use the Geronimo maven group id?  Its code is
in
> >> the
> >> >> > Geronimo package-space.
> >> >> > Just wondering.
> >> >> > Regards,
> >> >> >
> >> >> > Alan
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >> ------------------------------------
> >> Lanka Sofware Foundation
> >> ------------------------------------
> >>
> >
> >
> > --
> > Davanum Srinivas - http://webservices.apache.org/~dims/
> >
> >
>=20
>=20
> ------------------------------------
> Lanka Sofware Foundation
> ------------------------------------
>=20


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


-----------------------------------------------------------------
        Visit our Internet site at http://www.reuters.com

Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit http://www.reuters.com/messaging

Any views expressed in this message are those of  the  individual
sender,  except  where  the sender specifically states them to be
the views of Reuters Ltd.