Re: Custom WSDL file issue

[ERaj]

Keith your solution is superb - I fixed my issue . Many thanks,
Eraj


-- 
View this message in context: 
http://www.nabble.com/Custom-WSDL-file-issue-tp20082908p20104887.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Generated Java Files Are Too Large

[Nan Null]

I didn't mean to break down the WSDL file.  It is not written by me.
My job is just to consume it.  However, the generated code are too big
for Java compiler to take (code is larger than spec allowed).  Is
there a way to break this generated code down?  I know I can do that,
but it would take a lot of manual work.

On Tue, Oct 21, 2008 at 8:38 PM, Eran Chinthaka
<[EMAIL PROTECTED]> wrote:
> I don't think there is a way in Axis2 to break down your WSDL file.
>
> You will have to do it manually, I guess.
>
> On Tue, Oct 21, 2008 at 6:47 PM, Nan Null <[EMAIL PROTECTED]> wrote:
>>
>> Using Wsdl2Java, I have a bunch of Java files that are too large.
>>
>> ExtensionMapper.java: code too large
>> CoreServiceMessageReceiverInOut.java:30212: code too large for try
>> statement
>> CoreServiceMessageReceiverInOut.java:17: code too large
>>
>> The WSDL file is very big.  How do I get Axis to break down the file?
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
>
> --
> With Mettha,
> Eran Chinthaka
>
> 
> Health is the greatest gift; contentment is the greatest wealth; trusting is
> the best relationship; nirvana is the highest joy. - Dhammapada
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Versioning a service deployed on Axis2

[keith chapman]

Hi Barry,

I'd rather do it in this way. Deploy the two versions of the service as two
separate services in Axis2. But would front Axis2 with a mediation engine,
(you could use Apache Synapse or the WSO2
ESB[1] which is built on Apache
Synapse for this purpose). Synapse allows you
to create what is called proxy services. So for this purpose I could create
a proxy service on synapse and give that URL to my customers. Now depending
on some content in the message (either a targetnamespace or a custom SOAP
header or a HTTP Header, choice is yours) you could forward your message to
the correct service. What your essentially doing here is hiding your service
implementation details using synapse. Now your clients have a single URL to
talk to.

BTW synapse is lightweight and high has very good performance hence you need
not worry about a drop in performance in this case.

Thanks,
Keith.

[1] http://wso2.org/projects/esb/java


On Tue, Oct 21, 2008 at 11:27 PM, Barry Alexander <[EMAIL PROTECTED]
> wrote:

> Other than "you're on your own" advice, can you provide some guidelines or
> best practices regarding versioning?
>
>
>
> I thought this was an excellent question and currently of hot discussion
> with my co-workers.
>
>
>
> Some further questions:
>
>
>
> Should message version be embedded as part of SOAP headers using
> WS-Addressing standards?  Or part of the wsdl?
>
> Can end point resolution be used during in-flow phases/handlers to route
> services of various versions end points?
>
> Should versioning be handled as part of a 'mediator'?
>
>
> On Tue, Oct 21, 2008 at 10:12 AM, Deepal jayasinghe <[EMAIL PROTECTED]>wrote:
>
>> Howell, David wrote:
>> >
>> > Hi,
>> >
>> > Is there a recommended or commonly used approach to versioning a
>> > service (SOAP, doc/literal) that is to be deployed on Axis2? I'm
>> > trying to provide some means of not breaking consumers of an existing
>> > service if I have to deploy a new version that isn't backwards
>> > compatible. We're using AXIOM / no data binding for the service
>> > consumers and producers.
>> >
>> Actually we had some discussion on how to do the version support in
>> Axis2 (for service) , but we have not implement that. So only option is
>> to manage service yourself.
>> >
>> > In a lot of cases I think I'll just want to move from deploying
>> > MyService_V1.aar to deploying MyService_V2.aar. V1 can stay deployed
>> > on the Axis2 server until the consumers have all moved on to V2.
>> >
>> > I've been looking at including version information in the target
>> > namespace specified in the WSDL for the service as a mechanism for
>> > consumers to specify which version of the service they want to use.
>> > I'm struggling to understand what my options are for deploying the old
>> > and new versions of my service. Specifically:
>> >
>> > - I don't seem to need to deploy MyService_V1 and MyService_V2 on
>> > different endpoint addresses, but
>> >
>> > - I assume I do have to give them different names in the 
>> > element of the wsdl.
>> >
>> > Is this correct?
>> >
>> > Finally, is there any way of using a single endpoint and service name
>> > that accepts requests from consumers that may have different XML
>> > namespaces depending on the version of the service they are using?
>> >
>> > Thanks,
>> >
>> > Dave
>> >
>>
>>
>> --
>> Thank you!
>>
>>
>> http://blogs.deepal.org
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

[ANN] VTD-XML extended edition released

[jimmy Zhang]

The Java version of extended VTD-XmL is released and available for download. 
This version supports 256 GB max file sizes and memory mapped capabilities. 
The updated documentation is also available for download. In short, you can 
basically do full XPath query on documents that are bigger than memory space 
available on your machine. 

A special thanks to Duane May who provided value suggestions and inputs and 
helped refine the VTD specs to make this happen.

To download the package and the documentation, go to
https://sourceforge.net/project/downloading.php?group_id=110612&use_mirror=&filename=vtd-xml_2.4_doc.zip&64621261

https://sourceforge.net/project/downloading.php?group_id=110612&use_mirror=&filename=ximpleware_extended_2.4.zip&99532507

Hot update concerns

[Chen, Jennifer]

Hi, why is it not advisable to use hot update in a real-time system?
What are the concerns? I found the following paragraph online.

Thank you!

Jennifer

"Hot update is the ability to make changes to an existing Web service
without shutting down the system. This is an important feature and
required in a testing environment. However, it's not advisable to use
hot update in a real-time system, because it could result in the system
leading into an unknown state. Additionally, there's the possibility of
loosening the existing service data of that service. To prevent this,
Axis2 comes with the hot update parameter set to FALSE by default. If
you want to have this feature, you can do this by changing the
configuration parameter like this: true"

Re: Generated Java Files Are Too Large

[Eran Chinthaka]

I don't think there is a way in Axis2 to break down your WSDL file.

You will have to do it manually, I guess.

