Re: Questions for Axis2 folks re: JAXWS

[Lin Sun]

I have been giving some thoughts on this prob yesterday.  By looking at 
the java comments for AxisService.createService, it seems this method is 
only for RPCMessageReceiver, but we are using JAXWSMessageReceiver here. 
 Maybe dims or Lasantha can comment on this.


seems there are 2 scenarios:
1) no webservices.xml, no .wsdl, just java files with annotation:

One solution I can think of is to create a temp wsdl file when 
Axis2Builder is called based on the java files (seems this can be done 
either using the Java2WSDLCodegenEngine from Axis2 or using Sun's 
tools), and then set PortInfo properties there.   When 
Axis2WebServiceContainer is called, we'll treat it as wsdl file already 
exists.   Delete the temp wsdl file at the end.


2) no webservices.xml, just .wsdl and java files with annotation.

In this case, since there is no webservices.xml, should we scan the 
module to see if .wsdl file is included in Axis2Builder?  if so, set the 
wsdl-file property in PortInfo.


I haven't implemented anything yet as I think we should all agree to a 
solution first.


Lin

Jeff Genender wrote:

o.a.g.Axis2WebserviceContainer, line 99. A not-filled in PortInfo is
passed in since G is not processing a WebService annotation, and thus an
AxisService.create is called on line 104.

When Axis2WebserviceContainer.getWsdl() is ultimately called,
doService2() is called (line 212), then to processGetRequest (line 398),
leading us to line 435 where the PortInfo is checked as to whether a
wsdl file has been passed in or not.  If it has, it spits out the wsdl.
 If it has not, then the AxisService.printWsdl() is called and that call
spits out a generated wsdl.

The crux here is that the PortInfo object does not have all of the info
filled in such as seiClass, wsdl file, etc.  That stuff would have been
gotten from examining the WebService annotation.

The question is, where does that examination or, should that
examination, take place? Geronimo or Axis2?

Jeff

Lasantha Ranaweera wrote:

Jeff,

Sorry for a late reply due to my time stamp difference and don't know
exactly you have solved this problem right now or not. Anyway here is my
comment.

Since you haven't given me exact source code I won't be able to point
you in to the exact source code in the Axis2. May be remote debugging
...  ;-) .

Thanks,
Lasantha

Jeff Genender wrote:

Ok...

I am pretty certain at this stage that the WebService annotation is not
getting processed.  Can you point me to the code that handles this in
Axis2?

Thanks,

Jeff



Jeff Genender wrote:
 

Thanks...this is very helpful.

Then by this, looking at the PortInfo, it appears as though it is not
stuffing in the WSDL file, which tells me it's a G thang ;-)

Jeff

Lasantha Ranaweera wrote:
   

Hi Jeff,

To my understanding if we have given a WSDL in an archive it should get
the priority than the information in the annotations.

In Axis2 integration there are two parts of implementation with one for
with WSDL which is mainly handling by G side while with annotations
from
Axis2. For me it is something missing in G side.

Somebody in the list please correct me  if I am wrong here .

Thanks,
Lasantha
Jeff Genender wrote:
 

Hi,

I have noticed when I deploy a war file (with a WSDL), I have a
certain
target name specified both in the WSDL and in the code that uses a
WebService annotation.

However, when I go retrieve the WSDL, I notice the target name
seems to
be munged according to the package name (backwards) of the code that
contains the WebService annotation.

Example...

I have include a WSDL called Hello.wsdl that is in the war file in the
web-inf/wsdl directory and starts with:

http://example.com/hello/xsd";>
...

I have a HelloWorld.java that has this:

package test.mypackage;

import javax.jws.WebMethod;
import javax.jws.WebService;

@WebService(name="HelloWorld", targetNamespace =
"http://example.org/hello/xsd";)
public class HelloWorld {

@WebMethod
public String sayHello(String me){
return "Hello "+me;
}
}

However, when I request the wsdl...I get something like this:

http://mypackage.test/xsd";>
...

Notice the targetnamespace was munged and changed from it's originally
declared namespace of "http://example.com/hello/xsd";.  I want the one
that is both declared in the included wsdl (or the one declared in the
annotation).

Is this a facet of Axis2 or is Geronimo not passing a proper PortInfo
object with the necessary stuff filled in?

Any light on this subject would be greatly appreciated ;-)

Thanks,

Jeff

  
  

build a war file using maven when web.xml is not there

[Lin Sun]

FYI -

I have seeing a maven failure when building a war file and web.xml is 
not there in the project for the purpose to test we support optional 
web.xml.


And there is already a maven feature request for this - 
http://jira.codehaus.org/browse/MWAR-30


Seems this will be an important feature for us to have to test this 
optional web.xml feature in Java EE 5 tho. :-(


Lin

Re: Questions for Axis2 folks re: JAXWS

[Lin Sun]

Hi Jeff,

I see, so you are like running my 2nd scenario.  Seems Axis2 has some 
code to process the annotation when generating wsdl from java files (see 
java2wsdl.SchemaGenerator.java, but I agree with you that I don't see 
annotation is processed when looking at the printWSDL method.  I would 
think it is best to have this code reside in Axis2.


Lin

Jeff Genender wrote:

Lin,

The problem here is that there is no webservices.xml and is solely
dependent upon the WebService annotation.

The question is...is Axis2 processing the WebService annotation? Upon
stepping through the code, I did not see that getting called anywhere.

One possible solution is that Geronimo processes the annotation and
passes the proper PortInfo object to Axis2.

I didn't want to do that if Axis2 was also processing the annotation.

Jeff



Lin Sun wrote:

Hi Jeff,

Thanks for noticing this issue.  I just ran a bit test myself with a
faily recent server built last Friday, and I got different result than
you.  Here are mine:

1) when targetNamespace are specified in both wsdl and annotation and in
webservices.xml file, the wsdl-file is used like:

WEB-INF/wsdl/greeter_control.wsdl

I would get

targetNamespace="http://apache.org/greeter_control";

from a ?wsdl request.

This code should be fairly straight-forward, as we would just generate
the WSDLDefition using AxisServiceGenerator().getWSDLDefition and write
it out to the response.

So in summary, this is working correctly.  Seems your scenario is this
case, so I would suggest making sure you have a reference to your
wsdl-file in your webservices.xml file.

2) When wsdl is not used, for example, I specify
"" in my webservices.xml file, then I would
notice the prob you described.   In this case, we rely on Axis2 and call
AxisService.printWSDL.

HTH, Lin





Jeff Genender wrote:

Ok...

I am pretty certain at this stage that the WebService annotation is not
getting processed.  Can you point me to the code that handles this in
Axis2?

Thanks,

Jeff



Jeff Genender wrote:

Thanks...this is very helpful.

Then by this, looking at the PortInfo, it appears as though it is not
stuffing in the WSDL file, which tells me it's a G thang ;-)

Jeff

Lasantha Ranaweera wrote:

Hi Jeff,

To my understanding if we have given a WSDL in an archive it should get
the priority than the information in the annotations.

In Axis2 integration there are two parts of implementation with one for
with WSDL which is mainly handling by G side while with annotations
from
Axis2. For me it is something missing in G side.

Somebody in the list please correct me  if I am wrong here .

Thanks,
Lasantha
Jeff Genender wrote:

Hi,

I have noticed when I deploy a war file (with a WSDL), I have a
certain
target name specified both in the WSDL and in the code that uses a
WebService annotation.

However, when I go retrieve the WSDL, I notice the target name
seems to
be munged according to the package name (backwards) of the code that
contains the WebService annotation.

Example...

I have include a WSDL called Hello.wsdl that is in the war file in the
web-inf/wsdl directory and starts with:

http://example.com/hello/xsd";>
...

I have a HelloWorld.java that has this:

package test.mypackage;

import javax.jws.WebMethod;
import javax.jws.WebService;

@WebService(name="HelloWorld", targetNamespace =
"http://example.org/hello/xsd";)
public class HelloWorld {

@WebMethod
public String sayHello(String me){
return "Hello "+me;
}
}

However, when I request the wsdl...I get something like this:

http://mypackage.test/xsd";>
...

Notice the targetnamespace was munged and changed from it's originally
declared namespace of "http://example.com/hello/xsd";.  I want the one
that is both declared in the included wsdl (or the one declared in the
annotation).

Is this a facet of Axis2 or is Geronimo not passing a proper PortInfo
object with the necessary stuff filled in?

Any light on this subject would be greatly appreciated ;-)

Thanks,

Jeff

  

Re: Questions for Axis2 folks re: JAXWS

[Lin Sun]

Hi Jeff,

Thanks for noticing this issue.  I just ran a bit test myself with a 
faily recent server built last Friday, and I got different result than 
you.  Here are mine:


1) when targetNamespace are specified in both wsdl and annotation and in 
webservices.xml file, the wsdl-file is used like:


WEB-INF/wsdl/greeter_control.wsdl

I would get

targetNamespace="http://apache.org/greeter_control";

from a ?wsdl request.

This code should be fairly straight-forward, as we would just generate 
the WSDLDefition using AxisServiceGenerator().getWSDLDefition and write 
it out to the response.


So in summary, this is working correctly.  Seems your scenario is this 
case, so I would suggest making sure you have a reference to your 
wsdl-file in your webservices.xml file.


2) When wsdl is not used, for example, I specify 
"" in my webservices.xml file, then I would 
notice the prob you described.   In this case, we rely on Axis2 and call 
AxisService.printWSDL.


HTH, Lin





Jeff Genender wrote:

Ok...

I am pretty certain at this stage that the WebService annotation is not
getting processed.  Can you point me to the code that handles this in Axis2?

Thanks,

Jeff



Jeff Genender wrote:

Thanks...this is very helpful.

Then by this, looking at the PortInfo, it appears as though it is not
stuffing in the WSDL file, which tells me it's a G thang ;-)

Jeff

Lasantha Ranaweera wrote:

Hi Jeff,

To my understanding if we have given a WSDL in an archive it should get
the priority than the information in the annotations.

In Axis2 integration there are two parts of implementation with one for
with WSDL which is mainly handling by G side while with annotations from
Axis2. For me it is something missing in G side.

Somebody in the list please correct me  if I am wrong here .

Thanks,
Lasantha
Jeff Genender wrote:

Hi,

I have noticed when I deploy a war file (with a WSDL), I have a certain
target name specified both in the WSDL and in the code that uses a
WebService annotation.

However, when I go retrieve the WSDL, I notice the target name seems to
be munged according to the package name (backwards) of the code that
contains the WebService annotation.

Example...

I have include a WSDL called Hello.wsdl that is in the war file in the
web-inf/wsdl directory and starts with:

http://example.com/hello/xsd";>
...

I have a HelloWorld.java that has this:

package test.mypackage;

import javax.jws.WebMethod;
import javax.jws.WebService;

@WebService(name="HelloWorld", targetNamespace =
"http://example.org/hello/xsd";)
public class HelloWorld {

@WebMethod
public String sayHello(String me){
return "Hello "+me;
}
}

However, when I request the wsdl...I get something like this:

http://mypackage.test/xsd";>
...

Notice the targetnamespace was munged and changed from it's originally
declared namespace of "http://example.com/hello/xsd";.  I want the one
that is both declared in the included wsdl (or the one declared in the
annotation).

Is this a facet of Axis2 or is Geronimo not passing a proper PortInfo
object with the necessary stuff filled in?

Any light on this subject would be greatly appreciated ;-)

Thanks,

Jeff

  

[jira] Updated: (GERONIMO-2923) Axis2: remove the deprecated processHTTPGetRequest method in Axis2 integration code

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2923:
--

Attachment: G2923.patch

Able to run a full build and verify existing tests work.

> Axis2: remove the deprecated processHTTPGetRequest method in Axis2 
> integration code
> ---
>
> Key: GERONIMO-2923
> URL: https://issues.apache.org/jira/browse/GERONIMO-2923
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
> Environment: sun 1.5 + winXP
>Reporter: Lin Sun
>Priority: Minor
> Attachments: G2923.patch
>
>
> As titled - Axis2 team suggested us to use RESTUtil.processURLRequest 
> instead.   Will put a patch whenever I can run a full build.:)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2841) Valve reports request method as GET even though POST request was made

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477589
 ] 

Lin Sun commented on GERONIMO-2841:
---

Experienced the same thing (request.getMethod() always returns GET) when 
running the same jaxws-ejb test with Axis2.   Thanks, Lin

> Valve reports request method as GET even though POST request was made
> -
>
> Key: GERONIMO-2841
> URL: https://issues.apache.org/jira/browse/GERONIMO-2841
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Reporter: Jarek Gawor
>
> The Request of EJBWebServiceValve in Tomcat return the request method as GET 
> even though POST request was sent. In similar class in Jetty the request 
> method is reported correctly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: build error - caused by change in Axis2 repo?

[Lin Sun]

Thanks Dims - I can build now.  I was able to build at around 10AM EST 
after blow up my local .m2/repository/org/apache/axis2, but not at 
around 3PM EST also after blow up my local 
.m2/repository/org/apache/axis2.  Any idea why this can happen? 
Doesn't look like a network glitch coz I could not download any axis2 
jars at that time after a few tries.


Lin

Davanum Srinivas wrote:

I haven't seen this yet...but I started another deploy just now in any
case. Could you please try in another 15-20 mins? Please blow up your
local .m2/repository/org/apache/axis2 before you do.

thanks,
dims

On 3/2/07, Lin Sun <[EMAIL PROTECTED]> wrote:

Hi,

I am hitting this build error after I clean my local axis2 repo.  And I
could not find axis2-jaxws-api-SNAPSHOT.jar in any of the repos below
either.

I can only find axis2-jaxws-api-.jar like
axis2-jaxws-20070302.130022-22.jar at the apache repo below.

WARNING] Unable to get resource
'org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT'from repository
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repsitory)

INFO]

ERROR] BUILD ERROR
INFO]

INFO] Failed to resolve artifact.

issing:
-
)
org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT

   Try downloading the file manually from the project
website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.axis2 -DartifactId=axis2-jaxs-api \

-Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

Path to dependency:
  1)
org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT
 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT

  -
   required artifact is missing.

  or artifact:

org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT

   rom the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots
(http://people.apache.org/repo/m2-snapshot-repository),   codehaus
(http://repository.codehaus.org),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
   codehaus-snapshots (http://snapshots.repository.codehaus.org),
   apache-incubator
(http://people.apache.org/repo/m2-incubating-repository/),
axis2-m2-repo (http://ws.zones.apache.org/repository2/),
tomcat-m2-repo
(http://tomcat.apache.org/dev/dist/m2-repository/)


INFO]

INFO] For more information, run Maven with the -e switch
INFO]

INFO] Total time: 3 minutes 20 seconds
INFO] Finished at: Fri Mar 02 15:29:58 EST 2007
INFO] Final Memory: 56M/63M
INFO]

[jira] Created: (GERONIMO-2923) Axis2: remove the deprecated processHTTPGetRequest method in Axis2 integration code

[Lin Sun (JIRA)]

Axis2: remove the deprecated processHTTPGetRequest method in Axis2 integration 
code
---

 Key: GERONIMO-2923
 URL: https://issues.apache.org/jira/browse/GERONIMO-2923
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: webservices
 Environment: sun 1.5 + winXP
Reporter: Lin Sun
Priority: Minor


As titled - Axis2 team suggested us to use RESTUtil.processURLRequest instead.  
 Will put a patch whenever I can run a full build.:)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

build error - caused by change in Axis2 repo?

[Lin Sun]

Hi,

I am hitting this build error after I clean my local axis2 repo.  And I 
could not find axis2-jaxws-api-SNAPSHOT.jar in any of the repos below 
either.


I can only find axis2-jaxws-api-.jar like 
axis2-jaxws-20070302.130022-22.jar at the apache repo below.


WARNING] Unable to get resource 
'org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT'from repository 
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repsitory) 

INFO] 
 
ERROR] BUILD ERROR 
   INFO] 
 
INFO] Failed to resolve artifact. 

   issing: 
   - 
   ) 
org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT 

  Try downloading the file manually from the project 
website. 
   Then, install it using the command: 
   mvn install:install-file 
-DgroupId=org.apache.axis2 -DartifactId=axis2-jaxs-api \ 

-Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file 

   Path to dependency: 
 1) 
org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 
2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT 

 - 
  required artifact is missing. 

 or artifact: 

org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 

  rom the specified remote repositories: 
   central (http://repo1.maven.org/maven2), 
   apache.snapshots 
(http://people.apache.org/repo/m2-snapshot-repository),   codehaus 
(http://repository.codehaus.org), 
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), 
  codehaus-snapshots (http://snapshots.repository.codehaus.org), 
  apache-incubator 
(http://people.apache.org/repo/m2-incubating-repository/), 
axis2-m2-repo (http://ws.zones.apache.org/repository2/), 
   tomcat-m2-repo 
(http://tomcat.apache.org/dev/dist/m2-repository/) 



   INFO] 
 
INFO] For more information, run Maven with the -e switch 
   INFO] 
 
INFO] Total time: 3 minutes 20 seconds 
   INFO] Finished at: Fri Mar 02 15:29:58 EST 2007 
   INFO] Final Memory: 56M/63M 
   INFO] 
 

Re: SystemDatabase

[Lin Sun]

When I paid attention to this some time last year, it was in var\derby 
directory and derby.log was not turned on by default.   Wonder if this 
is caused by a change in derby itself?


Lin

Prasad Kashyap wrote:

IIRC, the derby.log was always in the bin directory. But then again, I
could be wrong.

Cheers
Prasad

On 3/2/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:

I've noticed recently that the SystemDatabase/ directory and derby.log
files are being created in the current working directory (the
directory from which I start the server from using java -jar ..) and
not in the installation directory of Geronimo. I'm not sure if that's
new or just something I've just noticed now but either way this seems
weird.

Jarek

Re: [BUILD] TRUNK: Failed for Revision: 513251

[Lin Sun]

I think this was resolved by Jeff this morning:

---//--
Author: jgenender
Date: Thu Mar  1 07:12:33 2007
New Revision: 513374

URL: http://svn.apache.org/viewvc?view=rev&rev=513374
Log:
Remove test classes
---//--

Anyway I am not seeing this when I do a full build about 1.5 hours ago.

Lin

Sachin Patel wrote:

Hitting the same now.

-sachin


On Mar 1, 2007, at 5:23 AM, [EMAIL PROTECTED]  
wrote:



