Re: [Axis2] Implementing Service Client API

2006-04-25 Thread Pete Robbins
Thanks guys. This is really helpful. One final question (for now!):Do you have a release planned to contain this new client api? If so when? (yes I know that was 2 questions).

Cheers,-- Pete 


Re: [C++] SDO Uri and QName

2006-04-24 Thread Pete Robbins
Thinking a bit more about this it would be nice to expose the XSDHelperImpl
method:
 void defineTypes(TypeDefinitions types);

Then I could create my own TypeDefinitions including the schema information
and simply call this method. This would require that the TypeDefinitions,
TypeDefinition and PropertyDefinitions were available to me to use.

Cheers,


On 24/04/06, Edward Slattery [EMAIL PROTECTED] wrote:

 I think it makes a lot of sense. I dont currently have an isQName flag,
 but I do have a whole lot of flags such as isFromList which tell me that
 the original many-valued element was loaded from a XSD list element. ( I
 have implemented list as a single valued element with a property called
 values, but it looks to the DataObject API like a multi-valued element
 with no properties).
 I agree that there is a more general need toretain more context upwards
 from
 XSD to DataFactory.
 Is anyone else having similar requirements?

 regards,
 Ed.


 On 21/04/06, Pete Robbins [EMAIL PROTECTED] wrote:
 
  The current SDO implementation handles the mapping of QName to the SDO
 Uri
  type as per the specification. So if I use XSDHelper to load a schema
  which
  defines a property as type xs:QName, e.g.xs:attribute
 name=joe
  type=xs:QName /then use XMLHelper to load my xml containing 
  joe=ns1:fred xmlns:ns1=myNS... then the value stored in the DO is
  myNS#fred. All fine... this is as it should be according to the spec.
 
  My problem is that I want to define the types programatically rather
 than
  using XSDHelper using DataFactory::addPropertyToType(). There is no
  way
  to say treat this as a QName so when I use XMLHelper to load my xml
 the
  value stored in the DO is ns1:myNS.
 
  Should there be an interface to add schema information to a Property (or
  Type)? As well as isQname there are other attributes available from a
  schema that can not be added using the current API such as isElement
  isAttribute to control the serialization to an element/attribute.
 
  Does this make sense?
 
  --
  Pete
 
 




--
Pete


[C++] SDO Uri and QName

2006-04-21 Thread Pete Robbins
The current SDO implementation handles the mapping of QName to the SDO Uri
type as per the specification. So if I use XSDHelper to load a schema which
defines a property as type xs:QName, e.g.xs:attribute name=joe
type=xs:QName /then use XMLHelper to load my xml containing 
joe=ns1:fred xmlns:ns1=myNS... then the value stored in the DO is
myNS#fred. All fine... this is as it should be according to the spec.

My problem is that I want to define the types programatically rather than
using XSDHelper using DataFactory::addPropertyToType(). There is no way
to say treat this as a QName so when I use XMLHelper to load my xml the
value stored in the DO is ns1:myNS.

Should there be an interface to add schema information to a Property (or
Type)? As well as isQname there are other attributes available from a
schema that can not be added using the current API such as isElement
isAttribute to control the serialization to an element/attribute.

Does this make sense?

--
Pete


Re: [Axis2] help required building

2006-04-13 Thread Pete Robbins
Many thanks I'l give that a try.-- Pete 


Re: [Axis2C] Setting SoapAction and SOAP version in a client

2006-04-13 Thread Pete Robbins

On 13/04/06, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
Hi Pete, You are correct, there seems to be a bug here; the API is supposedto be such that you can call AXIS2_MEP_CLIENT_PREPARE_SOAP_ENVELOPE,
then get the soap envelope though the message context returned by thatcall and set the SOAP version on that soap envelope. However, the logicin set SOAP version method of SOAP envelope seem to be commented out, I
am not sure why, have to dig into the cuase to find out why. Please raise a Jira on this.

I think the problem is in mep_client. The axis2_mep_client_prepare_soap_envelope creates a msg_ctx which will always have the default isSoap11 set to false. This flag is then used to call axis2_soap_envelope_create_default_soap_envelope.