On Tue, Oct 21, 2008 at 6:47 PM, Nan Null <[EMAIL PROTECTED]> wrote:

> Using Wsdl2Java, I have a bunch of Java files that are too large.
>
> ExtensionMapper.java: code too large
> CoreServiceMessageReceiverInOut.java:30212: code too large for try
> statement
> CoreServiceMessageReceiverInOut.java:17: code too large
>
> The WSDL file is very big.  How do I get Axis to break down the file?
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
With Mettha,
Eran Chinthaka


Health is the greatest gift; contentment is the greatest wealth; trusting is
the best relationship; nirvana is the highest joy. - Dhammapada

RE: Versioning a service deployed on Axis2

[Kraus, David]

Wouldn't it be possible to create a new schema namespace for the next
version of a webservice, and then manage the changes internally in one
web service?

So your first version of the web service might have a schema namespace
of:

http://xxx.com/webservices/V1";>

.

The process of creating the next version would involve creating new
versions of each datatype which changes, or API call (if parameter list
changes), and defining these new types, APIs, in a new namespace in the
same WSDL file.

http://xxx.com/webservices/V2";>

So, the V1 schema of your service might define XXXType, and the V2
schema would define an XXXType2 type to represent XXXType with changes.
Your web service would need to handle both.

Obviously, this could get messy over time, but guidelines that manage
the deprecation and removal of support for past versions could be used
to handle that.

-Original Message-
From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 4:42 PM
To: axis-user@ws.apache.org
Subject: Re: Versioning a service deployed on Axis2

Barry Alexander wrote:
>
> Other than "you're on your own" advice, can you provide some
> guidelines or best practices regarding versioning?
>
The only way to get the service version support in Axis2 is to deploy
two different services. And then use their service addresses to
differentiate the two services. If we use this way then the service
version will be automatically visible to outside as well. So for example
if you want to have two version of "foo" service , then you need to have
two different aar files in the repository , called (eg.) foo-1.aar and
foo-2.aar, in addition to that remember the service name of the two
services.xml file should also be different. In other word those will be
two different services in Axis2.

If you want to have the client transparent version support then one
solution could be  to write a handler which does the version based
dispatching. Meaning when a client send a request it will send the
request to the latest service.

-Deepal
>
>  
>
> I thought this was an excellent question and currently of hot
> discussion with my co-workers.
>
>  
>
> Some further questions:
>
>  
>
> Should message version be embedded as part of SOAP headers using
> WS-Addressing standards?  Or part of the wsdl?
>
> Can end point resolution be used during in-flow phases/handlers to
> route services of various versions end points?
>
> Should versioning be handled as part of a 'mediator'?
>
>
>
> On Tue, Oct 21, 2008 at 10:12 AM, Deepal jayasinghe <[EMAIL PROTECTED]
> > wrote:
>
> Howell, David wrote:
> >
> > Hi,
> >
> > Is there a recommended or commonly used approach to versioning a
> > service (SOAP, doc/literal) that is to be deployed on Axis2? I'm
> > trying to provide some means of not breaking consumers of an
> existing
> > service if I have to deploy a new version that isn't backwards
> > compatible. We're using AXIOM / no data binding for the service
> > consumers and producers.
> >
> Actually we had some discussion on how to do the version support
in
> Axis2 (for service) , but we have not implement that. So only
> option is
> to manage service yourself.
> >
> > In a lot of cases I think I'll just want to move from deploying
> > MyService_V1.aar to deploying MyService_V2.aar. V1 can stay
deployed
> > on the Axis2 server until the consumers have all moved on to V2.
> >
> > I've been looking at including version information in the target
> > namespace specified in the WSDL for the service as a mechanism
for
> > consumers to specify which version of the service they want to
use.
> > I'm struggling to understand what my options are for deploying
> the old
> > and new versions of my service. Specifically:
> >
> > - I don't seem to need to deploy MyService_V1 and MyService_V2
on
> > different endpoint addresses, but
> >
> > - I assume I do have to give them different names in the

> > element of the wsdl.
> >
> > Is this correct?
> >
> > Finally, is there any way of using a single endpoint and service
> name
> > that accepts requests from consumers that may have different XML
> > namespaces depending on the version of the service they are
using?
> >
> > Thanks,
> >
> > Dave
> >
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
>
>
>
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> 
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>
>


-- 
Thank you!


http://blogs.deepal.org


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--

Re: Versioning a service deployed on Axis2

[Deepal jayasinghe]

Barry Alexander wrote:
>
> Other than "you're on your own" advice, can you provide some
> guidelines or best practices regarding versioning?
>
The only way to get the service version support in Axis2 is to deploy
two different services. And then use their service addresses to
differentiate the two services. If we use this way then the service
version will be automatically visible to outside as well. So for example
if you want to have two version of "foo" service , then you need to have
two different aar files in the repository , called (eg.) foo-1.aar and
foo-2.aar, in addition to that remember the service name of the two
services.xml file should also be different. In other word those will be
two different services in Axis2.

If you want to have the client transparent version support then one
solution could be  to write a handler which does the version based
dispatching. Meaning when a client send a request it will send the
request to the latest service.

-Deepal
>
>  
>
> I thought this was an excellent question and currently of hot
> discussion with my co-workers.
>
>  
>
> Some further questions:
>
>  
>
> Should message version be embedded as part of SOAP headers using
> WS-Addressing standards?  Or part of the wsdl?
>
> Can end point resolution be used during in-flow phases/handlers to
> route services of various versions end points?
>
> Should versioning be handled as part of a 'mediator'?
>
>
>
> On Tue, Oct 21, 2008 at 10:12 AM, Deepal jayasinghe <[EMAIL PROTECTED]
> > wrote:
>
> Howell, David wrote:
> >
> > Hi,
> >
> > Is there a recommended or commonly used approach to versioning a
> > service (SOAP, doc/literal) that is to be deployed on Axis2? I'm
> > trying to provide some means of not breaking consumers of an
> existing
> > service if I have to deploy a new version that isn't backwards
> > compatible. We're using AXIOM / no data binding for the service
> > consumers and producers.
> >
> Actually we had some discussion on how to do the version support in
> Axis2 (for service) , but we have not implement that. So only
> option is
> to manage service yourself.
> >
> > In a lot of cases I think I'll just want to move from deploying
> > MyService_V1.aar to deploying MyService_V2.aar. V1 can stay deployed
> > on the Axis2 server until the consumers have all moved on to V2.
> >
> > I've been looking at including version information in the target
> > namespace specified in the WSDL for the service as a mechanism for
> > consumers to specify which version of the service they want to use.
> > I'm struggling to understand what my options are for deploying
> the old
> > and new versions of my service. Specifically:
> >
> > - I don't seem to need to deploy MyService_V1 and MyService_V2 on
> > different endpoint addresses, but
> >
> > - I assume I do have to give them different names in the 
> > element of the wsdl.
> >
> > Is this correct?
> >
> > Finally, is there any way of using a single endpoint and service
> name
> > that accepts requests from consumers that may have different XML
> > namespaces depending on the version of the service they are using?
> >
> > Thanks,
> >
> > Dave
> >
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> 
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>
>