Building with Maven version: 2.0.5
Revision: 513251 built with tests included
See the full build-0500.log file at 
http://people.apache.org/~prasad/binaries/20070301/build-0500.log


Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//org/apache/axis2/axis2-kernel/20070301.070125-44/axis2-kernel-20070301.070125-44.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-kernel:pom:20070301.070125-44' from repository 
tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/axis2/axis2-kernel/20070301.070125-44/axis2-kernel-20070301.070125-44.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-kernel:pom:20070301.070125-44' from repository 
axis2-m2-repo (http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//org/apache/axis2/axis2-kernel/20070301.070125-44/axis2-kernel-20070301.070125-44.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-kernel:pom:20070301.070125-44' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/org/apache/axis2/axis2-kernel/20070301.070125-44/axis2-kernel-20070301.070125-44.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-kernel:pom:20070301.070125-44' from repository 
codehaus (http://repository.codehaus.org)
Downloading: 
http://repo1.maven.org/maven2/org/apache/axis2/axis2-kernel/20070301.070125-44/axis2-kernel-20070301.070125-44.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-kernel:pom:20070301.070125-44' from repository 
central (http://repo1.maven.org/maven2)
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//org/apache/axis2/axis2-adb/20070301.070125-21/axis2-adb-20070301.070125-21.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-adb:pom:20070301.070125-21' from repository 
tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/axis2/axis2-adb/20070301.070125-21/axis2-adb-20070301.070125-21.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-adb:pom:20070301.070125-21' from repository 
axis2-m2-repo (http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//org/apache/axis2/axis2-adb/20070301.070125-21/axis2-adb-20070301.070125-21.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-adb:pom:20070301.070125-21' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/org/apache/axis2/axis2-adb/20070301.070125-21/axis2-adb-20070301.070125-21.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-adb:pom:20070301.070125-21' from repository 
codehaus (http://repository.codehaus.org)
Downloading: 
http://repo1.maven.org/maven2/org/apache/axis2/axis2-adb/20070301.070125-21/axis2-adb-20070301.070125-21.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-adb:pom:20070301.070125-21' from repository 
central (http://repo1.maven.org/maven2)
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//org/apache/axis2/axis2-metadata/20070301.070125-30/axis2-metadata-20070301.070125-30.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-metadata:pom:20070301.070125-30' from 
repository tomcat-m2-repo 
(http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/axis2/axis2-metadata/20070301.070125-30/axis2-metadata-20070301.070125-30.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-metadata:pom:20070301.070125-30' from 
repository axis2-m2-repo (http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//org/apache/axis2/axis2-metadata/20070301.070125-30/axis2-metadata-20070301.070125-30.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-metadata:pom:20070301.070125-30' from 
repository apache-incubator 
(http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/org/apache/axis2/axis2-metadata/20070301.070125-30/axis2-metadata-20070301.070125-30.pom
[WARNING] Unable to get resource 
'org.apache.axis2:axis2-metadata:pom:20070301.070125-30' from 
repository codehaus (http://repository.codehaus.org)
Downloading: 
http://repo1.maven.org/maven2/org/apache/axis2/axis2-metadata/20070301.070125-30/axis2-metadata-20070301.070125-30.pom
[WARNING] Unab

[jira] Commented: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477066
 ] 

Lin Sun commented on GERONIMO-2915:
---

Dims, I just updated G2914's patch to build on top of the latest trunk that has 
the G2915.   If G2914 is committed after the new jars are pushed to the repo 
(let me know when the jars are there...), the call to processHTTPGetRequest 
will be enabled with G2914-new.patch.

Thanks, Lin

> Disable the call to processHTTPGetRequest to fix the build error
> 
>
> Key: GERONIMO-2915
> URL: https://issues.apache.org/jira/browse/GERONIMO-2915
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0
> Environment: winzp + sun 1.5
>Reporter: Lin Sun
> Assigned To: Joe Bohn
> Fix For: 2.0
>
>
> Axis2 team commented out this processHTTPGetRequest method this AM and it 
> caused a build error!
> The quick workaround is to disable the call.  I was able to run a full build 
> with the workaround below and a clean Axis2 repo.
> // deal with GET request
> /*boolean processed = HTTPTransportUtils.processHTTPGetRequest(
> msgContext,
> response.getOutputStream(),
> soapAction,
> path,
> configurationContext,
> HTTPTransportReceiver.getGetRequestParameters(path));*/
> 
> boolean processed = false;
> Thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2914) Axis2: a few changes to set the servicepath, contextroot correctly in EJB to allow getWSDL() test working correctly

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2914:
--

Attachment: G2914-new.patch

created against latest trunk (with G2915).   

> Axis2: a few changes to set the servicepath, contextroot correctly in EJB to 
> allow getWSDL() test working correctly
> ---
>
> Key: GERONIMO-2914
> URL: https://issues.apache.org/jira/browse/GERONIMO-2914
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0
> Environment: winxp + sun 1.5 SDK
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: G2914-new.patch, G2914.patch
>
>
> This patch builds on top of GERONIMO-2894 since there are changes impacting 
> the same files (i.e. committing this patch will also commit the patch 
> submmitted in G2894).  I could not find a better way to create patches for 
> easier review as G2894 isn't committed yet.
> 1) The patch will change the initContextRoot() method to be an abstract 
> method and provide different implementation of it in POJO and EJB.
> 2) The patch will also setServicePath of the axis2 configurationcontext 
> differently for POJO and EJB.
> After applying the patch, please delete the 3 0KB files in 
> (Axis2WebServiceContext.java
> , EJBWebServiceGBean.java
> , Axis2WebServiceContainerFactoryGBean.java) in the 
> src\main\java\org\apache\geronimo\axis2 dir.   
> I have applied this patch and G2913 into an updated checkout dir and able to 
> run a full build with it.  With this patch, jaxws-ejb getWSDL() test works 
> for both Jetty and Tomcat.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [BUILD] TRUNK: Failed for Revision: 513438

[Lin Sun]

This error should go away with G2915... one revision after yours...:-(

Joe Bohn closed GERONIMO-2915.
--

Resolution: Fixed

checked in work-around with rev. 513439

Thanks, Lin


[EMAIL PROTECTED] wrote:

Building with Maven version: 2.0.5
Revision: 513438 built with tests skipped
See the full build-1400.log file at 
http://people.apache.org/~prasad/binaries/20070301/build-1400.log
 
Downloading: http://people.apache.org/repo/m2-incubating-repository//commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar

[WARNING] Unable to get resource 
'commons-httpclient:commons-httpclient:jar:3.0.1' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
[WARNING] Unable to get resource 
'commons-httpclient:commons-httpclient:jar:3.0.1' from repository codehaus 
(http://repository.codehaus.org)
Downloading: 
http://repo1.maven.org/maven2/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
273K downloaded
Downloading: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/axiom-api/SNAPSHOT/axiom-api-20070301.152743-9.jar
123K downloaded
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//xalan/xalan/2.6.0/xalan-2.6.0.jar
[WARNING] Unable to get resource 'xalan:xalan:jar:2.6.0' from repository 
tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//xalan/xalan/2.6.0/xalan-2.6.0.jar
[WARNING] Unable to get resource 'xalan:xalan:jar:2.6.0' from repository 
axis2-m2-repo (http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//xalan/xalan/2.6.0/xalan-2.6.0.jar
[WARNING] Unable to get resource 'xalan:xalan:jar:2.6.0' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: http://repository.codehaus.org/xalan/xalan/2.6.0/xalan-2.6.0.jar
[WARNING] Unable to get resource 'xalan:xalan:jar:2.6.0' from repository 
codehaus (http://repository.codehaus.org)
Downloading: http://repo1.maven.org/maven2/xalan/xalan/2.6.0/xalan-2.6.0.jar
3075K downloaded
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//xerces/xmlParserAPIs/2.6.0/xmlParserAPIs-2.6.0.jar
[WARNING] Unable to get resource 'xerces:xmlParserAPIs:jar:2.6.0' from 
repository tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//xerces/xmlParserAPIs/2.6.0/xmlParserAPIs-2.6.0.jar
[WARNING] Unable to get resource 'xerces:xmlParserAPIs:jar:2.6.0' from 
repository axis2-m2-repo (http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//xerces/xmlParserAPIs/2.6.0/xmlParserAPIs-2.6.0.jar
[WARNING] Unable to get resource 'xerces:xmlParserAPIs:jar:2.6.0' from 
repository apache-incubator 
(http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/xerces/xmlParserAPIs/2.6.0/xmlParserAPIs-2.6.0.jar
[WARNING] Unable to get resource 'xerces:xmlParserAPIs:jar:2.6.0' from 
repository codehaus (http://repository.codehaus.org)
Downloading: 
http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.0/xmlParserAPIs-2.6.0.jar
121K downloaded
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.jar
[WARNING] Unable to get resource 'jaxen:jaxen:jar:1.1-beta-10' from repository 
tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.jar
[WARNING] Unable to get resource 'jaxen:jaxen:jar:1.1-beta-10' from repository 
axis2-m2-repo (http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.jar
[WARNING] Unable to get resource 'jaxen:jaxen:jar:1.1-beta-10' from repository 
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.jar
[WARNING] Unable to get resource 'jaxen:jaxen:jar:1.1-beta-10' from repository 
codehaus (http://repository.codehaus.org)
Downloading: 
http://repo1.maven.org/maven2/jaxen/jaxen/1.1-beta-10/jaxen-1.1-beta-10.jar
233K downloaded
Downloading: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/schema/XmlSchema/SNAPSHOT/XmlSchema-20070301.144711-16.jar
123K downloaded
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
[WARNING] Unable to get resource 'org.apache.ant:ant-launcher:jar:1.7.0' from 
repository tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/a

[jira] Updated: (GERONIMO-2914) Axis2: a few changes to set the servicepath, contextroot correctly in EJB to allow getWSDL() test working correctly

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2914:
--

Attachment: G2914.patch

Dims, This patch needs to be committed after the method
processHTTPGetRequest is uncommented out in Axis2.

I'll be more than happy to run a full build again with a clean axis2 repo when 
the axis2 change is on the repo just to make sure the build still works.  Just 
let me know when the axis2 repo is ready.

Lin

> Axis2: a few changes to set the servicepath, contextroot correctly in EJB to 
> allow getWSDL() test working correctly
> ---
>
> Key: GERONIMO-2914
> URL: https://issues.apache.org/jira/browse/GERONIMO-2914
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0
> Environment: winxp + sun 1.5 SDK
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: G2914.patch
>
>
> This patch builds on top of GERONIMO-2894 since there are changes impacting 
> the same files (i.e. committing this patch will also commit the patch 
> submmitted in G2894).  I could not find a better way to create patches for 
> easier review as G2894 isn't committed yet.
> 1) The patch will change the initContextRoot() method to be an abstract 
> method and provide different implementation of it in POJO and EJB.
> 2) The patch will also setServicePath of the axis2 configurationcontext 
> differently for POJO and EJB.
> After applying the patch, please delete the 3 0KB files in 
> (Axis2WebServiceContext.java
> , EJBWebServiceGBean.java
> , Axis2WebServiceContainerFactoryGBean.java) in the 
> src\main\java\org\apache\geronimo\axis2 dir.   
> I have applied this patch and G2913 into an updated checkout dir and able to 
> run a full build with it.  With this patch, jaxws-ejb getWSDL() test works 
> for both Jetty and Tomcat.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2915:
--

Summary: Disable the call to processHTTPGetRequest to fix the build error  
(was: Disable to call to processHTTPGetRequest to fix the build error)

> Disable the call to processHTTPGetRequest to fix the build error
> 
>
> Key: GERONIMO-2915
> URL: https://issues.apache.org/jira/browse/GERONIMO-2915
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0
> Environment: winzp + sun 1.5
>Reporter: Lin Sun
> Fix For: 2.0
>
>
> Axis2 team commented out this processHTTPGetRequest method this AM and it 
> caused a build error!
> The quick workaround is to disable the call.  I was able to run a full build 
> with the workaround below and a clean Axis2 repo.
> // deal with GET request
> /*boolean processed = HTTPTransportUtils.processHTTPGetRequest(
> msgContext,
> response.getOutputStream(),
> soapAction,
> path,
> configurationContext,
> HTTPTransportReceiver.getGetRequestParameters(path));*/
> 
> boolean processed = false;
> Thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2915) Disable to call to processHTTPGetRequest to fix the build error

[Lin Sun (JIRA)]

Disable to call to processHTTPGetRequest to fix the build error
---

 Key: GERONIMO-2915
 URL: https://issues.apache.org/jira/browse/GERONIMO-2915
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 2.0
 Environment: winzp + sun 1.5
Reporter: Lin Sun
 Fix For: 2.0


Axis2 team commented out this processHTTPGetRequest method this AM and it 
caused a build error!

The quick workaround is to disable the call.  I was able to run a full build 
with the workaround below and a clean Axis2 repo.

// deal with GET request
/*boolean processed = HTTPTransportUtils.processHTTPGetRequest(
msgContext,
response.getOutputStream(),
soapAction,
path,
configurationContext,
HTTPTransportReceiver.getGetRequestParameters(path));*/

boolean processed = false;

Thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: trunk build failure

[Lin Sun]

I just refreshed my Axis2 trunk and looks like they commented out this 
entire method processHTTPGetRequest in Axis2 trunk just this morning!


Do you want to comment out this also in trunk before we work out a fix?
In 
geronimo/modules/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:


change
// deal with GET request
boolean processed = HTTPTransportUtils.processHTTPGetRequest(
msgContext,
response.getOutputStream(),
soapAction,
path,
configurationContext,
HTTPTransportReceiver.getGetRequestParameters(path));

to

boolean processed = false;

Lin

Joe Bohn wrote:
I'm now seeing a different build failure on trunk when building from a 
clean local repo.   This is when building the module for geronimo-axis2.



[ERROR] BUILD FAILURE
[INFO] 


[INFO] Compilation failure
/Users/bohn/geronimo/modules/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[358,50] 
cannot find symbol
symbol  : method 
processHTTPGetRequest(org.apache.axis2.context.MessageContext,java.io.OutputStream,java.lang.String,java.lang.String,org.apache.axis2.context.ConfigurationContext,java.util.Map) 


location: class org.apache.axis2.transport.http.HTTPTransportUtils

[jira] Created: (GERONIMO-2914) Axis2: a few changes to set the servicepath, contextroot correctly in EJB to allow getWSDL() test working correctly

[Lin Sun (JIRA)]

Axis2: a few changes to set the servicepath, contextroot correctly in EJB to 
allow getWSDL() test working correctly
---

 Key: GERONIMO-2914
 URL: https://issues.apache.org/jira/browse/GERONIMO-2914
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 2.0
 Environment: winxp + sun 1.5 SDK
Reporter: Lin Sun
 Fix For: 2.0


This patch builds on top of GERONIMO-2894 since there are changes impacting the 
same files (i.e. committing this patch will also commit the patch submmitted in 
G2894).  I could not find a better way to create patches for easier review as 
G2894 isn't committed yet.

1) The patch will change the initContextRoot() method to be an abstract method 
and provide different implementation of it in POJO and EJB.
2) The patch will also setServicePath of the axis2 configurationcontext 
differently for POJO and EJB.

After applying the patch, please delete the 3 0KB files in 
(Axis2WebServiceContext.java
, EJBWebServiceGBean.java
, Axis2WebServiceContainerFactoryGBean.java) in the 
src\main\java\org\apache\geronimo\axis2 dir.   

I have applied this patch and G2913 into an updated checkout dir and able to 
run a full build with it.  With this patch, jaxws-ejb getWSDL() test works for 
both Jetty and Tomcat.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2913) minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for Axis2

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2913:
--

Attachment: G2913.patch

> minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for 
> Axis2
> ---
>
> Key: GERONIMO-2913
> URL: https://issues.apache.org/jira/browse/GERONIMO-2913
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0
> Environment: winxp + sun 1.5 SDK
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: G2913.patch
>
>
> This patch contains the following change:
> 1) In Axis2 integration code, we use request.getURI().getQuery(), however 
> null is returned when running jaxws-ejb test as the queryString wasn't set.   
> The patch will pass the queryString as the parameter when constructing URI.
> 2) In our Axis2 integration code, we call request.getContextPath() and it 
> returns null from JettyEJBWebServiceContext and 
> /JAXWS-EJB-2.0-snapshot/JAXWSBEAN from TomcatEJBWebServiceContext when 
> running the jaxws-ejb test case.  To me, the tomcat behavior is right.  (See 
> dev list on some discussion of this prob.)  There seems to be a bug in Jetty 
> in request.getContextPath() so I propose to use request.getRequestURI() 
> instead to temply work around the prob.
> Patch has been tested and able to do a full build with it.
> Thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2913) minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for Axis2

[Lin Sun (JIRA)]

minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for 
Axis2
---

 Key: GERONIMO-2913
 URL: https://issues.apache.org/jira/browse/GERONIMO-2913
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 2.0
 Environment: winxp + sun 1.5 SDK
Reporter: Lin Sun
 Fix For: 2.0


This patch contains the following change:

1) In Axis2 integration code, we use request.getURI().getQuery(), however null 
is returned when running jaxws-ejb test as the queryString wasn't set.   The 
patch will pass the queryString as the parameter when constructing URI.

2) In our Axis2 integration code, we call request.getContextPath() and it 
returns null from JettyEJBWebServiceContext and 
/JAXWS-EJB-2.0-snapshot/JAXWSBEAN from TomcatEJBWebServiceContext when running 
the jaxws-ejb test case.  To me, the tomcat behavior is right.  (See dev list 
on some discussion of this prob.)  There seems to be a bug in Jetty in 
request.getContextPath() so I propose to use request.getRequestURI() instead to 
temply work around the prob.

Patch has been tested and able to do a full build with it.

Thanks, Lin





-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: request.getContextPath() in RequestAdapter class in JettyEJBWebServiceContext.java

[Lin Sun]

Thanks for the feedback, David and Dims!

I'll try using request.getRequestURI() instead which seems to return the 
correct value...


Lin

Davanum Srinivas wrote:

David,

:) 'twas a "cross your fingers" fix

-- dims

On 3/1/07, David Blevins <[EMAIL PROTECTED]> wrote:


On Feb 28, 2007, at 12:42 PM, Lin Sun wrote:

> Hi,
>
> I have noticed some behavior difference between
> JettyEJBWebServiceContext and TomcatEJBWebServiceContext.  Both of
> them have an inner class RequestAdapter that implements
> WebServiceContainer.Request and provides this method getContextPath().
>
> In our Axis2 integration code, we call request.getContextPath() and
> it returns null from JettyEJBWebServiceContext and /JAXWS-EJB-2.0-
> snapshot/JAXWSBEAN from TomcatEJBWebServiceContext when running the
> jaxws-ejb test case.  To me, the tomcat behavior is right. If
> someone could shed some light on making the jetty behavior to be
> correct, I'd appreciate that.

Huh, I don't recall that method being in the
WebServiceContainer.Request interface for 1.4 webservices.  I
remember wanting to keep it to a minimum and only adding what could
be supported by by both Jetty, Tomcat (which is just
HttpServletRequest), and at the time OpenEJB's light http
implementation.  Unfortunately, I don't recall too many of those
details.

Seems like this was added recently by Dims, which is fine.  Dims did
you test this out in Jetty?  Or was this more a "cross your fingers"
kind of add :) (which is also fine).

In any case, I seem to recall getURI being used in leu of adding a
getContextPath to do things like set the location of webservice
bindings, etc., but I'm not certain if that'll do the trick for
whatever you may need getContextPath for.

-David

[jira] Commented: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476948
 ] 

Lin Sun commented on GERONIMO-2894:
---

Thanks again Lasantha!!!   I'd be grateful if someone can commit this.   I am 
about to submit another patch that touches some of the same files and I don't 
quite know how to generate a patch out of a patched dir (instead of a 
revision). :-(

Lin

> Restructure geronimo-axis2 code to split between EJB and POJO containers
> 
>
> Key: GERONIMO-2894
> URL: https://issues.apache.org/jira/browse/GERONIMO-2894
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2894-latest.patch, G2894-new.zip, G2894.patch
>
>
> This is needed as certain methods are POJO container specific, per Jarek's 
> comment in G2876.   
> Also attempted to fix the ?wsdl call in EJB mode by stripping the extra 
> forward slash.   ?wsdl still not working yet.  current exception is a 
> Nullpointerexception returned from uri.getQuery().   This is with jetty.
> Need to track this one down next.
> Checked the POJO mode and jetty was able to return wsdl as the result of 
> uri.getQuery().
> Tested the above change with all the tests (handlertest, 
> axis2webservicecontainertest, jax-ws-war and jax-ws-ejb) and also able to do 
> a full build with the patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Geronimo 2.0 web services support table

[Lin Sun]

In case you haven't taken a look at the page below, Jarek has updated 
the page with the CXF portion.  In the next few days, I'll be working on 
updating the table for Axis2 - POJO portion to be accurate.  But others 
are invited to update the page as well.


Lin

Davanum Srinivas wrote:

Excellent! Jarek, Please cross-check when you have a chance.

-- dims

On 2/21/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:

Nice work Lin ! :)

Cheers!
Hernan

Lin Sun wrote:
> Hi there,
>
> I have created a table for Geronimo web services support.   The page is
> a child page of the Geronimo Java EE 5.0 report card page, but here 
is a

> direct link anyway -
> http://cwiki.apache.org/GMOxPMGT/geronimo-20-web-services-support.html.
>  Tried to break them down to JAX-WS 2.0, JAX-RPC 1.1, EJB and Client 
and

> some of them may just mean test items or stuff we won't implement. I
> invite you (Jarek, Dims, Lasantha, and others) to edit the page and 
fill

> in the missing contents.
>
> Thanks, Lin
>

request.getContextPath() in RequestAdapter class in JettyEJBWebServiceContext.java

[Lin Sun]

Hi,

I have noticed some behavior difference between 
JettyEJBWebServiceContext and TomcatEJBWebServiceContext.  Both of them 
have an inner class RequestAdapter that implements 
WebServiceContainer.Request and provides this method getContextPath().


In our Axis2 integration code, we call request.getContextPath() and it 
returns null from JettyEJBWebServiceContext and 
/JAXWS-EJB-2.0-snapshot/JAXWSBEAN from TomcatEJBWebServiceContext when 
running the jaxws-ejb test case.  To me, the tomcat behavior is right. 
If someone could shed some light on making the jetty behavior to be 
correct, I'd appreciate that.


Thanks, Lin

[jira] Updated: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2894:
--

Attachment: G2894-latest.patch

Hi Lasantha,

Thanks so much for reviewing the patch and notifying me of the build error.   
This is the first time I submit a patch to delete some files.   The patch would 
delete everything in the files but it didn't get rid of the files.  So you got 
three 0KB files in your src\main\java\org\apache\geronimo\axis2 dir which 
causes the compile error.  I don't know if committing them would delete them in 
the repo as I don't have committer's access to practice that.

Instead of using Tortoise SVN, I used svn diff this time to generate the above 
patch (G2894-latest.patch).  What is nice about svn diff is that it can handle 
adding new files fine.   Please use this latest patch instead.

Then I tried to apply the patch to a fresh checkout geronimo dir.  After 
applying the patch, I still got the three 0KB java files 
(Axis2WebServiceContext.java
, EJBWebServiceGBean.java
, Axis2WebServiceContainerFactoryGBean.java) in the 
src\main\java\org\apache\geronimo\axis2 dir.  Then I deleted these 3 files 
manually  and I was able to run a full build after that.

> Restructure geronimo-axis2 code to split between EJB and POJO containers
> 
>
> Key: GERONIMO-2894
> URL: https://issues.apache.org/jira/browse/GERONIMO-2894
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2894-latest.patch, G2894-new.zip, G2894.patch
>
>
> This is needed as certain methods are POJO container specific, per Jarek's 
> comment in G2876.   
> Also attempted to fix the ?wsdl call in EJB mode by stripping the extra 
> forward slash.   ?wsdl still not working yet.  current exception is a 
> Nullpointerexception returned from uri.getQuery().   This is with jetty.
> Need to track this one down next.
> Checked the POJO mode and jetty was able to return wsdl as the result of 
> uri.getQuery().
> Tested the above change with all the tests (handlertest, 
> axis2webservicecontainertest, jax-ws-war and jax-ws-ejb) and also able to do 
> a full build with the patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2894:
--

Attachment: G2894-new.zip

To apply patch:

1) apply G2894-new.patch as normal
2) unzip G2894-axis2-ejb-pojo.zip to your 
geronimo_checkoutdir\modules\geronimo-axis2\src\main\java\org\apache\geronimo\axis2
 directory.

