Java SCA 0.90 javadocs
I have generated the javadocs for the SCA 0.9 release, and have divided them in two groups : - API, this contains the OSOA Apis and the host-embedded definitions and is available at [1] - SPIs, this contains the javadoc for the spis listed on the CHANGES doc [3] as intended to be more stable over future releases, and it's available under [2] I'd like people to give it a quick review, and when we are comfortable with the contents, I'd like to move this to our website svn and link to it from our wiki. Thoughts ? [1] http://people.apache.org/~lresende/tuscany/javadoc/java-sca-0.9/sca-api/ [2] http://people.apache.org/~lresende/tuscany/javadoc/java-sca-0.9/sca-spi/ [3] https://svn.apache.org/repos/asf/incubator/tuscany/branches/sca-java-0.90/distribution/src/main/release/CHANGES -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Java SCA 0.90 javadocs
Luciano Resende wrote: I have generated the javadocs for the SCA 0.9 release, and have divided them in two groups : - API, this contains the OSOA Apis and the host-embedded definitions and is available at [1] - SPIs, this contains the javadoc for the spis listed on the CHANGES doc [3] as intended to be more stable over future releases, and it's available under [2] I'd like people to give it a quick review, and when we are comfortable with the contents, I'd like to move this to our website svn and link to it from our wiki. Thoughts ? [1] http://people.apache.org/~lresende/tuscany/javadoc/java-sca-0.9/sca-api/ [2] http://people.apache.org/~lresende/tuscany/javadoc/java-sca-0.9/sca-spi/ [3] https://svn.apache.org/repos/asf/incubator/tuscany/branches/sca-java-0.90/distribution/src/main/release/CHANGES Great, thanks for doing that, it will be useful to have these Javadocs on our web site. I have two minor comments: - It would be nice if we could exclude SCADomainBean and SCATestCaseRunner from the API as I don't think that they're really useful to application developers (I think we should remove them at some point). - The .impl and .util packages should be excluded from both the API and SPI javadocs. Thanks -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SDO fix for TUSCANY-1233 breaking DAS, was Fwd: svn commit: r543520 - in /incubator/tuscany/java/sdo/tools: src/main/java/org/apache/tuscany/sdo/generate/ src/main/java/org/apache/tuscany/sdo/gene
Looking at this now
Kelvin.
On 02/06/07, Luciano Resende [EMAIL PROTECTED] wrote:
After this commit, DAS test cases are failing as described on the
continuum build failure report[1]. I tried updating SDO to the
revision prior to this commit (svn update -r 543519), and then I get
a clean DAS build.
I have created JIRA TUSCANY-1323 to track the issue, Could someone on
the SDO team please take a look at this ?
[1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg18484.html
[2] https://issues.apache.org/jira/browse/TUSCANY-1323
-- Forwarded message --
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Jun 1, 2007 9:04 AM
Subject: svn commit: r543520 - in /incubator/tuscany/java/sdo/tools:
src/main/java/org/apache/tuscany/sdo/generate/
src/main/java/org/apache/tuscany/sdo/generate/templates/model/
templates/models/
To: [EMAIL PROTECTED]
Author: kelvingoodson
Date: Fri Jun 1 09:04:20 2007
New Revision: 543520
URL: http://svn.apache.org/viewvc?view=revrev=543520
Log:
Fix for TUSCANY-1233
Modified:
incubator/tuscany/java/sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/JavaGenerator.java
incubator/tuscany/java/sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/XSD2JavaGenerator.java
incubator/tuscany/java/sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/templates/model/SDOFactoryClass.java
incubator/tuscany/java/sdo/tools/templates/models/SDOFactoryClass.javajet
Modified:
incubator/tuscany/java/sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/JavaGenerator.java
URL:
http://svn.apache.org/viewvc/incubator/tuscany/java/sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/JavaGenerator.java?view=diffrev=543520r1=543519r2=543520
==
---
incubator/tuscany/java/sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/JavaGenerator.java
(original)
+++
incubator/tuscany/java/sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/JavaGenerator.java
Fri Jun 1 09:04:20 2007
@@ -27,6 +27,7 @@
import java.util.ArrayList;
import java.util.Collection;
import java.util.Collections;
+import java.util.Hashtable;
import java.util.Iterator;
import java.util.List;
import java.util.StringTokenizer;
@@ -84,6 +85,7 @@
* [ -generateLoader ]
* [ -interfaceDataObject ]
* [ -sparsePattern | -storePattern ]
+ * [ -noGenerate ]
*
* Basic options:
*
@@ -152,7 +154,10 @@
* implementation. It changes the generator pattern to
generate accessors which delegate to the
* reflective methods (as opposed to the other way around)
and changes the DataObject base class
* to org.apache.tuscany.sdo.impl.StoreDataObjectImpl. Note
that this option generates classes that
- * require a Store implementation to be provided before they
can be run.
+ * require a Store implementation to be provided before they
can be run.
+ * -noGenerate
+ * A basic implementation of this switch is in place, but is
not fully implemented. An intention
+ * behind this is to provide commentary on the artifacts that
would be generated.
*
*
*/
@@ -169,6 +174,7 @@
//FIXME Temporary, I need this option for now to get Switch classes
generated for the SCDL models
public static int OPTION_GENERATE_SWITCH=0x100;
public static int OPTION_INTERFACE_DO=0x400;
+ public static int OPTION_NO_GENERATE=0x800;
static
{
@@ -279,6 +285,10 @@
{
genOptions |= OPTION_INTERFACE_DO;
}
+else if (args[index].equalsIgnoreCase(-noGenerate))
+{
+ genOptions |= OPTION_NO_GENERATE;
+}
//else if (...)
else
{
@@ -340,29 +350,50 @@
}
}
- public static void generatePackages(Collection packageList, String
packageURI, String shortName, String targetDirectory, String
javaPackage, String prefix, int genOptions)
+ protected static void generatePackages(Collection packageList,
String packageURI, String shortName, String targetDirectory, String
javaPackage, String prefix, int genOptions)
+ {
+Hashtable packageInfoTable = new Hashtable();
+packageInfoTable.put(packageURI, new PackageInfo(javaPackage,
prefix, packageURI, shortName ));
+generatePackages(packageList, targetDirectory, packageInfoTable,
genOptions, false);
+ }
+
+ protected static GenModel generatePackages(Collection packageList,
String targetDirectory, Hashtable packageInfoTable, int genOptions,
boolean allNamespaces )
{
ResourceSet resourceSet = DataObjectUtil.createResourceSet();
List usedGenPackages = new ArrayList();
GenModel genModel = null;
+ArrayList packagesToModel = new ArrayList();
for (Iterator iter = packageList.iterator(); iter.hasNext();)
{
EPackage currentEPackage = (EPackage)iter.next();
- boolean generateCurrent = currentEPackage.getNsURI
().equals(packageURI);
- String currentBasePackage =
extractBasePackageName(currentEPackage, generateCurrent ?
[jira] Resolved: (TUSCANY-1140) Implementation of DAS Lite Command classes
[ https://issues.apache.org/jira/browse/TUSCANY-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Crestani resolved TUSCANY-1140. --- Resolution: Fixed All classes suggested are implemented and working Implementation of DAS Lite Command classes -- Key: TUSCANY-1140 URL: https://issues.apache.org/jira/browse/TUSCANY-1140 Project: Tuscany Issue Type: Sub-task Components: C++ DAS Reporter: Adriano Crestani Assignee: Adriano Crestani Fix For: Cpp-Next Attachments: DAS.zip, tuscany1040.crestani.20070315.patch, tuscany1140.crestani.20070406.patch Implementation of BaseCommandImpl, Command, CommandImpl and ReadCommandImpl classes as described on the DAS Lite class diagram: http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=45093 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-1220) FK columns name retrieved by dbms contain invalid characters
[ https://issues.apache.org/jira/browse/TUSCANY-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Crestani closed TUSCANY-1220. - Resolution: Won't Fix DAS C++ is no more using the class Database. FK columns name retrieved by dbms contain invalid characters Key: TUSCANY-1220 URL: https://issues.apache.org/jira/browse/TUSCANY-1220 Project: Tuscany Issue Type: Task Components: C++ DAS Reporter: Adriano Crestani Priority: Minor Fix For: Cpp-Next The method ResultSet* Database::getFKs(std::string tableName) const returns a ResultSet containing information about the tableName foreign keys. When getting specially the pk column name and fk column name, it is returning the column name surrounded by ' . For example: std::cout FK Column Name = fksResultSet-getSQLVarchar(7); // 7th column contains the fk column name std::cout \nPK Column Name = fksResultSet-getSQLVarchar(3); // 3th column contains the fk column name std::cout \nPK Table Name = fksResultSet-getSQLVarchar(2); // 2nd column contains the pk table name output: FK Column Name = 'COMPANY_ID' PK Column Name = 'ID' PK Table Name = DEPARTMENT As seen on the output, only the pk and fk column name are surrounded by ' . I'm actually solving this problem removing the ' from the string: std::string fkColumnName = fksResultSet-getSQLVarchar(7); std::string pkTableName = fksResultSet-getSQLVarchar(2); std::string pkColumnName = fksResultSet-getSQLVarchar(3); fkColumnName = fkColumnName.substr(1, fkColumnName.size() - 2); pkColumnName = pkColumnName.substr(1, pkColumnName.size() - 2); I'm using MySQL server. I don't know if it happens only with MySQL server or if there are others which do the same. I propose to test it using others DBMSs to test if it happens only on MySQL server or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RMI binding SCDL
As I started documenting the RMI binding SCDL at http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+binding.rmi I wondered if it could use a URI format instead of or as well as the separate host, port, and servicename attributes? There may be some reason its doesn't, has it ever been considered? Along the lines of whats described at http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-rmi.html#RMI, so: binding.rmi uri=rmi://localhost:1099/myservice/ and all those could have defaults so you could just have binding.rmi/ on a service and it would make it available using the component and service name as described in 1.7.2 of the assembly spec. ...ant
[jira] Commented: (TUSCANY-1323) DBInitializerTestCase failure after SDO changes to TUSCANY-1233
[ https://issues.apache.org/jira/browse/TUSCANY-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501158 ] Kelvin Goodson commented on TUSCANY-1323: - It would seem that the error is caused by a resequencing of the initialization of dependencies in the generated factory's init() method, so that the InternalFactory class initialization has moved from the end to the start of the dependency initialization. The InternalFactory initialization has a cyclic dependency on its own singleton instance by virtue of the reference to it in AttributeImpl, which is resolved if some other factory triggers AttributeImpl's initialization first. // Initialize simple dependencies SDOUtil.registerStaticTypes(SDOFactory.class); SDOUtil.registerStaticTypes(ModelFactory.class); SDOUtil.registerStaticTypes(InternalFactory.class); Investigating the fix now ... DBInitializerTestCase failure after SDO changes to TUSCANY-1233 --- Key: TUSCANY-1323 URL: https://issues.apache.org/jira/browse/TUSCANY-1323 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Affects Versions: Java-DAS-beta1 Reporter: Luciano Resende Priority: Blocker Fix For: Java-DAS-beta1 Failure report : http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg18484.html SDO Committ : http://www.mail-archive.com/tuscany-commits%40ws.apache.org/msg08488.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status of Java SCA 0.90 release
Point taken about the wordiness. I'm OK with this version. Simon ant elder wrote: Actually, as we're finding so much to do on the website and as June 2 is a Saturday how about we leave it till Monday June 4? Still not sure how to describe it, see below... ...ant On 6/1/07, Simon Nash [EMAIL PROTECTED] wrote: snip Apache Tuscany Java SCA provides a runtime based on the OASIS Open Composite Services Architecture SCA specifications which aim to simplify SOA Application Development. We shouldn't describe it in this way as this makes it sound like these are OASIS specs, which they aren't yet but will be (hopefully) in the future. I'd suggest ... a runtime based on the Service Component Architecture specifications from the Open SOA collaboration (osoa.org), aimed at simplifying SOA Application Development. These specifications have been submitted to OASIS for standardization as part of Open Composite Services Architecture (Open CSA). Is that starting to sound a little wordy for the 2nd line of an announcement with more info about specifications groups than Tuscany itself? I don't know the relationship btw the groups, do we need to mention Open SOA collaboration? Could it be something like: Apache Tuscany provides a runtime based on the Service Component Architecture. SCA is a set of specifications aimed at simplifying SOA Application Development which are now being standardized at OASIS as part of Open Composite Services Architecture (Open CSA). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Automated nightly builds
Comments inline below. Simon Luciano Resende wrote: I'm looking for a distribution that I could use directly, as the individual JARs are not so useful. Is there a way to get the distribution built as part of the automated build? For DAS, I have a distribution profile that generate javadoc, distributions, etc Maybe we could do same for SCA (and SDO) , and I could use this profile on the automated builds. Thougths ? +1 for including the distribution in the nightly build. On 6/3/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Luciano Resende wrote: On 6/3/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Luciano Resende wrote: I have changed all ports to 8085 and all the builds are working now on the apache machine [1]. I'll add a page to our Wiki describing how you can watch the results, I'll also configure the builds to send failure notification to the dev-list. I still have a todo to investigate the usage of the binary created on the build. [1] http://vmbuild.apache.org:8080/continuum/servlet/continuum The Apache Tuscany SCA Implementation Project says Tuscany SDO Implementation Project in the Group column. I was expecting to see SCA instead. What is the Group used for? The default behavior of the continuum admin ui is to add all sub-projects of a given pom, and because SCA was generating many projects, I decided to just re-use a SDO one and point to the SCA project pom to build it recursively. The group description you are seeing should not really affect anything, but also it's not an edit field (at least I couldn't find a place to edit it). I'm thinking that it's a little confusing, as our SCA implementation does not have a hard dependency on SDO. I think these should be kept separate. What is the disadvantage of doing this? I just triggered a successfull build of the SCA runtime. Where can I get the binaries produced by the build? I couldn't find a link to them... Open the continuum build project, go to Working copy tab on the top and you should have access to all built artifacts (same folder structure as local build) I'm looking for a distribution that I could use directly, as the individual JARs are not so useful. Is there a way to get the distribution built as part of the automated build? Thanks -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany website
Luciano, it's surprising how much better it feels without the redirect! How about we remove all of the old web site pages (or replace them with pointers to the new site) just in case people find them by accident? Simon
[jira] Resolved: (TUSCANY-1323) DBInitializerTestCase failure after SDO changes to TUSCANY-1233
[ https://issues.apache.org/jira/browse/TUSCANY-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1323. - Resolution: Fixed Preserved the order of simple dependencies by removing use of HashSet for building dependency list DBInitializerTestCase failure after SDO changes to TUSCANY-1233 --- Key: TUSCANY-1323 URL: https://issues.apache.org/jira/browse/TUSCANY-1323 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Affects Versions: Java-DAS-beta1 Reporter: Luciano Resende Priority: Blocker Fix For: Java-DAS-beta1 Failure report : http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg18484.html SDO Committ : http://www.mail-archive.com/tuscany-commits%40ws.apache.org/msg08488.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DAS M3 Release
Some more update, -mvn test on DAS is not running all tests, but only DBInitializerTestCase? -http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+-+Releases - added new para for beta1, please review, so M3 para can deleted if OK - Revised Starting with DAS, please give comments Regards, Amita On 5/28/07, Amita Vadhavkar [EMAIL PROTECTED] wrote: Hi , FAQs in place, please check and give comments/add to it http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+Java+-+FAQ Regards, Amita On 5/23/07, Amita Vadhavkar [EMAIL PROTECTED] wrote: Hi, Please take a look at the section Ongoing work items on page http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+-+Java+DAS+M3+Release and whatever is marked under review, please review and give your comments. This will help a lot in doing any necessary modifications to the DAS part of site. Also, I am gathering DAS questions discussed on ML and forming a FAQ, some archived messages are listed in the same section at the bottom. Please forward any FAQs you would like to include. Regards, Amita (Note: For memory analysis JIRA 1295 is added and patch is submitted, currently under review.) On 5/21/07, Amita Vadhavkar [EMAIL PROTECTED] wrote: Hi Adriano, It is still work-in-progress. Main changes I did are 1) use simple connection pool on Test Cases framework 2) use finalize() in RDB DAS code 3) Do cleanup (removing references) as needed 4) Decouple DatabaseSetup and DasTest - do not share connections With this, there is some success (i.e. I modified a few cases with these changes effective and the multi-schema are running with no out of memory , I repeated the same testcases multiple times to increase number of test cases) Now, I am trying the change on all test cases and will create a new JIRA with patch for the changes. This is not eliminating the memory leak 100% ,but reducing it. Will respond to this mail with the new JIRA number. Regards, Amita On 5/19/07, Adriano Crestani [EMAIL PROTECTED] wrote: Amita, did you solve the JIRA 952 memory leak problem? Except JIRA 800 that luciano is going to commit, is there any other new feature or bug to be implemented for this release? Adriano Crestani On 5/15/07, Luciano Resende [EMAIL PROTECTED] wrote: I have committed the initial part of TUSCANY-863 under revision 538267.** On 5/15/07, Amita Vadhavkar [EMAIL PROTECTED] wrote: Hi All, Points I gathered so far, we can sort out today. Will check more TODOs: 1) close JIRA-800, 863 2) remove JIRA-952 ? please see my last mail for memory leak, it still can happen with code without JIRA-952. It looks like it has to do with how our UT framework is setup.But so far I have not pin pointed the problem. So what path to follow for this JIRA? I will try more and find exact cause and resolution. 3) check all files license info (Adriano did this before, so just for any new code after that, we might need to do this.) 4) update http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+-+Java+DAS+M3+Release with closed/removed JIRAs 5) page - http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS [javadoc] - give link *Guides:- -Architecture Guide - should be on Tuscany Home Page and not DAS -Developer Guide - complete - how is working on it? (Some content from http://wiki.apache.org/ws/Tuscany/TuscanyJava/DAS_Java_Overview/RDBDAS_HOWTO_HelloDASApp can be used and completed here) Some content for htmlunit - http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg06053.html -User Guide - Advanced Web Sample - add link to this after JIRA-863, 800 are commited , dbsetuputility - as its a handy tool for users too -What's new? - list new features in this release -Downloads - add links after 1st RC - [New]Useful Links - http://incubator.apache.org/tuscany/RDB_DAS_white_paper_v-0.2.pdf(for outdated info - how to update?)http://issues.apache.org/jira/browse/TUSCANY-594 - TBD http://java.sys-con.com/read/260053.htm (for outdated info - how to update?) 6) page - http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS 7) page - http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+-+Releases Make this page in sync with what is going out in M3 8) page - http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+Java+-+FAQ Can add below list:- http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg04822.html http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg16300.html
Board Report for June 2007
Dear WS Committers, Please update the board report page with notable happening (releases, committers etc): http://wiki.apache.org/ws/ReportForJun2007 Old reports are available for comparison: http://wiki.apache.org/ws/FrontPage/BoardReports thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Contribute to SCA-OSGi integration
Hello, I would like to contribute to the SCA-OSGi integration activities. I have been looking at the existing OSGi binding implementation in Tuscany which exposes SCA services as OSGi services. Even though this binding is no longer working with the latest Tuscany builds, the samples were very useful to understand the scenarios. I was also looking at the notes on the mailing list (they are slightly old - dated Nov 2006) which talk about an OSGi host and also an OSGi implementation type. Is there any ongoing work in these areas? Graham Charters and I have been investigating the use of an OSGi implementation type which will enable existing OSGi bundles to be run as SCA components under Tuscany. We are particulary interested in the scenario where Tuscany is in control. If components of OSGi implementation type are specified in the composite, Tuscany starts up an OSGi runtime and deploys the OSGi bundles corresponding to the components into the OSGi runtime. If there are references from the OSGi component to other non-OSGi SCA components, a proxy service is registered by the Tuscany runtime with the OSGi registry so that the OSGi bundles can access these SCA services as normal OSGi services. References from non-OSGi components to OSGi components are resolved by looking up the OSGi registry. We would like to obtain feedback on using this approach and also would like to get involved in the ongoing support for SCA-OSGi integration. Thank you... Regards, Rajini
SDO Project Structure (was Re: [Vote] release Java SDO beta1)
Hi Ant, can I take you up on your offer of help to get the SDO distributions into the same structure as SCA now please? Regards, Kelvin. On 01/05/07, ant elder [EMAIL PROTECTED] wrote: +1 on the understanding that the SDO API use of the OSOA licensed code is clarified before we try to graduate. I think the SDO API Maven artifacts are missing from the staging repository so there will need to a vote update if we're releasing that. And I think it would be better and easier to merge all the distros into just src and binary distros and use the Maven assembly plugin to generate them, if it will help I'll volunteer to sort that out for the next release? ...ant On 4/26/07, kelvin goodson [EMAIL PROTECTED] wrote: Please vote to release the beta1 distribution of Tuscany SDO for Java The release candidate RC1 for Tuscany Java SDO beta1 archive distribution files are posted here at [1] The maven repository artifacts are posted in a staging repository [2] http://people.apache.org/%7Ekelvingoodson/sdo_java/M3/RC2/The release audit tool (rat) files and associated exceptions are attached to the jira under which the release work was done is at [3]. http://issues.apache.org/jira/browse/TUSCANY-1171 The tag for the source code is at [4] Changes in this release are shown in [5] http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubator-M3/sdo/distribution/RELEASE_NOTES.txt [1] http://people.apache.org/~kelvingoodson/sdo_java/beta1/RC1/ [2] http://people.apache.org/~kelvingoodson/repo/org/apache/tuscany/sdo/ [3] http://issues.apache.org/jira/browse/TUSCANY-1171 [4] http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/ [5] http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/sdo/distribution/RELEASE_NOTES.txt Thanks in advance, Kelvin.
Re: Even simpler SPI for binding and implementation extensions?
On 5/31/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
ant elder wrote:
I was trying to update the extension writers guide on the wiki and
found it
really hard to say simply and clearly what (and why) each step is
needed.
Now that there's quite a few extensions written to look at to see how
things
are being done I think we could simplify the SPI for these a bit moreby
having something like a new discoverable activator like this:
public interface BindingActivatorB extends Binding {
ClassB getModelType();
StAXArtifactProcessorB getSCDLProcessor();
ReferenceBindingProvider
createReferenceBindingProvider(RuntimeComponent
rc, RuntimeComponentReference rcr, B b);
ServiceBindingProvider
createServiceBindingProvider(RuntimeComponent rc,
RuntimeComponentService rcs, B b);
}
And then (borrowing an earlier idea from Sebastien) BindingActivator
impls
can use constructor args for any required extensions they need (eg
ServletHost) and the runtime automatically sets them without the impl
needing to explicitly locate them itself from the registry.
This would make the extension code a lot simpler and more obvious and
clear
exactly what must be implemented, and it removes the dependency on the
ExtensionPointRegistry.
All the old SPI continues to work, they would be like an advanced or
system
SPI, but simpler binding and implementation extensions could use this
more
simple interface.
Any objections if I go ahead and try this?
...ant
+1, I think we could even go a little bit further and provide a
simplification layer...
- covering component implementation types as well as bindings
- saving the extension developer from having to write an XML artifact
processor, for simple cases we could introspect the binding model and
simply map its fields to simple XML attributes.
- hiding the ProviderFactory and Provider layers
Ideally, for simple cases, I'd just want to write:
- a Binding or Implementation type model class
- an Invoker to handle invocations on SCA references
- a Listener to handle start/stop and incoming SCA service invocations
- a single Activator class tying the above together.
This layer would not alter or replace the current SPI, it would just be
a simplification convenience layer on top of the current pluggability
story, covering simple binding and implementation type cases. I'd
suggest to put this layer in different packages.
I've started an attempt at this keeping it completely separate from the
existing spi for right now by using a new extension-helper module. And i've
changed the script implementation and ajax binding to use it. Its only a
start and needs lot of work so anyone please feel free to comment, suggest
changes and alternatives, or just dive in with your own code.
...ant
Re: Contribute to SCA-OSGi integration
On 6/4/07, Rajini Sivaram [EMAIL PROTECTED] wrote: Hello, I would like to contribute to the SCA-OSGi integration activities. I have been looking at the existing OSGi binding implementation in Tuscany which exposes SCA services as OSGi services. Even though this binding is no longer working with the latest Tuscany builds, the samples were very useful to understand the scenarios. I was also looking at the notes on the mailing list (they are slightly old - dated Nov 2006) which talk about an OSGi host and also an OSGi implementation type. Is there any ongoing work in these areas? Graham Charters and I have been investigating the use of an OSGi implementation type which will enable existing OSGi bundles to be run as SCA components under Tuscany. We are particulary interested in the scenario where Tuscany is in control. If components of OSGi implementation type are specified in the composite, Tuscany starts up an OSGi runtime and deploys the OSGi bundles corresponding to the components into the OSGi runtime. If there are references from the OSGi component to other non-OSGi SCA components, a proxy service is registered by the Tuscany runtime with the OSGi registry so that the OSGi bundles can access these SCA services as normal OSGi services. References from non-OSGi components to OSGi components are resolved by looking up the OSGi registry. We would like to obtain feedback on using this approach and also would like to get involved in the ongoing support for SCA-OSGi integration. Thank you... Regards, Rajini Sounds really good to me, though I'm no OSGi expert so I've also CC'd a couple of others who've sounded interested in Tuscany's OSGi support in the past in case they're don't see this on the Tuscany mailing list. One approach would be to just start submitting code as that may prompt further discussion. We can get that added to SVN which makes it easier for you and everyone else, and it doesn't have to be beautiful finished code as we don't need to add it to the main build till you're ready. If you're not so familiar with the Tuscany SPIs yet we could set up a module for you with the standard Tuscany boiler plate stuff already done to help you get started. ...ant
autoexport of confluence wiki
When does the Confluence wiki get autexported to the published Web site? Is it based on change activity, or a schedule? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: autoexport of confluence wiki
Hi Simon, If you are asking for the export from http://cwiki.apache.org/confluence/display/TUSCANY to http://cwiki.apache.org/TUSCANY/ I guess its based on change activity. I am not sure about the export to http://incubator.apache.org/tuscany. Luciano, could you please help with some info on how you did this.. thanks. - Venkat On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote: When does the Confluence wiki get autexported to the published Web site? Is it based on change activity, or a schedule? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: autoexport of confluence wiki
The export from confluence [1] is based on change activity, and pages get exported when you saved them. Then, there is a scheduled cron task that runs about every 15 mins that pull these new contents and publish at [2] that will have a delay of about 45 mins to 1 hour to have it served for the general web community. BTW, I'll write a summary of the website infra structure and post in our wiki, with more details on what is coming from where and this sync details. [1] http://cwiki.apache.org/TUSCANY/ [2] http://incubator.apache.org/tuscany On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi Simon, If you are asking for the export from http://cwiki.apache.org/confluence/display/TUSCANY to http://cwiki.apache.org/TUSCANY/ I guess its based on change activity. I am not sure about the export to http://incubator.apache.org/tuscany. Luciano, could you please help with some info on how you did this.. thanks. - Venkat On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote: When does the Confluence wiki get autexported to the published Web site? Is it based on change activity, or a schedule? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RMI binding SCDL
Hi Ant, I was trying to avoid the uri scheme and thought this to be a sure way to keep out errors - getting explicit inputs for each. But then, this just about manages only the defaults for host and port. So, I am open to implementing your suggestion and understand it could be more consistent with the other bindings. Thanks - Venkat On 6/4/07, ant elder [EMAIL PROTECTED] wrote: As I started documenting the RMI binding SCDL at http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+binding.rmi I wondered if it could use a URI format instead of or as well as the separate host, port, and servicename attributes? There may be some reason its doesn't, has it ever been considered? Along the lines of whats described at http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-rmi.html#RMI, so: binding.rmi uri=rmi://localhost:1099/myservice/ and all those could have defaults so you could just have binding.rmi/ on a service and it would make it available using the component and service name as described in 1.7.2 of the assembly spec. ...ant
Re: Contribute to SCA-OSGi integration
This sounds like a good approach and I would be interested to see an implementation of this in Tuscany. I have a question on having Tuscany in control and starting up the OSGi runtime. I'm no OSGi expert either, but someone once told me that it's hard for OSGi to run inside another runtime that isn't OSGi-aware. Are there any issues here for allowing Tuscany to be embeddable in many environments, not all of which will be OSGi-aware? Simon ant elder wrote: On 6/4/07, Rajini Sivaram [EMAIL PROTECTED] wrote: Hello, I would like to contribute to the SCA-OSGi integration activities. I have been looking at the existing OSGi binding implementation in Tuscany which exposes SCA services as OSGi services. Even though this binding is no longer working with the latest Tuscany builds, the samples were very useful to understand the scenarios. I was also looking at the notes on the mailing list (they are slightly old - dated Nov 2006) which talk about an OSGi host and also an OSGi implementation type. Is there any ongoing work in these areas? Graham Charters and I have been investigating the use of an OSGi implementation type which will enable existing OSGi bundles to be run as SCA components under Tuscany. We are particulary interested in the scenario where Tuscany is in control. If components of OSGi implementation type are specified in the composite, Tuscany starts up an OSGi runtime and deploys the OSGi bundles corresponding to the components into the OSGi runtime. If there are references from the OSGi component to other non-OSGi SCA components, a proxy service is registered by the Tuscany runtime with the OSGi registry so that the OSGi bundles can access these SCA services as normal OSGi services. References from non-OSGi components to OSGi components are resolved by looking up the OSGi registry. We would like to obtain feedback on using this approach and also would like to get involved in the ongoing support for SCA-OSGi integration. Thank you... Regards, Rajini Sounds really good to me, though I'm no OSGi expert so I've also CC'd a couple of others who've sounded interested in Tuscany's OSGi support in the past in case they're don't see this on the Tuscany mailing list. One approach would be to just start submitting code as that may prompt further discussion. We can get that added to SVN which makes it easier for you and everyone else, and it doesn't have to be beautiful finished code as we don't need to add it to the main build till you're ready. If you're not so familiar with the Tuscany SPIs yet we could set up a module for you with the standard Tuscany boiler plate stuff already done to help you get started. ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: autoexport of confluence wiki
Maybe I am doing something wrong. It does not seem to be working as described. I made a small change to http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases This change does not appear to have been exported yet to http://cwiki.apache.org/TUSCANY/sca-java-releases.html My small change was to remove the word The from the start of the first line of text. Any pointers would be gratefully received. Simon Luciano Resende wrote: The export from confluence [1] is based on change activity, and pages get exported when you saved them. Then, there is a scheduled cron task that runs about every 15 mins that pull these new contents and publish at [2] that will have a delay of about 45 mins to 1 hour to have it served for the general web community. BTW, I'll write a summary of the website infra structure and post in our wiki, with more details on what is coming from where and this sync details. [1] http://cwiki.apache.org/TUSCANY/ [2] http://incubator.apache.org/tuscany On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi Simon, If you are asking for the export from http://cwiki.apache.org/confluence/display/TUSCANY to http://cwiki.apache.org/TUSCANY/ I guess its based on change activity. I am not sure about the export to http://incubator.apache.org/tuscany. Luciano, could you please help with some info on how you did this.. thanks. - Venkat On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote: When does the Confluence wiki get autexported to the published Web site? Is it based on change activity, or a schedule? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Contribute to SCA-OSGi integration
Hi, Please see my comments inline below. Thanks, Raymond - Original Message - From: Rajini Sivaram [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Monday, June 04, 2007 7:22 AM Subject: Contribute to SCA-OSGi integration Hello, I would like to contribute to the SCA-OSGi integration activities. That would be great! I have been looking at the existing OSGi binding implementation in Tuscany which exposes SCA services as OSGi services. Even though this binding is no longer working with the latest Tuscany builds, the samples were very useful to understand the scenarios. I was also looking at the notes on the mailing list (they are slightly old - dated Nov 2006) which talk about an OSGi host and also an OSGi implementation type. Is there any ongoing work in these areas? Graham Charters and I have been investigating the use of an OSGi implementation type which will enable existing OSGi bundles to be run as SCA components under Tuscany. We are particulary interested in the scenario where Tuscany is in control. If components of OSGi implementation type are specified in the composite, Tuscany starts up an OSGi runtime and deploys the OSGi bundles corresponding to the components into the OSGi runtime. If there are references from the OSGi component to other non-OSGi SCA components, a proxy service is registered by the Tuscany runtime with the OSGi registry so that the OSGi bundles can access these SCA services as normal OSGi services. References from non-OSGi components to OSGi components are resolved by looking up the OSGi registry. I think you covered two aproaches here: 1) An SCA OSGi Binding can enable interworking between SCA components and OSGi services 2) An SCA OSGi implementation type allows deploying existing OSGi applications/bundles in an SCA domain and using them as SCA components The third aspect would be: OSGi can be used as underlying technology for an SCA container providing an extension mechanism, dependency resolution and service registry capabilities. Which OSGi implementation are you considering? Eclipse Equinox, Apache Felix, or? I did a bit invesigation and it seems that Felix provides a way to be embedded. We would like to obtain feedback on using this approach and also would like to get involved in the ongoing support for SCA-OSGi integration. Thank you... Regards, Rajini - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: autoexport of confluence wiki
I also observe some changes not being reflected on the wiki exported site. Maybe the autoexport is not happening and we might have to do a manual export. Luciano, do you by any chance have administrator priveleges on the wiki to do this ? - Venkat On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote: Maybe I am doing something wrong. It does not seem to be working as described. I made a small change to http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases This change does not appear to have been exported yet to http://cwiki.apache.org/TUSCANY/sca-java-releases.html My small change was to remove the word The from the start of the first line of text. Any pointers would be gratefully received. Simon Luciano Resende wrote: The export from confluence [1] is based on change activity, and pages get exported when you saved them. Then, there is a scheduled cron task that runs about every 15 mins that pull these new contents and publish at [2] that will have a delay of about 45 mins to 1 hour to have it served for the general web community. BTW, I'll write a summary of the website infra structure and post in our wiki, with more details on what is coming from where and this sync details. [1] http://cwiki.apache.org/TUSCANY/ [2] http://incubator.apache.org/tuscany On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi Simon, If you are asking for the export from http://cwiki.apache.org/confluence/display/TUSCANY to http://cwiki.apache.org/TUSCANY/ I guess its based on change activity. I am not sure about the export to http://incubator.apache.org/tuscany. Luciano, could you please help with some info on how you did this.. thanks. - Venkat On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote: When does the Confluence wiki get autexported to the published Web site? Is it based on change activity, or a schedule? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: autoexport of confluence wiki
We would have to work with the Confluence Wiki admins on this, Herman Cunico has been helping us on this. We should also get admins status for members of our community. On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote: I also observe some changes not being reflected on the wiki exported site. Maybe the autoexport is not happening and we might have to do a manual export. Luciano, do you by any chance have administrator priveleges on the wiki to do this ? - Venkat On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote: Maybe I am doing something wrong. It does not seem to be working as described. I made a small change to http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases This change does not appear to have been exported yet to http://cwiki.apache.org/TUSCANY/sca-java-releases.html My small change was to remove the word The from the start of the first line of text. Any pointers would be gratefully received. Simon Luciano Resende wrote: The export from confluence [1] is based on change activity, and pages get exported when you saved them. Then, there is a scheduled cron task that runs about every 15 mins that pull these new contents and publish at [2] that will have a delay of about 45 mins to 1 hour to have it served for the general web community. BTW, I'll write a summary of the website infra structure and post in our wiki, with more details on what is coming from where and this sync details. [1] http://cwiki.apache.org/TUSCANY/ [2] http://incubator.apache.org/tuscany On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi Simon, If you are asking for the export from http://cwiki.apache.org/confluence/display/TUSCANY to http://cwiki.apache.org/TUSCANY/ I guess its based on change activity. I am not sure about the export to http://incubator.apache.org/tuscany. Luciano, could you please help with some info on how you did this.. thanks. - Venkat On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote: When does the Confluence wiki get autexported to the published Web site? Is it based on change activity, or a schedule? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re:
On 5/17/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: snip - any interest in an xslt binding that could take the incoming soap message and transform it to fit a business domain schema to allow for cleaner SDO generated object models? I had a play around with trying to get the script container working with xslt and now I'm not sure the JSR-223 xslt integration is the best approach, so think it would be great to have an xslt extension. Would you still be interested in having a go at that? The latest Tuscany code makes writing an extension quite easy, you could probably start by just copying the existing implementation-script module and changing that for xslt. ...ant
Re: Contribute to SCA-OSGi integration
Hi, As I may have mentioned earlier I also have been working on the SCA-OSGi integration, but from the third aspect that Raymond mentions, using OSGi as an underlying technology for an SCA container providing an extension mechanism, dependency resolution and service registry capabilities. I think my work would dovetail nicely with the work Rajini and Graham have been doing. Would it be possible to create an osgi directory under contrib with a subdir under that for each of our efforts (host, binding, implementation) What do you think? On 6/4/07, Raymond Feng [EMAIL PROTECTED] wrote: ... The third aspect would be: OSGi can be used as underlying technology for an SCA container providing an extension mechanism, dependency resolution and service registry capabilities. Which OSGi implementation are you considering? Eclipse Equinox, Apache Felix, or? I did a bit invesigation and it seems that Felix provides a way to be embedded. We would like to obtain feedback on using this approach and also would like to get involved in the ongoing support for SCA-OSGi integration. Thank you... Regards, Rajini - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Community is a verb, increase your Communitivity today! Visit us at http://Communitivity.com; =Bill.Barnhill, President Communitivity, Inc.
Re: autoexport of confluence wiki
For what I can see so far the update was made on
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
which is included in
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases
The plugin has an issue recognizing these kind of updates (with the {include}
macro). That is dynamically generated content based on the content of a
different page. This issue affects the menus too, with the difference that
menus don't change that often.
The only way around is to manually run an autoexport, which I just did and I
see the changes applied now.
One question though, why are you guys doing such include at that level? in how
many other pages you are using the same content from SCA+Java+0.90-incubating?
Cheers!
Hernan
Venkata Krishnan wrote:
I also observe some changes not being reflected on the wiki exported site.
Maybe the autoexport is not happening and we might have to do a manual
export. Luciano, do you by any chance have administrator priveleges on the
wiki to do this ?
- Venkat
On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote:
Maybe I am doing something wrong. It does not seem to be working
as described. I made a small change to
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases
This change does not appear to have been exported yet to
http://cwiki.apache.org/TUSCANY/sca-java-releases.html
My small change was to remove the word The from the start of the
first line of text.
Any pointers would be gratefully received.
Simon
Luciano Resende wrote:
The export from confluence [1] is based on change activity, and pages
get exported when you saved them. Then, there is a scheduled cron task
that runs about every 15 mins that pull these new contents and publish
at [2] that will have a delay of about 45 mins to 1 hour to have it
served for the general web community. BTW, I'll write a summary of the
website infra structure and post in our wiki, with more details on
what is coming from where and this sync details.
[1] http://cwiki.apache.org/TUSCANY/
[2] http://incubator.apache.org/tuscany
On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi Simon,
If you are asking for the export from
http://cwiki.apache.org/confluence/display/TUSCANY to
http://cwiki.apache.org/TUSCANY/ I guess its based on change
activity. I am
not sure about the export to http://incubator.apache.org/tuscany.
Luciano, could you please help with some info on how you did this..
thanks.
- Venkat
On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote:
When does the Confluence wiki get autexported to the published
Web site? Is it based on change activity, or a schedule?
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Java SDO] - How to load/save xsd:QName property?
I believe we have a bug in loading/saviing xsd:QName property value. Based on SDO 2.1 spec section 9.4.1, proper conversion should take place. Unfortunately, Tuscany SDO is not doing any conversion today. If no one objects, I will open a JIRA. When I started to look into possible solution for this problem, I discovered both xsd:anyURI and xsd:QName are mapped to SDO URI type. This is similar to JIRA 1223 Frank has fixed for xsd:base64Binary and xsd:hexBinary. I think we can copy what 1223 has done by internally mapping xsd:QName to SDO QName type then in the SDOXMLResourceImpl$SDOXMLHelperImpl, override createFromString and convertToString for deserialization and serialization respectively. Let me know if this proposed solution makes sense. Fuhwei
Re: [Java SDO] - How to load/save xsd:QName property?
Handling this in the same way as we handled base64Binary sounds right to me. We didn't override createFromString and convertToString, however. We simply mapped internally to the EMF base64Binary type and let EMF handle it in its default way. Note that the code to make this work is in AttributeImpl.getType() and in SDOXSDEcoreBuilder.getBuiltInEClassifier(). Thanks, Frank. Fuhwei Lwo [EMAIL PROTECTED] wrote on 06/04/2007 04:23:15 PM: I believe we have a bug in loading/saviing xsd:QName property value. Based on SDO 2.1 spec section 9.4.1, proper conversion should take place. Unfortunately, Tuscany SDO is not doing any conversion today. If no one objects, I will open a JIRA. When I started to look into possible solution for this problem, I discovered both xsd:anyURI and xsd:QName are mapped to SDO URI type. This is similar to JIRA 1223 Frank has fixed for xsd:base64Binary and xsd:hexBinary. I think we can copy what 1223 has done by internally mapping xsd:QName to SDO QName type then in the SDOXMLResourceImpl$SDOXMLHelperImpl, override createFromString and convertToString for deserialization and serialization respectively. Let me know if this proposed solution makes sense. Fuhwei - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: autoexport of confluence wiki
HI Hernan, thanks for running the export.
The contents of a release page like 'SCA+Java+0.90-incubating' get to be
used in two contexts - 1. when it is a latest release and 2. when it has
become a previous release'. Instead of duplicating the release content for
each of these contexts I thought of abstracting it out as a page and simply
including it when its a Latest Release and just linking to it when it has
become a Previous Release.
Like the Menus I suppose these pages will not change once they are made.
Do you have suggestions on a better way of doing this ?
Also, I see that the html export does not show the table borders, atleast on
my display - not sure if others are seeing this as well. Any clue on how we
could fix this ?
Thanks
- Venkat
On 6/5/07, Hernan Cunico [EMAIL PROTECTED] wrote:
For what I can see so far the update was made on
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
which is included in
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases
The plugin has an issue recognizing these kind of updates (with the
{include} macro). That is dynamically generated content based on the content
of a different page. This issue affects the menus too, with the difference
that menus don't change that often.
The only way around is to manually run an autoexport, which I just did and
I see the changes applied now.
One question though, why are you guys doing such include at that level? in
how many other pages you are using the same content from
SCA+Java+0.90-incubating?
Cheers!
Hernan
Venkata Krishnan wrote:
I also observe some changes not being reflected on the wiki exported
site.
Maybe the autoexport is not happening and we might have to do a manual
export. Luciano, do you by any chance have administrator priveleges on
the
wiki to do this ?
- Venkat
On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote:
Maybe I am doing something wrong. It does not seem to be working
as described. I made a small change to
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases
This change does not appear to have been exported yet to
http://cwiki.apache.org/TUSCANY/sca-java-releases.html
My small change was to remove the word The from the start of the
first line of text.
Any pointers would be gratefully received.
Simon
Luciano Resende wrote:
The export from confluence [1] is based on change activity, and pages
get exported when you saved them. Then, there is a scheduled cron
task
that runs about every 15 mins that pull these new contents and
publish
at [2] that will have a delay of about 45 mins to 1 hour to have it
served for the general web community. BTW, I'll write a summary of
the
website infra structure and post in our wiki, with more details on
what is coming from where and this sync details.
[1] http://cwiki.apache.org/TUSCANY/
[2] http://incubator.apache.org/tuscany
On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi Simon,
If you are asking for the export from
http://cwiki.apache.org/confluence/display/TUSCANY to
http://cwiki.apache.org/TUSCANY/ I guess its based on change
activity. I am
not sure about the export to http://incubator.apache.org/tuscany.
Luciano, could you please help with some info on how you did this..
thanks.
- Venkat
On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote:
When does the Confluence wiki get autexported to the published
Web site? Is it based on change activity, or a schedule?
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: autoexport of confluence wiki
We are using News for this kind of stuff. We categorize the news with labels and then we selectively display the info. See http://geronimo.apache.org/
As for the tables, well, that's something gone wrong in the css. Open the
default.css you guys are using and look for this entry
table.confluenceTable td.confluenceTd
make sure you replace this
{ padding: 0 4px 3px; }
with this
{ padding: 0 4px 3px; border: solid 1px #b4b4b5; }
If you guys prefer a JIRA let me know and I'll create one with a diff, but was
just 1/2 a line anyway ;-)
Cheers!
Hernan
Venkata Krishnan wrote:
HI Hernan, thanks for running the export.
The contents of a release page like 'SCA+Java+0.90-incubating' get to be
used in two contexts - 1. when it is a latest release and 2. when it has
become a previous release'. Instead of duplicating the release content for
each of these contexts I thought of abstracting it out as a page and simply
including it when its a Latest Release and just linking to it when it has
become a Previous Release.
Like the Menus I suppose these pages will not change once they are made.
Do you have suggestions on a better way of doing this ?
Also, I see that the html export does not show the table borders,
atleast on
my display - not sure if others are seeing this as well. Any clue on
how we
could fix this ?
Thanks
- Venkat
On 6/5/07, Hernan Cunico [EMAIL PROTECTED] wrote:
For what I can see so far the update was made on
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
which is included in
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases
The plugin has an issue recognizing these kind of updates (with the
{include} macro). That is dynamically generated content based on the
content
of a different page. This issue affects the menus too, with the
difference
that menus don't change that often.
The only way around is to manually run an autoexport, which I just did
and
I see the changes applied now.
One question though, why are you guys doing such include at that
level? in
how many other pages you are using the same content from
SCA+Java+0.90-incubating?
Cheers!
Hernan
Venkata Krishnan wrote:
I also observe some changes not being reflected on the wiki exported
site.
Maybe the autoexport is not happening and we might have to do a manual
export. Luciano, do you by any chance have administrator priveleges on
the
wiki to do this ?
- Venkat
On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote:
Maybe I am doing something wrong. It does not seem to be working
as described. I made a small change to
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases
This change does not appear to have been exported yet to
http://cwiki.apache.org/TUSCANY/sca-java-releases.html
My small change was to remove the word The from the start of the
first line of text.
Any pointers would be gratefully received.
Simon
Luciano Resende wrote:
The export from confluence [1] is based on change activity, and
pages
get exported when you saved them. Then, there is a scheduled cron
task
that runs about every 15 mins that pull these new contents and
publish
at [2] that will have a delay of about 45 mins to 1 hour to have it
served for the general web community. BTW, I'll write a summary of
the
website infra structure and post in our wiki, with more details on
what is coming from where and this sync details.
[1] http://cwiki.apache.org/TUSCANY/
[2] http://incubator.apache.org/tuscany
On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi Simon,
If you are asking for the export from
http://cwiki.apache.org/confluence/display/TUSCANY to
http://cwiki.apache.org/TUSCANY/ I guess its based on change
activity. I am
not sure about the export to http://incubator.apache.org/tuscany.
Luciano, could you please help with some info on how you did this..
thanks.
- Venkat
On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote:
When does the Confluence wiki get autexported to the published
Web site? Is it based on change activity, or a schedule?
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: autoexport of confluence wiki
Thanks Herman,
I have fixed the table border issue and this should get to the live
website soon.
On 6/4/07, Hernan Cunico [EMAIL PROTECTED] wrote:
We are using News for this kind of stuff. We categorize the news with labels
and then we selectively display the info. See http://geronimo.apache.org/
As for the tables, well, that's something gone wrong in the css. Open the
default.css you guys are using and look for this entry
table.confluenceTable td.confluenceTd
make sure you replace this
{ padding: 0 4px 3px; }
with this
{ padding: 0 4px 3px; border: solid 1px #b4b4b5; }
If you guys prefer a JIRA let me know and I'll create one with a diff, but was
just 1/2 a line anyway ;-)
Cheers!
Hernan
Venkata Krishnan wrote:
HI Hernan, thanks for running the export.
The contents of a release page like 'SCA+Java+0.90-incubating' get to be
used in two contexts - 1. when it is a latest release and 2. when it has
become a previous release'. Instead of duplicating the release content for
each of these contexts I thought of abstracting it out as a page and simply
including it when its a Latest Release and just linking to it when it has
become a Previous Release.
Like the Menus I suppose these pages will not change once they are made.
Do you have suggestions on a better way of doing this ?
Also, I see that the html export does not show the table borders,
atleast on
my display - not sure if others are seeing this as well. Any clue on
how we
could fix this ?
Thanks
- Venkat
On 6/5/07, Hernan Cunico [EMAIL PROTECTED] wrote:
For what I can see so far the update was made on
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
which is included in
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases
The plugin has an issue recognizing these kind of updates (with the
{include} macro). That is dynamically generated content based on the
content
of a different page. This issue affects the menus too, with the
difference
that menus don't change that often.
The only way around is to manually run an autoexport, which I just did
and
I see the changes applied now.
One question though, why are you guys doing such include at that
level? in
how many other pages you are using the same content from
SCA+Java+0.90-incubating?
Cheers!
Hernan
Venkata Krishnan wrote:
I also observe some changes not being reflected on the wiki exported
site.
Maybe the autoexport is not happening and we might have to do a manual
export. Luciano, do you by any chance have administrator priveleges on
the
wiki to do this ?
- Venkat
On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote:
Maybe I am doing something wrong. It does not seem to be working
as described. I made a small change to
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Releases
This change does not appear to have been exported yet to
http://cwiki.apache.org/TUSCANY/sca-java-releases.html
My small change was to remove the word The from the start of the
first line of text.
Any pointers would be gratefully received.
Simon
Luciano Resende wrote:
The export from confluence [1] is based on change activity, and
pages
get exported when you saved them. Then, there is a scheduled cron
task
that runs about every 15 mins that pull these new contents and
publish
at [2] that will have a delay of about 45 mins to 1 hour to have it
served for the general web community. BTW, I'll write a summary of
the
website infra structure and post in our wiki, with more details on
what is coming from where and this sync details.
[1] http://cwiki.apache.org/TUSCANY/
[2] http://incubator.apache.org/tuscany
On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi Simon,
If you are asking for the export from
http://cwiki.apache.org/confluence/display/TUSCANY to
http://cwiki.apache.org/TUSCANY/ I guess its based on change
activity. I am
not sure about the export to http://incubator.apache.org/tuscany.
Luciano, could you please help with some info on how you did this..
thanks.
- Venkat
On 6/4/07, Simon Nash [EMAIL PROTECTED] wrote:
When does the Confluence wiki get autexported to the published
Web site? Is it based on change activity, or a schedule?
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
SDO C++ loading data from XML
Is there a way to load data from a XML file without a XML schema file, only defining the graph type and properties manually on code? The code bellow works: DataFactoryPtr dataFactory = DataFactory::getDataFactory(); XSDHelperPtr xsdh = HelperProvider::getXSDHelper(dataFactory); xsdh-defineFile(config.xsd); XMLHelperPtr xmlh = HelperProvider::getXMLHelper(dataFactory); XMLDocumentPtr doc = xmlh-loadFile( config.xml); DataObjectPtr root = doc-getRootDataObject(); But when I defining manually the graph struct it does not: DataFactoryPtr dataFactory = DataFactory::getDataFactory(); dataFactory-addType(DAS_NAMESPACE, Table); const Type table = dataFactory-getType(DAS_NAMESPACE, Table); dataFactory-addPropertyToType(table, tableName, SDO_NAMESPACE, String, false, false, true); dataFactory-addPropertyToType(table, typeName, SDO_NAMESPACE, String, false, false, true); dataFactory-resolve(); XMLHelperPtr xmlh = HelperProvider::getXMLHelper(dataFactory); XMLDocumentPtr doc = xmlh-loadFile(config.xml, DAS_NAMESPACE); DataObjectPtr root = doc-getRootDataObject(); // the root data object returned is NULL Adriano Crestani
Re: Website - Consistent navigation menus
Hi, Website update is done. Below is the draft of 'cwiki development guide' that lays out the tree structure for cwiki. http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+cwiki+Development+Guideline Can we update it with your suggestions and once an agreement is reached make it the development guide for cwiki. It was very difficult to organize the content and I am sure it'll get into the same shape if we don't all follow some agreed to guidelines. Work remaining: - Convert the old download pages to the new format. Thanks Venkat for your help thus far for moving the content from the old style to the new style. - There is a lot of in-progress documentation. Are any of these ready to be added to the list of documentations for each project? Haleh On 6/2/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi Haleh, please see my comments inline. Thanks - Venkat On 6/1/07, haleh mahbod [EMAIL PROTECTED] wrote: I don't see a difference and in fact it is more work. In today's mode: you update one page. a) update Latest release b) move the old release to previous releases. (Note: I think previous releases should be on the same page). For every release I suppose we will have alteast 1 or 1.5 pages of information i.e. the release related info and the two tables. Do you mean we move all of this to the 'Previous Release' section. If we did this by the end of this year we will have several pages to scroll down to. In your proposal: Have a page for each release and then link it back to latest releases page. Yes.. the pages are short and concise. There is just about a list of releases and the user can choose any one and then get to read up what the release contains and what is downloadable on a diff. pages. This is not much overhead - what is more is just a couple of lines. Are we making this too complicated? My preference would be to convert the table we currently have into something readable that has a link to readme for the release on the same page. I'll add a sample to the page so we can take a look. On 6/1/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi Haleh, I am trying to re-org the downloads / release page for the following reason :-- Currently the SCA Release pages points to two things i) Latest Release ii) Previous Releases. In the Latest Release section we have hardcoded the content for the 0.90 release. This is something we will have to revisit every time we make a release and then the content there has to be moved over as well. i.e. for 0.91 we will have to edit this page and then move the contents of 0.90 else where. To help this to be a bit smooth, I suggest that for every release we create a separate page i.e. a page for 0.90, a page for 0.91 and so on. Then in the SCA Releases page we simply 'inlcude' the relevant page under the 'Latest Release' section. For the section on Previous Releases, I suggest that we put up a table/list of links to all the previous release pages. So when there is 0.91, we simply include 0.91 page to the 'Latest Release' section and then include ' 0.90' page to the 'Previous Releases' list. I feel this is maintainable in the long run. Hope I am no missing something in all of this - Venkat On 6/1/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi Kelvin, I've just added one more menu item 'SCA Java Home' to link back to the home page of the subproject. Will do the same for DAS and SDO as well, now. Also I am going to see if we can get the other downloads pages (M2 ones) to look the same as the current one. - Venkat On 6/1/07, kelvin goodson [EMAIL PROTECTED] wrote: Haleh, this looks really good, thanks. I particularly like the Latest Tuscany Releases inset box and the new download page layout. The sub-project menu doesn't provide a link back to the sub-project's home. Would it be possible to make the title of the sub-project menu to be a link back to the sub-project's home? Regards, Kelvin. On 01/06/07, haleh mahbod [EMAIL PROTECTED] wrote: Hi, The left navigation bar used to change as we navigated through pages. We also had a discussion around wanting a release page per subproject on the subproject page. Based on these comments, I have made the following updates for SCA Java for now. If it looks good, I'll go ahead and make the updates for other subprojects. - Left Menu remains consistent for Home page and Overview pages for all subprojects. Home and Overview pages are considered Tuscany General pages. Example: The following pages have the same navigation on the left. http://cwiki.apache.org/confluence/display/TUSCANY/Home http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Overview - The general information on the home page applies to the whole