-- 
Thank you!


http://blogs.deepal.org


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Generated Java Files Are Too Large

[Nan Null]

Using Wsdl2Java, I have a bunch of Java files that are too large.

ExtensionMapper.java: code too large
CoreServiceMessageReceiverInOut.java:30212: code too large for try statement
CoreServiceMessageReceiverInOut.java:17: code too large

The WSDL file is very big.  How do I get Axis to break down the file?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Generated client cannot read replies unless "build()" is called on envelope?

[WALTON Jason]

I've got an axis2 1.4 generated client, using ADB databinding.  When I
use the client, every request results in some bizzare ADBException about
"Unexpected subelement ...".
 
Here's the cool part.  If I open up eclipse, and put a break point in
the generated fromOM() method, and then in the debugger look at
"OMElement param"s value, the fault goes away, and everything works
fine.
 
Somehow, calling toString() on the incoming OMElement is changing the
behaviour of my client.  If I modify the generated client and call
"param.build()", then again, it seems to work fine (so long as I don't
get any faults back from the far-end).  What the heck is going on here?
 

Re: Versioning a service deployed on Axis2

[Barry Alexander]

Other than "you're on your own" advice, can you provide some guidelines or
best practices regarding versioning?



I thought this was an excellent question and currently of hot discussion
with my co-workers.



Some further questions:



Should message version be embedded as part of SOAP headers using
WS-Addressing standards?  Or part of the wsdl?

Can end point resolution be used during in-flow phases/handlers to route
services of various versions end points?

Should versioning be handled as part of a 'mediator'?


On Tue, Oct 21, 2008 at 10:12 AM, Deepal jayasinghe <[EMAIL PROTECTED]>wrote:

> Howell, David wrote:
> >
> > Hi,
> >
> > Is there a recommended or commonly used approach to versioning a
> > service (SOAP, doc/literal) that is to be deployed on Axis2? I'm
> > trying to provide some means of not breaking consumers of an existing
> > service if I have to deploy a new version that isn't backwards
> > compatible. We're using AXIOM / no data binding for the service
> > consumers and producers.
> >
> Actually we had some discussion on how to do the version support in
> Axis2 (for service) , but we have not implement that. So only option is
> to manage service yourself.
> >
> > In a lot of cases I think I'll just want to move from deploying
> > MyService_V1.aar to deploying MyService_V2.aar. V1 can stay deployed
> > on the Axis2 server until the consumers have all moved on to V2.
> >
> > I've been looking at including version information in the target
> > namespace specified in the WSDL for the service as a mechanism for
> > consumers to specify which version of the service they want to use.
> > I'm struggling to understand what my options are for deploying the old
> > and new versions of my service. Specifically:
> >
> > - I don't seem to need to deploy MyService_V1 and MyService_V2 on
> > different endpoint addresses, but
> >
> > - I assume I do have to give them different names in the 
> > element of the wsdl.
> >
> > Is this correct?
> >
> > Finally, is there any way of using a single endpoint and service name
> > that accepts requests from consumers that may have different XML
> > namespaces depending on the version of the service they are using?
> >
> > Thanks,
> >
> > Dave
> >
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: JWS file in AXIS2

[Sanjiva Weerawarana]

Virgilio wrote:

Could you tell me if AXIS2 support JWS extensión file?


No .. we never implemented it as there are now standard annotations for 
doing similar (and more) stuff. See JAX-WS support if you want an 
annotation programming model.


JWS was pretty cool though - and if you really wanted to do it you could 
easily port the code from Axis1 to Axis2.


Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

JWS file in AXIS2

[Virgilio]

Could you tell me if AXIS2 support JWS extensión file?

Re: Versioning a service deployed on Axis2

[Deepal jayasinghe]

Howell, David wrote:
>
> Hi,
>
> Is there a recommended or commonly used approach to versioning a
> service (SOAP, doc/literal) that is to be deployed on Axis2? I’m
> trying to provide some means of not breaking consumers of an existing
> service if I have to deploy a new version that isn’t backwards
> compatible. We’re using AXIOM / no data binding for the service
> consumers and producers.
>
Actually we had some discussion on how to do the version support in
Axis2 (for service) , but we have not implement that. So only option is
to manage service yourself.
>
> In a lot of cases I think I’ll just want to move from deploying
> MyService_V1.aar to deploying MyService_V2.aar. V1 can stay deployed
> on the Axis2 server until the consumers have all moved on to V2.
>
> I’ve been looking at including version information in the target
> namespace specified in the WSDL for the service as a mechanism for
> consumers to specify which version of the service they want to use.
> I’m struggling to understand what my options are for deploying the old
> and new versions of my service. Specifically:
>
> - I don’t seem to need to deploy MyService_V1 and MyService_V2 on
> different endpoint addresses, but
>
> - I assume I do have to give them different names in the 
> element of the wsdl.
>
> Is this correct?
>
> Finally, is there any way of using a single endpoint and service name
> that accepts requests from consumers that may have different XML
> namespaces depending on the version of the service they are using?
>
> Thanks,
>
> Dave
>


-- 
Thank you!


http://blogs.deepal.org


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Versioning a service deployed on Axis2

[Howell, David]

Hi,

 

Is there a recommended or commonly used approach to versioning a service
(SOAP, doc/literal) that is to be deployed on Axis2? I'm trying to
provide some means of not breaking consumers of an existing service if I
have to deploy a new version that isn't backwards compatible. We're
using AXIOM / no data binding for the service consumers and producers.

 