I tried to use my tortoise SVN to create a patch but the patch didn't get 
created well with brand new files.  That's why the new files are in the zip 
file now.  If someone can advise me on a better way to create a patch for 
modifications and new adds, I'd appreciate it.

Thx, Lin

> Restructure geronimo-axis2 code to split between EJB and POJO containers
> 
>
> Key: GERONIMO-2894
> URL: https://issues.apache.org/jira/browse/GERONIMO-2894
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2894-new.zip, G2894.patch
>
>
> This is needed as certain methods are POJO container specific, per Jarek's 
> comment in G2876.   
> Also attempted to fix the ?wsdl call in EJB mode by stripping the extra 
> forward slash.   ?wsdl still not working yet.  current exception is a 
> Nullpointerexception returned from uri.getQuery().   This is with jetty.
> Need to track this one down next.
> Checked the POJO mode and jetty was able to return wsdl as the result of 
> uri.getQuery().
> Tested the above change with all the tests (handlertest, 
> axis2webservicecontainertest, jax-ws-war and jax-ws-ejb) and also able to do 
> a full build with the patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476493
 ] 

Lin Sun commented on GERONIMO-2894:
---

Sorry but the patch was not generated correctly.  didn't delete the two classes 
(Axis2WebServiceContainerFactoryGBean.java + Axis2WebServiceContext.java) in 
axis2 folder when they are moved to axis2\pojo folder.   will attach a new one 
shortly.

> Restructure geronimo-axis2 code to split between EJB and POJO containers
> 
>
> Key: GERONIMO-2894
> URL: https://issues.apache.org/jira/browse/GERONIMO-2894
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2894.patch
>
>
> This is needed as certain methods are POJO container specific, per Jarek's 
> comment in G2876.   
> Also attempted to fix the ?wsdl call in EJB mode by stripping the extra 
> forward slash.   ?wsdl still not working yet.  current exception is a 
> Nullpointerexception returned from uri.getQuery().   This is with jetty.
> Need to track this one down next.
> Checked the POJO mode and jetty was able to return wsdl as the result of 
> uri.getQuery().
> Tested the above change with all the tests (handlertest, 
> axis2webservicecontainertest, jax-ws-war and jax-ws-ejb) and also able to do 
> a full build with the patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers

[Lin Sun (JIRA)]

Restructure geronimo-axis2 code to split between EJB and POJO containers


 Key: GERONIMO-2894
 URL: https://issues.apache.org/jira/browse/GERONIMO-2894
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: webservices
 Environment: winxp + sun 1.5
Reporter: Lin Sun


This is needed as certain methods are POJO container specific, per Jarek's 
comment in G2876.   

Also attempted to fix the ?wsdl call in EJB mode by stripping the extra forward 
slash.   ?wsdl still not working yet.  current exception is a 
Nullpointerexception returned from uri.getQuery().   This is with jetty.
Need to track this one down next.

Checked the POJO mode and jetty was able to return wsdl as the result of 
uri.getQuery().

Tested the above change with all the tests (handlertest, 
axis2webservicecontainertest, jax-ws-war and jax-ws-ejb) and also able to do a 
full build with the patch.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2894:
--

Attachment: G2894.patch

> Restructure geronimo-axis2 code to split between EJB and POJO containers
> 
>
> Key: GERONIMO-2894
> URL: https://issues.apache.org/jira/browse/GERONIMO-2894
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2894.patch
>
>
> This is needed as certain methods are POJO container specific, per Jarek's 
> comment in G2876.   
> Also attempted to fix the ?wsdl call in EJB mode by stripping the extra 
> forward slash.   ?wsdl still not working yet.  current exception is a 
> Nullpointerexception returned from uri.getQuery().   This is with jetty.
> Need to track this one down next.
> Checked the POJO mode and jetty was able to return wsdl as the result of 
> uri.getQuery().
> Tested the above change with all the tests (handlertest, 
> axis2webservicecontainertest, jax-ws-war and jax-ws-ejb) and also able to do 
> a full build with the patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2876) Initial web service EJB support for Axis2

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2876:
--

Attachment: G2876-2.patch

This updated patch contains the following:

- more formatting of axisservicegenerator file.   Add 2 methods in this file to 
generate wsdlDefinition when the wsdlFile is present in portinfo.  This is 
needed to get rid of axis2.PortInfo class as it creates inconvenience in the 
initial EJB support.

- Updated the Axis2Builder, Axix2WebServiceContainer, 
Axix2WebServiceContainerFactoryGbean, Axix2WebServiceContainerTest to reflect 
the change that axis2.PortInfo is gone.

- Added various config files for the intial support of EJB and the 
EJBWebServiceGBean.
I marked a todo there to forward the calls to openejb container.   

Able to build the patch with latest trunk today and tested with jaxws-ejb test 
case (1 out of 3 pass) and jaxws-war test case.  (2 out of 3 pass).

Lin

> Initial web service EJB support for Axis2
> -
>
> Key: GERONIMO-2876
> URL: https://issues.apache.org/jira/browse/GERONIMO-2876
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2876-2.patch, G2876.patch
>
>
> This work-in-progress patch tried to port the initial web service ejb support 
> from CXF to Axis2 (G2850) and here are a few details:
> 1) I had a hard time with classexception while working through the two 
> portinfo classes (org.apache.geronimo.jaxws.PortInfo and 
> org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of 
> org.apache.geronimo.axis2.PortInfo for simplicities.
> 2) I decided to keep the old Axis structure instead of the new CXF structure 
> for EJB support, as I envision that all the requests will be handled in one 
> Axis2WebServiceContainer. 
> Able to do a full build with the patch.Tested the patch with jax-ws-ejb 
> test.   For CXF, 2 out of 3 pass (same as before the patch).  For Axis2,  was 
> able to see the ejb module loaded and started.  However, get the jaxb error:
> 22:51:09,906 INFO  [JAXBUtils] Both ObjectFactory & package-info not found in 
> pa
> ckage hierachy
> 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying 
> to
>  invoke service method doService()
> org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]; 
> nested e
> xception is:
> javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
> at 
> org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa
> geReceiver.java:147)
> Will attempt to fix this tomorrow by supplying the generated ObjectFactory & 
> package-info classes for jax-ws-ejb test.
> Please let me know any comments you might have.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: M3 Build Error: Axis2 tests

[Lin Sun]

Worked for me with the latest trunk and some local modification about to 
be attached as a patch (tho I don't think the modification made a 
difference).


---
 T E S T S
---
Running org.apache.geronimo.axis2.Axis2HandlerResolverTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.578 sec
Running org.apache.geronimo.axis2.Axis2WebServiceContainerTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.563 sec

Results :
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0

Lin
Davanum Srinivas wrote:

Can you please post the surefire logs?

thanks,
dims

On 2/26/07, Sachin Patel <[EMAIL PROTECTED]> wrote:


---
 T E S T S
---
Running org.apache.geronimo.axis2.Axis2HandlerResolverTest
Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0.081 sec
<<< FAILURE!
Running
org.apache.geronimo.axis2.Axis2WebServiceContainerTest
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.242 sec
<<< FAILURE!

Results :
Tests run: 8, Failures: 0, Errors: 6, Skipped: 0

[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] There are test failures.
[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 6 minutes 42 seconds
[INFO] Finished at: Mon Feb 26 08:16:02 EST 2007
[INFO] Final Memory: 87M/508M
[INFO]


-sachin

[jira] Commented: (GERONIMO-2846) modified jax-ws calculator sample to work with CXF and Axis2

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475890
 ] 

Lin Sun commented on GERONIMO-2846:
---

Hi, I am not seeing these two issues with jetty.  I am able to get a slightly 
different sample (jax-ws test) working with both CXF and Axis2.   The 
calculator sample is based on the jax-ws test so I don't expect to see a big 
issue.   I am using Friday's trunk with a few modifications for EJB.

Lin

> modified jax-ws calculator sample to work with CXF and Axis2
> 
>
> Key: GERONIMO-2846
> URL: https://issues.apache.org/jira/browse/GERONIMO-2846
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: sample apps
>Affects Versions: 2.0-M2
> Environment: winxp + sun jsk 1.5
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: jax-ws-calculator.zip
>
>
> Hi Dims,
> Per your request, here's the modified version of the sample.  
> Current issues:
> 1) I haven't been able to run the webservice client outside of my eclipse 
> env.   Getting CNF error if I ran the client as "java -jar 
> jaxws-calculator-1.0.jar".   This could be fixed by providing an ant script 
> or build the java execution into maven's pom.xml.
> 2) Running the Axis2 CalculatorClient client caused 
> Caused by: java.lang.ClassNotFoundException: com.sun.xml.ws.spi.ProviderImpl
>   at java.net.URLClassLoader$1.run(Unknown Source)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(Unknown Source)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
>   at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:34)
>   ... 6 more
> I just added this client back in this morning so I probably have missed the 
> dependency for this one.   There are so many Axis2 dependencies so if you 
> know which one I need let me know.:)
> Running the Axis2 CalculatorClientAxiom client works fine.   
> Thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2877) Minor improvement to Axis2 Jaxws Integration

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475584
 ] 

Lin Sun commented on GERONIMO-2877:
---

Hi Lasantha, I am having trouble to apply this patch to my local machine.   
Kept getting tortoisemerge an unknown line type was found in line 115 error.
This is with a fresh checkout of geronimo\modules\geronimo-axis2 dir.   are you 
able to apply it on your machine with a fresh checkout?

Lin

> Minor improvement to Axis2 Jaxws Integration
> 
>
> Key: GERONIMO-2877
> URL: https://issues.apache.org/jira/browse/GERONIMO-2877
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Reporter: Lasantha Ranaweera
>Priority: Minor
> Attachments: GERONIMO-2877.patch
>
>
> This patch will improve the source code of the Axis2 JAXWS integration in 
> following areas.
> 1. Remove unnecessary Definition object used in the Axis2ServiceGenerator 
> class.
> 2. Source code formatting ( I am totally not sure this source code formatting 
> getting messing up. If somebody please point me out if this is due to a 
> problem of patches I have been submitting or not).
> Thanks,
> Lasantha

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2877) Minor improvement to Axis2 Jaxws Integration

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475499
 ] 

Lin Sun commented on GERONIMO-2877:
---

Patch looks good to me - can someone commit it please?  I'd like to submit 
another patch related to these two classes.

> Minor improvement to Axis2 Jaxws Integration
> 
>
> Key: GERONIMO-2877
> URL: https://issues.apache.org/jira/browse/GERONIMO-2877
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Reporter: Lasantha Ranaweera
>Priority: Minor
> Attachments: GERONIMO-2877.patch
>
>
> This patch will improve the source code of the Axis2 JAXWS integration in 
> following areas.
> 1. Remove unnecessary Definition object used in the Axis2ServiceGenerator 
> class.
> 2. Source code formatting ( I am totally not sure this source code formatting 
> getting messing up. If somebody please point me out if this is due to a 
> problem of patches I have been submitting or not).
> Thanks,
> Lasantha

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475495
 ] 

Lin Sun commented on GERONIMO-2876:
---

Jarek just showed me the portion of code in CXF that builds wsdlURL based on 
configurationBaseUrl and wsdlFile.  So let's not passing WSDLDefinition object 
around and build it inside of Axis2WebServiceContainer.  Hope this solution 
will make everyone happy.  :-)   I'll submit a patch for that.  thanks for all 
your comments and help!:-)

Lin

> Initial web service EJB support for Axis2
> -
>
> Key: GERONIMO-2876
> URL: https://issues.apache.org/jira/browse/GERONIMO-2876
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2876.patch
>
>
> This work-in-progress patch tried to port the initial web service ejb support 
> from CXF to Axis2 (G2850) and here are a few details:
> 1) I had a hard time with classexception while working through the two 
> portinfo classes (org.apache.geronimo.jaxws.PortInfo and 
> org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of 
> org.apache.geronimo.axis2.PortInfo for simplicities.
> 2) I decided to keep the old Axis structure instead of the new CXF structure 
> for EJB support, as I envision that all the requests will be handled in one 
> Axis2WebServiceContainer. 
> Able to do a full build with the patch.Tested the patch with jax-ws-ejb 
> test.   For CXF, 2 out of 3 pass (same as before the patch).  For Axis2,  was 
> able to see the ejb module loaded and started.  However, get the jaxb error:
> 22:51:09,906 INFO  [JAXBUtils] Both ObjectFactory & package-info not found in 
> pa
> ckage hierachy
> 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying 
> to
>  invoke service method doService()
> org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]; 
> nested e
> xception is:
> javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
> at 
> org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa
> geReceiver.java:147)
> Will attempt to fix this tomorrow by supplying the generated ObjectFactory & 
> package-info classes for jax-ws-ejb test.
> Please let me know any comments you might have.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475431
 ] 

Lin Sun commented on GERONIMO-2876:
---

Hi Lasantha,

The prob I am having is that in JAXWSServiceBuilder.configureEJB, it sets the 
jaxws.portInfo as the value of "portInfo" to the targetGBean.

I could overwrite it in Axis2Builder by providing an Axis2 version of the 
configureEJB method, but I had a hard time to get the axis2.portInfo from 
there.   A simple cast won't work.

I think the following might work:
1) check if wsdlFile exists, if exist, try cast it to axis2.portInfo.
2) if wsdlFile doesn't exist, construct a new axis2.portInfo by coping values 
from jaxws.portInfo.

Lin

> Initial web service EJB support for Axis2
> -
>
> Key: GERONIMO-2876
> URL: https://issues.apache.org/jira/browse/GERONIMO-2876
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2876.patch
>
>
> This work-in-progress patch tried to port the initial web service ejb support 
> from CXF to Axis2 (G2850) and here are a few details:
> 1) I had a hard time with classexception while working through the two 
> portinfo classes (org.apache.geronimo.jaxws.PortInfo and 
> org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of 
> org.apache.geronimo.axis2.PortInfo for simplicities.
> 2) I decided to keep the old Axis structure instead of the new CXF structure 
> for EJB support, as I envision that all the requests will be handled in one 
> Axis2WebServiceContainer. 
> Able to do a full build with the patch.Tested the patch with jax-ws-ejb 
> test.   For CXF, 2 out of 3 pass (same as before the patch).  For Axis2,  was 
> able to see the ejb module loaded and started.  However, get the jaxb error:
> 22:51:09,906 INFO  [JAXBUtils] Both ObjectFactory & package-info not found in 
> pa
> ckage hierachy
> 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying 
> to
>  invoke service method doService()
> org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]; 
> nested e
> xception is:
> javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
> at 
> org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa
> geReceiver.java:147)
> Will attempt to fix this tomorrow by supplying the generated ObjectFactory & 
> package-info classes for jax-ws-ejb test.
> Please let me know any comments you might have.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475373
 ] 

Lin Sun commented on GERONIMO-2876:
---

Thanks Jarek and Lasantha for reviewing the patch!  I intended to put out there 
to get some comments.:)

Jarek, yes I missed that few fines to invoke the ejbcontainer in 
EJBWebServiceGBean.java and will add that in.  

Lasantha, what I proposed is to have the javax.wsdl.Definition object stored in 
org.apache.geronimo.jaxws.PortInfo and this doesn't impact CXF at all  (see the 
patch I attached).   It is not good to have Axis2 or CXF specific info in JAXWS 
module in general but I propose we do that in this case for 
javax.wsdl.Definition before we have a better solution.

I'll submit a new patch later on.  Thanks again!:-)

Lin



> Initial web service EJB support for Axis2
> -
>
> Key: GERONIMO-2876
> URL: https://issues.apache.org/jira/browse/GERONIMO-2876
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2876.patch
>
>
> This work-in-progress patch tried to port the initial web service ejb support 
> from CXF to Axis2 (G2850) and here are a few details:
> 1) I had a hard time with classexception while working through the two 
> portinfo classes (org.apache.geronimo.jaxws.PortInfo and 
> org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of 
> org.apache.geronimo.axis2.PortInfo for simplicities.
> 2) I decided to keep the old Axis structure instead of the new CXF structure 
> for EJB support, as I envision that all the requests will be handled in one 
> Axis2WebServiceContainer. 
> Able to do a full build with the patch.Tested the patch with jax-ws-ejb 
> test.   For CXF, 2 out of 3 pass (same as before the patch).  For Axis2,  was 
> able to see the ejb module loaded and started.  However, get the jaxb error:
> 22:51:09,906 INFO  [JAXBUtils] Both ObjectFactory & package-info not found in 
> pa
> ckage hierachy
> 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying 
> to
>  invoke service method doService()
> org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]; 
> nested e
> xception is:
> javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
> at 
> org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa
> geReceiver.java:147)
> Will attempt to fix this tomorrow by supplying the generated ObjectFactory & 
> package-info classes for jax-ws-ejb test.
> Please let me know any comments you might have.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2876) Initial web service EJB support for Axis2

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2876:
--

Attachment: G2876.patch

> Initial web service EJB support for Axis2
> -
>
> Key: GERONIMO-2876
> URL: https://issues.apache.org/jira/browse/GERONIMO-2876
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Attachments: G2876.patch
>
>
> This work-in-progress patch tried to port the initial web service ejb support 
> from CXF to Axis2 (G2850) and here are a few details:
> 1) I had a hard time with classexception while working through the two 
> portinfo classes (org.apache.geronimo.jaxws.PortInfo and 
> org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of 
> org.apache.geronimo.axis2.PortInfo for simplicities.
> 2) I decided to keep the old Axis structure instead of the new CXF structure 
> for EJB support, as I envision that all the requests will be handled in one 
> Axis2WebServiceContainer. 
> Able to do a full build with the patch.Tested the patch with jax-ws-ejb 
> test.   For CXF, 2 out of 3 pass (same as before the patch).  For Axis2,  was 
> able to see the ejb module loaded and started.  However, get the jaxb error:
> 22:51:09,906 INFO  [JAXBUtils] Both ObjectFactory & package-info not found in 
> pa
> ckage hierachy
> 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying 
> to
>  invoke service method doService()
> org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]; 
> nested e
> xception is:
> javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://apache.org/g
> reeter_control/types", local:"greetMe"). Expected elements are (none)]
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
> at 
> org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa
> geReceiver.java:147)
> Will attempt to fix this tomorrow by supplying the generated ObjectFactory & 
> package-info classes for jax-ws-ejb test.
> Please let me know any comments you might have.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2876) Initial web service EJB support for Axis2

[Lin Sun (JIRA)]

Initial web service EJB support for Axis2
-

 Key: GERONIMO-2876
 URL: https://issues.apache.org/jira/browse/GERONIMO-2876
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
 Environment: winxp + sun 1.5
Reporter: Lin Sun


This work-in-progress patch tried to port the initial web service ejb support 
from CXF to Axis2 (G2850) and here are a few details:

1) I had a hard time with classexception while working through the two portinfo 
classes (org.apache.geronimo.jaxws.PortInfo and 
org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of 
org.apache.geronimo.axis2.PortInfo for simplicities.

2) I decided to keep the old Axis structure instead of the new CXF structure 
for EJB support, as I envision that all the requests will be handled in one 
Axis2WebServiceContainer. 

Able to do a full build with the patch.Tested the patch with jax-ws-ejb 
test.   For CXF, 2 out of 3 pass (same as before the patch).  For Axis2,  was 
able to see the ejb module loaded and started.  However, get the jaxb error:

22:51:09,906 INFO  [JAXBUtils] Both ObjectFactory & package-info not found in pa
ckage hierachy
22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to
 invoke service method doService()
org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
 - with linked exception:
