date:20090305

Re: new IBM book: Using WASCE 2.1

2009-03-05 Thread David Jencks



On Mar 5, 2009, at 5:59 PM, Shawn Jiang wrote:


In the traditional GBean, we could use:

   infoFactory.addOperation("isStarted", "String");

to expose a method of GBean, I'm asking if there is corresponding
annotation way to expose a method.


addOperation is not necessary any more because there is code that  
examines the class using reflection and adds all the operations.  This  
code works just as well if you are using annotations :-)


thanks
david jencks





On Thu, Mar 5, 2009 at 5:05 PM, David Jencks  
 wrote:


On Mar 5, 2009, at 12:45 AM, Shawn Jiang wrote:

Does anyone known how to define the GBean method in annotation way  
of

geronimo 2.2 ?

I could not find any info about this in:
http://cwiki.apache.org/GMOxDEV/gbean-annotations.html


I'm not sure what you are asking.  You don't need a getGBeanInfo()  
static

method if you are using annotations.

The DEV article leaves out:

you can specify the j2eeType of the gbean in the @GBean annotation  
and I

think the priority

the @Persistent and @Reference annotations on setter methods are like
specifying attributes and references in the gbean info builder.

I've been gradually converting gbeans to use the annotations but  
have not

yet used the @Persistent and @Reference annotations.

Some more examples are in the plugin farm clustering code and  
various places

in the kernel.

I guess we should move this page into the 2.2. docs

thanks
david jencks




On Thu, Mar 5, 2009 at 4:39 PM, Ying Tang   
wrote:


Hi Juergen,

Thanks for your suggestion.  I made some changes  and added a  
"GBean

methods" section:


http://cwiki.apache.org/GMOxDOC22/developing-and-deploying-a-geronimo-gbean.html

Any comment  is appreciated.


Best  Wishes,

Sophia


2009/3/5 Juergen Weber 


Hi Sophia,

I'd suggest you also write (the for me formerly non-obvious  
points ;-):


