Hi Venkat;
for better or for worse I am the only one activein the ews list ;)
Thanks very much for the comments
> I just took a look at the ews stuff and tried few things with
> JBossAS4. Just wanted to share my observations. May be these
> well-known, yet-to-be-taken-careof issues. Just sending them for the
> record-sake anyway.
>
> I ran ws4j2ee tool of EWS on of google.jar. Here are some observations.
>
> 1. I was expecting a jaxrpc-mapping.xml in META-INF, which basically
> defines wsdl type mappings. Are we doing this via deploy.wsdd?
a mapping file is created, Should we add it to the google.jar (input
jar) automatically? , have a look at the automatically generated code
to find the mapping file.
> 2. In case of jboss4, i think it automatically generates the wsdd file
> for the specific service,
> and updates the Axis engine configuration though AxisServiceMBean,
> without ever needing the server-config.wsdd. If this is true, we might
> not need deploy.wsdd atleast for jboss.
I have not try to do it via internals of the jboss, but at least for
jboss I think you are correct
> 3. The ejb-jar.xml in out/META-INF, which is also packaged in
> googlesearchport-ewsimpl.jar,
> has "null" as content for <display-name> and <local> elements.
>
> 4. The value for <ejb-link> inside webservices.xml doesn't match the
> <ejb-name> in ejb-jar.xml and in jboss.xml
> 5. Inside webservices.xml, I get <display-name>French
> Zip</display-name>. What's French Zip??
will check 3, 4,5
> 6. The build.xml in the out folder has a hard-coded value for the
> property "maven.repo.local". Need to be changed to
> "${user.home}/.maven/repository"
yap
thanks
Srinath
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