[javax.xml.bind.UnmarshalException: unexpected element (uri:"http://apache.org/g
reeter_control/types", local:"greetMe"). Expected elements are (none)]; nested e
xception is:
javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
 - with linked exception:
[javax.xml.bind.UnmarshalException: unexpected element (uri:"http://apache.org/g
reeter_control/types", local:"greetMe"). Expected elements are (none)]
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa
geReceiver.java:147)

Will attempt to fix this tomorrow by supplying the generated ObjectFactory & 
package-info classes for jax-ws-ejb test.

Please let me know any comments you might have.




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: anyone able to start geronimo with today's build?

[Lin Sun]

Thanks Prasad!  The jetty zip file I built is about 4-5Mb bigger than 
yours.  I am cleaning my .m2 repo and rebuild it.


Lin

Prasad Kashyap wrote:

Lin,

I am able to start/run G from the Jetty driver I got from here
http://people.apache.org/~prasad/binaries/20070221/

Haven't tried tomcat.

Cheers
Prasad

On 2/21/07, Lin Sun <[EMAIL PROTECTED]> wrote:

Hi there,

I found that I could not start AG with a new build I did this AM (with
rev 509970).  Here's the error -

E:\linsun\geronimo-jetty6-jee5-2.0-SNAPSHOT\bin>java -jar server.jar
Booting Geronimo Kernel (in Java 1.5.0_10)...
16:13:19,187 WARN  [ConfigurationUtil] Could not load gbean
org.apache.geronimo.
configs/j2ee-system/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j 


2ee-system/2.0-SNAPSHOT/car,j2eeType=Repository,name=Repository
org.apache.geronimo.gbean.InvalidConfigurationException: Could not find
a valid
constructor for GBean:
org.apache.geronimo.system.repository.Maven2Repository
ParameterTypes: [class java.net.URI, interface
org.apache.geronimo.system.server
info.ServerInfo, boolean]
constructor types: [class java.io.File]
constructor types: [class java.net.URI, interface
org.apache.geronimo.system.ser
verinfo.ServerInfo]

 at
org.apache.geronimo.gbean.runtime.GBeanInstance.(GBeanInstance.
java:351)
 at
org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja
va:354)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:363)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf
iguration(ConfigurationUtil.java:155)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf
iguration(ConfigurationUtil.java:126)
 at
org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242)
 at org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
 at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366)
[  ]  0%   0s Startup failed
org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start
exceptio
n
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:444)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf
iguration(ConfigurationUtil.java:155)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf
iguration(ConfigurationUtil.java:126)
 at
org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242)
 at org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
 at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366)
Caused by: org.apache.geronimo.gbean.InvalidConfigurationException:
Could not fi
nd a valid constructor for GBean:
org.apache.geronimo.system.repository.Maven2Re
pository
ParameterTypes: [class java.net.URI, interface
org.apache.geronimo.system.server
info.ServerInfo, boolean]
constructor types: [class java.io.File]
constructor types: [class java.net.URI, interface
org.apache.geronimo.system.ser
verinfo.ServerInfo]

 at
org.apache.geronimo.gbean.runtime.GBeanInstance.(GBeanInstance.
java:351)
 at
org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja
va:354)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:363)
 ... 5 more
org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start
exceptio
n
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:444)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf
iguration(ConfigurationUtil.java:155)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf
iguration(ConfigurationUtil.java:126)
 at
org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242)
 at org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
 at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366)
Caused by: org.apache.geronimo.gbean.InvalidConfigurationException:
Could not fi
nd a valid constructor for GBean:
org.apache.geronimo.system.repository.Maven2Re
pository
ParameterTypes: [class java.net.URI, interface
org.apache.geronimo.system.server
info.ServerInfo, boolean]
constructor types: [class java.io.File]
constructor types: [class java.net.URI, interface
org.apache.geronimo.system.ser
verinfo.ServerInfo]

 at
org.apache.geronimo.gbean.runtime.GBeanInstance.(GBeanInstance.
java:351)
 at
org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja
va:354)
 at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:363)
 ... 5 more
Server shutdown begun
Server shutdown completed

Anyone else has seen this?  Would a basic startup/shutdown test be
something interesting to be added to our four times daily auto build 
test?


Lin

anyone able to start geronimo with today's build?

[Lin Sun]

Hi there,

I found that I could not start AG with a new build I did this AM (with 
rev 509970).  Here's the error -


E:\linsun\geronimo-jetty6-jee5-2.0-SNAPSHOT\bin>java -jar server.jar
Booting Geronimo Kernel (in Java 1.5.0_10)...
16:13:19,187 WARN  [ConfigurationUtil] Could not load gbean 
org.apache.geronimo.

configs/j2ee-system/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j
2ee-system/2.0-SNAPSHOT/car,j2eeType=Repository,name=Repository
org.apache.geronimo.gbean.InvalidConfigurationException: Could not find 
a valid
constructor for GBean: 
org.apache.geronimo.system.repository.Maven2Repository
ParameterTypes: [class java.net.URI, interface 
org.apache.geronimo.system.server

info.ServerInfo, boolean]
constructor types: [class java.io.File]
constructor types: [class java.net.URI, interface 
org.apache.geronimo.system.ser

verinfo.ServerInfo]

at 
org.apache.geronimo.gbean.runtime.GBeanInstance.(GBeanInstance.

java:351)
at 
org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja

va:354)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio

nGBeans(ConfigurationUtil.java:363)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf

iguration(ConfigurationUtil.java:155)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf

iguration(ConfigurationUtil.java:126)
at 
org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242)

at org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366)
[  ]  0%   0s Startup failed
org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start 
exceptio

n
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio

nGBeans(ConfigurationUtil.java:444)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf

iguration(ConfigurationUtil.java:155)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf

iguration(ConfigurationUtil.java:126)
at 
org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242)

at org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366)
Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: 
Could not fi
nd a valid constructor for GBean: 
org.apache.geronimo.system.repository.Maven2Re

pository
ParameterTypes: [class java.net.URI, interface 
org.apache.geronimo.system.server

info.ServerInfo, boolean]
constructor types: [class java.io.File]
constructor types: [class java.net.URI, interface 
org.apache.geronimo.system.ser

verinfo.ServerInfo]

at 
org.apache.geronimo.gbean.runtime.GBeanInstance.(GBeanInstance.

java:351)
at 
org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja

va:354)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio

nGBeans(ConfigurationUtil.java:363)
... 5 more
org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start 
exceptio

n
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio

nGBeans(ConfigurationUtil.java:444)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf

iguration(ConfigurationUtil.java:155)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf

iguration(ConfigurationUtil.java:126)
at 
org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242)

at org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366)
Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: 
Could not fi
nd a valid constructor for GBean: 
org.apache.geronimo.system.repository.Maven2Re

pository
ParameterTypes: [class java.net.URI, interface 
org.apache.geronimo.system.server

info.ServerInfo, boolean]
constructor types: [class java.io.File]
constructor types: [class java.net.URI, interface 
org.apache.geronimo.system.ser

verinfo.ServerInfo]

at 
org.apache.geronimo.gbean.runtime.GBeanInstance.(GBeanInstance.

java:351)
at 
org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja

va:354)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio

nGBeans(ConfigurationUtil.java:363)
... 5 more
Server shutdown begun
Server shutdown completed

Anyone else has seen this?  Would a basic startup/shutdown test be 
something interesting to be added to our four times daily auto build test?


Lin

Re: New way to specify jaxws impl with a system property

[Lin Sun]

This is great - I like it!

Lin

David Jencks wrote:
After discussions with jgawor, dims, and jdillon we realized we could 
switch jaxws implementations using a system property and the expression 
evaluation features in config.xml.


If you specify nothing, you will get cxf with jetty and axis2 with tomcat.

To specify which one you want explicitly, include

-Dorg.apache.geronimo.jaxwsimpl=cxf
or
-Dorg.apache.geronimo.jaxwsimpl=axis2

in your command line

thanks
david jencks

Geronimo 2.0 web services support table

[Lin Sun]

Hi there,

I have created a table for Geronimo web services support.   The page is 
a child page of the Geronimo Java EE 5.0 report card page, but here is a 
direct link anyway - 
http://cwiki.apache.org/GMOxPMGT/geronimo-20-web-services-support.html. 
 Tried to break them down to JAX-WS 2.0, JAX-RPC 1.1, EJB and Client 
and some of them may just mean test items or stuff we won't implement. 
I invite you (Jarek, Dims, Lasantha, and others) to edit the page and 
fill in the missing contents.


Thanks, Lin

[jira] Updated: (GERONIMO-2846) modified jax-ws calculator sample to work with CXF and Axis2

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2846:
--

Attachment: jax-ws-calculator.zip

> modified jax-ws calculator sample to work with CXF and Axis2
> 
>
> Key: GERONIMO-2846
> URL: https://issues.apache.org/jira/browse/GERONIMO-2846
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: sample apps
>Affects Versions: 2.0-M2
> Environment: winxp + sun jsk 1.5
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: jax-ws-calculator.zip
>
>
> Hi Dims,
> Per your request, here's the modified version of the sample.  
> Current issues:
> 1) I haven't been able to run the webservice client outside of my eclipse 
> env.   Getting CNF error if I ran the client as "java -jar 
> jaxws-calculator-1.0.jar".   This could be fixed by providing an ant script 
> or build the java execution into maven's pom.xml.
> 2) Running the Axis2 CalculatorClient client caused 
> Caused by: java.lang.ClassNotFoundException: com.sun.xml.ws.spi.ProviderImpl
>   at java.net.URLClassLoader$1.run(Unknown Source)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(Unknown Source)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
>   at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:34)
>   ... 6 more
> I just added this client back in this morning so I probably have missed the 
> dependency for this one.   There are so many Axis2 dependencies so if you 
> know which one I need let me know.:)
> Running the Axis2 CalculatorClientAxiom client works fine.   
> Thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Simple Web Service with JAX-WS sample on AG wiki

[Lin Sun]

Sure - submitted G2846 for this.  Thanks for reviewing it.

Lin

Davanum Srinivas wrote:

Lin,

Before you update the online doc. Could you please post the modified
samples in JIRA? Let me take a quick look?

thanks,
dims

On 2/15/07, Lin Sun <[EMAIL PROTECTED]> wrote:

Hi there,

After making some changes to the sample[1], I am able to get it
(slightly different versions of it for CXF and Axis2) working with this
week's trunk.

Here are some observations:
1) I have to use the generated classes (package-info, objectFactory,
RequestWrapper and ResponseWrapper classes) for CXF to get the war file
deployed.  This was not required before...
2) I developed an Axiom based web services client for Axis2 so that it
doesn't require CXF specific jars at the runtime of the client.

I'll begin updating the docs and send out another update.   Initial
thought is to use the same wiki page for both CXF and Axis2 (instead of
creating a new page for Axis2) and highlight the differences.

Lin

[1]http://cwiki.apache.org/GMOxDOC20/simple-web-service-with-jax-ws.html

[jira] Created: (GERONIMO-2846) modified jax-ws calculator sample to work with CXF and Axis2

[Lin Sun (JIRA)]

modified jax-ws calculator sample to work with CXF and Axis2


 Key: GERONIMO-2846
 URL: https://issues.apache.org/jira/browse/GERONIMO-2846
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: sample apps
Affects Versions: 2.0-M2
 Environment: winxp + sun jsk 1.5
Reporter: Lin Sun
 Fix For: 2.0


Hi Dims,

Per your request, here's the modified version of the sample.  

Current issues:

1) I haven't been able to run the webservice client outside of my eclipse env.  
 Getting CNF error if I ran the client as "java -jar jaxws-calculator-1.0.jar". 
  This could be fixed by providing an ant script or build the java execution 
into maven's pom.xml.

2) Running the Axis2 CalculatorClient client caused 

Caused by: java.lang.ClassNotFoundException: com.sun.xml.ws.spi.ProviderImpl
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:34)
... 6 more

I just added this client back in this morning so I probably have missed the 
dependency for this one.   There are so many Axis2 dependencies so if you know 
which one I need let me know.:)

Running the Axis2 CalculatorClientAxiom client works fine.   

Thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Simple Web Service with JAX-WS sample on AG wiki

[Lin Sun]

To make Jarek's job easier, I'll start a wiki write-up by creating a 
table with lists of functions we need to do for CXF and Axis2.  I'll get 
this information from JSR109 which is the only spec we (geronimo) needs 
to implement IIUC.   Then we can check items that we think is developed 
and/or tested.   I'll have placeholders for stuff I don't know so that 
you guys can fill in the holes.:-)   I'll begin working on this next 
week as soon as I finish up with the sample.


Lin

Davanum Srinivas wrote:

Lasantha,

Jarek promised to write up a list of items implemented then we can
make a check list and fix whatever is missing. We need to test all the
code too. Since we don't know what works and what doesn't as we don't
have full test coverage.

thanks,
dims

On 2/15/07, Lasantha Ranaweera <[EMAIL PROTECTED]> wrote:

Hi Lin,

Great work... We are getting closer & closer to finish Axis2 with POJO
support ... Dims do you any idea to add what are we missing right now ?

Are you using latest version of trunk to build Geronimo? IMO in Axis2
there is a bug and I am submitting a patch for that too ;).

Please see my in line comments too.

Thanks,
Lasantha
Lin Sun wrote:
> Hi there,
>
> After making some changes to the sample[1], I am able to get it
> (slightly different versions of it for CXF and Axis2) working with
> this week's trunk.
>
> Here are some observations:
> 1) I have to use the generated classes (package-info, objectFactory,
> RequestWrapper and ResponseWrapper classes) for CXF to get the war
> file deployed.  This was not required before...
It wasn't necessary to generate these files in CXF for WSDL provided
situation before. I though it is only for Axis2 to necessary to do this
step. Jarek do you have any idea ? :-)
> 2) I developed an Axiom based web services client for Axis2 so that it
> doesn't require CXF specific jars at the runtime of the client.
>
> I'll begin updating the docs and send out another update.   Initial
> thought is to use the same wiki page for both CXF and Axis2 (instead
> of creating a new page for Axis2) and highlight the differences.
>
> Lin
>
> 
[1]http://cwiki.apache.org/GMOxDOC20/simple-web-service-with-jax-ws.html

>

Re: Simple Web Service with JAX-WS sample on AG wiki

[Lin Sun]

Hi Lasantha,

I am using a geronimo build I built on Monday which is probably why I 
didn't see the bug you hit.:-)


Re your inline comment below, seems there are sufficient changes in CXF 
recently to cause the previous example not working.  I tried to run the 
war file without these generated classes but got some stack trace asking 
for something like getResquestWrapper from CXF...  This can be easily 
recreated with the latest sample I have by just uncommenting out the 
java code generation portion in pom.xml if anyone is interested in more 
details.


Thanks,

Lin

Lasantha Ranaweera wrote:


Here are some observations:
1) I have to use the generated classes (package-info, objectFactory, 
RequestWrapper and ResponseWrapper classes) for CXF to get the war 
file deployed.  This was not required before...
It wasn't necessary to generate these files in CXF for WSDL provided 
situation before. I though it is only for Axis2 to necessary to do this 
step. Jarek do you have any idea ? :-)

Re: Simple Web Service with JAX-WS sample on AG wiki

[Lin Sun]

Hi Jarek,  good point - I dont have a good reason for that. :)  It is 
just the examples I found are using Axiom.  I'll let you know once I 
find out.


Lin

Jarek Gawor wrote:

Great. A few comments inline:

On 2/15/07, Lin Sun <[EMAIL PROTECTED]> wrote:

Hi there,

After making some changes to the sample[1], I am able to get it
(slightly different versions of it for CXF and Axis2) working with this
week's trunk.

Here are some observations:
1) I have to use the generated classes (package-info, objectFactory,
RequestWrapper and ResponseWrapper classes) for CXF to get the war file
deployed.  This was not required before...
2) I developed an Axiom based web services client for Axis2 so that it
doesn't require CXF specific jars at the runtime of the client.


Hmm... is that different from the javax.xml.ws.Service API? Why
couldn't you use the Axis2 implementation of the Service API?


I'll begin updating the docs and send out another update.   Initial
thought is to use the same wiki page for both CXF and Axis2 (instead of
creating a new page for Axis2) and highlight the differences.


Right, there should be only one page. And eventually (and hopefully)
those differences should disappear, so we should stress that these
differences are temporary.

Jarek

Simple Web Service with JAX-WS sample on AG wiki

[Lin Sun]

Hi there,

After making some changes to the sample[1], I am able to get it 
(slightly different versions of it for CXF and Axis2) working with this 
week's trunk.


Here are some observations:
1) I have to use the generated classes (package-info, objectFactory, 
RequestWrapper and ResponseWrapper classes) for CXF to get the war file 
deployed.  This was not required before...
2) I developed an Axiom based web services client for Axis2 so that it 
doesn't require CXF specific jars at the runtime of the client.


I'll begin updating the docs and send out another update.   Initial 
thought is to use the same wiki page for both CXF and Axis2 (instead of 
creating a new page for Axis2) and highlight the differences.


Lin

[1]http://cwiki.apache.org/GMOxDOC20/simple-web-service-with-jax-ws.html

wsdl:service name in .wsdl file

[Lin Sun]

Hi there,