Rather than checking AXIS2_MSG_CTX_GET_IS_SOAP_11, which will always be false, the code could use the value set by AXIS2_MEP_CLIENT_SET_SOAP_VERSION_URI to determine the call to axis2_soap_envelope_create_default_soap_envelope??

Cheers,
-- Pete 


[jira] Created: (AXIS2C-123) There is no way to set the SOAP version using the mep_client api

2006-04-13 Thread Pete Robbins (JIRA)
There is no way to set the SOAP version using the mep_client api


 Key: AXIS2C-123
 URL: http://issues.apache.org/jira/browse/AXIS2C-123
 Project: Axis2-C
Type: Bug

Versions: Current (Nightly)
Reporter: Pete Robbins
Priority: Minor


I tried using AXIS2_MEP_CLIENT_SET_SOAP_VERSION_URI but when I call 
AXIS2_MEP_CLIENT_PREPARE_SOAP_ENVELOPE it always uses SOAP12 to build the soap 
envelope.
 
I think the problem is in mep_client. The 
axis2_mep_client_prepare_soap_envelope creates a msg_ctx which will always have 
the default isSoap11 set to false. This flag is then used to call 
axis2_soap_envelope_create_default_soap_envelope. 
 
Rather than checking AXIS2_MSG_CTX_GET_IS_SOAP_11, which will always be false, 
the code could use the value set by AXIS2_MEP_CLIENT_SET_SOAP_VERSION_URI to 
determine the call to axis2_soap_envelope_create_default_soap_envelope?? 



-- 
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



Re: [Axis2C] Setting SoapAction and SOAP version in a client

2006-04-13 Thread Pete Robbins

On 13/04/06, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
I have fixed the problem and posted the latest source package at
http://people.apache.org/~samisa/Please have a look.Samisa...


That does the trick! Thank you. 
-- Pete 


[Axis2] help required building

2006-04-11 Thread Pete Robbins
I am working on the Tuscany project and I am trying to use Axis2C for webservice support. I'm running into a few problems :-(

I've downloaded the 0.90 binary release and get the samples running no problem.

What I would like is to write my own client code ... and here the problems start. Is there a document saying how to build a client? By this I mean which libraries you need to link with etc.. Trying to use the samples makefiles with the list of libraries (-laxis2_util etc..) gives errors. I get errors such as : /home/sahan/release/0.90/axis2c-
0.90/lib/libaxis2_attachments.la does not exist.

So I now decide to build from the source. The build instructions say to use ./configure, make, make install but this does not work as there are errors in the Makefile.am files. Do you still use this method to build? I see 
Maven.xml files in the source tree. Do you have instructions as to how to build with Maven??

Cheers,-- Pete 


Re: [Axis2] help required building

2006-04-11 Thread Pete Robbins
ok many thanks. Deleting the .la files cures the link problems.

I'll get back to you on the ./configure problem

Cheers,
On 11/04/06, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
Pete Robbins wrote: I am working on the Tuscany project and I am trying to use Axis2C for webservice support. I'm running into a few problems :-(
 I've downloaded the 0.90 binary release and get the samples running no problem. What I would like is to write my own client code ... and here the problems start. Is there a document saying how to build a client? By
 this I mean which libraries you need to link with etc..We do not have a doc on this, we should have, but unfortunately we donot have as of now, we should include this in the user guide.For the time being please have a look at the 
Makefile.am file of asample, then you can get an idea on this.The set of lib options on Linux should be:-L$AXIS2C_HOME/lib -laxis2_util -laxis2_om -laxis2_wsdl -laxis2_engine
-laxis2_parser -laxis2_unix-lpthread -laxis2_soap -laxis2_http_sender -laxis2_http_receiver -lxml2 Trying to use the samples makefiles with the list of libraries (-laxis2_util etc..) gives errors. I get errors such as :
 /home/sahan/release/0.90/axis2c- 0.90/lib/libaxis2_attachments.la does not exist.There is a problem with the .la files with the binary release. Henceplease delete the .la files from the lib folder and try to link directly