- a gbean consists of classes in a jar + plan
- you deploy both
- infoFactory.addAttribute("port"  relates to name="port">

- infoFactory.addOperation names the user methods you can call
- how do you call an operation?
 ->


http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410
- how do you put a GBean into JNDI
 ->


http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410

Thanks,
Juergen



Sophia Tang wrote:


Thanks Radim for your suggestion.

A  topic named "Developing and Deploying a Geronimo


GBean

" has been added to the


referencesection

in Geronimo 2.2 documentation wiki:



http://cwiki.apache.org/confluence/display/GMOxDOC22/Developing+and+Deploying+a+Geronimo+GBean



Any of your comments is welcome.


Best Regards,


Ying Tang



--
View this message in context:

http://www.nabble.com/new-IBM-book%3A-Using-WASCE-2.1-tp22117057s134p22334640.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.








--
Thanks,
Shawn







--
Shawn

Re: your current Geronimo evaluation

2009-03-05 Thread Kevan Miller



On Mar 5, 2009, at 1:20 PM, Aldian_00 wrote:




OK thank you all for the answers. We will consider this wit a lot of
attention. But to be frankly, we have difficulties to see in what  
Geronimo
is better than JBoss and Glassfish that are much mor famous and with  
a far
bigger community. Do you know some interessant points on which  
Geronimo is

better than its concurrent and that couterblance this?


As far as I know, Geronimo custom assemblies are unique and, in my  
opinion a very important feature. The ability to build fully- 
configured servers, rather than servers that require a mixture of  
deployment, administrative configuration, etc. would seem to be an  
advantage.


Another advantage is the Licensing and openness of Apache projects.  
Anyone can join the Geronimo community, and once sufficient karma has  
been earned, they' can help drive the community in new directions.  
Glassfish and JBoss will be happy to accept any contributions you  
might offer. But that's as far as it will go...


--kevan

Re: your current Geronimo evaluation

2009-03-05 Thread Kevan Miller



On Mar 4, 2009, at 11:54 AM, Juergen Weber wrote:


5 (geronimo deployment plans like this one are really, really  
difficult:
https://svn.apache.org/repos/asf/geronimo/daytrader/trunk/plans/dayTrader-db2-9.1-XA-plan.xml) 
,

the JEE standard parts are easy, the Java part of GBeans is easy, too.


Hi Juergen,
That is a complicated plan -- DayTrader does have a lot of parts.  
Would be interesting to hear what parts of the plan are difficult/what  
we should work on improving. For example:


* aggregation of all of the parts into a single geronimo deployment plan
* dependencies
* connector definitions
* etc
* all of the above... ;-)

--kevan

Re: new IBM book: Using WASCE 2.1

2009-03-05 Thread Shawn Jiang

In the traditional GBean, we could use:

infoFactory.addOperation("isStarted", "String");

to expose a method of GBean, I'm asking if there is corresponding
annotation way to expose a method.


On Thu, Mar 5, 2009 at 5:05 PM, David Jencks  wrote:
>
> On Mar 5, 2009, at 12:45 AM, Shawn Jiang wrote:
>
>> Does anyone known how to define the GBean method in annotation way of
>> geronimo 2.2 ?
>>
>> I could not find any info about this in:
>> http://cwiki.apache.org/GMOxDEV/gbean-annotations.html
>
> I'm not sure what you are asking.  You don't need a getGBeanInfo() static
> method if you are using annotations.
>
> The DEV article leaves out:
>
> you can specify the j2eeType of the gbean in the @GBean annotation and I
> think the priority
>
> the @Persistent and @Reference annotations on setter methods are like
> specifying attributes and references in the gbean info builder.
>
> I've been gradually converting gbeans to use the annotations but have not
> yet used the @Persistent and @Reference annotations.
>
> Some more examples are in the plugin farm clustering code and various places
> in the kernel.
>
> I guess we should move this page into the 2.2. docs
>
> thanks
> david jencks
>
>>
>>
>> On Thu, Mar 5, 2009 at 4:39 PM, Ying Tang  wrote:
>>>
>>> Hi Juergen,
>>>
>>> Thanks for your suggestion.  I made some changes  and added a "GBean
>>> methods" section:
>>>
>>>
>>> http://cwiki.apache.org/GMOxDOC22/developing-and-deploying-a-geronimo-gbean.html
>>>
>>> Any comment  is appreciated.
>>>
>>>
>>> Best  Wishes,
>>>
>>> Sophia
>>>
>>>
>>> 2009/3/5 Juergen Weber 

 Hi Sophia,

 I'd suggest you also write (the for me formerly non-obvious points ;-):

 - a gbean consists of classes in a jar + plan
 - you deploy both
 - infoFactory.addAttribute("port"  relates to 
 - infoFactory.addOperation names the user methods you can call
 - how do you call an operation?
  ->


 http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410
 - how do you put a GBean into JNDI
  ->


 http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410

 Thanks,
 Juergen



 Sophia Tang wrote:
>
> Thanks Radim for your suggestion.
>
> A  topic named "Developing and Deploying a Geronimo
>
>
> GBean
> " has been added to the
>
>
> referencesection
> in Geronimo 2.2 documentation wiki:
>
>
>
> http://cwiki.apache.org/confluence/display/GMOxDOC22/Developing+and+Deploying+a+Geronimo+GBean
>
>
>
> Any of your comments is welcome.
>
>
> Best Regards,
>
>
> Ying Tang


 --
 View this message in context:

 http://www.nabble.com/new-IBM-book%3A-Using-WASCE-2.1-tp22117057s134p22334640.html
 Sent from the Apache Geronimo - Users mailing list archive at
 Nabble.com.

>>>
>>>
>>
>>
>>
>> --
>> Thanks,
>> Shawn
>
>



-- 
Shawn

Re: Geronimo Axis2 update

2009-03-05 Thread Jarek Gawor

Kaupo,

I would strongly suggest changing your wsdl to use the "literal" mode.
The "encoded" mode is mostly obsolete now and unsupported by the
JAX-WS spec. Also, some parts of Axis2 might support the "encoded"
mode but other parts might not. And my guess is that the JAX-WS parts
of Axis2 do not. So updating Axis2 version might not work at all. But
if you want to try it, I would suggest testing with Geronimo
2.2-SNAPSHOT which uses Axis2 1.5-ish.

Jarek

On Thu, Mar 5, 2009 at 11:02 AM, Kaupo  wrote:
>
> I'm trying to make a new Webservice like this:
> import javax.annotation.Resource;
> import javax.jws.soap.SOAPBinding;
> import javax.xml.soap.SOAPException;
> import javax.xml.soap.SOAPMessage;
> import javax.xml.ws.Provider;
> import javax.xml.ws.ServiceMode;
> import javax.xml.ws.WebServiceContext;
> import javax.xml.ws.WebServiceProvider;
> import javax.xml.ws.Service.Mode;
>
> @WebServiceProvider(wsdlLocation = "myservice.wsdl", serviceName =
> "myservice", targetNamespace = "http://myservice.kparmas.ee/";, portName =
> "myservicePort")
> @SOAPBinding
> @ServiceMode(Mode.MESSAGE)
> public class MyService implements Provider {
>
>   �...@resource
>    protected WebServiceContext wsContext;
>
>   �...@override
>    public SOAPMessage invoke(SOAPMessage request) {
>        if (request != null) {
>            try {
>                System.out.println(request.getSOAPBody().toString());
>            } catch (SOAPException e) {
>                // TODO Auto-generated catch block
>                e.printStackTrace();
>            }
>        }
>        return request;
>    }
> }
>
> My wsdl file encodes the head and body of the soap message. Apparently axis2
> 1.3 doesn't support that, cause i get an error like this:
> 2009-03-05 17:54:09,337 WARN  [EndpointDescriptionImpl] The WSDL file could
> not be used due to an exception.  The WSDL will be ignored and annotations
> will be used.  Implementaiton class: MyService; WSDL Location: null;
> Exception: org.apache.axis2.AxisFault: Encoded use is not supported
> org.apache.axis2.AxisFault: Encoded use is not supported
>        at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
>        at
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:291)
>        at
> org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.buildAxisServiceFromWSDL(EndpointDescriptionImpl.java:789)
>        at
> org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.setupAxisServiceFromDBL(EndpointDescriptionImpl.java:698)
>        at
> org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.(EndpointDescriptionImpl.java:285)
>        at
> org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.(ServiceDescriptionImpl.java:202)
>        at
> org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescriptionFromDBCMap(DescriptionFactoryImpl.java:218)
>        at
> org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescriptionFromDBCMap(DescriptionFactory.java:125)
>        at
> org.apache.geronimo.axis2.AxisServiceGenerator.getEndpointDescription(AxisServiceGenerator.java:230)
>        at
> org.apache.geronimo.axis2.AxisServiceGenerator.getService(AxisServiceGenerator.java:226)
>        at
> org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:203)
>        at
> org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:137)
>        at
> org.apache.geronimo.axis2.pojo.POJOWebServiceContainer.init(POJOWebServiceContainer.java:71)
>        at
> org.apache.geronimo.axis2.pojo.POJOWebServiceContainerFactoryGBean.getWebServiceContainer(POJOWebServiceContainerFactoryGBean.java:94)
>        at
> org.apache.geronimo.tomcat.TomcatWebAppContext.createWebServices(TomcatWebAppContext.java:281)
>        at
> org.apache.geronimo.tomcat.TomcatWebAppContext.(TomcatWebAppContext.java:255)
>        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
>        at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>        at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>        at
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
>        at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
>        at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>        at
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
>        at
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
>        at
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
>        at
> org.apache.geronimo.gbean.runti