In a lot of cases I think I'll just want to move from deploying
MyService_V1.aar to deploying MyService_V2.aar. V1 can stay deployed on
the Axis2 server until the consumers have all moved on to V2. 

 

I've been looking at including version information in the target
namespace specified in the WSDL for the service as a mechanism for
consumers to specify which version of the service they want to use. I'm
struggling to understand what my options are for deploying the old and
new versions of my service. Specifically:

 

- I don't seem to need to deploy MyService_V1 and MyService_V2 on
different endpoint addresses, but

- I assume I do have to give them different names in the 
element of the wsdl.

 

Is this correct?

 

Finally, is there any way of using a single endpoint and service name
that accepts requests from consumers that may have different XML
namespaces depending on the version of the service they are using?

 

Thanks,

 

Dave

 

Re: [axis2] Huge .java generated by wsdl2java

[Bartolomeo Nicolotti]

I've had to modify the client... Now it takes 2 min to create the client
stub with the instruction:


XmlSelectStub stub = new XmlSelectStub( gwsUrl );

Where xmlSelectStub is the stub generated by axis2

I will try with jixb...

Best regards



Il giorno mar, 21/10/2008 alle 15.02 +0200, Bartolomeo Nicolotti ha
scritto:
> Eureka! 
> 
> With -d jaxbri it only takes one min to compile the 9.5Mb generated file
> (by the way the xsd is 2.5Mb).
> 
> but the option -S JavaSourec doesn't seem to take effect with -d jaxbri,
> i'll use mv to move the files from src/... to JavaSource/...
> 
> Many thanks, best regards!
> 
> B.Nicolotti
> 
> wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxbri -o ../.. 
>  Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
>  Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
> Retrieving document at 'XMLSelect_emea.wsdl'.
> Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'AirAvailability_8.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> 
> 
> Il giorno mar, 21/10/2008 alle 14.20 +0200, Bartolomeo Nicolotti ha
> scritto:
> > tried also jaxme
> > 
> > 
> > wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
> > resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxme -o ../.. 
> >  Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
> >  Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
> > Retrieving document at 'XMLSelect_emea.wsdl'.
> > Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'AirAvailability_8.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Exception in thread "main"
> > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > org.apache.axis2.wsdl.codegen.CodeGenerationException: No proper
> > databinding has taken place
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> > Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: No
> > proper databinding has taken place
> > at
> > org.apache.axis2.wsdl.codegen.extension.DefaultDatabindingExtension.engage(DefaultDatabindingExtension.java:41)
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> > ... 2 more
> > 
> > 
> > 
> > Il giorno mar, 21/10/2008 alle 14.05 +0200, Bartolomeo Nicolotti ha
> > scritto:
> > > Tried:
> > > 
> > > wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
> > > resources/XMLSelectClient -s -sd -u -ssi -sp -or -o ../.. 
> > >  Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
> > >  Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
> > > Retrieving document at 'XMLSelect_emea.wsdl'.
> > > Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> > > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > > Retrieving schema at 'AirAvailability_8.xsd', relative to
> > > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > > Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> > > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > > Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> > > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > > Exception in thread "main"
> > > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> > > at
> > > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> > > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> > > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> > > Ca

Re: Different address location in WSDL generated by Axis2

[keith chapman]

Hi,

Since Axis2 1.4 we have the concept of dispatching request to the endpoints
not just to the service. The reason is that security scenarios could be
configured on a endpoint level and hence we need to know the exact endpoint
a request is headed to in order to apply the security scenario accordingly.

This is the reason you see the unique addresses for each endpoint and it
takes the form serviceName.endpointName.

Thanks,
Keith.

On Tue, Oct 21, 2008 at 7:44 PM, Chinmoy Chakraborty <[EMAIL PROTECTED]>wrote:

> Hi All,
>
> Following is my service portion of the WSDL of service ABS generated by
> Axis2 1.4.
> 
> <
> wsdl:service name="ABS"> 
> http://192.168.1.54:8080/services/ABS.ABSHttpSoap11Endpoint"/>
> 
> 
> http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint"/>
> 
>  
>
> Can anyone tell me why the location is like "
> http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint";. It should be
> http://192.168.1.54:8080/services/ABS only.
>
> Is there anything through which I can configure this behavior?
>
> Chinmoy
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Different address location in WSDL generated by Axis2

[Chinmoy Chakraborty]

 Hi All,

Following is my service portion of the WSDL of service ABS generated by
Axis2 1.4.



http://192.168.1.54:8080/services/ABS.ABSHttpSoap11Endpoint"/>


http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint"/>

 

Can anyone tell me why the location is like "
http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint";. It should be
http://192.168.1.54:8080/services/ABS only.

Is there anything through which I can configure this behavior?

Chinmoy

Re: Configuring Axis2 client to use Rampart

[Bai Shen]

On Fri, Oct 17, 2008 at 4:03 PM, Bai Shen <[EMAIL PROTECTED]> wrote:

> I set up my server with Rampart.  So when I send a message from my Axis2
> client, it gets rejected because there's no security header.  So now I need
> to configure my client to use Rampart. I got the service client and told it
> to engage rampart, but I keep getting back the error that it can't engage
> Rampart.  I've copied over all of the jars from the Rampart lib dir, but
> that didn't see to help.  So I'm at a loss atm on how to configure my client
> to use Rampart.   Any help would be appreciated. TIA.
>

I finally got it working by referencing an axis2.xml file.  However, I was
trying to get it to work without using an axis2.xml file.  I'd like to do
everything in the code.  AFAIK, this is possible, but I wasn't able to get
it to work.

Re: Axis2.1.4 MTOM w/ XmlBeans

[Thilina Gunarathne]

Hi,

