date:20060909

[jira] Commented: (AXIS2-1116) WSDL2Java with Xmlbeans binding is not generating classes for all schema

2006-09-09 Thread Ajith Harshana Ranabahu (JIRA)

[ 
http://issues.apache.org/jira/browse/AXIS2-1116?page=comments#action_12433671 ] 

Ajith Harshana Ranabahu commented on AXIS2-1116:


#2 is fixed and the code checked in. Please test against the latest nightly and 
let us know


> WSDL2Java with Xmlbeans binding is not generating classes for all schema
> 
>
> Key: AXIS2-1116
> URL: http://issues.apache.org/jira/browse/AXIS2-1116
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: databinding
>Affects Versions: 1.0
> Environment: Windows XP, Axis 2.0 nightly build (2006-09-02)
>Reporter: Brennan Spies
>Priority: Blocker
> Attachments: files.zip
>
>
> I have 3 XML Schemas that are used by my service definition in Query.wsdl. I 
> am specifying 'xmlbeans' as the databinding option and doing the code 
> generation with the following ant task (see attached for source):
>output="${basedir}" serverside="true" 
>   generateservicexml="true" 
> packagename="com.ejgallo.workflow.service.query" synconly="true" 
>   
> namespaceToPackages="urn:ejgallo:workflow:routing=com.ejgallo.workflow.service.routing,urn:ejgallo:worklfow:service=com.ejgallo.workflow.service,urn:ejgallo:workflow:service:query=com.ejgallo.workflow.service.query"
>   databindingName="xmlbeans" 
> serviceName="QueryWebService" generateAllClasses="true" 
> serverSideInterface="true"
>   testcase="true" unpackclasses="true"/>
> There are 3 problems here:
> 1)  Only one of the schema files, workflowTypes.xsd, has XMLBeans source 
> files generated for it, though the console output indicates that all 3 are 
> found/referenced. (No problem when Xmlbeans' ant task is used instead).
> 2) Under the /resources directory, the referenced schema files are generated 
> as 'xsd0.xsd', 'xsd1.xsd', and 'xsd2.xsd'. Because the original schema file 
> names are referenced in the WSDL and XSD files, this leads to the appropriate 
> files not being found when it is deployed as an .aar.
> 3) The 'namespaceToPackages' attribute on the ant task is not being honored, 
> leading the source files for the generated Xmlbeans classes to be the default 
> that Axis chooses for them based on the namespace.

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



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

[jira] Commented: (AXIS2-1126) Compile error in the 'Nightly Builds'

2006-09-09 Thread Ajith Harshana Ranabahu (JIRA)