Re: your current Geronimo evaluation

2009-03-05 Thread Aldian_00



OK thank you all for the answers. We will consider this wit a lot of
attention. But to be frankly, we have difficulties to see in what Geronimo
is better than JBoss and Glassfish that are much mor famous and with a far
bigger community. Do you know some interessant points on which Geronimo is
better than its concurrent and that couterblance this?

Regards

Aldian
-- 
View this message in context: 
http://www.nabble.com/your-current-Geronimo-evaluation-tp22329850s134p22357416.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: Geronimo Axis2 update

2009-03-05 Thread David Jencks

I don't know if you will run into incompatibilities between axis2  
versions but the instructions here:

http://cwiki.apache.org/GMOxDOC22/substituting-one-module-with-another.html

should help you find out :-)

If you find the instructions hard to understand please let us know  
what is unclear so we can try to improve them.


thanks
david jencks
On Mar 5, 2009, at 8:02 AM, Kaupo wrote:



I'm trying to make a new Webservice like this:
import javax.annotation.Resource;
import javax.jws.soap.SOAPBinding;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.Provider;
import javax.xml.ws.ServiceMode;
import javax.xml.ws.WebServiceContext;
import javax.xml.ws.WebServiceProvider;
import javax.xml.ws.Service.Mode;

@WebServiceProvider(wsdlLocation = "myservice.wsdl", serviceName =
"myservice", targetNamespace = "http://myservice.kparmas.ee/";,  
portName =

"myservicePort")
@SOAPBinding
@ServiceMode(Mode.MESSAGE)
public class MyService implements Provider {

   @Resource
   protected WebServiceContext wsContext;

   @Override
   public SOAPMessage invoke(SOAPMessage request) {
   if (request != null) {
   try {
   System.out.println(request.getSOAPBody().toString());
   } catch (SOAPException e) {
   // TODO Auto-generated catch block
   e.printStackTrace();
   }
   }
   return request;
   }
}

My wsdl file encodes the head and body of the soap message.  
Apparently axis2

1.3 doesn't support that, cause i get an error like this:
2009-03-05 17:54:09,337 WARN  [EndpointDescriptionImpl] The WSDL  
file could
not be used due to an exception.  The WSDL will be ignored and  
annotations

will be used.  Implementaiton class: MyService; WSDL Location: null;
Exception: org.apache.axis2.AxisFault: Encoded use is not supported
org.apache.axis2.AxisFault: Encoded use is not supported
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
org 
.apache 
.axis2 
.description 
.WSDL11ToAxisServiceBuilder 
.populateService(WSDL11ToAxisServiceBuilder.java:291)

at
org 
.apache 
.axis2 
.jaxws 
.description 
.impl 
.EndpointDescriptionImpl 
.buildAxisServiceFromWSDL(EndpointDescriptionImpl.java:789)

at
org 
.apache 
.axis2 
.jaxws 
.description 
.impl 
.EndpointDescriptionImpl 
.setupAxisServiceFromDBL(EndpointDescriptionImpl.java:698)

at
org 
.apache 
.axis2 
.jaxws 
.description 
.impl.EndpointDescriptionImpl.(EndpointDescriptionImpl.java:285)

at
org 
.apache 
.axis2 
.jaxws 
.description 
.impl.ServiceDescriptionImpl.(ServiceDescriptionImpl.java:202)

at
org 
.apache 
.axis2 
.jaxws 
.description 
.impl 
.DescriptionFactoryImpl 
.createServiceDescriptionFromDBCMap(DescriptionFactoryImpl.java:218)

at
org 
.apache 
.axis2 
.jaxws 
.description 
.DescriptionFactory 
.createServiceDescriptionFromDBCMap(DescriptionFactory.java:125)

at
org 
.apache 
.geronimo 
.axis2 
.AxisServiceGenerator 
.getEndpointDescription(AxisServiceGenerator.java:230)

at
org 
.apache 
.geronimo 
.axis2.AxisServiceGenerator.getService(AxisServiceGenerator.java:226)

at
org 
.apache 
.geronimo 
.axis2 
.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java: 
203)

at
org 
.apache 
.geronimo 
.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java: 
137)

at
org 
.apache 
.geronimo 
.axis2 
.pojo.POJOWebServiceContainer.init(POJOWebServiceContainer.java:71)

at
org 
.apache 
.geronimo 
.axis2 
.pojo 
.POJOWebServiceContainerFactoryGBean 
.getWebServiceContainer(POJOWebServiceContainerFactoryGBean.java:94)

at
org 
.apache 
.geronimo 
.tomcat 
.TomcatWebAppContext.createWebServices(TomcatWebAppContext.java:281)

at
org 
.apache 
.geronimo.tomcat.TomcatWebAppContext.(TomcatWebAppContext.java: 
255)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native  
Method)

at
sun 
.reflect 
.NativeConstructorAccessorImpl 
.newInstance(NativeConstructorAccessorImpl.java:39)

at
sun 
.reflect 
.DelegatingConstructorAccessorImpl 
.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org 
.apache 
.geronimo 
.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)

at
org 
.apache 
.geronimo 
.gbean 
.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java: 
268)