>
> I see that Axis2.1.1 had documentation that supported MTOM with XmlBeans (
> http://ws.apache.org/axis2/1_1/mtom-guide.html#252).  Axis 2.1.4 no
> longers has this documentation.  Is MTOM supported with 2.1.4 and XmlBeans?
>  I am curious since it seems that schema containing binary data works with
> XmlBeans as expected.  The only difference is that the byte array is made
> available and not a data handler.

It was broken and nobody was able/interested in fixing it. Also I cannot
recall the exact error, may be you can find it in the JIRA.
To be honest I'm not a big fan of using XMLBeans for MTOM mainly due to the
following inefficiency in XMLBeans when it comes to binary data handling..
XMLBeans does not support binary, but Axiom supports. So when using XMLBeans
the binary data gets converted to base64 encoded string inside XMLBeans and
then back to binary when writing the message.


> ADB seems to have a "file caching" mechanism described here (
> http://ws.apache.org/axis2/1_3/mtom-guide.html#41).  Is this specific to
> ADB?  Or can this mechanism somehow be applied to XmlBeans?  I'd like to not
> have the entire document loaded into memory and would like to stream to to
> disk if over a certain size using XmlBeans as the data binding library.

File caching is generic to Axis2.. It does not depend on the data binding as
it happens in a much deeper layer.  But I feel that even when file caching
is there, XMLBeans might try to load the content of the attachment in to the
memory.

thanks,
Thilina

>
>
> Thanks,
>
> Alejandro
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Thilina Gunarathne  - http://thilinag.blogspot.com

Re: [axis2] Huge .java generated by wsdl2java

[Bartolomeo Nicolotti]

Eureka! 

With -d jaxbri it only takes one min to compile the 9.5Mb generated file
(by the way the xsd is 2.5Mb).

but the option -S JavaSourec doesn't seem to take effect with -d jaxbri,
i'll use mv to move the files from src/... to JavaSource/...

Many thanks, best regards!

B.Nicolotti

wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxbri -o ../.. 
 Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
 Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
Retrieving document at 'XMLSelect_emea.wsdl'.
Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'AirAvailability_8.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'PNRBFManagement_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.


Il giorno mar, 21/10/2008 alle 14.20 +0200, Bartolomeo Nicolotti ha
scritto:
> tried also jaxme
> 
> 
> wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxme -o ../.. 
>  Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
>  Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
> Retrieving document at 'XMLSelect_emea.wsdl'.
> Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'AirAvailability_8.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException:
> org.apache.axis2.wsdl.codegen.CodeGenerationException: No proper
> databinding has taken place
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: No
> proper databinding has taken place
> at
> org.apache.axis2.wsdl.codegen.extension.DefaultDatabindingExtension.engage(DefaultDatabindingExtension.java:41)
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> ... 2 more
> 
> 
> 
> Il giorno mar, 21/10/2008 alle 14.05 +0200, Bartolomeo Nicolotti ha
> scritto:
> > Tried:
> > 
> > wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
> > resources/XMLSelectClient -s -sd -u -ssi -sp -or -o ../.. 
> >  Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
> >  Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
> > Retrieving document at 'XMLSelect_emea.wsdl'.
> > Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'AirAvailability_8.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Exception in thread "main"
> > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> > Caused by: java.lang.RuntimeException:
> > java.lang.reflect.InvocationTargetException
> > at
> > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> > ... 2 more
> > Caused by: java.lang.reflect.InvocationTargetException
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.Native

Axis2 Timeout Configuration | Urgent

[Appasamy Thirugnana]

Hi all,

I have written a WSclient using Axis2 and I forgot to set timeout using

stub._getServiceClient().getOptions().setTimeOutInMilliSeconds

Now I want timeout to be configured.
If I change the following property in axis2.xml will the client class pick that 
one or Axis2.xml is only for server side?

 some_int_value

or

3

Also tell which one to use.

Appasamy T

Re: How to validate out going SOAP with Axis2?

[keith chapman]

There is no such API method. Are you using Service Client or using a
generated stub (as your client)? If you are using a stub the stub might so
this validation for you.

Thanks,
Keith.

On Tue, Oct 21, 2008 at 7:51 AM, Shao, Zhiren
<[EMAIL PROTECTED]>wrote:

>  Hi Martin,
>
> Thanks for your response. It's a good idea to make a client side validator.
> However, do you know if there's any supporting API from axis2? How to
> validate a SOAP message in AXIS2?
>
>
>
> Regards,
>
> Ren
>  --
>
> *From:* Martin Gainty [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, 21 October 2008 11:52 AM
> *To:* axis-user@ws.apache.org
> *Subject:* RE: How to validate out going SOAP with Axis2?
>
>
>
> the easiest answer would be to construct a validator on the client-side
> so lets say you have a JS validator function in your browser such as
> 
> 
> 
> var submitcount=0;
> function submitForm(var Name_Type)
> {
>   if (Name_Type.length() > 40)
>   {
> alert("String must be < = 40 characters");
> document.login_form.Name_Type.focus();
> return true;
>   }
> //normal functionality..will post to the webservice populated in url
>   document.login_form.action=url;
>   document.login_form.submit();
> }
> 
> 
>
> majority of validator functions such as Business Logic, DB and or any
> resource-based validators would be located on WS
> does this help?
> Martin
> __
> Disclaimer and confidentiality note
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>
>  --
>
> Subject: How to validate out going SOAP with Axis2?
> Date: Tue, 21 Oct 2008 11:03:54 +1100
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
>
> Hi,
>
> I'm using Axis2 to consume web service from another company. In WSDL I have
> a type which should be no more than 40 characters, here's the definition:
>
> 
>
> 
>
> 
>
> 
>
> 
>
>
>
> However, Axis2 allow me to construct a SOAP with morn than 40 chars and
> send out. Is there a way to configure Axis2 so it validates the soap before
> sending out?
>
>
>
> Thanks a lot.
>
> Ren
>
>
>
>
>
>
> This e-mail message (including any attachments) is private, intended solely 
> for the recipient(s) or entity to whom it
>
> is addressed and may contain material which is confidential and privileged.  
> No one other than the named recipient(s)
>
> may read, copy, rely on, redirect, save or alter any part of this message or 
> attachment(s) in any way. The views,
>
> opinions and information expressed in this message represent those of the 
> individual sender and do not reflect the
>
> views of the Travelex Group. Please take notice that the employees and/or 
> agents of the Travelex Group are not
>
> authorized to make corporate commitments or representations via e-mail and no 
> statement or representation made in this
>
> e-mail is binding upon the Travelex Group.  While reasonable effort has been 
> made to ensure this message (including any
>
> attachments) is free of viruses, opening and using this message (including 
> any attachments) is at the risk of the
>
> recipient(s). The Travelex Group consists of Travelex Limited, Ruesch 
> International, Inc. and any subsidiaries,
>
> affiliates or related entities.  Travelex can be found on the World Wide Web 
> at
> www.travelex.com.  Ruesch can be found
> on the World Wide Web at www.ruesch.com.
>
>
>  --
>
> Store, manage and share up to 5GB with Windows Live SkyDrive. Start
> uploading 
> now
>
>
>
>
>
> This e-mail message (including any attachments) is private, intended solely 
> for the recipient(s) or entity to whom it
>
> is addressed and may contain material which is confidential and privileged.  
> No one other than the named recipient(s)
>
> may read, copy, rely on, redirect, save or alter any part of this message or 
> attachment(s) in any way. The views,
>
> opinions and information expressed in this message represent those of the 
> individual sender and do not reflect the
>
> views of the Travelex Group. Please take notice that the employees and/or 
> agents of the Travelex Group are not
>
> authorized to make corporate commitments or representations via e-mail and no 
> statement or representation made in this
>
> e-mail is binding upon the Travelex Group.  While reasonable effort has been 
> made to ensure this message (including any
>
> attachments) is free of viruses, opening and using this message (including 
> any attachments) is at the risk of the
>
> recipient(s). The Travelex

Re: Custom WSDL file issue

[keith chapman]

I've answered this same question on a WSO2
forumhere [1]

Thanks,
Keith.

[1] http://wso2.org/forum/thread/4263#comment-7062

On Tue, Oct 21, 2008 at 9:20 AM, ERaj <[EMAIL PROTECTED]> wrote:

>
> I have added this too still the same issue - can anybody help here?
> import java.io.Serializable;
> public class Person implements Serializable{
> .
>
> --
> View this message in context:
> http://www.nabble.com/Custom-WSDL-file-issue-tp20082908p20083001.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: [axis2] Huge .java generated by wsdl2java

[Bartolomeo Nicolotti]

tried also jaxme


wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxme -o ../.. 
 Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
 Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
Retrieving document at 'XMLSelect_emea.wsdl'.
Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'AirAvailability_8.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'PNRBFManagement_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException: No proper
databinding has taken place
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: No
proper databinding has taken place
at
org.apache.axis2.wsdl.codegen.extension.DefaultDatabindingExtension.engage(DefaultDatabindingExtension.java:41)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
... 2 more



Il giorno mar, 21/10/2008 alle 14.05 +0200, Bartolomeo Nicolotti ha
scritto:
> Tried:
> 
> wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -o ../.. 
>  Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
>  Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
> Retrieving document at 'XMLSelect_emea.wsdl'.
> Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'AirAvailability_8.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException:
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> ... 2 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50)
> ... 3 more
> Caused by: org.apache.axis2.schema.SchemaCompilationException:
> java.lang.NullPointerException
> at
> org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:289)
> at
> org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:103)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.axis2.schema.SchemaCompiler.isComponetExists(SchemaCompiler.java:2723)
> at
> org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2670)
> at
> org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2704)
> at
> org.apache.axis2.schema.SchemaCompiler.getParentSchema(SchemaCompiler.java:2644)
> at
> org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:925)
> at
> org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> at
> org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
> at
> org.apache.axis2.s