[ 
http://issues.apache.org/jira/browse/AXIS2-1126?page=comments#action_12433667 ] 

Ajith Harshana Ranabahu commented on AXIS2-1126:


Hi,
Please provide more information about your environment (JDK version, Maven 
version etc). Most of the time errors such as this are due to problems in  the 
users configuration. 

> Compile error in the 'Nightly Builds'
> -
>
> Key: AXIS2-1126
> URL: http://issues.apache.org/jira/browse/AXIS2-1126
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Bug
> Environment: Windows XP
>Reporter: Evanthika Amarasiri
> Assigned To: Deepal Jayasinghe
>Priority: Blocker
>
> Downloaded the nightly builds from the axis2 site and got a compilation error 
> while building them.
> I have attached part of the error log below
> +
> | Gathering project list Apache Axis 2.0 - XMLBeans Data Binding
> | Memory: 6M/7M
> +
> Starting the reactor...
> Our processing order:
> Apache Axis 2.0 - Data Binding
> Apache Axis 2.0 - Addressing
> Apache Axis 2.0 - Java2WSDL
> Apache Axis 2.0 - Code Generation
> Apache Axis 2.0 - JAXB-RI Data Binding
> Apache Axis 2.0 - JiBX Data Binding
> Apache Axis 2.0 - Samples
> Apache Axis 2.0 - Tools
> Apache Axis 2.0 - XMLBeans Data Binding
> +
> | Executing multiproject:install-callback Apache Axis 2.0 - Data Binding
> | Memory: 6M/7M
> +
> Attempting to download axis2-kernel-SNAPSHOT.jar.
> Error retrieving artifact from 
> [http://cvs.apache.org/repository/axis2/jars/axis
> 2-kernel-SNAPSHOT.jar]: java.io.IOException: Unknown error downloading; 
> status c
> ode was: 302
> Error retrieving artifact from 
> [http://www.apache.org/dist/java-repository/axis2
> /jars/axis2-kernel-SNAPSHOT.jar]: java.io.IOException: Unknown error 
> downloading
> ; status code was: 301
> Error retrieving artifact from 
> [http://www.openejb.org/maven/axis2/jars/axis2-ke
> rnel-SNAPSHOT.jar]: java.io.IOException: Unknown error downloading; status 
> code
> was: 302
> warning: last-modified not specified
> 0K downloaded
> warning: last-modified not specified
> Error retrieving artifact from 
> [http://jibx.sourceforge.net/maven/axis2/jars/axi
> s2-kernel-SNAPSHOT.jar]: java.net.ConnectException: Connection timed out: 
> connec
> t
> Attempting to download activation-.jar.
> Error retrieving artifact from 
> [http://cvs.apache.org/repository/javax.activatio
> n/jars/activation-.jar]: java.io.IOException: Unknown error downloading; 
> status
> code was: 302
> Error retrieving artifact from 
> [http://www.apache.org/dist/java-repository/javax
> .activation/jars/activation-.jar]: java.io.IOException: Unknown error 
> downloadin
> g; status code was: 301
> Error retrieving artifact from 
> [http://www.openejb.org/maven/javax.activation/ja
> rs/activation-.jar]: java.io.IOException: Unknown error downloading; status 
> code
>  was: 302
> warning: last-modified not specified
> 0K downloaded
> warning: last-modified not specified
> multiproject:goal:
> build:start:
> multiproject:install-callback:
> [echo] Running jar:install for Apache Axis 2.0 - Data Binding
> java:prepare-filesystem:
> [mkdir] Created dir: C:\WSO2-Projects\Axis2\Nightly 
> builds\axis2-std-SNAPSHO
> T-src\modules\adb\target\classes
> java:compile:
> [echo] Compiling to C:\WSO2-Projects\Axis2\Nightly 
> builds\axis2-std-SNAPSHOT
> -src\modules\adb/target/classes
> [echo]
> ==
>   NOTE: Targetting JVM 1.5, classes
>   will not run on earlier JVMs
> ==
> [javac] Compiling 56 source files to C:\WSO2-Projects\Axis2\Nightly 
> builds\a
> xis2-std-SNAPSHOT-src\modules\adb\target\classes
> [javac] javac: invalid flag: C:\WSO2-Projects\Axis2\Nightly
> [javac] Usage: javac  
> [javac] where possible options include:
> [javac]   -g Generate all debugging info
> [javac]   -g:noneGenerate no debugging info
> [javac]   -g:{lines,vars,source} Generate only some debugging info
> [javac]   -nowarnGenerate no warnings
> [javac]   -verbose   Output messages about what the 
> compiler
>  is doing
> [javac]   -deprecation   Output source locations where 
> deprecate
> d APIs are used
> [javac]   -classpath   Specify where to find user class 
> files
> [javac]   -cp  Specify where to find user class 
> files
> [javac]   -sourcepath  Specify where to find input source 
> file
> s
> [javac]   -bootclasspath   Override location of bootstrap class 
> fi
> les
> [javac]   -extdirs

[jira] Commented: (AXIS2-937) WSDL2Java not generating parameters for stub methods

2006-09-09 Thread Ajith Harshana Ranabahu (JIRA)

[ 
http://issues.apache.org/jira/browse/AXIS2-937?page=comments#action_12433664 ] 

Ajith Harshana Ranabahu commented on AXIS2-937:
---

Hi,
The build problem you mentioned seems to be related to the XMLSchema jar not 
being updated. I guess the code is pretty much changed now so I suggest that 
you take an update and run the code.
One possible error that can happen when the batch file is used is that if your 
system has an AXIS2_HOME environment variable already set pointing to an older 
Axis2 installation, the class will be picked from that and not the new one. So 
it will be better if you can run the java class directly and not through the 
batch file.

> WSDL2Java not generating parameters for stub methods
> 
>
> Key: AXIS2-937
> URL: http://issues.apache.org/jira/browse/AXIS2-937
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: Tools
>Reporter: William Ferguson
> Assigned To: Deepal Jayasinghe
>Priority: Blocker
> Attachments: axis2-937.zip, JasperService.wsdl, JasperServiceStub.java
>
>
> WSDL2Java  from the nightly snapshot of 23-jul-2006 generates the 
> stub/interface, but tyhe methods on the stub don't have  any parameters when 
> they should. The stub is created fine using WSDL2Java from Axis2-1.0
> WSDL2Java params:
>   
>   
>
>
>
>
>
>
>   
>   
> I will attach the WSDL in question

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



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

Re: [Axis2] Build failing

2006-09-09 Thread Bill Nagy

Still doesn't work.  This is all that I have in the repo (for XmlSchema
that is):

~> ls -lah .maven/repository/org.apache.ws.commons/jars
total 144K
drwxrwxr-x 2 nagy nagy 4.0K Sep  8 21:05 ./
drwxrwxr-x 3 nagy nagy 4.0K Jun 19 13:38 ../
-rw-rw-r-- 1 nagy nagy 120K Sep  8 21:05 XmlSchema-SNAPSHOT.jar

-Bill


On Fri, 2006-09-08 at 19:05 -0400, Davanum Srinivas wrote:
> Please cleanup your old Xmlschema jar from your maven repo...
> 
> On 9/8/06, Bill Nagy <[EMAIL PROTECTED]> wrote:
> > I just pulled from Subversion, did a full build (maven clean; maven),
> > and found that some of the codegen tests are failing:
> >
> > Testsuite:
> > org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest
> > Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 0.397 sec
> >
> > Testcase:
> > testScenarioOne(org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest):
> >   Caused an ERROR
> > The prefix xs is not bound.
> > java.lang.IllegalStateException: The prefix xs is not bound.
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.getRefQName(SchemaBuilder.java:515)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.getRefQName(SchemaBuilder.java:496)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleElement(SchemaBuilder.java:1390)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleSequence(SchemaBuilder.java:956)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleComplexType(SchemaBuilder.java:584)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleElement(SchemaBuilder.java:1417)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:143)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:67)
> > at
> > org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:294)
> > at
> > org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:286)
> > at
> > org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest.loadSchema(SchemaUnwrapperExtensionTest.java:161)
> > at
> > org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest.createAndWalkSchema(SchemaUnwrapperExtensionTest.java:147)
> > at
> > org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest.testScenarioOne(SchemaUnwrapperExtensionTest.java:65)
> >
> >
> > Testcase:
> > testScenarioTwo(org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest):
> >   Caused an ERROR
> > The prefix xs is not bound.
> > java.lang.IllegalStateException: The prefix xs is not bound.
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.getRefQName(SchemaBuilder.java:515)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.getRefQName(SchemaBuilder.java:496)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleElement(SchemaBuilder.java:1390)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleSequence(SchemaBuilder.java:956)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleComplexType(SchemaBuilder.java:584)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:138)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:67)
> > at
> > org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:294)
> > at
> > org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:286)
> > at
> > org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest.loadSchema(SchemaUnwrapperExtensionTest.java:161)
> > at
> > org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest.createAndWalkSchema(SchemaUnwrapperExtensionTest.java:147)
> > at
> > org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest.testScenarioTwo(SchemaUnwrapperExtensionTest.java:87)
> >
> >
> > Testcase:
> > testScenarioThree(org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest):
> > Caused an ERROR
> > The prefix ns is not bound.
> > java.lang.IllegalStateException: The prefix ns is not bound.
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.getRefQName(SchemaBuilder.java:515)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.getRefQName(SchemaBuilder.java:496)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleComplexContentExtension(SchemaBuilder.java:875)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleComplexContent(SchemaBuilder.java:713)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleComplexType(SchemaBuilder.java:614)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:138)
> > at
> > org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:67)
> > at
> > org.apac