at
org 
.apache 
.geronimo 
.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)

at
org 
.apache 
.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)

at
org 
.apache 
.geronimo 
.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java: 
111)

at
org 
.apache 
.geronimo 
.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)

at
org.apache.geronimo.gbean.runtime.GBeanDependency 
$1.running(GBeanDependenc

Re: Newbie problem with Geronimo 2.1.3

2009-03-05 Thread David Jencks



On Mar 5, 2009, at 8:24 AM, Ricardo Peironcely wrote:


I've found my error, but i don't know how to solve it.

I'm working with eclipse geronimo adapter. And when I define the
modules in geronimo-application.xml i wrote:

   
   PruebaGeronimoWeb.war
   PruebaGeronimoWeb.war
   
   
   PruebaGeronimoEjb.ejb
   PruebaGeronimoEjb.jar
   

The error raises when try to open the jar file as an xml because is
referenced by the  tag.

But I don't know what write in this  tag. Must I create any
new file in the EAR package? Is not enough with the openejb-jar.xml
from EJB jar and geronimo-web.xml from WAR?


- if you have individual module plans (openejb-jar.xml and geronimo- 
web.xml) in the modules you should be able to completely leave out  
both app:module elements


- I prefer to have all my geronimo configuration in one place.  In  
this case you would put the content of the module plans inside the  
app:module elements in place of the app:alt-dd element.  I actually  
prefer to keep this single plan outside my ear file but this is  
certainly not necessary.


thanks
david jencks



Best regards and thanks.
Ricardo Peironcely

2009/3/4 Kevan Miller :


On Mar 4, 2009, at 3:25 PM, Ricardo Peironcely wrote:


Hello all!!

I've a problem with a very simple application.

I've developed an war with a simple JSP that uses a simple method  
in a

class of the same project. This class invoques a Stateless 3.0 EJB
that always return hello world. The application is packed in an EAR.

When I try to deply this app in Geronimo 2.1.3 with the "Deploy New"
option in the console, always get the same error:


That's certainly not a very helpful error message. Can you tell us  
what's in

your EAR file? Or, can you share your EAR file with us?

--kevan

Re: your current Geronimo evaluation

2009-03-05 Thread David Jencks

On Mar 5, 2009, at 2:44 AM, Aldian_00 wrote:

Ok thank you very much to both of you. I am sorry if I have been
unclear. I

wil now give some more explanations.

My company owns a Network Management System. We plan to developp a
NGOSS
(Next Generation Operations Support System). It will be interfaced
on front
end with a few client Web Browsers or desktop applications, and on
back end
with the NMS using load balancing. We actually plan to implement
only a few
features, but in the end it might become a very big software. So
when I ask
if it is easy, it is because at the end many persons in our
developpement

team will have to migrate from the old technologies they are currently
working on to this new one, and we don't want to loose too much time
with

the complexities of the system.

In consequence of the fact many parts of software will come from many
different person, our deployment plans will probably be really
complex ones,
so if you say it is inadequate on geronimo, we might consider using
another

one, what do you think?

I think you will have the best results thus:
use maven for your build system. Set up a nexus instance to manage
company-wide released code distribution. Maven can be extremely
annoying sometimes but its the only solution I know of that provides
any real support for managing development of large projects with
managed code exchange between components.

Use geronimo for your app server and assembling your application
bits into geronimo plugins. push them to the nexus repo, and assemble
custom servers for the various test and production scenarios you
need. Basically this means you can use maven to manage the complexity
of your component interdependencies.

This approach is a lot easier on trunk (2.2-SNAPSHOT) but can be done
with released versions of geronimo. In trunk we are starting to use
it in several places to assemble special purpose servers to test
particular subsystems. For instance, the activemq and monitoring bits
have custom servers.

This isn't documented as well as I'd like. There's a little bit of
documentation here: http://cwiki.apache.org/GMOxDOC22/assembling-a-server-using-maven.html

Hope this helps and please ask as many questions as you'd like :-) I
think the whole idea of using maven to attach the server bits needed
to your application to assemble a server is rather new and we could
certainly use advice from large projects on how to improve our
implementation.

thanks
david jencks

best regards

Aldian

Xasima Xirohata wrote:

Boring note.

I have a little remark on the "easy" word in your test questions. I
think that this word DOES specify the aim of the comparing, so your
tests may be named as "the best server to start for newbie/common
task"-competition. But it's not very good to perform comparing ONLY
for newbies or for common projects.

EASY TO INSTALL
For example, the "easy to install"-test supposes "is it easy to
install geronimo for regular needs". Yeap, it's easy. But nothing too
specific (or extreme) in comparing with the installation of other
products I think. Moreover, I would never take into account the
'simplicity of installation' since no something complex occurs in any
of them if no troubles start.

But just imagine, that some ports (RMI/services) are already busy,
you

has misplaced your java-environment installation, you want to upgrade
server or specific parts, and so on. If it occurs I insist that, for
example, geronimo is much easy to tune or fix than ... (i can't
compare with jboss or glassfish now, so put what i know) ..regular
IBM

WebSphere (not the community edition).

As for me, all servers are easy to install in normal circumstances,
but i don't know how easy to tune or fix JBOSS/Glassfish installation
if something goes wrong.

The next question is what actually you 're going to install easily.
If

it's just common out-of-box server, it's not the problem for any of
them. But if you're in need to bundle your server with specific
services (change the web services implementation, change any of jee
SPINE services like JMS and so on), or even cut off most services to
reduce your server up to specific configuration (we just tried to
perform this some time ago when want to ship little server to run on
customer side with derby as db), then i think you probably need to
choose geronimo.
Geronimo tends to support different projects as parts and allow easy
substitution / reducing between them. As far as I know, it's better
for this purpose than others. JBoss and Glassfish used to avoid such
of reconfiguration as REGULAR, easy process, although they has hk2/
module architectures too.

Thus, on my point of view Geronimo is more easy to tune and
configure,

more easy to fix. But if compare just an typical installation process
with no troubles or specific reasons occurs, then probably all of
them

(and even an IBM WebSphere) do this process easily.

EASY DEPLOYMENT

Re: Newbie problem with Geronimo 2.1.3

2009-03-05 Thread Ricardo Peironcely

I've found my error, but i don't know how to solve it.

I'm working with eclipse geronimo adapter. And when I define the
modules in geronimo-application.xml i wrote:

PruebaGeronimoWeb.war
PruebaGeronimoWeb.war

PruebaGeronimoEjb.ejb
PruebaGeronimoEjb.jar

The error raises when try to open the jar file as an xml because is
referenced by the  tag.

But I don't know what write in this  tag. Must I create any
new file in the EAR package? Is not enough with the openejb-jar.xml
from EJB jar and geronimo-web.xml from WAR?

Best regards and thanks.
Ricardo Peironcely

2009/3/4 Kevan Miller :
>
> On Mar 4, 2009, at 3:25 PM, Ricardo Peironcely wrote:
>
>> Hello all!!
>>
>> I've a problem with a very simple application.
>>
>> I've developed an war with a simple JSP that uses a simple method in a
>> class of the same project. This class invoques a Stateless 3.0 EJB
>> that always return hello world. The application is packed in an EAR.
>>
>> When I try to deply this app in Geronimo 2.1.3 with the "Deploy New"
>> option in the console, always get the same error:
>
> That's certainly not a very helpful error message. Can you tell us what's in
> your EAR file? Or, can you share your EAR file with us?
>
> --kevan
>
>

Geronimo Axis2 update

2009-03-05 Thread Kaupo


I'm trying to make a new Webservice like this:
import javax.annotation.Resource;
import javax.jws.soap.SOAPBinding;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.Provider;
import javax.xml.ws.ServiceMode;
import javax.xml.ws.WebServiceContext;
import javax.xml.ws.WebServiceProvider;
import javax.xml.ws.Service.Mode;

@WebServiceProvider(wsdlLocation = "myservice.wsdl", serviceName =
"myservice", targetNamespace = "http://myservice.kparmas.ee/";, portName =
"myservicePort")
@SOAPBinding
@ServiceMode(Mode.MESSAGE)
public class MyService implements Provider {
  
@Resource
protected WebServiceContext wsContext;

@Override
public SOAPMessage invoke(SOAPMessage request) {
if (request != null) {
try {
System.out.println(request.getSOAPBody().toString());
} catch (SOAPException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
return request;
}
}

My wsdl file encodes the head and body of the soap message. Apparently axis2
1.3 doesn't support that, cause i get an error like this:
2009-03-05 17:54:09,337 WARN  [EndpointDescriptionImpl] The WSDL file could
not be used due to an exception.  The WSDL will be ignored and annotations
will be used.  Implementaiton class: MyService; WSDL Location: null;
Exception: org.apache.axis2.AxisFault: Encoded use is not supported
org.apache.axis2.AxisFault: Encoded use is not supported
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:291)
at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.buildAxisServiceFromWSDL(EndpointDescriptionImpl.java:789)
at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.setupAxisServiceFromDBL(EndpointDescriptionImpl.java:698)
at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.(EndpointDescriptionImpl.java:285)
at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.(ServiceDescriptionImpl.java:202)
at
org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescriptionFromDBCMap(DescriptionFactoryImpl.java:218)
at
org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescriptionFromDBCMap(DescriptionFactory.java:125)
at
org.apache.geronimo.axis2.AxisServiceGenerator.getEndpointDescription(AxisServiceGenerator.java:230)
at
org.apache.geronimo.axis2.AxisServiceGenerator.getService(AxisServiceGenerator.java:226)
at
org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:203)
at
org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:137)
at
org.apache.geronimo.axis2.pojo.POJOWebServiceContainer.init(POJOWebServiceContainer.java:71)
at
org.apache.geronimo.axis2.pojo.POJOWebServiceContainerFactoryGBean.getWebServiceContainer(POJOWebServiceContainerFactoryGBean.java:94)
at
org.apache.geronimo.tomcat.TomcatWebAppContext.createWebServices(TomcatWebAppContext.java:281)
at
org.apache.geronimo.tomcat.TomcatWebAppContext.(TomcatWebAppContext.java:255)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronim

Re: Custom Login Module HttpServletRequest access for webservice

2009-03-05 Thread Kaupo




kevan wrote:
> 
> 
> On Mar 5, 2009, at 5:40 AM, Kaupo wrote:
> 
>> I'd love to file a jira enhancement request. But I've never done that
>> before, so when can I do it?
> 
> Thanks Kaupo.
> 
> Geronimo's Jira page is here --
> http://issues.apache.org/jira/browse/GERONIMO
> 
> You'll need a Jira account to create Jira's. Do this here --
> https://issues.apache.org/jira/secure/Signup!default.jspa
> 
> --kevan
> 
> 

Thanks Kevan!

Just created the new Issue: 
http://issues.apache.org/jira/browse/GERONIMO-4572
http://issues.apache.org/jira/browse/GERONIMO-4572 
Hope it's appropriate 

-Kaupo
-- 
View this message in context: 
http://www.nabble.com/Custom-Login-Module-HttpServletRequest-access-for-webservice-tp22303812s134p22354239.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: your current Geronimo evaluation

2009-03-05 Thread Forrest Xia

For deployment plan aspect, I believe you will spend equal time among those
app servers, there is no obvious learning curve differences.

Re: Custom Login Module HttpServletRequest access for webservice

2009-03-05 Thread Kevan Miller