Re: [axis2] Huge .java generated by wsdl2java

[Bartolomeo Nicolotti]

Tried:

wsdl2java.sh  -uri XMLSelect_emea.wsdl -S JavaSource -R
resources/XMLSelectClient -s -sd -u -ssi -sp -or -o ../.. 
 Using AXIS2_HOME:   /home/user/software/axis2-1.4.1
 Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun/
Retrieving document at 'XMLSelect_emea.wsdl'.
Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'AirAvailability_8.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'PNRBFManagement_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50)
... 3 more
Caused by: org.apache.axis2.schema.SchemaCompilationException:
java.lang.NullPointerException
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:289)
at
org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:103)
... 8 more
Caused by: java.lang.NullPointerException
at
org.apache.axis2.schema.SchemaCompiler.isComponetExists(SchemaCompiler.java:2723)
at
org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2670)
at
org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2704)
at
org.apache.axis2.schema.SchemaCompiler.getParentSchema(SchemaCompiler.java:2644)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:925)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
at
org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
at
org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:563)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:370)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:280)
... 9 more



Il giorno mar, 21/10/2008 alle 16.49 +0530, keith chapman ha scritto:
> As an alternative to xmlbeans (which actually generates quite a lot of
> code) did you try using adb?
> 
> Thanks,
> Keith.
> 
> On Tue, Oct 21, 2008 at 4:37 PM, Bartolomeo Nicolotti
> <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I've tried the -u option, with the command:
> 
> wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSou

Re: [axis2] Huge .java generated by wsdl2java

[keith chapman]

As an alternative to xmlbeans (which actually generates quite a lot of code)
did you try using adb?

Thanks,
Keith.

On Tue, Oct 21, 2008 at 4:37 PM, Bartolomeo Nicolotti
<[EMAIL PROTECTED]>wrote:

>  Hi,
>
> I've tried the -u option, with the command:
>
> wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -d xmlbeans -o ../..
>
> but the result is the same, .java 12Mb and Impl.java 34Mb, I think because
> in the xsd there's only one named complexType.
>
> Many thanks, best regards,
>
> B.Nicolotti
>
> Il giorno mar, 21/10/2008 alle 12.31 +0200, Bartolomeo Nicolotti ha
> scritto:
>
>  No, I don't use -u option, the command is:
>
> wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient -s -sd -ssi
> -sp -d xmlbeans -o .. -ns2p [... namespace mappings]
> the xsd has the form
>
>
>   http://webservices.galileo.com";
>   xmlns:xs="http://www.w3.org/2001/XMLSchema";
>   elementFormDefault="qualified" version="1.0" id="SG2008A">
>
> 
>   
> 
>
> 
>   
>   
> 
>
> (   maxOccurs="unbounded" >
> 
>   
>
>   
> 
> 
>   
>  type="xs:int"  >
>   
> 
>Determines insertion point for next segment
> 
>   
> 
>   
> 
>  ) repeated for many elments and also nested
>
> 
>   
>   
>
>
>
> Many thanks, Best Regards,
>
> B.Nicolotti
>
> Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha scritto:
>
> Did you use the -u option when generating code? If not try using it this
> will unpack the code and create a java class for each datatype used.
>
> Thanks,
> Keith.
>
> On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti <
> [EMAIL PROTECTED]> wrote:
>
> Hi
>
> I'm using axis2 to consume document/literal web services, but one xsd
> for Galileo travel supplier is is 64227 lines long and the .java
> generated by wsdl2java is 12Mb and the corresponding Impl.java is also
> 34Mb long. The preblem is that when I must compile these .java it takes
> 10minutes. Does someone know why and how to make this task faster?
>
> Many thanks, Best Regards.
>
> Bartolomeo Nicolotti.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>   --
> Bartolomeo Nicolotti
> SIAP s.r.l.www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519
>
> --
> Bartolomeo Nicolotti
> SIAP s.r.l.www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: [axis2] Huge .java generated by wsdl2java