[jira] Commented: (AXIS2-1130) Build with Maven 2

2006-09-09 Thread Davanum Srinivas (JIRA)

[ 
http://issues.apache.org/jira/browse/AXIS2-1130?page=comments#action_12433615 ] 

Davanum Srinivas commented on AXIS2-1130:
-

jochen,

you have karma for Axis2 as a ws committer. could you please work directly with 
svn? :)

thx,
dims

> Build with Maven 2
> --
>
> Key: AXIS2-1130
> URL: http://issues.apache.org/jira/browse/AXIS2-1130
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Improvement
>Reporter: Jochen Wiedmann
> Assigned To: Jochen Wiedmann
> Attachments: axis2-maven2.patch
>
>
> This is a tracker bug, which serves the following purposes:
> - Keep people informed about the ongoing efforts.
> - Prevent that someone else starts working on the same topic.
> - If possible, attract other people to start working here.
> - Collect dependencies on related bugs like AXIS2-1128

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



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

[jira] Commented: (AXIS2-1128) Layout of axis2/modules/tool

2006-09-09 Thread Davanum Srinivas (JIRA)

[ 
http://issues.apache.org/jira/browse/AXIS2-1128?page=comments#action_12433614 ] 

Davanum Srinivas commented on AXIS2-1128:
-

yep, i will be doing that too.


-- dims

> Layout of axis2/modules/tool
> 
>
> Key: AXIS2-1128
> URL: http://issues.apache.org/jira/browse/AXIS2-1128
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: Tools
>Reporter: Jochen Wiedmann
>
> Hello,
> while working on the Maven 2 build of Axis 2, I detected a problem in the 
> layout of the directory axis2/modules/tool. This directory contains, among 
> others, a directory "src" and several directories with Maven 2 plugins.
> The "src" subdirectory means, that the directory is meant to produce 
> artifacts, for example "axis2-tools.jar". In other words, the "axis2-tool" 
> project should have packaging "jar".
> On the other hand, the presence of maven plugins below means, that the 
> directory is a parent directory. In other words, it should have packaging 
> "pom".
> I see no other possibility to resolve the problem, apart from changing the 
> directory layout. Suggested new layout:
> axis2
> +-- modules
>   +-- tool  (I'd personally consider "tools" a better name.)
> +-- maven2
>  |+-- axis2-aar-maven-plugin
>  |+-- axis2-idea-plugin
>  |+-- axis2-java2wsdl-maven-plugin
>  |+-- axis2-wsdl2code-maven-plugin
>  |+-- pom.xml
>  +-- general
>  | +-- src
>  | +-- conf
>  | +-- script
>  | +-- test
>  | +-- pom.xml
>  | +-- project.xml
>  +-- pom.xml
>  I do personally believe, that the directory "general" should be splitted 
> into more subprojects. However, that could as well be done at a later point.

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



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

[jira] Commented: (AXIS2-747) Missing namespace on subelement

2006-09-09 Thread Ajith Harshana Ranabahu (JIRA)

[ 
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12433599 ] 

Ajith Harshana Ranabahu commented on AXIS2-747:
---

Is this still there - I mean has anyone tried the nightlies ?

>  Missing namespace on subelement
> 
>
> Key: AXIS2-747
> URL: http://issues.apache.org/jira/browse/AXIS2-747
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: om
>Affects Versions: 1.0
> Environment: Windows 2K3, JDK 1.5, AXIS2 1.0 and Eclipse 3.1 with 
> tomcat plugin
>Reporter: Qi An
> Assigned To: Ajith Harshana Ranabahu
>Priority: Blocker
>
> The below all worked fine on 0.95:
> The complex type in question is defined in the wsdl as:
> 
>   
>   
>   
>   
>  
>  
>  
>  
>  
>  
>  
>   
>  
> 
> In the provider's skeleton, we have the following:
> public com.businessobjects.dsws.session.LoginResponseDocument login(
> com.businessobjects.dsws.session.LoginDocument param12)
> throws  
> com.businessobjects.dsws.session.SessionSkeleton.DSWSExceptionException, 
> RemoteException {
>   Login obj = param12.getLogin();
>   Credential cred = obj.getCredential();
> The problem is, on the getCredential() call, we actually get back an 
> object of type Credential (base class) when the method was invoked with 
> an enterprise credential.  So that further on, on the line:
> EnterpriseCredential enterpriseCredential = (EnterpriseCredential) cred;
> We get a class cast exception.
> Tracing through a bit with the SOAPMonitor, we noticed that the xml 
> envelope actually ends up looking like:
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> 
> 
> 
> http://www.w3.org/2001/XMLSchema-instance";
> Password="" Domain="vanyma01" xsi:type="ses:EnterpriseCredential"
> Login="administrator" />
> 
> 
> 
> Where the namespace definition of "ses" is clearly missing.  If you 
> trace through the deserialization code a bit, this is why the object 
> comes back as the base class instead of the extended type.
> Once thing interesting one of our developer's noticed, is that if, on 
> the consumer side, you add the lines:
> XmlOptions op1 = new XmlOptions();
> op1.setSaveNamespacesFirst();
> m_credential =
> EnterpriseCredential.Factory.newInstance(op1);
> At the time you create the credential, it seems that *some of the time* 
> this fixes the problem, so that the xml appears as:
> 
>   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> 
> 
>  
>  http://www.w3.org/2001/XMLSchema-instance";
>  xmlns:ses="session.dsws.businessobjects.com" Password=""
>  Domain="vanyma01" xsi:type="ses:EnterpriseCredential"
>   Login="administrator" />
>  
>  
> 
> But only some of the time.

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



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

[jira] Commented: (AXIS2-1129) Doubled wrapper elements around XMLBeans-generated XML

2006-09-09 Thread Ajith Harshana Ranabahu (JIRA)

[ 
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12433598 ] 

Ajith Harshana Ranabahu commented on AXIS2-1129:


This does seem to be a user error to me. For instance when I generated and 
tried to compile your code this line seems to be in error
final FullDocument full = Full.Factory.newInstance(); 

it should be
final FullDocument full = FullDocument.Factory.newInstance(); 

I would also recommend that you try generating the object structure rather than 
parsing the XML
something like this

 private static Full getSituation ()
throws XmlException
{
Full f = Full.Factory.newInstance();
EventReference eventReference = f.addNewEventReference();
eventReference.setEventId("blah blah");
eventReference.setResponsePlanId("blah blah");
eventReference.setUpdate(234234234);

MessageHeader messageHeader = f.addNewMessageHeader();
//set something

return f;
}

When I do that I get the proper output from toString().



> Doubled wrapper elements around XMLBeans-generated XML
> --
>
> Key: AXIS2-1129
> URL: http://issues.apache.org/jira/browse/AXIS2-1129
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: core, om, wsdl, client-api, databinding
>Affects Versions: 1.0
>Reporter: Derek Foster
>Priority: Blocker
>
> I recently noticed a big problem in how Axis2 generates XML for  XMLBeans 
> objects. It appears to be creating the wrapper element around
> an XMLBean twice, thus generating erroneous XML for a SOAP message. This 
> appears to be a big problem that would affect a lot of web services, and is 
> making it impossible for my company to use Axis2 to talk to our server.
> This error was found in the latest nightly build (September 8), but has 
> apparently been around for some time.
> I have a particular WSDL, as follows:
> 
> targetNamespace="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:tns="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:c="http://www.c-corp.com/wsdl/2004-10-01/c";
>xmlns:F="http://www.dummy-temp-address";
>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns="http://schemas.xmlsoap.org/wsdl/";>
>
>   http://www.c-corp.com/wsdl/2004-10-01/F";>
>  http://www.dummy-temp-address"; 
> schemaLocation="F.xsd"/>
>  
>  
>   
>   http://www.c-corp.com/wsdl/2004-10-01/c";>
>  
>  
>   
>
>
>   
>
>
>   
>
>
>   
>
>
>   
>
>
>   
>
>
>   F Port Type
>   
>  
>  
>  
>   
>
>
>   F Soap Binding
>transport="http://schemas.xmlsoap.org/soap/http"/>
>   
>  
>  
> 
>  use="literal"/>
> 
>  
>  
> 
>  
>  
> 
>  
>   
>
>
>   F Web Service
>   
>   location="http://localhost:8080/axis/services/FService"/>
>   
>
> 
> My WSDL references the following XML schema:
> 
> http://www.dummy-temp-address";
>xmlns="http://www.dummy-temp-address";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns:c="http://www.c-corp.com/schemas/c/schema_annotation";
>elementFormDefault="unqualified"
>attributeFormDefault="unqualified"
>version="DRAFT">
>
>
>   
>  
>  
>  
>   
>
>
>   
>  
>   
>
>
>   
>  
>  
>  
>   
>
> 
> After running WSDL2Java to generate the appropriate classes, I am using the 
> following code to generate and transmit a client message to my SOAP server:
>protected ReturnDocument executeTest (
>   final String targetEndpoint,
>   final CLoginDocument login,
>   final CPasswordDocument password )
>   throws Exception
>{
>   final FServiceStub service = new FServiceStub( null, targetEndpoint );
>   final Options options = service._getServiceClient().getOptions();
>   options.setProperty( 
> org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE );
>   service._getServiceClient().setOptions( options );
>   final FullDocument full = Full.Factory.newInstance();
>   full.setFull( getSituation() );
>   return service.acceptFEvent( full, login, password );
>}
>private Full getSituation ()
>   throws XmlException
>{
>   return Full.Factory.parse(
>  "   http://www.dummy-temp-address\";>\n" +
> "  \n" +
> ... and so forth: see output for the res

Re: [Axis2] An approach for clustering Axis2

2006-09-09 Thread Chamikara Jayalath

Hi Filip, Rajith, AllThanks to all the resources from Filip I guess we can now get a good undestanding of tribes and  use  it for an implementation of the ClusterManager. As u guys had mentioned the session updates hv to be done periodically. I guess this can be decided based on the Axis2 contexts we hope to replicate.
As it was decided earlier we will only be replicating ConfigurationContext, ServiceContexts and ServiceGroupContexts.(Fillip, Axis2 comes with a context hierarchy which should be used to store runtime infomation of various statget. For 
e.g. ConfigurationContext is for the whole system, ServiceContexts for each service etc., so replicating the state of Axis2 system implies replicating a subset of this context hierarchy).Therefore a good place for calling the state update method would be at the end of an OperationContext. In other words when the cleanup method of the OperationContext get called.
ChamikaraOn 9/8/06, Filip Hanik - Dev Lists <
[EMAIL PROTECTED]> wrote:
Sure, resources can be found at:A brief introductionhttp://people.apache.org/~fhanik/tribes/docs/introduction.html
<
http://people.apache.org/%7Efhanik/tribes/docs/introduction.html>Simple summary
http://people.apache.org/~fhanik/tribes/javadoc/org/apache/catalina/trib
es/package-summary.htmlDownloads
http://people.apache.org/~fhanik/tribes/archive/<
http://people.apache.org/%7Efhanik/tribes/archive/
>You can take a look at the org.apache.catalina.tribes.demos.MapDemojava -cp tribes-0.9.5.2.jar;commons-logging-api.jarorg.apache.catalina.tribes.demos.MapDemothis example uses a primary/secondary backup strategy, there is also a
similar all to all map as well.The replicated map extends HashMap, so if you implement your session manager to use a HashMap all you need to do is replace this hashmap with a replicated one.Take a look at

http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/modules/ha/src/share/org/apache/catalina/ha/session/BackupManager.java?view=markup
at the method*public* *void* start() *throws* LifecycleException {*if* ( *this*.started ) *return*;*try* {CatalinaCluster catclust = (CatalinaCluster)cluster;
catclust.addManager(getName(), *this*);LazyReplicatedMap map = *new* LazyReplicatedMap(*this*,  catclust.getChannel(),  DEFAULT_REPL_TIMEOUT,
  getMapName(),  getClassLoaders());map.setChannelSendOptions(mapSendOptions);*this*.sessions = map; //swap out the old hashmap for the replicated hashmap
*super*.start();}  *catch* ( Exception x ) {log.error(*"Unable to start BackupManager"*,x);*throw* *new* LifecycleException(*"Failed to start BackupManager"*,x);
}}The objects your store in your HashMap can implement theorg.apache.catalina.tribes.tipis.ReplicatedMapEntry interface, and bydoing that allow for diffs/deltas to be replicated.

just a few examples, I can give more if you decide to use thisimplementation. Another option you have is to use the Jakarta JCS (JavaCaching System), Aaron there has done tons of work, and believe added ina small module for replication as well.
FilipRajith Attapattu wrote:> Filip,>> Thank you for picking up the baton. Can u please provide a list of> resources that people should be looking at if they are to use Tribes?
>> like where to download, documentation ...etc?>> Chamikar and Chathura (and everybody else interested)... shall we get> started on the impl?> We can each choose an area and then start working on the code.
> comments?>> Regards,>> Rajith>> On 9/8/06, *Filip Hanik - Dev Lists* < 
[EMAIL PROTECTED]> 
[EMAIL PROTECTED]>> wrote:>> it all looks kosher to me. the logic that you are talking about is> axis> invocation logic.> in tomcat for example, we intercept the request with a valve, and
> after> the request is complete, we simple check to see if the session was> updated,> and then notify the replicated map to flush out the changes.>> I'm not familiar enough with axis to know the details of the
> invocation> chain, but I can imagine it being pretty similar.>> I agree with that it should be easy and non intrusive, goes for all> software :)>> Filip
>>> Rajith Attapattu wrote:> > Hi All,> >> > As Chamikara pointed out we have left the proposal for about a week> > now for any comments/concerns.
> > I guess people are happy so far with the proposal.> >> > Shall we move on to the implementation stage?> >> > Filip could you please have a look and let us know your ideas?
> >> > Regards,> >> > Rajith> >> > On 8/25/06, *Rajith Attapattu* < 
[EM

[jira] Updated: (AXIS2-1130) Build with Maven 2

2006-09-09 Thread Jochen Wiedmann (JIRA)

 [ http://issues.apache.org/jira/browse/AXIS2-1130?page=all ]

Jochen Wiedmann updated AXIS2-1130:
---

Attachment: axis2-maven2.patch

Current state

> Build with Maven 2
> --
>
> Key: AXIS2-1130
> URL: http://issues.apache.org/jira/browse/AXIS2-1130
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Improvement
>Reporter: Jochen Wiedmann
> Assigned To: Jochen Wiedmann
> Attachments: axis2-maven2.patch
>
>
> This is a tracker bug, which serves the following purposes:
> - Keep people informed about the ongoing efforts.
> - Prevent that someone else starts working on the same topic.
> - If possible, attract other people to start working here.
> - Collect dependencies on related bugs like AXIS2-1128

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



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

[jira] Work started: (AXIS2-1130) Build with Maven 2

2006-09-09 Thread Jochen Wiedmann (JIRA)

 [ http://issues.apache.org/jira/browse/AXIS2-1130?page=all ]

Work on AXIS2-1130 started by Jochen Wiedmann.

> Build with Maven 2
> --
>
> Key: AXIS2-1130
> URL: http://issues.apache.org/jira/browse/AXIS2-1130
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Improvement
>Reporter: Jochen Wiedmann
> Assigned To: Jochen Wiedmann
> Attachments: axis2-maven2.patch
>
>
> This is a tracker bug, which serves the following purposes:
> - Keep people informed about the ongoing efforts.
> - Prevent that someone else starts working on the same topic.
> - If possible, attract other people to start working here.
> - Collect dependencies on related bugs like AXIS2-1128

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



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

[jira] Created: (AXIS2-1130) Build with Maven 2

2006-09-09 Thread Jochen Wiedmann (JIRA)

Build with Maven 2
--

 Key: AXIS2-1130
 URL: http://issues.apache.org/jira/browse/AXIS2-1130
 Project: Apache Axis 2.0 (Axis2)
  Issue Type: Improvement
Reporter: Jochen Wiedmann
 Assigned To: Jochen Wiedmann


This is a tracker bug, which serves the following purposes:

- Keep people informed about the ongoing efforts.
- Prevent that someone else starts working on the same topic.
- If possible, attract other people to start working here.
- Collect dependencies on related bugs like AXIS2-1128


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



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

Re: [Axis2] XmlSchema & Axiom for next Axis2 release

2006-09-09 Thread Eran Chinthaka

John Kaputin (gmail) wrote:
> Hi all,
> what plans does the Axis2 community have regarding XmlSchema and Axiom
> releases for the next release of Axis2 proposed for later this month?

Axiom release will, most probably, available by 15th Sep. XmlSchema,
there are some changes that are being done these days by Dims and
Jochen. I prefer if one of them can talk about it.
Anyway, we need to have a release on XmlSchema, before Woden and Axis2
releases.

Any volunteers for that?

> 
> At the weekly Woden chat we discussed doing a milestone release of Woden
> in time for the next Axis2 release, but as Woden depends on XmlSchema
> and Axiom we really need to build against the same releases used (or to
> be used) by the next Axis2 release.

John, I prefer if Woden also can depend on the latest Xmlschema stuff.
So +1 for deciding Woden release plans soon after XmlSchema release.

Thanks,
Chinthaka

signature.asc
Description: OpenPGP digital signature

[jira] Commented: (AXIS2-1128) Layout of axis2/modules/tool

2006-09-09 Thread Jochen Wiedmann (JIRA)

[ 
http://issues.apache.org/jira/browse/AXIS2-1128?page=comments#action_12433576 ] 

Jochen Wiedmann commented on AXIS2-1128:



But, Dims, isn't that just another argument to break up the eclipse specific 
stuff into a separate directory? At least, I find it quite inconvenient to work 
with compiler excludes.


> Layout of axis2/modules/tool
> 
>
> Key: AXIS2-1128
> URL: http://issues.apache.org/jira/browse/AXIS2-1128
> Project: Apache Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: Tools
>Reporter: Jochen Wiedmann
>
> Hello,
> while working on the Maven 2 build of Axis 2, I detected a problem in the 
> layout of the directory axis2/modules/tool. This directory contains, among 
> others, a directory "src" and several directories with Maven 2 plugins.
> The "src" subdirectory means, that the directory is meant to produce 
> artifacts, for example "axis2-tools.jar". In other words, the "axis2-tool" 
> project should have packaging "jar".
> On the other hand, the presence of maven plugins below means, that the 
> directory is a parent directory. In other words, it should have packaging 
> "pom".
> I see no other possibility to resolve the problem, apart from changing the 
> directory layout. Suggested new layout:
> axis2
> +-- modules
>   +-- tool  (I'd personally consider "tools" a better name.)
> +-- maven2
>  |+-- axis2-aar-maven-plugin
>  |+-- axis2-idea-plugin
>  |+-- axis2-java2wsdl-maven-plugin
>  |+-- axis2-wsdl2code-maven-plugin
>  |+-- pom.xml
>  +-- general
>  | +-- src
>  | +-- conf
>  | +-- script
>  | +-- test
>  | +-- pom.xml
>  | +-- project.xml
>  +-- pom.xml
>  I do personally believe, that the directory "general" should be splitted 
> into more subprojects. However, that could as well be done at a later point.

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



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

[jira] Commented: (AXIS2-1116) WSDL2Java with Xmlbeans binding is not generating classes for all schema

[jira] Commented: (AXIS2-1126) Compile error in the 'Nightly Builds'

[jira] Commented: (AXIS2-937) WSDL2Java not generating parameters for stub methods

Re: [Axis2] Build failing

[jira] Commented: (AXIS2-1130) Build with Maven 2

[jira] Commented: (AXIS2-1128) Layout of axis2/modules/tool

[jira] Commented: (AXIS2-747) Missing namespace on subelement

[jira] Commented: (AXIS2-1129) Doubled wrapper elements around XMLBeans-generated XML

Re: [Axis2] An approach for clustering Axis2

[jira] Updated: (AXIS2-1130) Build with Maven 2

[jira] Work started: (AXIS2-1130) Build with Maven 2

[jira] Created: (AXIS2-1130) Build with Maven 2

Re: [Axis2] XmlSchema & Axiom for next Axis2 release

[jira] Commented: (AXIS2-1128) Layout of axis2/modules/tool

14 matches

Site Navigation

Mail list logo

Footer information