with .so files. So I now decide to build from the source. The build instructions say to use ./configure, make, make install but this does not work as there are errors in the 
Makefile.am http://Makefile.am files. Do you still use this method to build? I see Maven.xml files in the source tree. Do you have instructions as to how to build with Maven??
We use the maven system only to build the web site. You have to use themake based system to build the source.If you use ./confiure; make; make install tuple, it is not supposd tolook for the 
Makefile.am. If it does, it is an error in the buildsystem. However, according to the pre release testing, the make systemof the source package was working. Please send us the exact problem
Thanks,Samisa... Cheers, -- Pete-- Pete 


Re: [axis2c] Adding elements to SOAP envelope header in client

2006-04-11 Thread Pete Robbins
Here is what I'm trying to do. Please tell me my mistakes ;-)

A) extract axis2c tree from svn
B)as per the instructions run ./configure 

Problem 1: there is no configure script in the svn tree
Solution?: I used the autogen.sh script to create the automake files

Problem 2: This gets errors as there are problems in some of the Makefile.am files:
 modules/Makefile.am:2: directory should not contain '/'
 modules/core/Makefile.am:1: directory should not contain '/'
These are caused by SUBDIRS = platforms/unix ... which would appear to be invalid on my system (RH linux)

The configure script generated is invalid.
I also get errors because the configure.ac file has:

 test/unit/xml/om/Makefile\
 test/core/transport/Makefile\

My system likes a space before the \

I have autoconf version 2.59, automake version 1.6.3

Cheers,







Re: [axis2c] Adding elements to SOAP envelope header in client

2006-04-11 Thread Pete Robbins
oops... sorry wrong thread :-(


Re: [Axis2] help required building

2006-04-11 Thread Pete Robbins
Here is what I'm trying to do. Please tell me my mistakes ;-)

A) extract axis2c tree from svn
B)as per the instructions run ./configure 

Problem 1: there is no configure script in the svn tree
Solution?: I used the autogen.sh script to create the automake files

Problem 2: This gets errors as there are problems in some of the Makefile.am files:
 modules/Makefile.am:2: directory should not contain '/'
 modules/core/Makefile.am:1: directory should not contain '/'
These are caused by SUBDIRS = platforms/unix ... which would appear to be invalid on my system (RH linux)

The configure script generated is invalid.
I also get errors because the configure.ac file has:

 test/unit/xml/om/Makefile\
 test/core/transport/Makefile\

My system likes a space before the \

I have autoconf version 2.59, automake version 1.6.3

Cheers,
-- Pete 


Re: [Axis2] help required building

2006-04-11 Thread Pete Robbins

On 11/04/06, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
We use automake 1.9.5, it is a real problem to support multiple versionsof automake (infact it is almost impossible with my experiance with Axis
C++)If you could, please try to upgrade to automake 1.9.5.Thnaks,Samisa...

I updated to automake 1.9.5. I also had to update libtool to 1.5.22.

Now when running ./configure I get:

./configure: line 19923: syntax error near unexpected token `LIBXML2,'./configure: line 19923: `PKG_CHECK_MODULES(LIBXML2, libxml-2.0)'
I do have libxml2 installed.

Are there any other particular levels of automake/conf/libtool/??? that I would need?

Cheers,-- Pete 


[jira] Created: (TUSCANY-164) Add encoding of parameter types to Operation

2006-04-10 Thread Pete Robbins (JIRA)
Add encoding of parameter types to Operation


 Key: TUSCANY-164
 URL: http://issues.apache.org/jira/browse/TUSCANY-164
 Project: Tuscany
Type: New Feature

  Components: C++ SCA  
Reporter: Pete Robbins
 Assigned to: Pete Robbins 


The Operation message passed internally requires an encoding of the parameters' 
types.

-- 
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



Re: [help wanted] Moving position of import elements in SCDL

2006-04-07 Thread Pete Robbins
On 07/04/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
If nobody objects, I can move the wsdl.import up in the XSD. I'm in the
middle of changes to this project anyway.

Where in the source tree is the schema you are using? Is it in spec/... ?
--
Pete


Re: [help wanted] Moving position of import elements in SCDL