I found out that the simple jax-ws example we put on the wiki 
(http://cwiki.apache.org/GMOxDOC20/simple-web-service-with-jax-ws.html) 
doesn't work with the latest trunk - CXF.   I assumed it worked before 
when the article was put out there.


Here's the error I got:

22:54:17,781 ERROR [GBeanInstanceState] Error while starting; GBean is 
now in the FAILED state: 
abstractName="org.apache.geronimo.samples.jws/Calculator/1.0/car

?J2EEApplication=null,WebModule=org.apache.geronimo.samples.jws/Calculator/1.0/c
ar,j2eeType=Servlet,name=CalculatorService"
org.apache.cxf.service.factory.ServiceConstructionException: Could not 
find definition for service 
{http://jws.samples.geronimo.apache.org}CalculatorService.
at 
org.apache.cxf.wsdl11.WSDLServiceFactory.create(WSDLServiceFactory.ja

va:69)
at 
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializ

eServiceModel(ReflectionServiceFactoryBean.java:176)
at 
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Re

flectionServiceFactoryBean.java:116)
at org.apache.geronimo.cxf.CXFEndpoint.(CXFEndpoint.java:113)
at 
org.apache.geronimo.cxf.CXFWebServiceContainer.publishEndpoint(CXFWeb

ServiceContainer.java:141)
at 
org.apache.geronimo.cxf.CXFWebServiceContainer.(CXFWebServiceCo

ntainer.java:94)
at 
org.apache.geronimo.cxf.CXFWebServiceContainerFactoryGBean.getWebServ

iceContainer(CXFWebServiceContainerFactoryGBean.java:84)

After modifying the wsdl:name name from



to



I can deploy the war file fine.  Would this be a bug in CXF (or 
integration code) that you have to specify 'Service' at the end of the name?


P.S. I ran into another error first where the .wsdl file cannot be 
located in the repo thus I moved the location of .wsdl file to 
WEB-INFO\wsdl and it solved that error.


Lin

Re: [BUILD] Failed for Revision: 506686

[Lin Sun]

This file is there in the Axis2 maven 2 repo - 
http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-java2wsdl/SNAPSHOT/


Maybe just a network glitch?  (happened to Donald last week I think...)

lin

Prasad Kashyap wrote:

Dims,

Has this been fixed now ?

Cheers
Prasad

On 12 Feb 2007 22:14:44 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Revision: 506686 built with tests skipped
See the full build-1700.log file at 
http://people.apache.org/~prasad/binaries/20070212/build-1700.log


Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//org/apache/httpcomponents/jakarta-httpcore/4.0-alpha3/jakarta-httpcore-4.0-alpha3.jar 

[WARNING] Unable to get resource from repository tomcat-m2-repo 
(http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/httpcomponents/jakarta-httpcore/4.0-alpha3/jakarta-httpcore-4.0-alpha3.jar 

[WARNING] Unable to get resource from repository axis2-m2-repo 
(http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//org/apache/httpcomponents/jakarta-httpcore/4.0-alpha3/jakarta-httpcore-4.0-alpha3.jar 

[WARNING] Unable to get resource from repository apache-incubator 
(http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/org/apache/httpcomponents/jakarta-httpcore/4.0-alpha3/jakarta-httpcore-4.0-alpha3.jar 

[WARNING] Unable to get resource from repository codehaus 
(http://repository.codehaus.org)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/httpcomponents/jakarta-httpcore/4.0-alpha3/jakarta-httpcore-4.0-alpha3.jar 

[WARNING] Unable to get resource from repository apache-ws-snapshots2 
(http://ws.zones.apache.org/repository2/)
Downloading: 
http://repo1.maven.org/maven2//org/apache/httpcomponents/jakarta-httpcore/4.0-alpha3/jakarta-httpcore-4.0-alpha3.jar 


125K downloaded
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.jar 

[WARNING] Unable to get resource from repository tomcat-m2-repo 
(http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.jar 

[WARNING] Unable to get resource from repository axis2-m2-repo 
(http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.jar 

[WARNING] Unable to get resource from repository apache-incubator 
(http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.jar 

[WARNING] Unable to get resource from repository codehaus 
(http://repository.codehaus.org)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.jar 

[WARNING] Unable to get resource from repository apache-ws-snapshots2 
(http://ws.zones.apache.org/repository2/)
Downloading: 
http://repo1.maven.org/maven2//org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.jar 


30K downloaded
Downloading: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/axiom-dom/SNAPSHOT/axiom-dom-SNAPSHOT.jar 

[WARNING] Unable to get resource from repository apache-snapshots 
(http://people.apache.org/repo/m2-snapshot-repository)
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/ws/commons/axiom/axiom-dom/SNAPSHOT/axiom-dom-SNAPSHOT.jar 


130K downloaded
[WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for 
org/apache/ws/commons/axiom/axiom-dom/SNAPSHOT/axiom-dom-SNAPSHOT.jar 
- IGNORING
Downloading: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-adb/SNAPSHOT/axis2-adb-20070212.215012-1.jar 


135K downloaded
Downloading: 
http://tomcat.apache.org/dev/dist/m2-repository//com/sun/xml/bind/jaxb-impl/2.0.2/jaxb-impl-2.0.2.jar 

[WARNING] Unable to get resource from repository tomcat-m2-repo 
(http://tomcat.apache.org/dev/dist/m2-repository/)
Downloading: 
http://ws.zones.apache.org/repository2//com/sun/xml/bind/jaxb-impl/2.0.2/jaxb-impl-2.0.2.jar 

[WARNING] Unable to get resource from repository axis2-m2-repo 
(http://ws.zones.apache.org/repository2/)
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//com/sun/xml/bind/jaxb-impl/2.0.2/jaxb-impl-2.0.2.jar 

[WARNING] Unable to get resource from repository apache-incubator 
(http://people.apache.org/repo/m2-incubating-repository/)
Downloading: 
http://repository.codehaus.org/com/sun/xml/bind/jaxb-impl/2.0.2/jaxb-impl-2.0.2.jar 

[WARNING] Unable to get resource from repository codehaus 
(http://repository.codehaus.org)
Downloading: 
http://ws.zones.apache.or

[jira] Updated: (GERONIMO-2824) port the handler tests from CXF to Axis2

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2824:
--

Attachment: geronimo-axis2-test.zip

Able to build the patch with the latest trunk fine.

> port the handler tests from CXF to Axis2
> 
>
> Key: GERONIMO-2824
> URL: https://issues.apache.org/jira/browse/GERONIMO-2824
> Project: Geronimo
>  Issue Type: Test
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: geronimo-axis2-test.zip
>
>
> Port the handler tests from CXF to Axis2.
> Patch is tested with Axis2 and all handler tests pass!
> To apply patch just unzip it to modules\geronimo-axis2\src directory.
> thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2824) port the handler tests from CXF to Axis2

[Lin Sun (JIRA)]

port the handler tests from CXF to Axis2


 Key: GERONIMO-2824
 URL: https://issues.apache.org/jira/browse/GERONIMO-2824
 Project: Geronimo
  Issue Type: Test
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 2.0
 Environment: winxp + sun 1.5
Reporter: Lin Sun
 Fix For: 2.0


Port the handler tests from CXF to Axis2.

Patch is tested with Axis2 and all handler tests pass!

To apply patch just unzip it to modules\geronimo-axis2\src directory.

thanks, Lin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: CXF and Axis2 (dogs and cats?)

[Lin Sun]

Dims/Jarek,

What if we add property substitution capability in the config.xml and 
plan files so that people can just specify axis2, Axis2Builder and 
axis2-deployer as the value of the properties when they want Axis2.  If 
they want CXF, they can specify cxf, CXFBuilder and cxf-deployer 
instead.   Ted Kirby has recently submitted a patch to enable this 
(https://issues.apache.org/jira/browse/GERONIMO-2735).


Thanks, Lin

Jarek Gawor wrote:

Dims,

I don't think that alone will work. I think we need to stop the entire
cxf-deployer/car or axis2-deployer/car modules to deregister several
gbeans. Basically what Lin Sun was saying which can either be done by
changing the config.xml file or through the console today. So I
believe the changes you made are unnecessary and won't quite work.

Jarek

On 2/11/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:

Found a spot in WebServicesBuilder.configurePojo where i can skip
stuff. will try to use that.

thanks,
dims

On 2/11/07, David Jencks <[EMAIL PROTECTED]> wrote:
>
> On Feb 11, 2007, at 6:28 AM, Davanum Srinivas wrote:
>
> > Dain,
> >
> > Just reviewed the code in OpenJPA. Am going to try to add some 
similar

> > switch Keying off of javax.xml.ws.spi.Provider (defined by the JSR)
> > and specific implementations are 
org.apache.cxf.jaxws.spi.ProviderImpl

> > and org.apache.axis2.jaxws.spi.Provider. It's getting to be very
> > annoying to keep changing the plan.xml/pom.xml/config.xml before
> > debugging. One question am not sure is if i make these changes in
> > corresponding deployers, will that be enough?
>
> I think so.  If not we'll deal with it when problems show up.
>
> thanks
> david jencks
>
> >
> > thanks,
> > dims
> >
> > On 1/11/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> >> It would be very nice if this could work like JPA where I set a
> >> single property in my application to switch implementations.
> >>
> >> -dain
> >>
> >> On Jan 11, 2007, at 1:16 PM, Matt Hogstrom wrote:
> >>
> >> > I am not overly knowledgeable about WebServices so I'll bear my
> >> > ignorance directly.  Given that we'll have two options that users
> >> > will be able to choose from is there some way to abstract CXF and
> >> > Axis2 to a common point so users could install their preference
> >> > through a plugin?  It would certainly simplify the user experience
> >> > as well as reduce the number of assemblies.  Any CXF / Axis guys
> >> > have thoughts on this?
> >> >
> >> >
> >> > Matt Hogstrom
> >> > [EMAIL PROTECTED]
> >> >
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
> > Developers
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services 
Developers

Re: java.lang.OutOfMemoryError: Java heap space

[Lin Sun]

I've seen the same thing with the jax-ws test!  It took over 15 secs to 
deploy and I know it wasn't taken that long a few weeks ago.


Lin

Also, the deployment itself now seems to take atleast 2x-4x longer than 
before.


Cheers
Prasad

working on handling cases where .wsdl file isnt there

[Lin Sun]

Hi Lasantha,

I plan to work on building wsdldefinition where .wsdl file isn't there. 
 This is an area that I can still test by issuing .wsdl request when 
invoke() is broken so I decided to work on that for now.


Thanks,
Lin

RE: Build successful for Revision: 504936

[Lin Sun]

Thanks!  I think it would be really good to have a blessed build every
day!:-)

Lin
-Original Message-
From: Prasad Kashyap [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 08, 2007 11:50 AM
To: dev@geronimo.apache.org
Subject: Build successful for Revision: 504936

-- Forwarded message --
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: 8 Feb 2007 16:33:33 -
Subject: Build successful for Revision: 504936
To: [EMAIL PROTECTED]


See the full build log file at http://people.apache.org/~prasad/build.log

[INFO] Reactor Summary:
[INFO]

[INFO] Geronimo .. SUCCESS
[21.427s]
[INFO] Geronimo Test Support . SUCCESS
[0.023s]
[INFO] Geronimo Test Support :: Common ... SUCCESS
[14.738s]
[INFO] Geronimo Test Support :: Selenium . SUCCESS
[7.661s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 ... SUCCESS
[0.017s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 :: EJB  SUCCESS
[4.098s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 :: WAR  SUCCESS
[7.694s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 :: RAR  SUCCESS
[4.331s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.3 :: EAR  SUCCESS
[0.304s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 ... SUCCESS
[0.018s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 :: EJB  SUCCESS
[0.920s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 :: WAR  SUCCESS
[0.159s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 :: RAR  SUCCESS
[0.091s]
[INFO] Geronimo Test Support, Test Deployment J2EE 1.4 :: EAR  SUCCESS
[0.069s]
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 ... SUCCESS
[0.016s]
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 :: EJB  SUCCESS
[0.657s]
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 :: WAR  SUCCESS
[0.134s]
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 :: RAR  SUCCESS
[0.105s]
[INFO] Geronimo Test Support, Test Deployment JAVAEE 5 :: EAR  SUCCESS
[0.071s]
[INFO] Geronimo :: Modules ... SUCCESS
[0.038s]
[INFO] Geronimo :: Activation  SUCCESS
[7.899s]
[INFO] Geronimo :: ActiveMQ Embedded RAR . SUCCESS
[24.014s]
[INFO] Geronimo :: Kernel  SUCCESS
[12.383s]
[INFO] Geronimo :: Common  SUCCESS
[1.748s]
[INFO] Geronimo :: Util .. SUCCESS
[6.803s]
[INFO] Geronimo :: System  SUCCESS
[12.972s]
[INFO] Geronimo :: Management API  SUCCESS
[2.878s]
[INFO] Geronimo :: ActiveMQ GBean Management Interfaces .. SUCCESS
[0.648s]
[INFO] Geronimo :: J2EE .. SUCCESS
[1.242s]
[INFO] Geronimo :: Interceptor ... SUCCESS
[0.601s]
[INFO] Geronimo :: Core .. SUCCESS
[1.260s]
[INFO] Geronimo :: Security .. SUCCESS
[13.073s]
[INFO] Geronimo :: Transaction ... SUCCESS
[4.918s]
[INFO] Geronimo :: Naming  SUCCESS
[4.710s]
[INFO] Geronimo :: Deployment  SUCCESS
[3.627s]
[INFO] Geronimo :: Connector . SUCCESS
[28.052s]
[INFO] Geronimo :: ActiveMQ GBeans ... SUCCESS
[9.383s]
[INFO] Geronimo :: Web Services .. SUCCESS
[13.939s]
[INFO] Geronimo :: Axis .. SUCCESS
[19.085s]
[INFO] Geronimo :: Deploy :: Common Config ... SUCCESS
[2.173s]
[INFO] Geronimo :: Service :: Builder  SUCCESS
[18.155s]
[INFO] Geronimo :: J2EE Schema ... SUCCESS
[10.906s]
[INFO] Geronimo :: J2EE :: Builder ... SUCCESS
[8.509s]
[INFO] Geronimo :: Naming :: Builder . SUCCESS
[7.560s]
[INFO] Geronimo :: Webservices :: Builder  SUCCESS
[7.339s]
[INFO] Geronimo :: Axis :: Builder ... SUCCESS
[2.904s]
[INFO] Geronimo :: Client  SUCCESS
[1.369s]
[INFO] Geronimo :: Test :: DDBeans ... SUCCESS
[1.200s]
[INFO] Geronimo :: Connector :: Builder .. SUCCESS
[13.100s]
[INFO] Geronimo :: Security :: Builder ... SUCCESS
[6.390s]
[INFO] Geronimo :: Client Builder  SUCCESS
[5.898s]
[INFO] Geronimo :: Clustering  SUCCESS
[0.810s]
[INFO] Geronimo :: Clustering WADI ... SUCCESS
[24.421s]
[INFO] Geronimo :: Configuration Converter ... SUCCESS
[1.088s]
[INFO] Geronimo :: Dep

[jira] Commented: (GERONIMO-2812) Axis2 integration - getWSDL with new Axis2 Version

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471388
 ] 

Lin Sun commented on GERONIMO-2812:
---

Hi Lasantha, I understand! :-)   I didn't remove it and didn't got any CCE.

I am at this error right now:

11:27:49,406 ERROR [Axis2WebServiceContainer] Exception occurred while trying to
 invoke service method doService()
java.lang.NoSuchMethodError: org.apache.axis2.jaxws.description.EndpointDescript
ion.getPackages()Ljava/util/Set;
at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMarshal
ler.demarshalRequest(DocLitWrappedMethodMarshaller.java:196)
at org.apache.axis2.jaxws.server.dispatcher.JavaBeanDispatcher.invoke(Ja
vaBeanDispatcher.java:69)
at org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointContr
oller.java:79)
at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa
geReceiver.java:101)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:177)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReq
uest(HTTPTransportUtils.java:275)
at 
org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2We 

which comes from:   TreeSet packages = endpointDesc.getPackages();

this is a few lines before it failed last time 
(message.getBodyBlock(blockContext, factory)).  

Please let me know if you are seeing a different error.  Thx, Lin

> Axis2 integration - getWSDL with new Axis2 Version
> --
>
> Key: GERONIMO-2812
> URL: https://issues.apache.org/jira/browse/GERONIMO-2812
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Reporter: Lasantha Ranaweera
> Attachments: GERONIMO-2812.patch
>
>
> Both getWSDL & invoke methods of Axis2WebServiceContainer fails with new 
> Axis2 snapshot.  This simple patch will address the issue as given way.
> 1. Change the way of serviceName created using more generalize way.
> 2. Remove the HTTPConstants.MC_HTTP_SERVLETREQUEST property from 
> MessageContext since it gives CCE problem in the Axis2 side.
> Still we have to find solution to the invoke() method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-2812) Axis2 integration - getWSDL with new Axis2 Version

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471347
 ] 

Lin Sun commented on GERONIMO-2812:
---

Hi Lasantha, see patch 2811 for a different way to solve a similar prob.   :)

Lin

> Axis2 integration - getWSDL with new Axis2 Version
> --
>
> Key: GERONIMO-2812
> URL: https://issues.apache.org/jira/browse/GERONIMO-2812
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
>Reporter: Lasantha Ranaweera
> Attachments: GERONIMO-2812.patch
>
>
> Both getWSDL & invoke methods of Axis2WebServiceContainer fails with new 
> Axis2 snapshot.  This simple patch will address the issue as given way.
> 1. Change the way of serviceName created using more generalize way.
> 2. Remove the HTTPConstants.MC_HTTP_SERVLETREQUEST property from 
> MessageContext since it gives CCE problem in the Axis2 side.
> Still we have to find solution to the invoke() method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2811) got runtimeexception when processing soap request in doservice2

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2811:
--

Attachment: G2811.patch

> got runtimeexception when processing soap request in doservice2
> ---
>
> Key: GERONIMO-2811
> URL: https://issues.apache.org/jira/browse/GERONIMO-2811
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: G2811.patch
>
>
> Some code change (from Axis2) recently caused the code below to add 2 
> services to axis configurationcontext.
> configurationContext.getAxisConfiguration().addService(service);
> AxisConfiguration.addService(service) calls 
> AxisConfiguration.addServiceGroup(...) method and inside the 
> addServiceGroup method:
>if (endpoints.isEmpty()) {
> allServices.put(serviceName, axisService);
> } else if (endpoints.size() == 1) {
> // if we have one endpoint, just process it. This is special 
> case as this will be the case
> // most of the time
> allServices.put(serviceName, axisService);
> allServices.put(serviceName + "." + 
> axisService.getEndpointName(), axisService);
> It is putting 2 axisServices there which results services.size() = 2 in in 
> doservice2() call, thus runtimeexception is thrown.
> I haven't been able to identify where the change came from.  It can be they 
> changed the way how wsdlBuilder.populateService() works
> so that endpoints is set to something with the new code while it was empty 
> before.
> The fix is to determine axisservice based on the endpointclassname which 
> seems a more robust way.   I have tested the fix and was able to run .wsdl 
> test with jax-ws test.
> Also was able to run a full build with the latest trunk successfully.:)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2811) got runtimeexception when processing soap request in doservice2

[Lin Sun (JIRA)]

got runtimeexception when processing soap request in doservice2
---

 Key: GERONIMO-2811
 URL: https://issues.apache.org/jira/browse/GERONIMO-2811
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: webservices
 Environment: winxp + sun 1.5
Reporter: Lin Sun
 Fix For: 2.0


Some code change (from Axis2) recently caused the code below to add 2 services 
to axis configurationcontext.

configurationContext.getAxisConfiguration().addService(service);

AxisConfiguration.addService(service) calls 
AxisConfiguration.addServiceGroup(...) method and inside the 
addServiceGroup method:

   if (endpoints.isEmpty()) {
allServices.put(serviceName, axisService);
} else if (endpoints.size() == 1) {
// if we have one endpoint, just process it. This is special 
case as this will be the case
// most of the time
allServices.put(serviceName, axisService);
allServices.put(serviceName + "." + 
axisService.getEndpointName(), axisService);

It is putting 2 axisServices there which results services.size() = 2 in in 
doservice2() call, thus runtimeexception is thrown.

I haven't been able to identify where the change came from.  It can be they 
changed the way how wsdlBuilder.populateService() works
so that endpoints is set to something with the new code while it was empty 
before.

The fix is to determine axisservice based on the endpointclassname which seems 
a more robust way.   I have tested the fix and was able to run .wsdl test with 
jax-ws test.

Also was able to run a full build with the latest trunk successfully.:)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-2810) Fix build error at getting incubator-woden

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2810:
--

Attachment: G2810.patch

> Fix build error at getting incubator-woden 
> ---
>
> Key: GERONIMO-2810
> URL: https://issues.apache.org/jira/browse/GERONIMO-2810
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
>Priority: Critical
> Attachments: G2810.patch
>
>
> My build run fine with a clean repo at the end. :-)
> Hi, I am seeing a build error at getting incubator-woden (see below).  I 
> removed the reference to the jar in root pom.xml and configs\axis2\pom.xml 
> and my build is still running.  I don't see a need why we need them. :-)
> Lin
> --
> 1) incubator-woden:woden:jar:1.0.0M6
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=incubator-woden -DartifactId=woden \
>   -Dversion=1.0.0M6 -Dpackaging=jar -Dfile=/path/to/file
>   Path to dependency:
> 1) org.apache.geronimo.configs:axis2:car:2.0-SNAPSHOT
> 2) incubator-woden:woden:jar:1.0.0M6
> --
> 1 required artifact is missing.
> for artifact:
>   org.apache.geronimo.configs:axis2:car:2.0-SNAPSHOT
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
>   codehaus (http://repository.codehaus.org),
>   apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
>   codehaus-snapshots (http://snapshots.repository.codehaus.org),
>   apache-incubator (http://people.apache.org/repo/m2-incubating-repository/),
>   axis2-m2-repo (http://ws.zones.apache.org/repository2/),
>   tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2810) Fix build error at getting incubator-woden

[Lin Sun (JIRA)]

Fix build error at getting incubator-woden 
---

 Key: GERONIMO-2810
 URL: https://issues.apache.org/jira/browse/GERONIMO-2810
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
 Environment: winxp + sun 1.5
Reporter: Lin Sun
Priority: Critical


My build run fine with a clean repo at the end. :-)

Hi, I am seeing a build error at getting incubator-woden (see below).  I 
removed the reference to the jar in root pom.xml and configs\axis2\pom.xml and 
my build is still running.  I don't see a need why we need them. :-)

Lin

--
1) incubator-woden:woden:jar:1.0.0M6

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=incubator-woden -DartifactId=woden \
  -Dversion=1.0.0M6 -Dpackaging=jar -Dfile=/path/to/file

  Path to dependency:
1) org.apache.geronimo.configs:axis2:car:2.0-SNAPSHOT
2) incubator-woden:woden:jar:1.0.0M6

--
1 required artifact is missing.

for artifact:
  org.apache.geronimo.configs:axis2:car:2.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  codehaus (http://repository.codehaus.org),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  codehaus-snapshots (http://snapshots.repository.codehaus.org),
  apache-incubator (http://people.apache.org/repo/m2-incubating-repository/),
  axis2-m2-repo (http://ws.zones.apache.org/repository2/),
  tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

build error at getting incubator-woden

[Lin Sun]

Hi, I am seeing a build error at getting incubator-woden (see below).  I
removed the reference to the jar in root pom.xml and configs\axis2\pom.xml
and my build is still running.  I don't see a need why we need them. :-)

Lin

--
1) incubator-woden:woden:jar:1.0.0M6

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=incubator-woden -DartifactId=woden
\
  -Dversion=1.0.0M6 -Dpackaging=jar -Dfile=/path/to/file

  Path to dependency:
1) org.apache.geronimo.configs:axis2:car:2.0-SNAPSHOT
2) incubator-woden:woden:jar:1.0.0M6

--
1 required artifact is missing.

for artifact:
  org.apache.geronimo.configs:axis2:car:2.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  codehaus (http://repository.codehaus.org),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  codehaus-snapshots (http://snapshots.repository.codehaus.org),
  apache-incubator
(http://people.apache.org/repo/m2-incubating-repository/),
  axis2-m2-repo (http://ws.zones.apache.org/repository2/),
  tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)

RE: build error when test turned off

[Lin Sun]

Okay I am able to build Geronimo now with a clean repo and a fresh checkout
of trunk.  Thanks, Lin

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek
Laskowski
Sent: Tuesday, February 06, 2007 5:12 PM
To: dev@geronimo.apache.org
Subject: Re: build error when test turned off

On 2/6/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> You are right - that won't change much:-)   Seeing a different error now:

Can't be! Wipe out the org/apache/geronimo and org/apache/openejb
directories in the m2 local repo of yours and start it over. It worked
for me and so should for you.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

RE: build error when test turned off

[Lin Sun]

Yeah I did start with a clean c:\.m2 repo and I constantly got this error.
I was able to build Geronimo this am and I didn't make any code change in
between (only run maven -o eclipse:eclipse, updated 2 pom.xml files and
refreshed trunk).  

I am rechecking out a fresh trunk and trying it again with a clean .m2
repo.:-)  

Lin

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek
Laskowski
Sent: Tuesday, February 06, 2007 5:12 PM
To: dev@geronimo.apache.org
Subject: Re: build error when test turned off

On 2/6/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> You are right - that won't change much:-)   Seeing a different error now:

Can't be! Wipe out the org/apache/geronimo and org/apache/openejb
directories in the m2 local repo of yours and start it over. It worked
for me and so should for you.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

getting CNF error when deploying jax-ws test

[Lin Sun]

Hi Dims, I am getting the javax.wsdl.Definition classnotfound error when
deploying the jax-ws test.  I think this is introduced by removing the
wsdl4j dependency on either configs\axis2 or module\geornimo-axis2 but I
haven't been able to build Geronimo to verify that.  I'll continue to try
building the server with fresh everything.:-)

 

Lin

build error when test turned off

[Lin Sun]

You are right - that won't change much:-)   Seeing a different error now:

[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] Unresolved compilation problem:
schemaorg_apache_xmlbeans.system.s0B2C6F16DB8124A722ED70C47675C78C
canno
t be resolved

[INFO]

[INFO] Trace
java.lang.Error: Unresolved compilation problem:
schemaorg_apache_xmlbeans.system.s0B2C6F16DB8124A722ED70C47675C78C
canno
t be resolved

at
org.apache.geronimo.deployment.xbeans.EnvironmentDocument.(En
vironmentDocument.java:19)
at
org.apache.geronimo.deployment.service.EnvironmentBuilder.(En
vironmentBuilder.java:51)
at
org.apache.geronimo.mavenplugins.car.PlanProcessorMojo.mergeEnvironme
nt(PlanProcessorMojo.java:181)
at
org.apache.geronimo.mavenplugins.car.PlanProcessorMojo.doExecute(Plan
ProcessorMojo.java:134)
at
org.apache.geronimo.genesis.MojoSupport.execute(MojoSupport.java:122)

at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

any ideas?

Lin

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek
Laskowski
Sent: Tuesday, February 06, 2007 4:06 PM
To: dev@geronimo.apache.org
Subject: Re: anyone able to build geronimo with test/itest turned on

On 2/6/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Hi there, for the past few times, I didn't have any luck in building
> Geronimo using just mvn or mvn install.  I had to use
> '-Dmaven.test.skip=true -Dmaven.itest.skip=true' to skip both the test and
> itest.   This is the latest error I saw when I forgot to turn off the
> test/itest.:-)

You're not alone, but I don't think it'lll change your developer's
life much ;-) Thanks for sharing the tip with
'-Dmaven.test.skip=true', though. I completely forgot about it.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

RE: anyone able to build geronimo with test/itest turned on

[Lin Sun]

Hi Paul,

I am using winxp pro and sun 1.5 jdk (1.5.0_10-b02).  I am in the middle of
another build but I will provide the target/surefire-reports directory
whenever I hit this error again.:-)  

Thanks,
Lin

-Original Message-
From: Paul McMahan [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 3:41 PM
To: dev@geronimo.apache.org
Subject: Re: anyone able to build geronimo with test/itest turned on

Lin,  I was seeing this problem intermittently when geronimo used
tomcat 6.0.2 so I disabled the unit test and planned to investigate
later.  Then after upgrading geronimo's tomcat version to 6.0.8 I
could not recreate the problem so I reenabled the unit test.   I
believe you will find that the problem is intermittent, so trying to
run the test a couple more times might get you past the error.  But
that could get really aggravating if you're doing top-down builds of
trunk :-)

I will also disable the unit test again but since I'm not able to
recreate the failure can you describe your environment (OS, java
version, etc)?  Also it would be a big help if you could provide the
contents of target/surefire-reports for a failed run.

Best wishes,
Paul

On 2/6/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Hi there, for the past few times, I didn't have any luck in building
> Geronimo using just mvn or mvn install.  I had to use
> '-Dmaven.test.skip=true -Dmaven.itest.skip=true' to skip both the test and
> itest.   This is the latest error I saw when I forgot to turn off the
> test/itest.:-)
>
> Feb 6, 2007 1:17:15 PM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
> SEVERE: Socket accept failed
> java.net.SocketException: socket closed
> at java.net.PlainSocketImpl.socketAccept(Native Method)
> at java.net.PlainSocketImpl.accept(Unknown Source)
> at java.net.ServerSocket.implAccept(Unknown Source)
> at java.net.ServerSocket.accept(Unknown Source)
> at
> org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(De
> faultServerSocketFactory.java:61)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:
> 310)
> at java.lang.Thread.run(Unknown Source)
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.531 sec
> <<< FA
> ILURE!
>
> Results :
> Tests run: 8, Failures: 0, Errors: 1, Skipped: 0
>
> Anyone able to build geronimo with test/itest turned on?
>
> Thx, Lin
>
>

RE: anyone able to build geronimo with test/itest turned on

[Lin Sun]

Yeah this is on trunk... if we don't have any itests (good to know that)
then using '-Dmaven.test.skip=true' must have made a difference.  I still
cannot build Geronimo without this option.

Lin

-Original Message-
From: Prasad Kashyap [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 2:54 PM
To: dev@geronimo.apache.org
Subject: Re: anyone able to build geronimo with test/itest turned on

Is this on trunk ? We don't have any itests in the regular build of
trunk. So that config option (with or without) shouldn't be doing
anything to you.

Cheers
Prasad

On 2/6/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Hi there, for the past few times, I didn't have any luck in building
> Geronimo using just mvn or mvn install.  I had to use
> '-Dmaven.test.skip=true -Dmaven.itest.skip=true' to skip both the test and
> itest.   This is the latest error I saw when I forgot to turn off the
> test/itest.:-)
>
> Feb 6, 2007 1:17:15 PM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
> SEVERE: Socket accept failed
> java.net.SocketException: socket closed
> at java.net.PlainSocketImpl.socketAccept(Native Method)
> at java.net.PlainSocketImpl.accept(Unknown Source)
> at java.net.ServerSocket.implAccept(Unknown Source)
> at java.net.ServerSocket.accept(Unknown Source)
> at
> org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(De
> faultServerSocketFactory.java:61)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:
> 310)
> at java.lang.Thread.run(Unknown Source)
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.531 sec
> <<< FA
> ILURE!
>
> Results :
> Tests run: 8, Failures: 0, Errors: 1, Skipped: 0
>
> Anyone able to build geronimo with test/itest turned on?
>
> Thx, Lin
>
>

RE: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code

[Lin Sun]

This is avail here -

http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-jaxws-api/SNAP
SHOT/

And the ws.zones.apache.org repo is specified in root pom.xml:


axis2-m2-repo
Axis2 M2 Repository
http://ws.zones.apache.org/repository2/
default

true


true



Could this be a network glitch?

Lin

-Original Message-
From: Donald Woods [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 06, 2007 11:13 AM
To: dev@geronimo.apache.org
Subject: Re: Trunk build failure in geronimo-openejb-builder w/ latest
OpenEJB3 code

I finally got past the geronimo-openejb-builder failure using OpenEJB3 
Rev504103 and Server Rev504171, but now I'm seeing a failure in 
"Building Geronimo :: JAXWS"

Downloading: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/axi
s2/axis2-jaxws-api/SNAPSHOT/axis2-jaxws-api-SNAPSHOT.jar
[WARNING] Unable to get resource from repository apache.snapshots 
(http://people
.apache.org/repo/m2-snapshot-repository)
[INFO] 

[ERROR] BUILD ERROR
[INFO] 

[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT
   Try downloading the file manually from the project website.
   Then, install it using the command:
   mvn install:install-file -DgroupId=org.apache.axis2 
-DartifactId=axis2-jax
ws-api \
   -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
   Path to dependency:
 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT
 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT
--
1 required artifact is missing.
for artifact:
   org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT
from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
   codehaus (http://repository.codehaus.org),
   apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
   codehaus-snapshots (http://snapshots.repository.codehaus.org),
   apache-incubator 
(http://people.apache.org/repo/m2-incubating-repository/),
   axis2-m2-repo (http://ws.zones.apache.org/repository2/),
   tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)


-Donald

Sachin Patel wrote:
> I just hit this as well.
> 
> -sachin
> 
> 
> On Feb 5, 2007, at 5:30 PM, Donald Woods wrote:
> 
>> I can't get the Server trunk Rev503689 to build against a local build 
>> of the latest OpenEJB3 code at Rev503514.  Also noticed, that the 
>> OpenEJB3 build is still using the Geronimo 1.2-beta artifacts instead 
>> of 2.0-M2 or 2.0-SNAPSHOT -
>>
>> [INFO] [compiler:compile]
>> Compiling 7 source files to 
>> E:\g20\server\modules\geronimo-openejb-builder\target\classes
>> [INFO] 
>> ---
>> [ERROR] BUILD FAILURE
>> [INFO] 
>> ---
>> [INFO] Compilation failure
>>
E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero
nimo
>> \openejb\deployment\EjbModuleBuilder.java:[74,44] cannot find symbol
>> symbol  : class Cmp2Builder
>> location: package org.apache.openejb.assembler.classic
>>
E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero
nimo
>> \openejb\deployment\EjbModuleBuilder.java:[359,8] cannot find symbol
>> symbol  : class Cmp2Builder
>> location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder
>>
E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero
nimo
>> \openejb\deployment\EjbModuleBuilder.java:[359,38] cannot find symbol
>> symbol  : class Cmp2Builder
>> location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder
>>
>>
>> -Donald
> 

anyone able to build geronimo with test/itest turned on

[Lin Sun]

Hi there, for the past few times, I didn't have any luck in building
Geronimo using just mvn or mvn install.  I had to use
'-Dmaven.test.skip=true -Dmaven.itest.skip=true' to skip both the test and
itest.   This is the latest error I saw when I forgot to turn off the
test/itest.:-)

Feb 6, 2007 1:17:15 PM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
SEVERE: Socket accept failed
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(De
faultServerSocketFactory.java:61)
at
org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:
310)
at java.lang.Thread.run(Unknown Source)
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.531 sec
<<< FA
ILURE!

Results :
Tests run: 8, Failures: 0, Errors: 1, Skipped: 0

Anyone able to build geronimo with test/itest turned on?

Thx, Lin

[jira] Updated: (GERONIMO-2802) Axis2 integration - allow users to deploy jax-ws test, log the exceptions, set a few more messagecontext properties

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2802:
--

Attachment: G2802.patch

> Axis2 integration - allow users to deploy jax-ws test, log the exceptions, 
> set a few more messagecontext properties
> ---
>
> Key: GERONIMO-2802
> URL: https://issues.apache.org/jira/browse/GERONIMO-2802
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: webservices
> Environment: winxp + sun 1.5 jdk
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: G2802.patch
>
>
> This patch contains the following updates to current axis2 integration code:
> 1) removed a few unnecessary imports
> 2) had to comment out a line where we setEndInterface to webserviceAnnot, as 
> this is causing an axis2 validation error upon the war deployment.  With this 
> change, I was able to run .wsdl request.
> 3) the code didn't set setAxisService on the messagecontext inside of 
> doservice2(). This caused a "The requested service could not be found" error 
> from axis2 when processing post request .
> 4) also set a few other messagecontext properties and added the 
> Axis2RequestResponseTransport inner class that can allow for an 
> acknowledgement to be transmitted before processing has completed and also 
> allow for processing to be paused and resumed on a separate thread without 
> having a response be sent back.
> 5) also tried to log the exceptions when statuscode=500 during doservice 
> calls.
> The most recent error is:
> org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [javax.xml.bind.UnmarshalException: unexpected element 
> (uri:"http://hello_world_
> soap_http.apache.org", local:"greetMe"). Expected elements are (none)]; 
> nested e
> xception is:
> javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
>  - with linked exception:
> Which i posted to axis2-dev list and awaiting for help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2802) Axis2 integration - allow users to deploy jax-ws test, log the exceptions, set a few more messagecontext properties

[Lin Sun (JIRA)]

Axis2 integration - allow users to deploy jax-ws test, log the exceptions, set 
a few more messagecontext properties
---

 Key: GERONIMO-2802
 URL: https://issues.apache.org/jira/browse/GERONIMO-2802
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: webservices
 Environment: winxp + sun 1.5 jdk
Reporter: Lin Sun
 Fix For: 2.0


This patch contains the following updates to current axis2 integration code:
1) removed a few unnecessary imports
2) had to comment out a line where we setEndInterface to webserviceAnnot, as 
this is causing an axis2 validation error upon the war deployment.  With this 
change, I was able to run .wsdl request.
3) the code didn't set setAxisService on the messagecontext inside of 
doservice2(). This caused a "The requested service could not be found" error 
from axis2 when processing post request .
4) also set a few other messagecontext properties and added the 
Axis2RequestResponseTransport inner class that can allow for an acknowledgement 
to be transmitted before processing has completed and also allow for processing 
to be paused and resumed on a separate thread without having a response be sent 
back.
5) also tried to log the exceptions when statuscode=500 during doservice calls.