On Mar 5, 2009, at 5:40 AM, Kaupo wrote:


I'd love to file a jira enhancement request. But I've never done that
before, so when can I do it?


Thanks Kaupo.

Geronimo's Jira page is here -- http://issues.apache.org/jira/browse/GERONIMO

You'll need a Jira account to create Jira's. Do this here -- 
https://issues.apache.org/jira/secure/Signup!default.jspa

--kevan

Re: your current Geronimo evaluation

2009-03-05 Thread Aldian_00


Ok thank you very much to both of you. I am sorry if I have been unclear. I
wil now give some more explanations.

My company owns a Network Management System. We plan to developp a NGOSS
(Next Generation Operations Support System). It will be interfaced on front
end with a few client Web Browsers or desktop applications, and on back end
with the NMS using load balancing. We actually plan to implement only a few
features, but in the end it might become a very big software. So when I ask
if it is easy, it is because at the end many persons in our developpement
team will have to migrate from the old technologies they are currently
working on to this new one, and we don't want to loose too much time with
the complexities of the system.

In consequence of the fact many parts of software will come from many
different person, our deployment plans will probably be really complex ones,
so if you say it is inadequate on geronimo, we might consider using another
one, what do you think?

best regards

Aldian





Xasima Xirohata wrote:
> 
> Boring note.
> 
> I have a little remark on the "easy" word in your test questions. I
> think that this word DOES specify the aim of the comparing, so your
> tests may be named as "the best server to start for newbie/common
> task"-competition. But it's not very good to perform comparing ONLY
> for newbies or for common projects.
> 
> EASY TO INSTALL
> For example, the "easy to install"-test supposes "is it easy to
> install geronimo for regular needs". Yeap, it's easy. But nothing too
> specific (or extreme) in comparing with the installation of other
> products I think. Moreover, I would never take into account the
> 'simplicity of installation' since no something complex occurs in any
> of them if no troubles start.
> 
> But just imagine, that some ports (RMI/services) are already busy, you
> has misplaced your java-environment installation, you want to upgrade
> server or specific parts, and so on. If it occurs I insist that, for
> example, geronimo is much easy to tune or fix than ... (i can't
> compare with jboss or glassfish now, so put what i know) ..regular IBM
> WebSphere (not the community edition).
> 
> As for me, all servers are easy to install in normal circumstances,
> but i don't know how easy to tune or fix JBOSS/Glassfish installation
> if something goes wrong.
> 
> The next question is what actually you 're going to install easily. If
> it's just common out-of-box server, it's not the problem for any of
> them. But if you're in need to bundle your server with specific
> services (change the web services implementation, change any of jee
> SPINE services like JMS and so on), or even cut off most services to
> reduce your server up to specific configuration (we just tried to
> perform this some time ago when want to ship little server to run on
> customer side with derby as db), then i think you probably need to
> choose geronimo.
> Geronimo tends to support different projects as parts and allow easy
> substitution / reducing between them. As far as I know, it's better
> for this purpose than others. JBoss and Glassfish used to avoid such
> of reconfiguration as REGULAR, easy process, although they has hk2/
> module architectures too.
> 
> Thus, on my point of view Geronimo is more easy to tune and configure,
> more easy to fix. But if compare just an typical installation process
> with no troubles or specific reasons occurs, then probably all of them
> (and even an IBM WebSphere) do this process easily.
> 
> EASY DEPLOYMENT
> 
> Geronimo allow deployment both from console, from web interface and
> from IDE, although it's possible to monitor the server using maven
> plugins. The same is for rest of servers (JBOSS/Glassfish). I don't
> think that we need to compare which GUI is most easy to use to deploy.
> It's interesting for me to compare the ability to manage dependencies
> and services in complex projects. What's actually more easy to write
> (specific plans) and use (manage): gbeans + geronimo repositories, hk2
> + repository, jboss and (?) osgi.
> 
> So it's not question to do simple things easy (since all of servers
> comparatively simple), it's a question if it's possible to perform
> complex things at all (with reasonable time or at least
> well-documented).
> 
> EASY ADMINISTRATION
> Is it a question to do simple administration (JMX / Deployed
> Application, Memory Consumption) easily? As for me the more
> interesting question is how to monitor and manage an application
> server in cluster environment what we can manage / administrate. If
> it's possible to easily integrate server with predefined  monitoring
> service (*).
> 
> EASY  IDE INTERFACING
> 6 (If you don't know what to do, IDE will not help)... I will mark 10
> if even you don't sure exactly what to do, IDE will assist you
> COMPLETELY.
> 
> EASY DEVELOPMENT
> 
> Agree with Juergen Weber
> 
>> 5 (geronimo deployment plans like this one are really, really difficult:
>> https://svn.apache.org/re

Re: Custom Login Module HttpServletRequest access for webservice

2009-03-05 Thread Kaupo




djencks wrote:
> 
> 
> I'm pretty sure that the specs don't support what your login module is  
> doing, and that it only works due to some accidents of implementation  
> in geronimo.  However, we ought to be able to make it work for ejb  
> webservices just as well as for servlets.  I doubt it will be a big  
> change.  I'm not sure we can get it fixed for 2.1.4 we'll see.   
> Could you file a jira enhancement request?
> 
> The "official" way to do this is really to use JASPI and set up a  
> custom authentication method that replaces the BASIC auth and fishes  
> the info out of the request and provides it to the login service  
> in this case presumably a login module.  However JASPI is only  
> available in trunk and with the currently rapidly changing jetty 7  
> integration and we don't have the tck for it yet.
> 
> thanks
> david jencks
> 

I'd love to file a jira enhancement request. But I've never done that
before, so when can I do it?
JASPI sounds interesting but unfortunately I don't have time to learn it -
the project deadline is approaching.

Thanks for the fast reply David!

-Kaupo
-- 
View this message in context: 
http://www.nabble.com/Custom-Login-Module-HttpServletRequest-access-for-webservice-tp22303812s134p22349175.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: new IBM book: Using WASCE 2.1

2009-03-05 Thread Ying Tang

Hi all,

I will draft a GBean
annotations
page under GBeans  in
Geronimo 2.2 docs, starting from what we have in Geronimo DEV.

Best  Regards,

Ying Tang



2009/3/5 David Jencks 

>
> On Mar 5, 2009, at 12:45 AM, Shawn Jiang wrote:
>
>  Does anyone known how to define the GBean method in annotation way of
>> geronimo 2.2 ?
>>
>> I could not find any info about this in:
>> http://cwiki.apache.org/GMOxDEV/gbean-annotations.html
>>
>
> I'm not sure what you are asking.  You don't need a getGBeanInfo() static
> method if you are using annotations.
>
> The DEV article leaves out:
>
> you can specify the j2eeType of the gbean in the @GBean annotation and I
> think the priority
>
> the @Persistent and @Reference annotations on setter methods are like
> specifying attributes and references in the gbean info builder.
>
> I've been gradually converting gbeans to use the annotations but have not
> yet used the @Persistent and @Reference annotations.
>
> Some more examples are in the plugin farm clustering code and various
> places in the kernel.
>
> I guess we should move this page into the 2.2. docs
>
> thanks
> david jencks
>
>
>
>>
>> On Thu, Mar 5, 2009 at 4:39 PM, Ying Tang  wrote:
>>
>>> Hi Juergen,
>>>
>>> Thanks for your suggestion.  I made some changes  and added a "GBean
>>> methods" section:
>>>
>>>
>>> http://cwiki.apache.org/GMOxDOC22/developing-and-deploying-a-geronimo-gbean.html
>>>
>>> Any comment  is appreciated.
>>>
>>>
>>> Best  Wishes,
>>>
>>> Sophia
>>>
>>>
>>> 2009/3/5 Juergen Weber 
>>>

 Hi Sophia,

 I'd suggest you also write (the for me formerly non-obvious points ;-):

 - a gbean consists of classes in a jar + plan
 - you deploy both
 - infoFactory.addAttribute("port"  relates to 
 - infoFactory.addOperation names the user methods you can call
 - how do you call an operation?
  ->


 http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410
 - how do you put a GBean into JNDI
  ->


 http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410

 Thanks,
 Juergen



 Sophia Tang wrote:

>
> Thanks Radim for your suggestion.
>
> A  topic named "Developing and Deploying a Geronimo
>
> GBea<
> http://cwiki.apache.org/confluence/display/GMOxDOC22/Developing+and+Deploying+a+Geronimo+GBean
> >n
> " has been added to the
>
> reference<
> http://cwiki.apache.org/confluence/display/GMOxDOC22/Reference>section
> in Geronimo 2.2 documentation wiki:
>
>
>
> http://cwiki.apache.org/confluence/display/GMOxDOC22/Developing+and+Deploying+a+Geronimo+GBean
>
>
>
> Any of your comments is welcome.
>
>
> Best Regards,
>
>
> Ying Tang
>


 --
 View this message in context:

 http://www.nabble.com/new-IBM-book%3A-Using-WASCE-2.1-tp22117057s134p22334640.html
 Sent from the Apache Geronimo - Users mailing list archive at
 Nabble.com.


>>>
>>>
>>
>>
>> --
>> Thanks,
>> Shawn
>>
>
>

Re: new IBM book: Using WASCE 2.1

2009-03-05 Thread David Jencks



On Mar 5, 2009, at 12:45 AM, Shawn Jiang wrote:


Does anyone known how to define the GBean method in annotation way of
geronimo 2.2 ?

I could not find any info about this in:
http://cwiki.apache.org/GMOxDEV/gbean-annotations.html


I'm not sure what you are asking.  You don't need a getGBeanInfo()  
static method if you are using annotations.


The DEV article leaves out:

you can specify the j2eeType of the gbean in the @GBean annotation and  
I think the priority


the @Persistent and @Reference annotations on setter methods are like  
specifying attributes and references in the gbean info builder.


I've been gradually converting gbeans to use the annotations but have  
not yet used the @Persistent and @Reference annotations.


Some more examples are in the plugin farm clustering code and various  
places in the kernel.


I guess we should move this page into the 2.2. docs

thanks
david jencks




On Thu, Mar 5, 2009 at 4:39 PM, Ying Tang   
wrote:

Hi Juergen,

Thanks for your suggestion.  I made some changes  and added a "GBean
methods" section:

http://cwiki.apache.org/GMOxDOC22/developing-and-deploying-a-geronimo-gbean.html

Any comment  is appreciated.


Best  Wishes,

Sophia


2009/3/5 Juergen Weber 


Hi Sophia,

I'd suggest you also write (the for me formerly non-obvious  
points ;-):


- a gbean consists of classes in a jar + plan
- you deploy both
- infoFactory.addAttribute("port"  relates to name="port">

- infoFactory.addOperation names the user methods you can call
- how do you call an operation?
 ->

http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410
- how do you put a GBean into JNDI
 ->

http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410

Thanks,
Juergen



Sophia Tang wrote:


Thanks Radim for your suggestion.

A  topic named "Developing and Deploying a Geronimo

GBean

" has been added to the

referencesection

in Geronimo 2.2 documentation wiki:


http://cwiki.apache.org/confluence/display/GMOxDOC22/Developing+and+Deploying+a+Geronimo+GBean



Any of your comments is welcome.


Best Regards,


Ying Tang



--
View this message in context:
http://www.nabble.com/new-IBM-book%3A-Using-WASCE-2.1-tp22117057s134p22334640.html
Sent from the Apache Geronimo - Users mailing list archive at  
Nabble.com.









--
Thanks,
Shawn

Re: new IBM book: Using WASCE 2.1

2009-03-05 Thread Shawn Jiang

Does anyone known how to define the GBean method in annotation way of
geronimo 2.2 ?

I could not find any info about this in:
http://cwiki.apache.org/GMOxDEV/gbean-annotations.html

On Thu, Mar 5, 2009 at 4:39 PM, Ying Tang  wrote:
> Hi Juergen,
>
> Thanks for your suggestion.  I made some changes  and added a "GBean
> methods" section:
>
> http://cwiki.apache.org/GMOxDOC22/developing-and-deploying-a-geronimo-gbean.html
>
> Any comment  is appreciated.
>
>
> Best  Wishes,
>
> Sophia
>
>
> 2009/3/5 Juergen Weber 
>>
>> Hi Sophia,
>>
>> I'd suggest you also write (the for me formerly non-obvious points ;-):
>>
>> - a gbean consists of classes in a jar + plan
>> - you deploy both
>> - infoFactory.addAttribute("port"  relates to 
>> - infoFactory.addOperation names the user methods you can call
>> - how do you call an operation?
>>  ->
>>
>> http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410
>> - how do you put a GBean into JNDI
>>  ->
>>
>> http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410
>>
>> Thanks,
>> Juergen
>>
>>
>>
>> Sophia Tang wrote:
>> >
>> > Thanks Radim for your suggestion.
>> >
>> > A  topic named "Developing and Deploying a Geronimo
>> >
>> > GBean
>> > " has been added to the
>> >
>> > referencesection
>> > in Geronimo 2.2 documentation wiki:
>> >
>> >
>> > http://cwiki.apache.org/confluence/display/GMOxDOC22/Developing+and+Deploying+a+Geronimo+GBean
>> >
>> >
>> >
>> > Any of your comments is welcome.
>> >
>> >
>> > Best Regards,
>> >
>> >
>> > Ying Tang
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/new-IBM-book%3A-Using-WASCE-2.1-tp22117057s134p22334640.html
>> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>>
>
>



-- 
Thanks,
Shawn

Re: new IBM book: Using WASCE 2.1

2009-03-05 Thread Ying Tang

Hi Juergen,

Thanks for your suggestion.  I made some changes  and added a "GBean
methods" section:

http://cwiki.apache.org/GMOxDOC22/developing-and-deploying-a-geronimo-gbean.html

Any comment  is appreciated.


Best  Wishes,

Sophia


2009/3/5 Juergen Weber 

>
> Hi Sophia,
>
> I'd suggest you also write (the for me formerly non-obvious points ;-):
>
> - a gbean consists of classes in a jar + plan
> - you deploy both
> - infoFactory.addAttribute("port"  relates to 
> - infoFactory.addOperation names the user methods you can call
> - how do you call an operation?
>  ->
>
> http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410
> - how do you put a GBean into JNDI
>  ->
>
> http://www.nabble.com/How-do-you-access-a-GBean-via-JNDI--td21621410s134.html#a21621410
>
> Thanks,
> Juergen
>
>
>
> Sophia Tang wrote:
> >
> > Thanks Radim for your suggestion.
> >
> > A  topic named "Developing and Deploying a Geronimo
> > GBea<
> http://cwiki.apache.org/confluence/display/GMOxDOC22/Developing+and+Deploying+a+Geronimo+GBean
> >n
> > " has been added to the
> > reference >section
> > in Geronimo 2.2 documentation wiki:
> >
> >
> http://cwiki.apache.org/confluence/display/GMOxDOC22/Developing+and+Deploying+a+Geronimo+GBean
> >
> >
> >
> > Any of your comments is welcome.
> >
> >
> > Best Regards,
> >
> >
> > Ying Tang
>
>
> --
> View this message in context:
> http://www.nabble.com/new-IBM-book%3A-Using-WASCE-2.1-tp22117057s134p22334640.html
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>

Re: new IBM book: Using WASCE 2.1

Re: your current Geronimo evaluation

Re: your current Geronimo evaluation

Re: new IBM book: Using WASCE 2.1

Re: Geronimo Axis2 update

Re: your current Geronimo evaluation

Re: Geronimo Axis2 update

Re: Newbie problem with Geronimo 2.1.3

Re: your current Geronimo evaluation

Re: Newbie problem with Geronimo 2.1.3

Geronimo Axis2 update

Re: Custom Login Module HttpServletRequest access for webservice

Re: your current Geronimo evaluation

Re: Custom Login Module HttpServletRequest access for webservice

Re: your current Geronimo evaluation

Re: Custom Login Module HttpServletRequest access for webservice

Re: new IBM book: Using WASCE 2.1

Re: new IBM book: Using WASCE 2.1

Re: new IBM book: Using WASCE 2.1

Re: new IBM book: Using WASCE 2.1

20 matches

Site Navigation

Mail list logo

Footer information