2006-04-07 Thread Pete Robbins
Ignore that.. I found it :-(

On 07/04/06, Pete Robbins [EMAIL PROTECTED] wrote:



  Where in the source tree is the schema you are using? Is it in spec/... ?
 --
 Pete




--
Pete


Re: Axis2C Milestone Release M0.5 Released

2006-03-16 Thread Pete Robbins
That is a great idea. I spent a long time trying to find the Axis2C home page! 

We will be looking at providing Axis2C bindings for the Tuscany C++ project.

Pete
On 16/03/06, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
BTW, our website is up at http://ws.apache.org/axis2/c/. Should we
request a link from http://ws.apache.org/axis2/, the Axis2 Java site?Also, what about a link from Axis C++ page?Samisa...Sahan Gamage wrote: Hi All,
 The fifth milestone release of Axis2 C, M0.5 has been released and could be downloaded at http://ws.apache.org/axis2/c/download.cgi
 We have done considerable amount of improvements in the past three weeks since the M0.4 release. Hence this release. We have the following features added on top of the 
M0.4 release 1. Improving code quality by fixing memory leaks and reviewing the code. 2. Apache2 integration. 3. More samples and tests 4. Initial documentation(User guide, Developer Guide and Installation
 Guide) 5. Numerous bug fixes since last release By now, we have implemented all the core features except MTOM support. The following are a list of TODOs to be handled in the next release.
 1. Dynamic Invocation 2. HTTP client using libcurl 3. WSDL Object Model built based on the proposed WSDL 2.0 Component Model. 4. MTOM/SWA attachments support We welcome your early feedback on this implementation.
 Best Regards Sahan


[jira] Created: (TUSCANY-108) SCA Windows build fails on runtime/test

2006-03-10 Thread Pete Robbins (JIRA)
SCA Windows build fails on runtime/test
---

 Key: TUSCANY-108
 URL: http://issues.apache.org/jira/browse/TUSCANY-108
 Project: Tuscany
Type: Bug
  Components: C++ Build  
Reporter: Pete Robbins


The generated wrappers/proxies are missing from the source tree

-- 
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



[jira] Assigned: (TUSCANY-108) SCA Windows build fails on runtime/test

2006-03-10 Thread Pete Robbins (JIRA)
 [ http://issues.apache.org/jira/browse/TUSCANY-108?page=all ]

Pete Robbins reassigned TUSCANY-108:


Assign To: Pete Robbins

 SCA Windows build fails on runtime/test
 ---

  Key: TUSCANY-108
  URL: http://issues.apache.org/jira/browse/TUSCANY-108
  Project: Tuscany
 Type: Bug
   Components: C++ Build
 Reporter: Pete Robbins
 Assignee: Pete Robbins


 The generated wrappers/proxies are missing from the source tree

-- 
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



[jira] Resolved: (TUSCANY-108) SCA Windows build fails on runtime/test

2006-03-10 Thread Pete Robbins (JIRA)
 [ http://issues.apache.org/jira/browse/TUSCANY-108?page=all ]
 
Pete Robbins resolved TUSCANY-108:
--

Resolution: Fixed

fix applied - files re-added to svn

 SCA Windows build fails on runtime/test
 ---

  Key: TUSCANY-108
  URL: http://issues.apache.org/jira/browse/TUSCANY-108
  Project: Tuscany
 Type: Bug
   Components: C++ Build
 Reporter: Pete Robbins
 Assignee: Pete Robbins


 The generated wrappers/proxies are missing from the source tree

-- 
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



Re: Stable C++ code tagged

2006-03-10 Thread Pete Robbins
fixed as TUSCANY-108 on Jira

On 10/03/06, Colin Thorne [EMAIL PROTECTED] wrote:

 I tried building SCA using Axis 1.5. I received an error:

 Linking...
   Creating library Debug/tuscany_sca.lib and object Debug/tuscany_sca.exp
 Logger.obj : error LNK2001: unresolved external symbol public: __thiscall
 tuscany::sca::FileLogWriter::FileLogWriter(char const *) (
 [EMAIL PROTECTED]@tuscany@@[EMAIL PROTECTED]@Z)
 Debug/tuscany_sca.dll : fatal error LNK1120: 1 unresolved externals

 I foudn the source file for this in:
 tuscany\cpp\sca\runtime\core\src\tuscany\sca\util and added this to the
 project and rebuilt. I got a bit further this time: but now have:

 Build : warning : failed to (or don't know how to) build

 'D:\tuscany\cpp\sca\runtime\core\test\CustomerInfo\CustomerInfoImpl_CustomerInfoService_Wrapper.cpp'
 Compiling...
 CustomerInfoImpl.cpp
 CustomerInfoImpl_CustomerInfoService_Proxy.cpp
 fatal error C1083: Cannot open source file:

 'D:\tuscany\cpp\sca\runtime\core\test\CustomerInfo\CustomerInfoImpl_CustomerInfoService_Proxy.cpp':
 No such file or directory
 CustomerInfoImpl_CustomerInfoService_Wrapper.cpp
 fatal error C1083: Cannot open source file:

 'D:\tuscany\cpp\sca\runtime\core\test\CustomerInfo\CustomerInfoImpl_CustomerInfoService_Wrapper.cpp':
 No such file or directory
 Generating Code...
 Error executing cl.exe.


 --
 Colin Thorne




Re: Exception running SCA for C++ tests

2006-03-10 Thread Pete Robbins
Yes. I will update the instructions for running the tests on Windows.

On 10/03/06, Colin Thorne [EMAIL PROTECTED] wrote:

 I've taken a new extract of the code from SVN, and I have built SDO and
 SCA
 (for C++). When I run the SCA test program (tuscany_sca_test.exe) I get an
 exception:

 Exception object :
 class:   SystemConfigurationException
 description: Default subsystem 'SubSystem1' not found

 Should I be setting some environment variable to pick up the deployed
 modules?
 --
 Colin Thorne




[jira] Assigned: (TUSCANY-105) Use environment variable to locate dependencies in Windows build projects

2006-03-10 Thread Pete Robbins (JIRA)
 [ http://issues.apache.org/jira/browse/TUSCANY-105?page=all ]

Pete Robbins reassigned TUSCANY-105:


Assign To: Pete Robbins

 Use environment variable to locate dependencies in Windows build projects
 -

  Key: TUSCANY-105
  URL: http://issues.apache.org/jira/browse/TUSCANY-105
  Project: Tuscany
 Type: Improvement
   Components: C++ Build
  Environment: Windows MS Studio projects
 Reporter: Pete Robbins
 Assignee: Pete Robbins


 Existing Studio projects don't work out of the box unless you use the exact 
 versions of dependencies. We should change the projects to locate the 
 dependencies by environment variables.

-- 
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



[jira] Updated: (TUSCANY-113) Provide Windows batch file to run SCA C++ test

2006-03-10 Thread Pete Robbins (JIRA)
 [ http://issues.apache.org/jira/browse/TUSCANY-113?page=all ]

Pete Robbins updated TUSCANY-113:
-

Priority: Minor  (was: Major)

 Provide Windows batch file to run SCA C++ test
 --

  Key: TUSCANY-113
  URL: http://issues.apache.org/jira/browse/TUSCANY-113
  Project: Tuscany
 Type: Improvement
   Components: C++ SCA
 Reporter: Pete Robbins
 Priority: Minor


 Add a scatest.bat to perform the same function as scatest.sh does on linux

-- 
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



[jira] Created: (TUSCANY-113) Provide Windows batch file to run SCA C++ test

2006-03-10 Thread Pete Robbins (JIRA)
Provide Windows batch file to run SCA C++ test
--

 Key: TUSCANY-113
 URL: http://issues.apache.org/jira/browse/TUSCANY-113
 Project: Tuscany
Type: Improvement
  Components: C++ SCA  
Reporter: Pete Robbins


Add a scatest.bat to perform the same function as scatest.sh does on linux

-- 
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



[jira] Resolved: (TUSCANY-105) Use environment variable to locate dependencies in Windows build projects

2006-03-10 Thread Pete Robbins (JIRA)
 [ http://issues.apache.org/jira/browse/TUSCANY-105?page=all ]
 
Pete Robbins resolved TUSCANY-105:
--

Resolution: Fixed

 Use environment variable to locate dependencies in Windows build projects
 -

  Key: TUSCANY-105
  URL: http://issues.apache.org/jira/browse/TUSCANY-105
  Project: Tuscany
 Type: Improvement
   Components: C++ Build
  Environment: Windows MS Studio projects
 Reporter: Pete Robbins
 Assignee: Pete Robbins


 Existing Studio projects don't work out of the box unless you use the exact 
 versions of dependencies. We should change the projects to locate the 
 dependencies by environment variables.

-- 
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



[jira] Resolved: (TUSCANY-71) Provide logging to file

2006-03-09 Thread Pete Robbins (JIRA)
 [ http://issues.apache.org/jira/browse/TUSCANY-71?page=all ]
 
Pete Robbins resolved TUSCANY-71:
-

Resolution: Fixed

Basic file logigng added

 Provide logging to file
 ---

  Key: TUSCANY-71
  URL: http://issues.apache.org/jira/browse/TUSCANY-71
  Project: Tuscany
 Type: New Feature
   Components: C++ SCA
 Reporter: Pete Robbins
 Assignee: Pete Robbins


 Default internal logging for C++ SCA is to stdout which can not be accessed 
 when running as apache/axis webservice.
 Create a simple log-to-file mechanism

-- 
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



[jira] Created: (TUSCANY-89) Provide Axis2C bindings

2006-03-09 Thread Pete Robbins (JIRA)
Provide Axis2C bindings
---

 Key: TUSCANY-89
 URL: http://issues.apache.org/jira/browse/TUSCANY-89
 Project: Tuscany
Type: New Feature
  Components: C++ SCA  
Reporter: Pete Robbins


Provide support for Axis2 ws bindings using Axis2C

-- 
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



[jira] Created: (TUSCANY-90) SCA Remotable binding

2006-03-09 Thread Pete Robbins (JIRA)
SCA Remotable binding
-

 Key: TUSCANY-90
 URL: http://issues.apache.org/jira/browse/TUSCANY-90
 Project: Tuscany
Type: New Feature
  Components: C++ SCA  
Reporter: Pete Robbins


Add support for remotable interfaces ans pass-by-value semantics

-- 
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



[jira] Created: (TUSCANY-91) Replace Tuscany-model.config with import.wsdl

2006-03-09 Thread Pete Robbins (JIRA)
Replace Tuscany-model.config with import.wsdl
---

 Key: TUSCANY-91
 URL: http://issues.apache.org/jira/browse/TUSCANY-91
 Project: Tuscany
Type: New Feature
  Components: C++ SCA  
Reporter: Pete Robbins
Priority: Minor


Sync with Java SCA method of defining wsdls

-- 
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



Re: [SDO C++] JIRA Issues: Specification or Implementation concerns?

2006-03-09 Thread Pete Robbins
I'm not sure where the SDO spec is being discussed. It is separate from the
C++ CI group.

On 09/03/06, Mike Edwards [EMAIL PROTECTED] wrote:

 Ant,

 At the moment, neither the SDO nor the SCA specification lists are
 publicly viewable.

 For SCA, we are investigating setting up a public website - one function
 of this website would be to allow for publicly viewable lists.

 Yours,  Mike.

 ant elder wrote:
  On 3/9/06, Mike Edwards [EMAIL PROTECTED] wrote:
  snip
 
   (the spec group have their own
 
 infrastructure and email lists).
 
 
 
  I remember a post from months ago saying these lists were going to be
 made
  publicly viewable, has that ever happened, is there an archive I can
 look
  at?
 
 ...ant
 



Re: Stable C++ code tagged

2006-03-09 Thread Pete Robbins
Looks like the Windows projects need to be updated (along with the
instructions) to use an environment variable for the location of the
dependencies. I'll raise an issue on Jira.

On 09/03/06, Colin Thorne [EMAIL PROTECTED] wrote:

 I've tried downloading and building the SCA for C++ code but I'm having a
 problem building the SDO code on Windows. I get the message:
 d:\tuscany\cpp\sdo\runtime\core\src\commonj\sdo\sdoxmlstring.h(26) : fatal
 error C1083: Cannot open include file: 'libxml/xmlstring.h': No such file
 or
 directory.

 I have downloaded and extracted the prereqs to the tuscany/cpp/sdo/lib
 directory.

 Also, wouldn't it be better to use the latest version of libxml2 being
 used
 (which is 2.6.23)?


 On 06/03/06, Pete Robbins [EMAIL PROTECTED] wrote:
 
  A stable version of C++ Tuscany can be found at:
 
 http://svn.apache.org/repos/asf/incubator/tuscany/tags/cpp-stable-20060304
 
  The build.txt file in the top level explains how to build the code.
 
  The sca/readme.txt describes the current function supported.
 
  Pete
 
 


 --
 Colin Thorne




[jira] Created: (TUSCANY-105) Use environment variable to locate dependencies in Windows build projects

2006-03-09 Thread Pete Robbins (JIRA)
Use environment variable to locate dependencies in Windows build projects
-

 Key: TUSCANY-105
 URL: http://issues.apache.org/jira/browse/TUSCANY-105
 Project: Tuscany
Type: Improvement
  Components: C++ Build  
 Environment: Windows MS Studio projects
Reporter: Pete Robbins


Existing Studio projects don't work out of the box unless you use the exact 
versions of dependencies. We should change the projects to locate the 
dependencies by environment variables.

-- 
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



[jira] Created: (TUSCANY-72) Improve handling of Axis exceptions

2006-03-07 Thread Pete Robbins (JIRA)
Improve handling of Axis exceptions
---

 Key: TUSCANY-72
 URL: http://issues.apache.org/jira/browse/TUSCANY-72
 Project: Tuscany
Type: Improvement
  Components: C++ SCA  
Reporter: Pete Robbins


Axis exceptions should be caught and handled to give better feedback on the 
causes of problems

-- 
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



C++ build opinions/help

2006-01-19 Thread Pete Robbins
The current cpp SDO and SCA were developed using MS Visual Studio on Windows
and eclipse + CDT on Linux. For a command line build on linux we simply
created a shell script that used the makefiles generated by the CDT managed
make.

I would like to create a more robust and portable build environment for the
cpp code and would welcome some guidance on what the best build style is
for C++.

Options:
1) Handcrafted Makefiles
2) Use Autotools (autoconf/automake)
3) Eclipse + CDT only
4) Ant + cpptasks
5) ???

Does Maven help with any of these?

Any help or opinions would be greatly appreciated before I set off down the
wrong path ;-)

Pete


Adding Jira components

2006-01-18 Thread Pete Robbins
How do I create new Components in Jira for Tuscany. I'd like:

cpp Build
cpp SCA
cpp SDO

Pete


[jira] Assigned: (TUSCANY-13) Change C++ build to use Autoconf/Automake

2006-01-18 Thread Pete Robbins (JIRA)
 [ http://issues.apache.org/jira/browse/TUSCANY-13?page=all ]

Pete Robbins reassigned TUSCANY-13:
---

Assign To: Pete Robbins

 Change C++ build to use Autoconf/Automake
 -

  Key: TUSCANY-13
  URL: http://issues.apache.org/jira/browse/TUSCANY-13
  Project: Tuscany
 Type: Improvement
   Components: C++ Build
 Reporter: Pete Robbins
 Assignee: Pete Robbins


 The current command line build of SDO and SCA C++ uses makefiles generated 
 via eclipse CDT. These are difficult to maintain.

-- 
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



Re: Java code contribution committed

2006-01-06 Thread Pete Robbins
Having trunk and branches folders seems to be the most common layout across
other projects.

Pete


Re: Java code contribution committed

2006-01-06 Thread Pete Robbins
So does anyone else have any opinion on whether we should move the cpp and
java folder structures under a tuscany/trunk ?

Now would be a good time to do this (before the java code is merged across
from the contrib folder). I'm happy to move the cpp folder if that's what we
want.

I think this is the right thing to do.

Pete

On 06/01/06, Pete Robbins [EMAIL PROTECTED] wrote:

 Having trunk and branches folders seems to be the most common layout
 across other projects.

 Pete





<    6   7   8   9   10   11