The most recent error is:

org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
 - with linked exception:
[javax.xml.bind.UnmarshalException: unexpected element (uri:"http://hello_world_
soap_http.apache.org", local:"greetMe"). Expected elements are (none)]; nested e
xception is:
javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
 - with linked exception:

Which i posted to axis2-dev list and awaiting for help.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

attempting to run jax-ws test

[Lin Sun]

Hi Dims,

I made a little bit progress into this but not as much as I like.  Thought
I'd keep you updated.

First, I had to comment out a line where we setEndInterface to
webserviceAnnot, as this is causing an axis2 validation error upon the war
deployment.  With this change, I was able to run .wsdl request.

Second, the code didn't set setAxisService on the messagecontext inside of
doservice2(). This caused a "The requested service could not be found" error
from Axis2.

I am debugging the third issue (hope it is the final issue) where an
exception is thrown at the demarshalRequest inside of
DocLitWrappedMethodMarshaller.

I haven't attempted to get the jax-ws tutorial working yet
(http://cwiki.apache.org/GMOxDOC20/simple-web-service-with-jax-ws.html) as I
would be really surprised that it works before we pass the jax-ws test.

Thanks, Lin

RE: any chance our axis2 repo doesn't have the right jars?

[Lin Sun]

The new jars look all right.  Thanks Dims!

Lin

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 01, 2007 12:45 PM
To: dev@geronimo.apache.org
Subject: Re: any chance our axis2 repo doesn't have the right jars?

There was a svn lock and i had to clean it up this morning. Can you
please check if these jars are ok?

http://ws.zones.apache.org/repository/org.apache.axis2/jars/

thanks,
dims

On 2/1/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Hi Dims, I am trying to debug the prob where the deployer cannot start the
> jax-ws test module.   I am getting some NPE during deployment and the NPE
> appears to come from below:
>
> Caused by: java.lang.NullPointerException
> at
> org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.setupW
> sdlDefinition(ServiceDescriptionImpl.java:442)
>
> However, when I attach a debugger to the server and step over the code, it
> was not stepping through the right version of ServiceDescriptionImpl.java
> file, as it is running/doing stuff at comment lines or empty lines.   The
> debugger is using the latest axis2 trunk code, but I didn't build axis2
> myself (currently having trouble w/ that) and got the jars from the repo
> specified in Geronimo-axis2\pom.xml.   This file is inside of
> axis2-metadata-SNAPSHOT.jar, which I downloaded from the repo yesterday pm
> when I built Geronimo and has a timestamp of 1/31 pm.   Any chance we may
> not have the latest axis2 jar files (specifically
> axis2-metadata-SNAPSHOT.jar) in our axis2 repo?
>
> Thanks, Lin
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

any chance our axis2 repo doesn't have the right jars?

[Lin Sun]

Hi Dims, I am trying to debug the prob where the deployer cannot start the
jax-ws test module.   I am getting some NPE during deployment and the NPE
appears to come from below:

Caused by: java.lang.NullPointerException
at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.setupW
sdlDefinition(ServiceDescriptionImpl.java:442)

However, when I attach a debugger to the server and step over the code, it
was not stepping through the right version of ServiceDescriptionImpl.java
file, as it is running/doing stuff at comment lines or empty lines.   The
debugger is using the latest axis2 trunk code, but I didn't build axis2
myself (currently having trouble w/ that) and got the jars from the repo
specified in Geronimo-axis2\pom.xml.   This file is inside of
axis2-metadata-SNAPSHOT.jar, which I downloaded from the repo yesterday pm
when I built Geronimo and has a timestamp of 1/31 pm.   Any chance we may
not have the latest axis2 jar files (specifically
axis2-metadata-SNAPSHOT.jar) in our axis2 repo?

Thanks, Lin

url-pattern issue continues

[Lin Sun]

Hi there,

Continue the discussion in a new thread (without Axis2 in the title) as the
questions are not specific to web services. :-)

1) I tried to run a test where a user didn't specify servlet-mapping for the
jaxws test servlet and that didn't go well.  (BTW, this is allowed per JSR
109).  How is the web container handling the cases where servlet-mapping
isn't specified by the user.  Would the container set the url-pattern to a
default value? Can someone shed some light on that?