[Bartolomeo Nicolotti]

Hi,

I've tried the -u option, with the command:

wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
resources/XMLSelectClient -s -sd -u -ssi -sp -or -d xmlbeans -o ../..

but the result is the same, .java 12Mb and Impl.java 34Mb, I think
because in the xsd there's only one named complexType.

Many thanks, best regards,

B.Nicolotti

Il giorno mar, 21/10/2008 alle 12.31 +0200, Bartolomeo Nicolotti ha
scritto:

> No, I don't use -u option, the command is:
> 
> wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient -s -sd
> -ssi -sp -d xmlbeans -o .. -ns2p [... namespace mappings]
> the xsd has the form
> 
> 
>   http://webservices.galileo.com";
>   xmlns:xs="http://www.w3.org/2001/XMLSchema";
>   elementFormDefault="qualified" version="1.0"
> id="SG2008A"> 
> 
> 
>   
> 
>   
> 
>   
>   
> 
> 
> (   maxOccurs="unbounded" >
> 
>   
> 
>   
> 
> 
>   
>  type="xs:int"  >
>   
> 
>Determines insertion point for next segment 
> 
>   
> 
>   
> 
>  ) repeated for many elments and also nested
> 
> 
>   
>   
> 
> 
> 
> Many thanks, Best Regards,
> 
> B.Nicolotti
> 
> Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha scritto: 
> 
> > Did you use the -u option when generating code? If not try using it
> > this will unpack the code and create a java class for each datatype
> > used.
> > 
> > Thanks,
> > Keith.
> > 
> > On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
> > <[EMAIL PROTECTED]> wrote:
> > 
> > Hi
> > 
> > I'm using axis2 to consume document/literal web services,
> > but one xsd
> > for Galileo travel supplier is is 64227 lines long and
> > the .java
> > generated by wsdl2java is 12Mb and the corresponding
> > Impl.java is also
> > 34Mb long. The preblem is that when I must compile
> > these .java it takes
> > 10minutes. Does someone know why and how to make this task
> > faster?
> > 
> > Many thanks, Best Regards.
> > 
> > Bartolomeo Nicolotti.
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> > 
> > 
> > 
> > 
> > 
> > -- 
> > Keith Chapman
> > Senior Software Engineer
> > WSO2 Inc.
> > Oxygenating the Web Service Platform.
> > http://wso2.org/
> > 
> > blog: http://www.keith-chapman.org
> > 
> 
> -- 
> Bartolomeo Nicolotti
> SIAP s.r.l.
> www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519

-- 
Bartolomeo Nicolotti
SIAP s.r.l.
www.siapcn.it
v.S.Albano 13 12049
Trinità(CN) Italy
ph:+39 0172 652553
centralino: +39 0172 652511
fax: +39 0172 652519

Re: Clustering and passive replication

[Igor Nogueira]

Thanks Afkham!

2008/10/21 Afkham Azeez <[EMAIL PROTECTED]>

> Hi Igor,
> At the moment, a member can only be started in the ACTIVE state. I started
> work last week on making it possible to configure a member to be ACTIVE or
> PASSIVE in the cluster configuration section. Part of this work is already
> available in the trunk. When an active member fails, the coordinator will
> activate one of the passive members. Also, the passive member will not start
> any transport listeners, hence will not be able to do anything useful until
> it is activated. Hopefully, this feature will be available in the next Axis2
> release.
>
> Also like Paul said, you can use a Linux HA setup to achieve the same.
>
> Thanks
> Azeez
>
>
> On Tue, Oct 21, 2008 at 4:21 AM, Igor Nogueira <
> [EMAIL PROTECTED]> wrote:
>
>> Thanks Paul! So, with clustering I can only use active replication,  ins't
>> it?
>>
>> Best regards,
>>
>> Igor Nogueira
>>
>> 2008/10/20 Paul Fremantle <[EMAIL PROTECTED]>
>>
>> Igor
>>>
>>> Typically you would do this without Axis2 being aware of it - e.g.
>>> either using a Linux IP renegotiation system or Linux HA, or by
>>> setting up your IP sprayer (or mod_proxy) that way.
>>>
>>> Paul
>>>
>>> On Mon, Oct 20, 2008 at 2:11 AM, Igor Nogueira
>>> <[EMAIL PROTECTED]> wrote:
>>> > Guys is it possible to build a classic passive replication schema with
>>> axis2
>>> > clustering support? I mean, only one of the servers actually answers
>>> the
>>> > client's invocations while the backup replicas "sleep" ?
>>> >
>>> > Thanks in advance,
>>> >
>>> > Igor Nogueira
>>> >
>>>
>>>
>>>
>>> --
>>> Paul Fremantle
>>> Co-Founder and CTO, WSO2
>>> Apache Synapse PMC Chair
>>> OASIS WS-RX TC Co-chair
>>>
>>> blog: http://pzf.fremantle.org
>>> [EMAIL PROTECTED]
>>>
>>> "Oxygenating the Web Service Platform", www.wso2.com
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>
>
> --
> Thanks
> Afkham Azeez
>
> Blog: http://afkham.org
> Developer Portal: http://www.wso2.org
> WSAS Blog: http://wso2wsas.blogspot.com
> Company: http://wso2.com
> GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
>

Re: [axis2] Huge .java generated by wsdl2java

[keith chapman]

Try using -u and see whether it bets any better.

Thanks,
Keith.

On Tue, Oct 21, 2008 at 4:01 PM, Bartolomeo Nicolotti
<[EMAIL PROTECTED]>wrote:

>  No, I don't use -u option, the command is:
>
> wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient -s -sd -ssi
> -sp -d xmlbeans -o .. -ns2p [... namespace mappings]
>
> the xsd has the form
>
>
>   http://webservices.galileo.com";
>   xmlns:xs="http://www.w3.org/2001/XMLSchema";
>   elementFormDefault="qualified" version="1.0" id="SG2008A">
>
> 
>   
> 
>
> 
>   
>   
> 
>
> (   maxOccurs="unbounded" >
> 
>   
>
>   
> 
> 
>   
>  type="xs:int"  >
>   
> 
>Determines insertion point for next segment
> 
>   
> 
>   
> 
>  ) repeated for many elments and also nested
>
> 
>   
>   
>
>
>
> Many thanks, Best Regards,
>
> B.Nicolotti
>
> Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha scritto:
>
> Did you use the -u option when generating code? If not try using it this
> will unpack the code and create a java class for each datatype used.
>
> Thanks,
> Keith.
>
>  On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti <
> [EMAIL PROTECTED]> wrote:
>
> Hi
>
> I'm using axis2 to consume document/literal web services, but one xsd
> for Galileo travel supplier is is 64227 lines long and the .java
> generated by wsdl2java is 12Mb and the corresponding Impl.java is also
> 34Mb long. The preblem is that when I must compile these .java it takes
> 10minutes. Does someone know why and how to make this task faster?
>
> Many thanks, Best Regards.
>
> Bartolomeo Nicolotti.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>   --
> Bartolomeo Nicolotti
> SIAP s.r.l.www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: [axis2] Huge .java generated by wsdl2java

[Bartolomeo Nicolotti]

No, I don't use -u option, the command is:

wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient -s -sd -ssi
-sp -d xmlbeans -o .. -ns2p [... namespace mappings]

the xsd has the form


  http://webservices.galileo.com";
  xmlns:xs="http://www.w3.org/2001/XMLSchema";
  elementFormDefault="qualified" version="1.0"
id="SG2008A"> 


  

  

  
  


(  

  

  


  

  

   Determines insertion point for next segment 

  

  

 ) repeated for many elments and also nested


  
  



Many thanks, Best Regards,

B.Nicolotti

Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha scritto:
> Did you use the -u option when generating code? If not try using it
> this will unpack the code and create a java class for each datatype
> used.
> 
> Thanks,
> Keith.
> 
> 
> On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
> <[EMAIL PROTECTED]> wrote:
> 
> Hi
> 
> I'm using axis2 to consume document/literal web services, but
> one xsd
> for Galileo travel supplier is is 64227 lines long and
> the .java
> generated by wsdl2java is 12Mb and the corresponding Impl.java
> is also
> 34Mb long. The preblem is that when I must compile these .java
> it takes
> 10minutes. Does someone know why and how to make this task
> faster?
> 
> Many thanks, Best Regards.
> 
> Bartolomeo Nicolotti.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> -- 
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
> 
> blog: http://www.keith-chapman.org
> 

-- 
Bartolomeo Nicolotti
SIAP s.r.l.
www.siapcn.it
v.S.Albano 13 12049
Trinità(CN) Italy
ph:+39 0172 652553
centralino: +39 0172 652511
fax: +39 0172 652519

Re: [axis2] Huge .java generated by wsdl2java

[keith chapman]

Did you use the -u option when generating code? If not try using it this
will unpack the code and create a java class for each datatype used.

Thanks,
Keith.

On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
<[EMAIL PROTECTED]>wrote:

> Hi
>
> I'm using axis2 to consume document/literal web services, but one xsd
> for Galileo travel supplier is is 64227 lines long and the .java
> generated by wsdl2java is 12Mb and the corresponding Impl.java is also
> 34Mb long. The preblem is that when I must compile these .java it takes
> 10minutes. Does someone know why and how to make this task faster?
>
> Many thanks, Best Regards.
>
> Bartolomeo Nicolotti.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

[axis2] Huge .java generated by wsdl2java

[Bartolomeo Nicolotti]

Hi

I'm using axis2 to consume document/literal web services, but one xsd
for Galileo travel supplier is is 64227 lines long and the .java
generated by wsdl2java is 12Mb and the corresponding Impl.java is also
34Mb long. The preblem is that when I must compile these .java it takes
10minutes. Does someone know why and how to make this task faster?

Many thanks, Best Regards.

Bartolomeo Nicolotti.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Clustering and passive replication

[Afkham Azeez]

Hi Igor,
At the moment, a member can only be started in the ACTIVE state. I started
work last week on making it possible to configure a member to be ACTIVE or
PASSIVE in the cluster configuration section. Part of this work is already
available in the trunk. When an active member fails, the coordinator will
activate one of the passive members. Also, the passive member will not start
any transport listeners, hence will not be able to do anything useful until
it is activated. Hopefully, this feature will be available in the next Axis2
release.

Also like Paul said, you can use a Linux HA setup to achieve the same.

Thanks
Azeez

On Tue, Oct 21, 2008 at 4:21 AM, Igor Nogueira <[EMAIL PROTECTED]
> wrote:

> Thanks Paul! So, with clustering I can only use active replication,  ins't
> it?
>
> Best regards,
>
> Igor Nogueira
>
> 2008/10/20 Paul Fremantle <[EMAIL PROTECTED]>
>
> Igor
>>
>> Typically you would do this without Axis2 being aware of it - e.g.
>> either using a Linux IP renegotiation system or Linux HA, or by
>> setting up your IP sprayer (or mod_proxy) that way.
>>
>> Paul
>>
>> On Mon, Oct 20, 2008 at 2:11 AM, Igor Nogueira
>> <[EMAIL PROTECTED]> wrote:
>> > Guys is it possible to build a classic passive replication schema with
>> axis2
>> > clustering support? I mean, only one of the servers actually answers the
>> > client's invocations while the backup replicas "sleep" ?
>> >
>> > Thanks in advance,
>> >
>> > Igor Nogueira
>> >
>>
>>
>>
>> --
>> Paul Fremantle
>> Co-Founder and CTO, WSO2
>> Apache Synapse PMC Chair
>> OASIS WS-RX TC Co-chair
>>
>> blog: http://pzf.fremantle.org
>> [EMAIL PROTECTED]
>>
>> "Oxygenating the Web Service Platform", www.wso2.com
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>


-- 
Thanks
Afkham Azeez

Blog: http://afkham.org
Developer Portal: http://www.wso2.org
WSAS Blog: http://wso2wsas.blogspot.com
Company: http://wso2.com
GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760