2) We had to have an asterisk ("*") in the url-pattern (e.g. /servlet/*) of
the jaxws test servlet.  I tried to remove the * but I would get 404 when I
issue ?wsdl from the browser.  I think this is something we may have to
write code to work around the spec requirement, as a user needs to be able
to run ?wsdl calls using different syntax (like GreeterImpl?wsdl or
test?wsdl...).   For example, a user can only specify 1 (or 0)
servlet-mapping and url-pattern for one servlet in web.xml, but the Axis2
integration code can add other url-patterns to the web deployment plan that
will be used by the web container. I am wondering if there is anyway to
overwrite the in-memory version of servlet-mapping or url-pattern for
Geronimo to use (of course, don't overwrite the original web.xml)?  Any
pointer is appreciated!

Thanks, Lin

Reference doc:
JSR 109 rev 1.2 Page 61 (sec 7.1.2) where it says:
--//--
Servlet Mapping. A developer may optionally specify a servlet-mapping, In
the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service Endpoint.
No more than one servlet-mapping may be specified for a servlet that is
linked to by a port-component.
The url-pattern of the servlet-mapping must be an exact match pattern  (i.e.
it must not contain an asterisk ("*")).
--//--

[jira] Updated: (GERONIMO-2789) allow users to specify something other than services in url-pattern in axis2 jax-ws wars

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2789:
--

Attachment: G2789.patch

> allow users to specify something other than services in url-pattern in axis2 
> jax-ws wars
> 
>
> Key: GERONIMO-2789
> URL: https://issues.apache.org/jira/browse/GERONIMO-2789
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0-M2
> Environment: winxp + sun jdk 1.5
>Reporter: Lin Sun
> Fix For: 2.0-M2
>
> Attachments: G2789.patch
>
>
> In jax-ws test for axis2, we had to specify /services/* as the url-pattern 
> for the servlet:
> 
> cxfPojoServlet
> /services/*
> 
> This is because the axis2 configurationcontext default the servicePath to 
> "services".   However, that is not good for our user, which means they have 
> to put services inside of their url-pattern.   The fix is to use the 
> configurationContext.setServicePath method to override the default 'services' 
> value.  This looks okay to me as we are building one configurationcontext and 
> one axisservice per endpointClass.
> To do this, I grab the url-pattern from servlet-mapping specified in web.xml 
> and set url-pattern for the user when none is specified for the 
> servlet/Implclass.   I've tested the cases where a user specified /servlet/* 
> or /servlet/lin/* as the url-pattern and it both works fine when running the 
> jax-ws test with the RPCMessageReceiver code (before 2776 is checked in).  
> I've commented code where it will throws exception when the url-pattern 
> contains a star as that issue hasn't been resolved yet.
> The code built fine with the latest change in trunk but  I haven't been able 
> to get the jax-ws  war file deployed yet (issues not related to this patch).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-2789) allow users to specify something other than services in url-pattern in axis2 jax-ws wars

[Lin Sun (JIRA)]

allow users to specify something other than services in url-pattern in axis2 
jax-ws wars


 Key: GERONIMO-2789
 URL: https://issues.apache.org/jira/browse/GERONIMO-2789
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 2.0-M2
 Environment: winxp + sun jdk 1.5
Reporter: Lin Sun
 Fix For: 2.0-M2


In jax-ws test for axis2, we had to specify /services/* as the url-pattern for 
the servlet:


cxfPojoServlet
/services/*


This is because the axis2 configurationcontext default the servicePath to 
"services".   However, that is not good for our user, which means they have to 
put services inside of their url-pattern.   The fix is to use the 
configurationContext.setServicePath method to override the default 'services' 
value.  This looks okay to me as we are building one configurationcontext and 
one axisservice per endpointClass.

To do this, I grab the url-pattern from servlet-mapping specified in web.xml 
and set url-pattern for the user when none is specified for the 
servlet/Implclass.   I've tested the cases where a user specified /servlet/* or 
/servlet/lin/* as the url-pattern and it both works fine when running the 
jax-ws test with the RPCMessageReceiver code (before 2776 is checked in).  

I've commented code where it will throws exception when the url-pattern 
contains a star as that issue hasn't been resolved yet.

The code built fine with the latest change in trunk but  I haven't been able to 
get the jax-ws  war file deployed yet (issues not related to this patch).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

RE: [Fwd: Re: url-pattern issue during Axis2 integration]

[Lin Sun]

Hi Dims, that didn't work either.

Here's what I did:

In web.xml:


cxfPojoServlet
/servlet/*


Deploying the war file fine.   Hit
http://localhost:8080/jaxws-war-2.0-SNAPSHOT/servlet/ or
http://localhost:8080/jaxws-war-2.0-SNAPSHOT/servlet/GreeterImpl?wsdl on the
browser, got 404.  Noticed that the url got redirected to
http://localhost:8080/jaxws-war-2.0-SNAPSHOT/// immediately in both cases.

On the other hand, I've got code working to setServicePath to the
url-pattern of the servlet.  With the same war file, I can visit
http://localhost:8080/jaxws-war-2.0-SNAPSHOT/servlet/ and
http://localhost:8080/jaxws-war-2.0-SNAPSHOT/servlet/GreeterImpl?wsdl fine
but I could not constantly get the same good result. :-(

Lin
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 30, 2007 5:05 PM
To: Lin Sun
Cc: dev@geronimo.apache.org
Subject: Re: [Fwd: Re: url-pattern issue during Axis2 integration]

I remember a special setting for setServicePath("/") can u please try that
one?

On 1/30/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Something went wrong with my gmail so I didn't see the reply till now.
>
> No, I've tried that yesterday and it didn't work.  I wish it could. :-)
> Basically, you cannot have servicepath set to empty or null.
>
> public String getServicePath() {
> if (servicePath == null || servicePath.trim().length() == 0) {
> throw new IllegalArgumentException("service path cannot be
null
> or empty");
> }
> return servicePath.trim();
> }
>
> Thanks,
> Lin
>
>  Original Message 
> Subject:Re: url-pattern issue during Axis2 integration
> Date:   Tue, 30 Jan 2007 00:47:12 -0500
> From:   Davanum Srinivas <[EMAIL PROTECTED]>
> Reply-To:   dev@geronimo.apache.org, [EMAIL PROTECTED]
> To: dev@geronimo.apache.org
> References:
<[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]>
>
>
>
> Lin,
>
> Isn't setServicePath("") enough to do the trick?
>
> thanks,
> dims
>
> On 1/30/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> > Hi there,
> >
> > I have been working on one particular issue related to Axis2 integration
> > into Geronimo.  Basically the problem is that in the jaxws test, we had
to
> > use /services/* as the url-pattern for the servlet:
> >
> > 
> > cxfPojoServlet
> > /services/*
> > 
> >
> > This is invalid per JSR 109 spec.  There are two problems here:
> >
> > First, a user will have to use /services as part of the url-pattern.
> After
> > digging into this prob, I found out that the axis2 configurationcontext
> > default the servicePath to 'services'.   One fix that I can think of
> > (without a lot of work) is to use the
configurationContext.setServicePath
> > method to override the default 'services' value.  This looks okay to me
as
> > we are building one configurationcontext and one axisservice per
> > endpointClass.
> >
> > To do this, I will have to either set url-pattern for the user when none
> is
> > specified for the servlet/Implclass, or grab the url-pattern from
web.xml.
> > So I have been studying on how to get the url-pattern for a particular
> > servlet from Geronimo.  One approach I can think of is:
> > 1) inside Axis2Builder, the module object is passed in when
configurePOJO
> is
> > called.
> > 2) then I can get the getOriginalSpecDD from webmodule, then use
> > webModuleBuilder.convertToServletSchema to get the webAppType object.
> > 3) I can then get the url-pattern from webApp.getServletMappingArray()
> with
> > some processing.
> >
> > This seems rather complicated to me so please let me know if there is a
> > better way to do it.
> >
> > Second, the url-pattern of the servlet-mapping must be an exact match
> > pattern (* is not permitted).   I tried to remove the * but I would get
> 404
> > when I issue ?wsdl from the browser.  I think this is something we may
> have
> > to write code to work around the spec requirement, as a user needs to be
> > able to run ?wsdl calls using different syntax (like GreeterImpl?wsdl or
> > test?wsdl...).   For example, a user can only specify 1 (or 0)
> > servlet-mapping and url-pattern for one servlet in web.xml, but the
Axis2
> > integration code can add other url-patterns to the web deployment plan
> > (web.xml). I am wondering if there is anyway to overwrite the in- memory
> > version of servlet-mapping or url-pattern for Geronimo to use (of
course,
> > don't overwrite the original web.

RE: [Fwd: Re: url-pattern issue during Axis2 integration]

[Lin Sun]

Something went wrong with my gmail so I didn't see the reply till now.

No, I've tried that yesterday and it didn't work.  I wish it could. :-)
Basically, you cannot have servicepath set to empty or null.

public String getServicePath() {
if (servicePath == null || servicePath.trim().length() == 0) {
throw new IllegalArgumentException("service path cannot be null
or empty");
}
return servicePath.trim();
}

Thanks,
Lin
 
 Original Message 
Subject:Re: url-pattern issue during Axis2 integration
Date:   Tue, 30 Jan 2007 00:47:12 -0500
From:   Davanum Srinivas <[EMAIL PROTECTED]>
Reply-To:   dev@geronimo.apache.org, [EMAIL PROTECTED]
To: dev@geronimo.apache.org
References: <[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]>



Lin,

Isn't setServicePath("") enough to do the trick?

thanks,
dims

On 1/30/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I have been working on one particular issue related to Axis2 integration
> into Geronimo.  Basically the problem is that in the jaxws test, we had to
> use /services/* as the url-pattern for the servlet:
>
> 
> cxfPojoServlet
> /services/*
> 
>
> This is invalid per JSR 109 spec.  There are two problems here:
>
> First, a user will have to use /services as part of the url-pattern.
After
> digging into this prob, I found out that the axis2 configurationcontext
> default the servicePath to 'services'.   One fix that I can think of
> (without a lot of work) is to use the configurationContext.setServicePath
> method to override the default 'services' value.  This looks okay to me as
> we are building one configurationcontext and one axisservice per
> endpointClass.
>
> To do this, I will have to either set url-pattern for the user when none
is
> specified for the servlet/Implclass, or grab the url-pattern from web.xml.
> So I have been studying on how to get the url-pattern for a particular
> servlet from Geronimo.  One approach I can think of is:
> 1) inside Axis2Builder, the module object is passed in when configurePOJO
is
> called.
> 2) then I can get the getOriginalSpecDD from webmodule, then use
> webModuleBuilder.convertToServletSchema to get the webAppType object.
> 3) I can then get the url-pattern from webApp.getServletMappingArray()
with
> some processing.
>
> This seems rather complicated to me so please let me know if there is a
> better way to do it.
>
> Second, the url-pattern of the servlet-mapping must be an exact match
> pattern (* is not permitted).   I tried to remove the * but I would get
404
> when I issue ?wsdl from the browser.  I think this is something we may
have
> to write code to work around the spec requirement, as a user needs to be
> able to run ?wsdl calls using different syntax (like GreeterImpl?wsdl or
> test?wsdl...).   For example, a user can only specify 1 (or 0)
> servlet-mapping and url-pattern for one servlet in web.xml, but the Axis2
> integration code can add other url-patterns to the web deployment plan
> (web.xml). I am wondering if there is anyway to overwrite the in- memory
> version of servlet-mapping or url-pattern for Geronimo to use (of course,
> don't overwrite the original web.xml)?
>
> Reference doc:
> JSR 109 rev 1.2 Page 61 (sec 7.1.2) where it says:
> --//--
> Servlet Mapping. A developer may optionally specify a servlet-mapping,
> In the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service
> Endpoint.
> No more than one servlet-mapping may be specified for a servlet that is
> linked to by a port-component.
> The url-pattern of the servlet-mapping must be an exact match pattern
>  (i.e. it must not contain an asterisk ("*")).
> --//--
>
> Thanks for any input in advance!
>
> Lin
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

url-pattern issue during Axis2 integration

[Lin Sun]

Hi there,

I have been working on one particular issue related to Axis2 integration
into Geronimo.  Basically the problem is that in the jaxws test, we had to
use /services/* as the url-pattern for the servlet:


cxfPojoServlet
/services/*


This is invalid per JSR 109 spec.  There are two problems here:

First, a user will have to use /services as part of the url-pattern.  After
digging into this prob, I found out that the axis2 configurationcontext
default the servicePath to 'services'.   One fix that I can think of
(without a lot of work) is to use the configurationContext.setServicePath
method to override the default 'services' value.  This looks okay to me as
we are building one configurationcontext and one axisservice per
endpointClass.

To do this, I will have to either set url-pattern for the user when none is
specified for the servlet/Implclass, or grab the url-pattern from web.xml.
So I have been studying on how to get the url-pattern for a particular
servlet from Geronimo.  One approach I can think of is:
1) inside Axis2Builder, the module object is passed in when configurePOJO is
called.
2) then I can get the getOriginalSpecDD from webmodule, then use
webModuleBuilder.convertToServletSchema to get the webAppType object.  
3) I can then get the url-pattern from webApp.getServletMappingArray() with
some processing.   

This seems rather complicated to me so please let me know if there is a
better way to do it.  

Second, the url-pattern of the servlet-mapping must be an exact match
pattern (* is not permitted).   I tried to remove the * but I would get 404
when I issue ?wsdl from the browser.  I think this is something we may have
to write code to work around the spec requirement, as a user needs to be
able to run ?wsdl calls using different syntax (like GreeterImpl?wsdl or
test?wsdl...).   For example, a user can only specify 1 (or 0)
servlet-mapping and url-pattern for one servlet in web.xml, but the Axis2
integration code can add other url-patterns to the web deployment plan
(web.xml). I am wondering if there is anyway to overwrite the in- memory
version of servlet-mapping or url-pattern for Geronimo to use (of course,
don't overwrite the original web.xml)?  

Reference doc:
JSR 109 rev 1.2 Page 61 (sec 7.1.2) where it says:
--//--
Servlet Mapping. A developer may optionally specify a servlet-mapping,
In the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service
Endpoint.
No more than one servlet-mapping may be specified for a servlet that is
linked to by a port-component.
The url-pattern of the servlet-mapping must be an exact match pattern
 (i.e. it must not contain an asterisk ("*")).
--//--

Thanks for any input in advance!

Lin

RE: Axis2 Integration - Replace RPCMessageReciever with JAXWSMessageReciever

[Lin Sun]

Hi Lasantha,

Were you able to make any progress towards the replacing RPCMessageReciever
with JAXWSMessageReciever?  I went through my eclipse debugger a few times
and looks like a classloader issue...  Let me know if you want me to look
into this.  

I tried to look into No. 2 below. Looks like the following code would create
default configuration context based on axis2-default.xml on the classpath.
However, the servicepath is always set to "services" no matter what
url-pattern I specify in web.xml.

configurationContext =
ConfigurationContextFactory.createDefaultConfigurationContext();
AxisService service =
AxisService.createService(endpointClassName,
configurationContext.getAxisConfiguration(), RPCMessageReceiver.class);

I am hoping you or dims can comment a bit on this.  I'll dig more into it...


Lin

-Original Message-
From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 24, 2007 6:17 AM
To: dev@geronimo.apache.org
Subject: Re: Axis2 Integration - Replace RPCMessageReciever with
JAXWSMessageReciever

Hi Lin,

Thanks for reviewing the patch. Please read my in line comments.

Thanks,
Lasantha

Lin Sun wrote:
> Hi Lasantha,
>
> Thanks for submitting the patch!  Your patch (java portion) looks look to
> me.  I don't quite understand the pom.xml portion of the patch as to why
the
> changes are needed.   Was this related to some class loading issues you
> mentioned to me in another note?
Yes I had so many class linkage problems with our previous model when I 
was doing some changes in the source code and was trying to follow the 
same structure of CXF.
>Also, my guess is that you don't have
> G2746-new patch yet which I removed the hardcoded version to use
> dependencymanagement.   I'd appreciate if you could apply that onto your
> machine to make the applying patch process easier.
>   
Sure, I will do it. It would be fine if somebody in the list with 
committer rights will apply in to the trunk if it is correct.
> I noticed the following aren't working yet and I'll work on them while you
> work on Axis2ServiceRefBuilder.
>
> 1) haven't able to get first test of jaxws-test running (post a soap
request
> and get a soap response).   Did that work for you?   ?wsdl works fine.   
>   
Yes you are correct here and I have missed the soap response test and it 
is not working correctly either :-\ . I will correct it and create a new 
patch soon.
> 2) we had two servlet-mappings & used an asterisk in the jax-ws test app
for
> axis2.  This seems invalid per the spec.
>
> I have been reading JSR 109 rev 1.2 lately and I saw the following in page
> 61 (sec 7.1.2) where it says:
> --//--
> Servlet Mapping. A developer may optionally specify a servlet-mapping, in
> the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service
Endpoint.
> No more than one servlet-mapping may be specified for a servlet that is
> linked to by a port-component.
> The url-pattern of the servlet-mapping must be an exact match pattern
(i.e.
> it must not contain an asterisk ("*")).
> --//--
>
>   
> I am also interested in handling cases where wsdl files aren't there and
> users are using web services annotation.  Currently the code just throws a
> warning or exception.
>   
Please go ahead since I am not going to touch that part pretty soon. My 
plan is to finish the JAXWS stuff with XML file and moving in to the 
RefBuilder ASAP.
> Please keep me posted on what you are working on.  Thanks.
>
> Lin
>
>
> 
> From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, January 23, 2007 6:13 AM
> To: dev@geronimo.apache.org
> Subject: Axis2 Integration - Replace RPCMessageReciever with
> JAXWSMessageReciever
>
> Hi,
>
> Initial patch for the replacing RPCMessageReciever with
JAXWSMessageReciever
> is submitted under GERONIMO-2776.  Had to change some of the coding to
> handle ?wsdl request correctly in the newer version. 
>
> Thanks,
> Lasantha Ranaweera
>
>
>   

[jira] Commented: (GERONIMO-2188) Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467397
 ] 

Lin Sun commented on GERONIMO-2188:
---

Hi David, Finally able to verify the patch but it didn't work.  It acted as if 
the patch isn't there - transaction aren't committed to the database right away 
- I was doing query on the order (like select * from orderejb where 
account_accountid=203;)

> Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
> 
>
> Key: GERONIMO-2188
> URL: https://issues.apache.org/jira/browse/GERONIMO-2188
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector
>Affects Versions: 1.1.1
>Reporter: Krishnakumar B
> Assigned To: Matt Hogstrom
> Attachments: G2188-2.patch, G2188.patch
>
>
> We have to configure CommitBeforeAutCommit="true" property exclusively in the 
> database connection pool plan, to have the ejb -based transactions 
> immediately committed for oracle database. Otherwise it only commits 
> transaction when  the server  shuts-down. This problem is not faces with 
> Derby database.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

RE: Axis2 Integration - Replace RPCMessageReciever with JAXWSMessageReciever

[Lin Sun]

Hi Lasantha,

Thanks for submitting the patch!  Your patch (java portion) looks look to
me.  I don't quite understand the pom.xml portion of the patch as to why the
changes are needed.   Was this related to some class loading issues you
mentioned to me in another note?   Also, my guess is that you don't have
G2746-new patch yet which I removed the hardcoded version to use
dependencymanagement.   I'd appreciate if you could apply that onto your
machine to make the applying patch process easier.

I noticed the following aren't working yet and I'll work on them while you
work on Axis2ServiceRefBuilder.

1) haven't able to get first test of jaxws-test running (post a soap request
and get a soap response).   Did that work for you?   ?wsdl works fine.   

2) we had two servlet-mappings & used an asterisk in the jax-ws test app for
axis2.  This seems invalid per the spec.

I have been reading JSR 109 rev 1.2 lately and I saw the following in page
61 (sec 7.1.2) where it says:
--//--
Servlet Mapping. A developer may optionally specify a servlet-mapping, in
the web.xml deployment descriptor, for a JAX-RPC or JAX-WS Service Endpoint.
No more than one servlet-mapping may be specified for a servlet that is
linked to by a port-component.
The url-pattern of the servlet-mapping must be an exact match pattern (i.e.
it must not contain an asterisk (“*”)).
--//--


I am also interested in handling cases where wsdl files aren't there and
users are using web services annotation.  Currently the code just throws a
warning or exception.

Please keep me posted on what you are working on.  Thanks.

Lin



From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 23, 2007 6:13 AM
To: dev@geronimo.apache.org
Subject: Axis2 Integration - Replace RPCMessageReciever with
JAXWSMessageReciever

Hi,

Initial patch for the replacing RPCMessageReciever with JAXWSMessageReciever
is submitted under GERONIMO-2776.  Had to change some of the coding to
handle ?wsdl request correctly in the newer version. 

Thanks,
Lasantha Ranaweera

RE: Axis2/Geronimo Status

[Lin Sun]

Hi Dims,

For some reason I missed your note till tonight.  I have gone through the
axis2 related code in Geronimo lately but haven't had much chance to study
the axis2 modules.  If no one has started to work on this, I think replace
RPCMessageReceiver with JAXWSMessageReceiver could be a good task for me.

I'd be happy to have discussions on what else needs to be done
both in terms of features and bugs. :o)  I know we need to support pojo, ejb
, webservices client and webservices annotation, and we have a good start
work for pojo but that is about it.  It would be great to know your thoughts
on what needs to be done.

Thanks, Lin

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 16, 2007 12:14 AM
To: Geronimo Dev; Axis developer list
Subject: Axis2/Geronimo Status

Lin Sun, Lasantha,

Please see the attached diff that is not checked in yet. Basically
i've commented out some of the cxf stuff so that Axis2 integration
kicks in. There are some changes in JaxWSTest.java for the url for the
web service itself.

Right now the "?wsdl" works a bit. But the wsdl itself has some stuff
missing. Am working on getting the actual call to work. Hopefully will
be able to do that in a day or two. Once the two of you get familiar
with the current code. We can talk about what else needs to be done
both in terms of features and bugs :) For example, i am currently
using RPCMessageReceiver, we will need to switch to the
JAXWSMessageReceiver. I will drop a note as soon as i get the actual
web service call working. But in the mean while please go thru the
code in geronimo svn repo as well as Axis2 (basically the kernel
module and jaxws module).

Sounds good?

thanks,
dims

-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

[jira] Commented: (GERONIMO-2746) use dependencymanagement for some axis2 dependent modules

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466208
 ] 

Lin Sun commented on GERONIMO-2746:
---

Please ignore the first patch.

1) The new patch uses dependencymanagement.

2) woodstox and jaxb-impl has been removed from axis2 config module, as it is 
getting them as dependencies from the webservices-common config.

3) jaxb-xjc has been removed.

Tested the change with rev 497927 and was able to run the jaxws-war test with 
the jetty assembly.


> use dependencymanagement for some axis2 dependent modules 
> --
>
> Key: GERONIMO-2746
> URL: https://issues.apache.org/jira/browse/GERONIMO-2746
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0-M1
> Environment: winxp + sun jdk 1.5
>Reporter: Lin Sun
>Priority: Minor
> Attachments: G2746-new.patch, G2746.patch
>
>
> This patch is intended to use the dependencymanagement for the axis2 
> dependencies that have the same version specified in root pom.xml file.  
> I removed the following dependency as I dont see a need of it:
> -
> -com.sun.xml.bind
> -jaxb-xjc
> -2.0.2
> -
> Also, tried to correct the 202 typo.  The logic doesn't look right so I went 
> back to the code where I think this portion of code was copied from 
> (HTTPWorker.service), and it has 200 there.
> patch is created against rev 496844 and I was able to get jax-ws testing 
> running (both soap call + ?wsdl call), even tho I am not sure if the ?wsdl 
> call result looks completely correct.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (GERONIMO-2746) use dependencymanagement for some axis2 dependent modules

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2746:
--

Attachment: G2746-new.patch

> use dependencymanagement for some axis2 dependent modules 
> --
>
> Key: GERONIMO-2746
> URL: https://issues.apache.org/jira/browse/GERONIMO-2746
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0-M1
> Environment: winxp + sun jdk 1.5
>Reporter: Lin Sun
>Priority: Minor
> Attachments: G2746-new.patch, G2746.patch
>
>
> This patch is intended to use the dependencymanagement for the axis2 
> dependencies that have the same version specified in root pom.xml file.  
> I removed the following dependency as I dont see a need of it:
> -
> -com.sun.xml.bind
> -jaxb-xjc
> -2.0.2
> -
> Also, tried to correct the 202 typo.  The logic doesn't look right so I went 
> back to the code where I think this portion of code was copied from 
> (HTTPWorker.service), and it has 200 there.
> patch is created against rev 496844 and I was able to get jax-ws testing 
> running (both soap call + ?wsdl call), even tho I am not sure if the ?wsdl 
> call result looks completely correct.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: Build failure

[Lin Sun]

I just did on my winxp laptop and finally got a successful build (with rev
497935).  I had a few failures (different than yours) earlier on, so I wiped
out the local repo and rechecked out Geronimo\trunk.   

lin
-Original Message-
From: Hernan Cunico [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 19, 2007 3:25 PM
To: dev@geronimo.apache.org
Subject: Re: Build failure

Did anybody on windows totally nuked the local repo and tried to build from
scratch?

even if I try to build openejb first I get this error.

Cheers!
Hernan

Donald Woods wrote:
> I just built Rev497904 on my XP laptop and didn't run into any problems, 
> but I didn't start with a clean repo.  I only cleaned the 
> org\apache\axis2 and org\apache\geronimo directories from the repo 
> first, built the latest openejb3 code locally and then built the latest 
> server code.
> 
> -Donald
> 
> Hernan Cunico wrote:
>> Hi All,
>> I have been consistently having this build failure all day while 
>> building from trunk rev #497879.
>>
>> For the record I have removed several times the entire local .m2 repo 
>> and did brand new svn co on totally different directories. This 
>> problem shows up on my Windows XP box (which I rebooted a number of 
>> times also just to make sure)
>>
>> Here is the last piece of the log with the error I am consistently 
>> getting. I am building Geronimo with either mvn install, mvn clean 
>> install or mvn -U clean install
>>
>> Any pointer will be greatly appreciated, so far I can't figure out 
>> what the problem is.
>>
>> Cheers!
>> Hernan
>>
>> Compiling 15 source files to 
>> d:\trunk\modules\geronimo-openejb\target\classes
>> [INFO] [resources:testResources]
>> [INFO] Using default encoding to copy filtered resources.
>> [INFO] [compiler:testCompile]
>> [INFO] Not compiling test sources
>> [INFO] [surefire:test]
>> [INFO] Tests are skipped.
>> [INFO] [jar:jar]
>> [INFO] Building jar: 
>>
d:\trunk\modules\geronimo-openejb\target\geronimo-openejb-2.0-SNAPSHOT.jar 
>>
>> [INFO] [install:install]
>> [INFO] Installing 
>>
d:\trunk\modules\geronimo-openejb\target\geronimo-openejb-2.0-SNAPSHOT.jar 
>> to 
>>
C:\.m2\org\apache\geronimo\modules\geronimo-openejb\2.0-SNAPSHOT\geronimo-op
enejb-2.0-SNAPSHOT.jar 
>>
>> [INFO] 
>>


>>
>> [INFO] Building Geronimo :: OpenEJB :: Builder
>> [INFO]task-segment: [install]
>> [INFO] 
>>


>>
>> [INFO] [tools:require-java-version {execution: validate-java-version}]
>> Downloading: 
>>
http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/
specs/geronimo-j2ee-management_1.1_spec/1.0-M1/geronimo-j2ee-management_1.1_
spec-1.0-M1.jar 
>>
>> [WARNING] Unable to get resource from repository apache-incubator 
>> (http://people.apache.org/repo/m2-incubating-repository/)
>> Downloading: 
>>
http://repository.codehaus.org/org/apache/geronimo/specs/geronimo-j2ee-manag
ement_1.1_spec/1.0-M1/geronimo-j2ee-management_1.1_spec-1.0-M1.jar 
>>
>> [WARNING] Unable to get resource from repository codehaus 
>> (http://repository.codehaus.org)
>> Downloading: 
>>
http://people.apache.org/repo/m2-incubating-repository/org/apache/geronimo/s
pecs/geronimo-j2ee-management_1.1_spec/1.0-M1/geronimo-j2ee-management_1.1_s
pec-1.0-M1.jar 
>>
>> [WARNING] Unable to get resource from repository 
>> apache-incubating-repository 
>> (http://people.apache.org/repo/m2-incubating-repository)
>> Downloading: 
>>
http://repo.mergere.com/maven2/org/apache/geronimo/specs/geronimo-j2ee-manag
ement_1.1_spec/1.0-M1/geronimo-j2ee-management_1.1_spec-1.0-M1.jar 
>>
>> 19K downloaded
>> [INFO] [xmlbeans:xmlbeans {execution: default}]
>> Time to build schema type system: 0.078 seconds
>> Time to generate code: 0.437 seconds
>> error: error reading 
>>
C:\.m2\org\apache\openejb\container\3.0-incubating-SNAPSHOT\container-3.0-in
cubating-SNAPSHOT.pom; 
>> error in opening zip file
>> Note: Some input files use or override a deprecated API.
>> Note: Recompile with -Xlint:deprecation for details.
>> 1 error
>>
>> BUILD FAILED
>> [INFO] 
>> 
>> [ERROR] BUILD ERROR
>> [INFO] 
>> 
>> [INFO] XmlBeans compile failed:
>> xml ErrorLoading schema file 
>>
d:\trunk\modules\geronimo-openejb-builder\src\main\schema\geronimo-openejb-2
.0.xsd 
>>
>> xml ErrorLoading config file 
>> d:\trunk\modules\geronimo-openejb-builder\src\main\schema\xmlconfig.xml
>>
>> [INFO] 
>> 
>> [INFO] For more information, run Maven with the -e switch
>> [INFO] 
>> 
>> [INFO] Total time: 3 minutes 47 seconds
>> [INFO] Finished at: Fri Jan 19 13:57:50 EST 2007
>> [INFO] Final Memory: 56M/110M
>> [INFO] 

[jira] Commented: (GERONIMO-2752) Axis2 integration displays invalid information for URL requests

[Lin Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465949
 ] 

Lin Sun commented on GERONIMO-2752:
---

I have reviewed the patch.   There is a small error here below.  The 'return;' 
should not be deleted.  

@@ -237,18 +246,11 @@
 }
 }
 if (uri.getQuery().startsWith("wsdl")) {
-String serviceName = path.substring(path.lastIndexOf("/") + 1);
-HashMap services = 
configurationContext.getAxisConfiguration().getServices();
-final AxisService service = (AxisService) 
services.get(serviceName);
-if (service != null) {
-service.printWSDL(response.getOutputStream(), 
uri.getHost(), servicePath);
-return;
-}
+   if(service != null){
+   service.printWSDL(response.getOutputStream(), 
uri.getHost(), servicePath);
+   }

I think the patch works but the original solution works too, except that it may 
not work if the uri contains '?wsdl2'.   But if you replace the line below it 
should work.

 if (uri.getQuery().startsWith("wsdl2")) {
-String serviceName = path.substring(path.lastIndexOf("/") + 1, 
path.length() - 6);

+   String serviceName = path.substring(path.lastIndexOf("/") + 1);

Overall I don't see a big benefit of using the new proposed approach - use 
(AxisService)(services.values().iterator().next()) to get the AxisService while 
the original approach - use (AxisService) services.get(serviceName) to get the 
AxisService.   I think both work well in my simple scenario, but I could easily 
have missed something.:-)

Lin








> Axis2 integration displays invalid information for URL requests
> ---
>
> Key: GERONIMO-2752
> URL: https://issues.apache.org/jira/browse/GERONIMO-2752
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0-M1
>Reporter: Lasantha Ranaweera
> Attachments: GERONIMO-2752.patch1, GERONIMO-2752.patch2
>
>
> Current integration of Axis2 gives wrong information to the wsdl, wsdl2, xsd= 
> .. etc URL requests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: Axis2/Geronimo Status

[Lin Sun]

Hi Dims,  I didn't get your tip!:-(  I set the breakpoint in AxisFault in
Axis2WebServiceContainer.java but nothing happens when I issue '?wsdl' from
firefox.  Also tried to put a breakpoint in AxisFault in
AxisService.printWSDL(..) but didn't stop there either.

>From the AxisService.printWSDL(..) method, the isUseUserWSDL() value is
false, thus the system generated wsdl was displayed.  Initially I had
thought it was a prob that the '?wsdl" isn't given me pretty much same thing
as the .wsdl file inside the jaxws-test war, but it may not be a prob as
there is no where the jaxws-test project specified something like below in
services.xml: 

true

Thoughts?  Lin

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 18, 2007 1:05 AM
To: Lin Sun
Cc: dev@geronimo.apache.org
Subject: Re: Axis2/Geronimo Status

TIP: In your debugger put a break point on org.apache.axis2.AxisFault
(Exception) and then open "?wsdl" in your browser :)

-- dims

On 1/17/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Hi Dims, This is great progress!  I was able to get it running.  The ?wsdl
> call doesn't look completely right to me but this is an area that I am
> trying to learn.  I'll investigate more and post back.
>
> Lin
>
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 17, 2007 12:36 AM
> To: [EMAIL PROTECTED]; Geronimo Dev
> Subject: Axis2/Geronimo Status
>
> Lin, Lasantha,
>
> Got both the ?wsdl and the actual call working with following diff.
> You will need to wait an hour for some axis2 changes i checked in to
> see this working. (Axis2 svn rev - 496938)
>
> thanks,
> dims
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

RE: more than one versions of different modules in geronimo-axis2 and dependencyManagement (root pom.xml)

[Lin Sun]

Ok I'll submit a patch so that the axis2 modules can use
dependencyManagement as well.  Thx, Lin

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 18, 2007 1:04 AM
To: dev@geronimo.apache.org
Subject: Re: more than one versions of different modules in geronimo-axis2
and dependencyManagement (root pom.xml)

Lin,

No need to use the newer versions, older versions should work ok.

-- dims

On 1/17/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> I submitted G2746 to remove some of the versions in axis2\pom.xml so that
it
> can use whatever specified in the root pom.xml. I suppose we can move to
> jaxb-impl 2.0.3 for Axis2 modules.  However, I don't know what to do with
> the other 5 modules below as Axis2 uses newer versions and there may be a
> reason for that.   Doesn't seem reasonable to me if we create two versions
> of the same module in the root pom.xml so it may just be better to move to
> the later version in the root pom.xml?
>
> Thanks, Lin
>
>
> -Original Message-
> From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
> Sent: Wednesday, January 17, 2007 12:01 AM
> To: dev@geronimo.apache.org
> Subject: Re: more than one versions of different modules in geronimo-axis2
> and dependencyManagement (root pom.xml)
>
> If the asix2 stuff is no longer experimental than all of it deps
> should be created in dependencyManagement.  I've already added a few
> comments to those poms to that affect.
>
> --jason
>
>
> On Jan 16, 2007, at 7:11 PM, Lin Sun wrote:
>
> > I spent some time to compare what modules are specified in
> > Geronimo-axis2\pom.xml and what versions specified in
> > dependencyManagement
> > for the common modules.   The following 6 modules have different
> > versions.
> > Seems all modules in axis2\pom.xml have newer versions except jaxb-
> > impl
> > which moved to 2.0.3 very recently.   Is there any plan to move to the
> > module versions (except jaxb-impl) specified below in root pom.xml?
> >
> > From Geronimo-axis2\pom.xml:
> >
> > 
> > org.apache.ws.commons.schema
> > XmlSchema
> > 1.2 
> > 
> > 
> > commons-logging
> > commons-logging
> > 1.1  
> > 
> > 
> > log4j
> > log4j
> > 
> > 
> > logkit
> > logkit
> > 
> > 
> > avalon-framework
> > avalon-framework
> > 
> > 
> > 
> > 
> > wsdl4j
> > wsdl4j
> > 1.6.2 
> > 
> > 
> > xmlbeans
> > xbean
> > 2.2.0  
> > 
> > 
> > com.sun.xml.bind
> > jaxb-impl
> > 2.0.2  
> > 
> > 
> > javax.xml.bind
> > jaxb-api
> > 2.0.2 
> > 
> > 
> >
> > Thanks, Lin
> >
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

RE: more than one versions of different modules in geronimo-axis2 and dependencyManagement (root pom.xml)

[Lin Sun]

I submitted G2746 to remove some of the versions in axis2\pom.xml so that it
can use whatever specified in the root pom.xml. I suppose we can move to
jaxb-impl 2.0.3 for Axis2 modules.  However, I don't know what to do with
the other 5 modules below as Axis2 uses newer versions and there may be a
reason for that.   Doesn't seem reasonable to me if we create two versions
of the same module in the root pom.xml so it may just be better to move to
the later version in the root pom.xml?

Thanks, Lin


-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dillon
Sent: Wednesday, January 17, 2007 12:01 AM
To: dev@geronimo.apache.org
Subject: Re: more than one versions of different modules in geronimo-axis2
and dependencyManagement (root pom.xml)

If the asix2 stuff is no longer experimental than all of it deps  
should be created in dependencyManagement.  I've already added a few  
comments to those poms to that affect.

--jason


On Jan 16, 2007, at 7:11 PM, Lin Sun wrote:

> I spent some time to compare what modules are specified in
> Geronimo-axis2\pom.xml and what versions specified in  
> dependencyManagement
> for the common modules.   The following 6 modules have different  
> versions.
> Seems all modules in axis2\pom.xml have newer versions except jaxb- 
> impl
> which moved to 2.0.3 very recently.   Is there any plan to move to the
> module versions (except jaxb-impl) specified below in root pom.xml?
>
> From Geronimo-axis2\pom.xml:
>
> 
> org.apache.ws.commons.schema
> XmlSchema
> 1.2 
> 
> 
> commons-logging
> commons-logging
> 1.1  
> 
> 
> log4j
> log4j
> 
> 
> logkit
> logkit
> 
> 
> avalon-framework
> avalon-framework
> 
> 
> 
> 
> wsdl4j
> wsdl4j
> 1.6.2 
> 
> 
> xmlbeans
> xbean
> 2.2.0  
> 
> 
> com.sun.xml.bind
> jaxb-impl
> 2.0.2  
> 
> 
> javax.xml.bind
> jaxb-api
> 2.0.2 
> 
> 
>
> Thanks, Lin
>

RE: Axis2/Geronimo Status

[Lin Sun]

Hi Dims, This is great progress!  I was able to get it running.  The ?wsdl
call doesn't look completely right to me but this is an area that I am
trying to learn.  I'll investigate more and post back.

Lin

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 17, 2007 12:36 AM
To: [EMAIL PROTECTED]; Geronimo Dev
Subject: Axis2/Geronimo Status

Lin, Lasantha,

Got both the ?wsdl and the actual call working with following diff.
You will need to wait an hour for some axis2 changes i checked in to
see this working. (Axis2 svn rev - 496938)

thanks,
dims

-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

[jira] Updated: (GERONIMO-2746) use dependencymanagement for some axis2 dependent modules

[Lin Sun (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lin Sun updated GERONIMO-2746:
--

Attachment: G2746.patch

> use dependencymanagement for some axis2 dependent modules 
> --
>
> Key: GERONIMO-2746
> URL: https://issues.apache.org/jira/browse/GERONIMO-2746
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 2.0-M1
> Environment: winxp + sun jdk 1.5
>Reporter: Lin Sun
>Priority: Minor
> Attachments: G2746.patch
>
>
> This patch is intended to use the dependencymanagement for the axis2 
> dependencies that have the same version specified in root pom.xml file.  
> I removed the following dependency as I dont see a need of it:
> -
> -com.sun.xml.bind
> -jaxb-xjc
> -2.0.2
> -
> Also, tried to correct the 202 typo.  The logic doesn't look right so I went 
> back to the code where I think this portion of code was copied from 
> (HTTPWorker.service), and it has 200 there.
> patch is created against rev 496844 and I was able to get jax-ws testing 
> running (both soap call + ?wsdl call), even tho I am not sure if the ?wsdl 
> call result looks completely correct.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (GERONIMO-2746) use dependencymanagement for some axis2 dependent modules

[Lin Sun (JIRA)]

use dependencymanagement for some axis2 dependent modules 
--

 Key: GERONIMO-2746
 URL: https://issues.apache.org/jira/browse/GERONIMO-2746
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 2.0-M1
 Environment: winxp + sun jdk 1.5
Reporter: Lin Sun
Priority: Minor


This patch is intended to use the dependencymanagement for the axis2 
dependencies that have the same version specified in root pom.xml file.  

I removed the following dependency as I dont see a need of it:
-
-com.sun.xml.bind
-jaxb-xjc
-2.0.2
-

Also, tried to correct the 202 typo.  The logic doesn't look right so I went 
back to the code where I think this portion of code was copied from 
(HTTPWorker.service), and it has 200 there.

patch is created against rev 496844 and I was able to get jax-ws testing 
running (both soap call + ?wsdl call), even tho I am not sure if the ?wsdl call 
result looks completely correct.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: svn commit: r496446 - /geronimo/server/trunk/modules/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java

[Lin Sun]

Thanks - will load it up and see if I can get it working.  Lin

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 16, 2007 10:35 PM
To: Geronimo Dev
Subject: Re: svn commit: r496446 -
/geronimo/server/trunk/modules/geronimo-axis2/src/main/java/org/apache/geron
imo/axis2/Axis2WebServiceContainer.java

Hi,

See enclosed diff. Specifically the url :)

thanks,
dims

On 1/16/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Hi Dims, just curious... how were you able to verify '?wsdl' working?  I
> haven't been able to get '?wsdl' working with the cxfpojows test case.
>
> Thanks, Lin
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 15, 2007 2:08 PM
> To: scm@geronimo.apache.org
> Subject: svn commit: r496446 -
>
/geronimo/server/trunk/modules/geronimo-axis2/src/main/java/org/apache/geron
> imo/axis2/Axis2WebServiceContainer.java
>
> Author: dims
> Date: Mon Jan 15 11:07:43 2007
> New Revision: 496446
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=496446
> Log:
> get ?wsdl working. next step is to get the actual call working
>
> Modified:
>
>
geronimo/server/trunk/modules/geronimo-axis2/src/main/java/org/apache/geroni
> mo/axis2/Axis2WebServiceContainer.java
>
> Modified:
>
geronimo/server/trunk/modules/geronimo-axis2/src/main/java/org/apache/geroni
> mo/axis2/Axis2WebServiceContainer.java
> URL:
>
http://svn.apache.org/viewvc/geronimo/server/trunk/modules/geronimo-axis2/sr
>
c/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java?view=dif
> f&rev=496446&r1=496445&r2=496446
>

> ==
> ---
>
geronimo/server/trunk/modules/geronimo-axis2/src/main/java/org/apache/geroni
> mo/axis2/Axis2WebServiceContainer.java (original)
> +++
>
geronimo/server/trunk/modules/geronimo-axis2/src/main/java/org/apache/geroni
> mo/axis2/Axis2WebServiceContainer.java Mon Jan 15 11:07:43 2007
> @@ -44,6 +44,7 @@
>  import javax.xml.namespace.QName;
>  import java.io.PrintWriter;
>  import java.net.SocketException;
> +import java.net.URI;
>  import java.util.HashMap;
>  import java.util.Map;
>
> @@ -58,7 +59,7 @@
>  private transient final ClassLoader classLoader;
>  private final String endpointClassName;
>  private final PortInfo portInfo;
> -ConfigurationContext configurationContext =
> ConfigurationContextFactory.createEmptyConfigurationContext();
> +private ConfigurationContext configurationContext;
>  private String contextRoot = null;
>
>  public Axis2WebServiceContainer(PortInfo portInfo, String
> endpointClassName, ClassLoader classLoader) {
> @@ -66,10 +67,13 @@
>  this.endpointClassName = endpointClassName;
>  this.portInfo = portInfo;
>  try {
> +configurationContext =
> ConfigurationContextFactory.createDefaultConfigurationContext();
>  AxisService service =
> AxisService.createService(endpointClassName,
> configurationContext.getAxisConfiguration(), RPCMessageReceiver.class);
>
> configurationContext.getAxisConfiguration().addService(service);
>  } catch (AxisFault af) {
>  throw new RuntimeException(af);
> +} catch (Exception e) {
> +throw new RuntimeException(e);
>  }
>  }
>
> @@ -144,12 +148,9 @@
>  } else {
>  response.setStatusCode(500);
>  String msg = ex.getMessage();
> -if (msg == null || msg.trim().length() == 0) {
> -msg = "Exception message unknown";
> -}
>  response.setHeader(HTTPConstants.HEADER_CONTENT_TYPE,
> "text/plain");
>  PrintWriter pw = new
> PrintWriter(response.getOutputStream());
> -pw.write(msg);
> +ex.printStackTrace(pw);
>  pw.flush();
>  }
>  }
> @@ -184,7 +185,8 @@
>  final String servicePath =
> configurationContext.getServiceContextPath();
>  final String contextPath = (servicePath.startsWith("/") ?
> servicePath : "/" + servicePath) + "/";
>
> -String uri = request.getURI().toString();
> +URI uri = request.getURI();
> +String path = uri.getPath();
>  String soapAction =
> request.getHeader(HTTPConstants.HEADER_SOAP_ACTION);
>
>  // TODO: Port this section
> @@ -209,14 +211,14 @@
>  //}
>
>  if (request.getMethod() == Request.GE