[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to convert DataObjects to and from Java objects
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549058 ] Kelvin Goodson commented on TUSCANY-1493: - I've just made some observations on the tuscany-user mailing list which should appear in the mailing list archives shortly, under the thread that contains http://www.mail-archive.com/[EMAIL PROTECTED]/msg02162.html Snapshot mapping framework to convert DataObjects to and from Java objects -- Key: TUSCANY-1493 URL: https://issues.apache.org/jira/browse/TUSCANY-1493 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: agfasdo.tar.gz, sdo-snapshot.zip, sdo.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa). To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts. - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly. - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects). - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily. This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion. I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component. -- 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] Resolved: (TUSCANY-1545) Change default XML encoding to UTF-8.
[ https://issues.apache.org/jira/browse/TUSCANY-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1545. - Resolution: Fixed Patch applied, thanks David. Change default XML encoding to UTF-8. Key: TUSCANY-1545 URL: https://issues.apache.org/jira/browse/TUSCANY-1545 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-1.0 Reporter: Frank Budinsky Priority: Minor Fix For: Java-SDO-Next Attachments: 1545.patch XMLHelper.save() uses ASCII encoding by default, but the spec says the default encoding is UTF-8. -- 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: [Java SDO] What should we be attacking?
David, thanks for the fixes. I'll apply them as soon as I can get to them. I've been away unwell for most of the last weeks so I have some catching up to do. Anything you can do to reduce the JIRA backlog further would be great, thanks. Kelvin. On 29/11/2007, David Adcox [EMAIL PROTECTED] wrote: Kelvin, I have some free cycles, so I'd like to help knock some things off this list for you. I've gone ahead and contributed a patch for 1483. I'll address 1545 as well. I believe that 1384 is already done. On Nov 20, 2007 6:36 AM, kelvin goodson [EMAIL PROTECTED] wrote: What should we be concentrating our efforts on in SDO Java. I posted a while back to suggest we think about the content of a next release. We've had a few fixes go in recently, but I'd like to see more consideration of release content before we crank the handle. It would be great to see a balance of new features and bug fixes. For my part I want to get back to ... TUSCANY-1527Allow for custom data binding of DataObjects in a Swing UI TUSCANY-1493Snapshot mapping framework to convert DataObjects to and from Java objects as soon as I can. And I believe that at least 1527 can move beyond proof of concept in my sandbox, and become part of the trunk. I've been taking a pass through the SDO java JIRA backlog, and seeing from my perspective what's simple / tricky / big / high priority etc, etc. Of course simplicity is in the eye of the beholder, for example, I don't view the OSGi topic as simple as I don't have experience there, but someone out there may find it so; if so please speak up. The same goes for priority, etc. As you might imagine, in my estimation there are no simple high priority JIRAs left, but there are a few simple medium priority ones, or simple low priority ones that would be good to just get out of the way. These are Simple Starters === TUSCANY-1360New SDOUtil: Getting the enumeration facet TUSCANY-1178DynamicTypesFromSchemaTestCase expecting *Object types to be created TUSCANY-1263XMLEqualityChecker too strict TUSCANY-1359New SDOUtil: Upper and lower bound on properties where 'isMany' is true TUSCANY-1384SequenceAddOpenTest.setUp() needs to check if type exists before creating it TUSCANY-1545Change default XML encoding to UTF-8. TUSCANY-1659SDO DateConversion test cases fail under linux Particular Skills JIRAs = For anyone with JavaJet experience there's TUSCANY-1483Static SDO generator: problem with elements named internal* which would be simple For someone with maven build experience there TUSCANY-257 recently added file Interface2JavaGenerator.java is not compatible with JDK 1.4 For someone with Grobu-Utils and maven skills there's ... TUSCANY-1182Add multi-threaded test case for data object creation Someone with Axis2 skills TUSCANY-1038SDO databinding for Axis2 (This may be better done within the Axis2 project) OSGi Skills TUSCANY-1293SDO does not work with OSGi Biting off something a bit Bigger For somebody wanting something a bit bigger to take on there's TUSCANY-1192Preserve demand created global properties TUSCANY-1361New Util: Validation TUSCANY-1021CopyHelper and EqualityHelper should handle ChangeSummary TUSCANY-1817Improve SDO test infrastructure to re-use/re-execute most dynamic tests as static tests This isn't a full list, and I may post more soon. Please feel free to disagree with my assessment and speak up with your own priorities. Better still step forward to help fix something. I'd be only too pleased to help you understand what's required. Kelvin. - 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]
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to convert DataObjects to and from Java objects
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544782 ] Kelvin Goodson commented on TUSCANY-1493: - Kris, I downloaded and manually installed the eclipse core and osgi dependencies at the appropriate level into my maven repository. Currently I'm getting more eclipse missing classes such as IExtension, which I guess is because the eclipse artifacts have transitive dependencies which would be known if maven had installed the artifacts itself. I'm guessing you have a repository in your settings.xml file for maven that can resolve these artifacts automatically. I can continue to dig out jars and manually install them into my repo until all requirements are resolved, but if you happen to be able to point me at a maven repo to do the job automatically that would be great, thanks. Snapshot mapping framework to convert DataObjects to and from Java objects -- Key: TUSCANY-1493 URL: https://issues.apache.org/jira/browse/TUSCANY-1493 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: agfasdo.tar.gz, sdo-snapshot.zip, sdo.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa). To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts. - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly. - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects). - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily. This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion. I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component. -- 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] Commented: (TUSCANY-1293) SDO does not work with OSGi
[ https://issues.apache.org/jira/browse/TUSCANY-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544420 ] Kelvin Goodson commented on TUSCANY-1293: - There's an offer of help from Rajini to get this fixed that's current on the tuscany-dev mailing list. I'm actively trying to help Rajini with her request for info, but if anyone watching this JRIA wan't to pitch in, please do so. See http://marc.info/?l=tuscany-devm=119563682818977w=2 SDO does not work with OSGi --- Key: TUSCANY-1293 URL: https://issues.apache.org/jira/browse/TUSCANY-1293 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-beta1 Environment: OS X Eclipse 3.3 M7 Reporter: Bryan Hunt Priority: Blocker Fix For: Java-SDO-Next When I execute: XSDHelper.INSTANCE.define(schema, null); I end up with a NullPointerException. I've tracked down root cause ... The static initializer of the HelperProvider executes this code: provider = getInstance(HelperProvider.class.getClassLoader()); which ends up calling: HelperProvider provider = loadImplementation(cl, implName); implName is null so if (implName == null) { implName = getImplementationName(cl); } ends up calling implName = getImplementationName(cl); which ends up calling: InputStream is = cl.getResourceAsStream(SERVICE_RESOURCE_NAME); where SERVICE_RESORUCE_NAME = META-INF/services/commonj.sdo.impl.HelperProvider getResourceAsStream() return null because META-INF/services does not exist in the API bundle. It exists in the IMPL bundle and since you are using the class loader from the API bundle, it won't work. You can set -Dcommonj.sdo.impl.HelperProvider=org.apache.tuscany.sdo.helper.HelperProviderImpl to get around the above problem, but as soon as return (HelperProvider) cl.loadClass(implName).newInstance(); executes, you get a CalssNotFoundException. Again, this is because you are trying to load a class outside the bundle with the wrong class loader. tried modifying the API manifest by hand to add Eclipse-BuddyPolicy: dependent and Eclipse-BuddyPolicy: global Either of those buddy policies will get past the class loader problem (although I believe this is specific to eclipse and won't work for OSGi in general), but when HelperProvider is initializing, you get the following exception: java.lang.ExceptionInInitializerError at org.apache.tuscany.sdo.impl.AttributeImpl.clinit(AttributeImpl.java:126) at org.apache.tuscany.sdo.impl.SDOFactoryImpl.createAttribute(SDOFactoryImpl.java:239) at org.apache.tuscany.sdo.impl.ClassImpl.clinit(ClassImpl.java:68) at org.apache.tuscany.sdo.impl.SDOFactoryImpl$SDOEcoreFactory.createEClass(SDOFactoryImpl.java:76) at org.apache.tuscany.sdo.impl.SDOPackageImpl.createEClass(SDOPackageImpl.java:622) at org.apache.tuscany.sdo.impl.SDOPackageImpl.createPackageContents(SDOPackageImpl.java:550) at org.apache.tuscany.sdo.impl.SDOPackageImpl.init(SDOPackageImpl.java:259) at org.apache.tuscany.sdo.SDOPackage.clinit(SDOPackage.java:76) at sun.misc.Unsafe.ensureClassInitialized(Native Method) at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25) at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122) at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917) at java.lang.reflect.Field.getFieldAccessor(Field.java:898) at java.lang.reflect.Field.get(Field.java:357) at org.apache.tuscany.sdo.util.SDOUtil.registerStaticTypes(SDOUtil.java:196) at org.apache.tuscany.sdo.model.impl.ModelFactoryImpl.init(ModelFactoryImpl.java:731) at org.apache.tuscany.sdo.model.ModelFactory.clinit(ModelFactory.java:41) at org.apache.tuscany.sdo.helper.TypeHelperImpl.getBuiltInModels(TypeHelperImpl.java:61) at org.apache.tuscany.sdo.helper.TypeHelperImpl.init(TypeHelperImpl.java:79) at org.apache.tuscany.sdo.helper.HelperContextImpl.init(HelperContextImpl.java:46) at org.apache.tuscany.sdo.helper.HelperProviderImpl.createDefaultHelpers(HelperProviderImpl.java:38) at org.apache.tuscany.sdo.rtlib.helper.HelperProviderBase.init(HelperProviderBase.java:78) at org.apache.tuscany.sdo.helper.HelperProviderImpl.init(HelperProviderImpl.java:31) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at commonj.sdo.impl.HelperProvider.loadImplementation
Re: [Java SDO] What should we be attacking?
Rajini, Many thanks for your offer of help here!. We don't have documentation on this, but I hope as a community we can develop it. I have created a page in the wiki to begin organising our thoughts [0]. My problem is I don't have sufficient feel for the issues in OSGi to understand how best to approach documenting SDO's class loader usage. I imagine it's a reasonable assumption that the only place where we could violate constraints imposed by working in an OSGi environment would be the places where SDO touches the ClassLoader interface. I'll put some words around what seems to be happening in each of those places in the SDO code. We only have 3 relevant places where the ClassLoader interface is imported in the SDO code (+1 test case which may add to our understanding) DefaultHelperContextImpl [1] XSDHelperImpl [2] DataObjectUtil [3] ByteCodeInterfaceGeneratorTestCase [4] (Note: I'm part way through my investigation here, but in the interests of responding in a timely manner and paving the way for people to chip in and save me the trouble of researching the issues, I'm going to post this without having completed the researches, and then continue to research it) .. more to investigate ... The ClassLoader code that is currently in DataObjectUtil (which originates from Tuscany-1110 and was originally in TypeHelperImpl). It is there to support the retrieval of the SDO type represented by a generated Java interface/class, and this is performed by introspection of the supplied interface/class. Kelvin. [0] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SDO+Java+Documentation+in+Preparation [1] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/DefaultHelperContextImpl.java [2] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/XSDHelperImpl.java [3] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/util/DataObjectUtil.java [4] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/impl/src/test/java/org/apache/tuscany/sdo/codegen/BytecodeInterfaceGeneratorTestCase.java On 21/11/2007, Rajini Sivaram [EMAIL PROTECTED] wrote: Kelvin, I ran into the same NPE as TUSCANY-1293 yesterday when running Tuscany SCA under OSGi. I would be very keen to see this fixed so that SCA databinding-sdo can be used under OSGi. I will be happy to help with the classloading/OSGi issues, but I have no understanding of the architecture of SDO. If there is some documentation on the classloading architecture for SDO, I can take a look. The classloading hierarchy that is causing the problem in SDO is the same as the one we had with SCA, but unless I understand the classloading in SDO, I can't be sure if we can adopt a similar solution as the one used now in SCA. Thank you... Regards, Rajini On 11/20/07, kelvin goodson [EMAIL PROTECTED] wrote: What should we be concentrating our efforts on in SDO Java. I posted a while back to suggest we think about the content of a next release. We've had a few fixes go in recently, but I'd like to see more consideration of release content before we crank the handle. It would be great to see a balance of new features and bug fixes. For my part I want to get back to ... TUSCANY-1527Allow for custom data binding of DataObjects in a Swing UI TUSCANY-1493Snapshot mapping framework to convert DataObjects to and from Java objects as soon as I can. And I believe that at least 1527 can move beyond proof of concept in my sandbox, and become part of the trunk. I've been taking a pass through the SDO java JIRA backlog, and seeing from my perspective what's simple / tricky / big / high priority etc, etc. Of course simplicity is in the eye of the beholder, for example, I don't view the OSGi topic as simple as I don't have experience there, but someone out there may find it so; if so please speak up. The same goes for priority, etc. As you might imagine, in my estimation there are no simple high priority JIRAs left, but there are a few simple medium priority ones, or simple low priority ones that would be good to just get out of the way. These are Simple Starters === TUSCANY-1360New SDOUtil: Getting the enumeration facet TUSCANY-1178DynamicTypesFromSchemaTestCase expecting *Object types to be created TUSCANY-1263XMLEqualityChecker too strict TUSCANY-1359New SDOUtil: Upper and lower bound on properties where 'isMany' is true TUSCANY-1384SequenceAddOpenTest.setUp() needs to check if type exists before creating it TUSCANY-1545Change default XML encoding to UTF-8. TUSCANY-1659SDO DateConversion test cases fail under linux Particular Skills JIRAs = For anyone with JavaJet experience there's TUSCANY-1483Static SDO generator
[Java SDO] What should we be attacking?
What should we be concentrating our efforts on in SDO Java. I posted a while back to suggest we think about the content of a next release. We've had a few fixes go in recently, but I'd like to see more consideration of release content before we crank the handle. It would be great to see a balance of new features and bug fixes. For my part I want to get back to ... TUSCANY-1527Allow for custom data binding of DataObjects in a Swing UI TUSCANY-1493Snapshot mapping framework to convert DataObjects to and from Java objects as soon as I can. And I believe that at least 1527 can move beyond proof of concept in my sandbox, and become part of the trunk. I've been taking a pass through the SDO java JIRA backlog, and seeing from my perspective what's simple / tricky / big / high priority etc, etc. Of course simplicity is in the eye of the beholder, for example, I don't view the OSGi topic as simple as I don't have experience there, but someone out there may find it so; if so please speak up. The same goes for priority, etc. As you might imagine, in my estimation there are no simple high priority JIRAs left, but there are a few simple medium priority ones, or simple low priority ones that would be good to just get out of the way. These are Simple Starters === TUSCANY-1360New SDOUtil: Getting the enumeration facet TUSCANY-1178DynamicTypesFromSchemaTestCase expecting *Object types to be created TUSCANY-1263XMLEqualityChecker too strict TUSCANY-1359New SDOUtil: Upper and lower bound on properties where 'isMany' is true TUSCANY-1384SequenceAddOpenTest.setUp() needs to check if type exists before creating it TUSCANY-1545Change default XML encoding to UTF-8. TUSCANY-1659SDO DateConversion test cases fail under linux Particular Skills JIRAs = For anyone with JavaJet experience there's TUSCANY-1483Static SDO generator: problem with elements named internal* which would be simple For someone with maven build experience there TUSCANY-257 recently added file Interface2JavaGenerator.java is not compatible with JDK 1.4 For someone with Grobu-Utils and maven skills there's ... TUSCANY-1182Add multi-threaded test case for data object creation Someone with Axis2 skills TUSCANY-1038SDO databinding for Axis2 (This may be better done within the Axis2 project) OSGi Skills TUSCANY-1293SDO does not work with OSGi Biting off something a bit Bigger For somebody wanting something a bit bigger to take on there's TUSCANY-1192Preserve demand created global properties TUSCANY-1361New Util: Validation TUSCANY-1021CopyHelper and EqualityHelper should handle ChangeSummary TUSCANY-1817Improve SDO test infrastructure to re-use/re-execute most dynamic tests as static tests This isn't a full list, and I may post more soon. Please feel free to disagree with my assessment and speak up with your own priorities. Better still step forward to help fix something. I'd be only too pleased to help you understand what's required. Kelvin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to write a simple SDO class for the tutorial?
Sebastien, There's the basis of a Java interface to SDO generator at [1] but it hasn't been developed to a working state and hasn't been looked since the initial drop of code into Tuscany. It would be great to get this or similar function up and running. If you take a look at the noInterfaces test [2] of the toolsTest project you'll see that we don't need interfaces, we can use classes. I think in the scenario that you paint it's just abut possible you may just about be able to get away without a factory. As evidence I changes the referenced sample [2] to have //com.example.noInterfaces.simple.Quote quote = //(com.example.noInterfaces.simple.Quote)scope.getDataFactory().create(com.example.noInterfaces.simple.Quote.class); com.example.noInterfaces.simple.Quote quote = new Quote(); and the test passed. But this wouldn't be acceptable in general. The major showstopper that occurs to me instantly is having a Type that has a Property of a generated Type. so the call to myComplexType.createDataObject(myPropertyOfGeneratedType); must have a means to create a child DataObject using the generated class rather than the generic DataObject. It does this by maintaining an association with the Type of the Property and the associated Factory. Regards, Kelvin. [1] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/Interface2JavaGenerator.java [2] http://svn.apache.org/viewvc/incubator/tuscany/java/sdo/tools-test/src/test/java/org/apache/tuscany/sdo/test/GenPatternsTestCase.java?view=markup On 17/11/2007, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: kelvin goodson wrote: If you are discounting using XSD for the source of metadata to describe the SDO types then there is the SDO API provided for dynamic metadata creation. The sample at [1] gives an introduction to this. The paper at [2] discusses the subject also, and the program underlying the discussion in the paper is at [3] (no change monitoring) and [4] (with change monitoring). You say that you want to write the minimum code. There is a quick and simple Tuscany API for simple cases that you could use instead (See the MetaDataBuilder inner class in [5]). Whilst the code to create the type system with this project specific API is simple to understand and implement it has some drawbacks. We don't have a sample program for this, but I believe the DAS uses it) I'm happy to discuss further if you want some more insight into this. Kelvin. [1] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/intermediate/DynamicCustomerTypeSample.java [2] http://java.sys-con.com/read/358059_2.htm [3] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/advanced/MedicalScenario.java [4] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/advanced/MedicalScenarioWithChangeMonitoring.java [5] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/lib/src/main/java/org/apache/tuscany/sdo/api/SDOHelper.java Thanks. Follow-up questions: - Is there an SDO Helper that can introspect my handwritten Item Java class and drive the calls to the TypeHelper APIs? If not, can I add one? - I see that I can associate a class with a type, does it have to be an interface or can it be a class? - If it can be a class do I really need a factory class or is the SDO runtime able to instantiate the class? - I see methods like getStaticType on generated SDOs, do I need to implement that method in my handwritten SDO and why? -- Jean-Sebastien - 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: How to write a simple SDO class for the tutorial?
I missed you last point in my reply. getStaticType() is required to underpin fundamental EMF behaviour. Without it EMF's capacity to know the class of an EObject (which all our DataObjects are derived from) is broken for all static classes, and that would break many SDO behaviours, e.g. serialization, copying, and I'm sure lots more. Kelvin. On 17/11/2007, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: kelvin goodson wrote: If you are discounting using XSD for the source of metadata to describe the SDO types then there is the SDO API provided for dynamic metadata creation. The sample at [1] gives an introduction to this. The paper at [2] discusses the subject also, and the program underlying the discussion in the paper is at [3] (no change monitoring) and [4] (with change monitoring). You say that you want to write the minimum code. There is a quick and simple Tuscany API for simple cases that you could use instead (See the MetaDataBuilder inner class in [5]). Whilst the code to create the type system with this project specific API is simple to understand and implement it has some drawbacks. We don't have a sample program for this, but I believe the DAS uses it) I'm happy to discuss further if you want some more insight into this. Kelvin. [1] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/intermediate/DynamicCustomerTypeSample.java [2] http://java.sys-con.com/read/358059_2.htm [3] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/advanced/MedicalScenario.java [4] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/advanced/MedicalScenarioWithChangeMonitoring.java [5] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/lib/src/main/java/org/apache/tuscany/sdo/api/SDOHelper.java Thanks. Follow-up questions: - Is there an SDO Helper that can introspect my handwritten Item Java class and drive the calls to the TypeHelper APIs? If not, can I add one? - I see that I can associate a class with a type, does it have to be an interface or can it be a class? - If it can be a class do I really need a factory class or is the SDO runtime able to instantiate the class? - I see methods like getStaticType on generated SDOs, do I need to implement that method in my handwritten SDO and why? -- Jean-Sebastien - 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]
[jira] Updated: (TUSCANY-1899) Java2WSDL (trivial) - do we have to assume method names start w/ a lowercase char?
[ https://issues.apache.org/jira/browse/TUSCANY-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-1899: Component/s: (was: Java SDO Tools) In the SDO tools we do this is in generation of XML schemas from existing Properties and Types. We do have a method formGlobalElementName which does this lower casing of the first letter when generating a global element in the schema. The behaviour is due to the paragraph in section 10 of the SDO spec which says ... The global element for the type: • lowercase(TYPE.NAME) is the type name with the first letter converted to lower case as defined type java.lang.Character.toLowerCase() Java2WSDL (trivial) - do we have to assume method names start w/ a lowercase char? -- Key: TUSCANY-1899 URL: https://issues.apache.org/jira/browse/TUSCANY-1899 Project: Tuscany Issue Type: Bug Components: Java SCA Tools Affects Versions: Java-SCA-1.0, Java-SCA-1.0.1 Reporter: Scott Kurz Priority: Trivial Fix For: Java-SCA-Next The fact that: TuscanyWSDLTypesGenerator .createSchemaTypeForMethodPart on line 267 calls: globalElement.setName(formGlobalElementName(localPartName)); which lowercases the first char in the parm passed to formGlobalElementName ends up implying that method names must start in a lowercase char. Because otherwise..the elem name so constructed won't match the operation name... which will cause us to not end up with doc-lit-wrapped WSDL. Since everyone uses lowercase method names this in Java, I ranked this as 'trivial'. Still, I opened this anyway because I didn't see why we bother to lowercase this string at all, and thought that if someone cancelled this JIRA, at least I'd learn there was a good reason for doing so. -- 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] Resolved: (TUSCANY-1842) IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content
[ https://issues.apache.org/jira/browse/TUSCANY-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1842. - Resolution: Fixed Applied patch, many thanks Ron. IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content --- Key: TUSCANY-1842 URL: https://issues.apache.org/jira/browse/TUSCANY-1842 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Environment: Windows XP, Sun JDK 1.5.0_09 Reporter: Ron Gavlin Priority: Critical Fix For: Java-SDO-Next Attachments: 1842data.zip, tuscany-sdo.TUSCANY-1842.patch In the test method, testComplexTypeWithSimpleContentExtensionChangeSummary() listed below, a DataGraph is created with a dataObject whose property type extends a complexType with simple integer content. After the dataObject is deleted, an attempt is made to save and load the DataGraph. While the DataGraph is being loaded, an unsuccessful attempt is made to convert a zero-length string into a BigInteger. Any suggestions on how to best fix this are most welcome. Thanks, - Ron == substitutionWithExtensionValues.xsd == schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV; xmlns:sev=http://www.example.com/substitutionEV; !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- element name=results type=sev:ResultsType / element name=result type=sev:ResultType / element name=myResult type=sev:MyResultType substitutionGroup=sev:result / complexType name=ResultsType sequence element name=id type=sev:IdType / element ref=sev:result minOccurs=0 maxOccurs=unbounded / element name=comment type=sev:CommentType / /sequence /complexType complexType name=ResultType sequence element name=id type=sev:IdType / element name=name type=string / element name=value type=sev:ValueType / /sequence /complexType complexType name=MyResultType complexContent extension base=sev:ResultType / /complexContent /complexType simpleType name=IdType restriction base=sev:AsciiStringType maxLength value=32 / pattern value=[0-9a-fA-F]* / /restriction /simpleType simpleType name=AsciiStringType restriction base=string pattern value=\p{IsBasicLatin}* / /restriction /simpleType complexType name=ValueType simpleContent extension base=sev:Integer32Bit / /simpleContent /complexType complexType name=Integer32Bit simpleContent restriction base=integer minInclusive value=0 / maxInclusive value=429000 / /restriction /simpleContent /complexType complexType name=CommentType simpleContent extension base=sev:AsciiStringType attribute name=language use=optional simpleType restriction base=string
Re: How to write a simple SDO class for the tutorial?
If you are discounting using XSD for the source of metadata to describe the SDO types then there is the SDO API provided for dynamic metadata creation. The sample at [1] gives an introduction to this. The paper at [2] discusses the subject also, and the program underlying the discussion in the paper is at [3] (no change monitoring) and [4] (with change monitoring). You say that you want to write the minimum code. There is a quick and simple Tuscany API for simple cases that you could use instead (See the MetaDataBuilder inner class in [5]). Whilst the code to create the type system with this project specific API is simple to understand and implement it has some drawbacks. We don't have a sample program for this, but I believe the DAS uses it) I'm happy to discuss further if you want some more insight into this. Kelvin. [1] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/intermediate/DynamicCustomerTypeSample.java [2] http://java.sys-con.com/read/358059_2.htm [3] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/advanced/MedicalScenario.java [4] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/sample/src/main/java/org/apache/tuscany/samples/sdo/advanced/MedicalScenarioWithChangeMonitoring.java [5] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/lib/src/main/java/org/apache/tuscany/sdo/api/SDOHelper.java On 13/11/2007, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: The online store tutorial currently uses a simple handwritten JavaBean to represent the Items in the store catalog and shopping cart. I'm able to flow that Item bean over local calls, WS, Atom and JSON bindings. Here's what it looks like: https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/tutorial/assets/services/Item.java Note: the implements Serializable is a work around and should be eventually removed. If I want to start using SDO in the tutorial, make that Item an SDO and write it by hand (with my user hat on, I'm going to assume that I don't know what XSD is about), what is the minimum code that I need to write? Thanks -- Jean-Sebastien - 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]
[jira] Resolved: (TUSCANY-1812) XMLHelper.load() IOException using schema that has both a substitution group and an extension
[ https://issues.apache.org/jira/browse/TUSCANY-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1812. - Resolution: Fixed Patch Applied (many thanks Ron) XMLHelper.load() IOException using schema that has both a substitution group and an extension - Key: TUSCANY-1812 URL: https://issues.apache.org/jira/browse/TUSCANY-1812 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Reporter: Ron Gavlin Priority: Critical Fix For: Java-SDO-Next Attachments: tuscany-sdo.TUSCANY-1812_1830_1832.patch Below, please find a failing Java test case and its XSD and XML test resources. Also, please find the stacktrace from the failing Java test case. It is interesting to note that this test does not fail when using dynamic SDO. Please comment if you have questions. - Ron package org.apache.tuscany.sdo.test; import java.io.IOException; import junit.framework.TestCase; import com.example.substitution.ev.SEVFactory; import commonj.sdo.DataObject; import commonj.sdo.helper.HelperContext; import commonj.sdo.helper.XMLHelper; import commonj.sdo.impl.HelperProvider; public final class SubstitutionWithExtensionValuesTestCase extends TestCase { public void test() throws IOException { HelperContext hc = HelperProvider.getDefaultContext(); SEVFactory.INSTANCE.register(hc); XMLHelper xmlHelper = hc.getXMLHelper(); DataObject loadedObject = xmlHelper.load(getClass().getResourceAsStream(/substitutionWithExtensionValues1.xml)).getRootObject(); } } substitutionWithExtensionValues.xsd schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV; xmlns:sv=http://www.example.com/substitutionEV; !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- element name=results type=sv:ResultsType/ element name=result type=sv:ResultType/ element name=myResult type=sv:MyResultType substitutionGroup=sv:result/ complexType name=ResultsType sequence element ref=sv:result minOccurs=0 maxOccurs=unbounded/ element name=comment type=string/ /sequence /complexType complexType name=ResultType sequence element name=name type=string/ element name=value type=string/ /sequence /complexType complexType name=MyResultType complexContent extension base=sv:ResultType/ /complexContent /complexType /schema substitutionWithExtensionValues1.xml ?xml version=1.0 encoding=ASCII? sev:results xmlns:sev=http://www.example.com/substitutionEV; sev:result sev:namename1/sev:name sev:valuevalue1/sev:value /sev:result sev:myResult sev:namemyName1/sev:name sev:valuemyValue1/sev:value /sev:myResult sev:commentcomment1/sev:comment /sev:results STACKTRACE org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'myResult' not found. (http:///temp.xml, 7, 17) at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLLoadImpl.java:83) at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:278) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:666) at org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl.doLoad(SDOXMLResourceImpl.java:585) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResourceImpl.java:634) at org.apache.tuscany.sdo.helper.XMLDocumentImpl.load(XMLDocumentImpl.java:266) at org.apache.tuscany.sdo.helper.XMLDocumentImpl.load(XMLDocumentImpl.java:239) at org.apache.tuscany.sdo.helper.XMLHelperImpl.load(XMLHelperImpl.java:97) at org.apache.tuscany.sdo.helper.XMLHelperImpl.load(XMLHelperImpl.java:79) at org.apache.tuscany.sdo.test.SubstitutionWithExtensionValuesTestCase.test
[jira] Resolved: (TUSCANY-1830) SimpleType extension across mixed static/dynamic namespaces is broken
[ https://issues.apache.org/jira/browse/TUSCANY-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1830. - Resolution: Fixed Fixed by updates in TUSCANY-1812 SimpleType extension across mixed static/dynamic namespaces is broken - Key: TUSCANY-1830 URL: https://issues.apache.org/jira/browse/TUSCANY-1830 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Reporter: Ron Gavlin Fix For: Java-SDO-Next I have a statically registered namespace http://www.example.com/substitutionEV; with a simpleType named UuidType with a pattern facet. I also have a dynamically registered namespace http://www.example.com/substitutionEV2; with a simpleType named Uuid2Type which is a restriction of UuidType. When I invoke uuid2Type.getBaseTypes(), the parent UuidType is not returned. I have included a sample test below. == substitutionWithExtensionValues.xsd == schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV; xmlns:sev=http://www.example.com/substitutionEV; !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- element name=results type=sev:ResultsType/ element name=result type=sev:ResultType/ element name=myResult type=sev:MyResultType substitutionGroup=sev:result/ complexType name=ResultsType sequence element name=uuid type=sev:UuidType/ element ref=sev:result minOccurs=0 maxOccurs=unbounded/ element name=comment type=string/ /sequence /complexType complexType name=ResultType sequence element name=uuid type=sev:UuidType/ element name=name type=string/ element name=value type=string/ /sequence /complexType complexType name=MyResultType complexContent extension base=sev:ResultType/ /complexContent /complexType simpleType name=UuidType restriction base=sev:AsciiStringType pattern value=[0-9a-fA-F]{8}\-[0-9a-fA-F]{4}\-[0-9a-fA-F]{4}\-[0-9a-fA-F]{4}\-[0-9a-fA-f]{12}/ /restriction /simpleType simpleType name=AsciiStringType restriction base=string pattern value=\p{IsBasicLatin}*/ /restriction /simpleType /schema == substitutionWithExtensionValues2.xsd == schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV2; xmlns:sev2=http://www.example.com/substitutionEV2; xmlns:sev=http://www.example.com/substitutionEV; !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- import namespace=http://www.example.com/substitutionEV; schemaLocation=substitutionWithExtensionValues.xsd / element name=allResults type=sev2:AllResultsType / complexType name=AllResultsType sequence element name=uuid type
[jira] Resolved: (TUSCANY-1832) Complex type w/simple content restriction facets are ignored
[ https://issues.apache.org/jira/browse/TUSCANY-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1832. - Resolution: Fixed Fixed by updates in TUSCANY-1812 Complex type w/simple content restriction facets are ignored Key: TUSCANY-1832 URL: https://issues.apache.org/jira/browse/TUSCANY-1832 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Reporter: Ron Gavlin Fix For: Java-SDO-Next Namespace http://www.example.com/substitutionEV; includes two complex type with simple content named CommentType and MyCommentType. MyCommentType restricts CommentType with facet maxLength=40. This maxLength facet does not appear to exist in the SDO metadata. The sample test case named testComplexTypeWithSimpleContentExtension() is included below. == substitutionWithExtensionValues.xsd == schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV; xmlns:sev=http://www.example.com/substitutionEV; !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- element name=results type=sev:ResultsType / element name=result type=sev:ResultType / element name=myResult type=sev:MyResultType substitutionGroup=sev:result / complexType name=ResultsType sequence element name=id type=sev:IdType / element ref=sev:result minOccurs=0 maxOccurs=unbounded / element name=comment type=sev:CommentType / /sequence /complexType complexType name=ResultType sequence element name=id type=sev:IdType / element name=name type=string / element name=value type=sev:CommentType / /sequence /complexType complexType name=MyResultType complexContent extension base=sev:ResultType / /complexContent /complexType simpleType name=IdType restriction base=sev:AsciiStringType maxLength value=32 / pattern value=[0-9a-fA-F]* / /restriction /simpleType simpleType name=AsciiStringType restriction base=string pattern value=\p{IsBasicLatin}* / /restriction /simpleType complexType name=CommentType simpleContent extension base=sev:AsciiStringType attribute name=language use=optional simpleType restriction base=string enumeration value=English / enumeration value=French / enumeration value=Spanish / /restriction /simpleType /attribute /extension /simpleContent /complexType complexType name=MyCommentType simpleContent restriction base=sev:CommentType minLength value=0 / maxLength value=40 / /restriction /simpleContent /complexType /schema == substitutionWithExtensionValues2.xsd == schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV2
[jira] Resolved: (TUSCANY-1811) ClassCastException saving codegen-based DataGraph with ChangeSummary containing an xsd:float
[ https://issues.apache.org/jira/browse/TUSCANY-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1811. - Resolution: Fixed Applied patch, thanks Ron. ClassCastException saving codegen-based DataGraph with ChangeSummary containing an xsd:float Key: TUSCANY-1811 URL: https://issues.apache.org/jira/browse/TUSCANY-1811 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-1.0 Reporter: Ron Gavlin Fix For: Java-SDO-Next Attachments: tuscany-sdo.TUSCANY-1811.patch This problem is similar to TUSCANY-1393 except the schema type in this case is an xsd:float instead of an xsd:int. The fix involves adding the following lines to DataObjectBase.java. If you would like me to submit a patch with a revised testcase, let me know. LINES TO BE ADDED to DataObjectBase.java: protected void notify(int changeKind, int property, float oldFloatValue, float newFloatValue) { eNotify(new ENotificationImpl(this, Notification.SET, property, oldFloatValue, newFloatValue)); } protected void notify(int changeKind, int property, float oldFloatValue, float newFloatValue, boolean isSetChange) { eNotify(new ENotificationImpl(this, Notification.SET, property, oldFloatValue, newFloatValue, isSetChange)); } END OF LINES TO BE ADDED - Ron P.S., below I have included the stacktrace for the problem. java.lang.ClassCastException: java.lang.Double at org.apache.tuscany.sdo.model.impl.ModelFactoryImpl.convertFloatToString(ModelFactoryImpl.java:2036) at org.apache.tuscany.sdo.model.impl.ModelFactoryImpl.convertToString(ModelFactoryImpl.java:318) at org.apache.tuscany.sdo.impl.FactoryBase$SDOEFactoryImpl.convertToString(FactoryBase.java:291) at org.eclipse.emf.ecore.util.EcoreUtil.convertToString(EcoreUtil.java:2994) at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.getDataValue(FeatureChangeImpl.java:228) at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.eIsSet(FeatureChangeImpl.java:771) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eIsSet(BasicEObjectImpl.java:818) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1107) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElementID(XMLSaveImpl.java:2462) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1036) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:922) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2182) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1390) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElementID(XMLSaveImpl.java:2462) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1036) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:922) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2182) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1390) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElementID(XMLSaveImpl.java:2462) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.writeTopObject(XMLSaveImpl.java:620) at org.apache.tuscany.sdo.util.DataGraphResourceFactoryImpl$DataGraphResourceImpl$SaveImpl.traverse(DataGraphResourceFactoryImpl.java:382) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:233) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:203) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:993) at org.apache.tuscany.sdo.helper.SDOHelperImpl.saveDataGraph(SDOHelperImpl.java:182) at org.apache.tuscany.sdo.api.SDOUtil.saveDataGraph(SDOUtil.java:158) at org.apache.tuscany.sdo.test.ChangeSummaryGenTestCase.testChangeSummaryOnDataGraphWithIntAndFloat(ChangeSummaryGenTestCase.java:128) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109
[jira] Updated: (TUSCANY-1842) IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content
[ https://issues.apache.org/jira/browse/TUSCANY-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-1842: Attachment: 1842data.zip Hi Ron, I'm having trouble getting the data files to validate before I run the test cases. I have made some updates, but need some assistance in fixing the final errors without changing the meaning of the test case. I have attached my updates to the files in 1842data.zip. In these files I have fixed up some of the validation errors by ... adding elementFormDefault=qualified to both schema files changing the sev:results to sev2:results elements changing the values of the sev2:id and sev2:comment elements to match the appropriate facets but I am left with the errors below, and no matter how I try to vary the method of type derivation I cant seem to create a valid schema that conveys the meaning I think you want. Can you take a look please? src-ct.2.1: Complex Type Definition Representation Error for type 'Integer32Bit'. When simpleContent is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'integer' satisfies none of these conditions. tuscany-sdo-tools-test/src/main/resources substitutionWithExtensionValues.xsd line 69 src-ct.2.1: Complex Type Definition Representation Error for type 'StringBasedCommentType'. When simpleContent is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'string' satisfies none of these conditions.tuscany-sdo-tools-test/src/main/resources substitutionWithExtensionValues.xsd line 103 src-ct.2.1: Complex Type Definition Representation Error for type 'ValueType'. When simpleContent is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'Integer32Bit' satisfies none of these conditions. tuscany-sdo-tools-test/src/main/resources substitutionWithExtensionValues.xsd line 63 IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content --- Key: TUSCANY-1842 URL: https://issues.apache.org/jira/browse/TUSCANY-1842 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Environment: Windows XP, Sun JDK 1.5.0_09 Reporter: Ron Gavlin Priority: Critical Fix For: Java-SDO-Next Attachments: 1842data.zip, tuscany-sdo.TUSCANY-1842.patch In the test method, testComplexTypeWithSimpleContentExtensionChangeSummary() listed below, a DataGraph is created with a dataObject whose property type extends a complexType with simple integer content. After the dataObject is deleted, an attempt is made to save and load the DataGraph. While the DataGraph is being loaded, an unsuccessful attempt is made to convert a zero-length string into a BigInteger. Any suggestions on how to best fix this are most welcome. Thanks, - Ron == substitutionWithExtensionValues.xsd == schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV; xmlns:sev=http://www.example.com/substitutionEV; !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- element name
Re: [jira] Updated: (TUSCANY-1842) IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content
Thanks, I'm looking at your triple JIRA patch now (1812,30,32) Kelvin. On 13/11/2007, Ron Gavlin [EMAIL PROTECTED] wrote: I'll take a look and get back to you. Thanks, - Ron - Original Message From: Kelvin Goodson (JIRA) tuscany-dev@ws.apache.org To: [EMAIL PROTECTED] Sent: Tuesday, November 13, 2007 9:12:50 AM Subject: [jira] Updated: (TUSCANY-1842) IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content [ https://issues.apache.org/jira/browse/TUSCANY-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-1842: Attachment: 1842data.zip Hi Ron, I'm having trouble getting the data files to validate before I run the test cases. I have made some updates, but need some assistance in fixing the final errors without changing the meaning of the test case. I have attached my updates to the files in 1842data.zip. In these files I have fixed up some of the validation errors by ... adding elementFormDefault=qualified to both schema files changing the sev:results to sev2:results elements changing the values of the sev2:id and sev2:comment elements to match the appropriate facets but I am left with the errors below, and no matter how I try to vary the method of type derivation I cant seem to create a valid schema that conveys the meaning I think you want. Can you take a look please? src-ct.2.1: Complex Type Definition Representation Error for type 'Integer32Bit'. When simpleContent is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'integer' satisfies none of these conditions.tuscany-sdo-tools-test/src/main/resources substitutionWithExtensionValues.xsdline 69 src-ct.2.1: Complex Type Definition Representation Error for type 'StringBasedCommentType'. When simpleContent is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'string' satisfies none of these conditions.tuscany-sdo-tools-test/src/main/resources substitutionWithExtensionValues.xsdline 103 src-ct.2.1: Complex Type Definition Representation Error for type 'ValueType'. When simpleContent is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'Integer32Bit' satisfies none of these conditions.tuscany-sdo-tools-test/src/main/resources substitutionWithExtensionValues.xsdline 63 IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content --- Key: TUSCANY-1842 URL: https://issues.apache.org/jira/browse/TUSCANY-1842 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Environment: Windows XP, Sun JDK 1.5.0_09 Reporter: Ron Gavlin Priority: Critical Fix For: Java-SDO-Next Attachments: 1842data.zip, tuscany-sdo.TUSCANY-1842.patch In the test method, testComplexTypeWithSimpleContentExtensionChangeSummary() listed below, a DataGraph is created with a dataObject whose property type extends a complexType with simple integer content. After the dataObject is deleted, an attempt is made to save and load the DataGraph. While the DataGraph is being loaded, an unsuccessful attempt is made to convert a zero-length string into a BigInteger. Any suggestions on how to best fix this are most welcome. Thanks, - Ron == substitutionWithExtensionValues.xsd == schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV; xmlns:sev=http://www.example.com/substitutionEV; !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy
Re: Tuscany November Board Report
It looks fine from my perspective. Kelvin. On 09/11/2007, Luciano Resende [EMAIL PROTECTED] wrote: I have added couple more things there too... it would be great if others could review and update by EOD today, then I'd move this to the Incubator wiki at night. On Nov 9, 2007 4:56 AM, Simon Laws [EMAIL PROTECTED] wrote: On Nov 5, 2007 6:13 PM, Luciano Resende [EMAIL PROTECTED] wrote: It's that time again, and I have created a placeholder for us to collaborate on the Incubator board report. Right now it's just a copy of our previous report, please jump in and help get this updated/rewritten. Let's aim to get something done by Thursday or Friday... as the deadline is this weekend. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+November+Board+Report -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi Luciano I've done the basic updates. Take a look and see what else is needed. Simon -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Mark Combellack voted as Tuscany committer
Welcome Mark! -- Kelvin On 01/11/2007, ant elder [EMAIL PROTECTED] wrote: The Tuscany PPMC and Incubator PMC have voted for Mark Combellack to become a Tuscany committer. Congratulations and welcome Mark! ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to convert DataObjects to and from Java objects
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539055 ] Kelvin Goodson commented on TUSCANY-1493: - Kris, thanks for this. It's going to be a couple of days before I can get to looking at it, but I look forward to doing so. Snapshot mapping framework to convert DataObjects to and from Java objects -- Key: TUSCANY-1493 URL: https://issues.apache.org/jira/browse/TUSCANY-1493 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: agfasdo.tar.gz, sdo-snapshot.zip, sdo.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa). To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts. - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly. - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects). - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily. This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion. I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component. -- 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] Commented: (TUSCANY-1527) Allow for custom data binding of DataObjects in a Swing UI
[ https://issues.apache.org/jira/browse/TUSCANY-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539056 ] Kelvin Goodson commented on TUSCANY-1527: - OK, thanks, I'll take a peek ASAP and see how it fits with what's in my sandbox already, and how we can advance that. Allow for custom data binding of DataObjects in a Swing UI -- Key: TUSCANY-1527 URL: https://issues.apache.org/jira/browse/TUSCANY-1527 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: agfasdoui.tar.gz, com.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. On the client side we use sdo objects as model objects for our UI. As such, we need a mechanism for binding our objects to the UI controls such that changes in the objects are reflected in the UI and vice versa. At the moment, there is no real standard for data binding and many different implementations exist. As such, it would not be a good idea to build support for this directly into the sdo core. Ideally, the sdo core would allow implementations supporting data binding to be added as extensions [an extension as in jar, module, bundle, component, ...]. This is a request for supporting this in Tuscany SDO. - For our applications, we developed our own implementation of the sdo specification. This implementation is designed to support that kind of extensions. In the rest of this description, I'd like to show more details on our implementation to make this more clear and to serve as food for a possible discussion. Our sdo core module defines the abstract class AbstractPartialDataObject implementing DataObject. This class (together with its superclasses) implements the majority of the bevahiour of DataObject. This includes bi-directional property updates, type-safe properties, containment, ... It doesn't implement however the basic access to property values. Here's a code fragment. public abstract class AbstractPartialDataObject extends AbstractDataObject implements PartialDataObject { protected abstract Object basicGet(Property property); protected abstract void basicSet(Property property, Object value); public Object get(Property property) { ... } public void set(Property property, Object value) { ... } ... } The sdo core module also provides a non-abstract class DataObjectImplementation that provides a simple implementation of this abstract behaviour where the property values are stored in an ArrayList. On top of that we defined an extension that deals with our UI requirements. Our UI is based on a proprietary UI framework. This framework has the following requirements: - single valued properties should be exposed as XObservables. An XObservable is a kind of ValueModel that provides access to a value (get/set) and also allows for registration of change listeners - multi valued properties should be exposed as ListModel instances. A ListModel is a proprietary class (a bit similar to the javax.swing.ListModel) that provides List functionality and also allows for change listeners - the data object itself should allow registration of attribute change listeners that are notified each time a property changes The extension implements these requirements by providing an appropriate subclass ObservableDataObject of AbstractPartialDataObject. The only other pieces of code needed in the extension is an appropriate implementation of DataFactory and a wrapper to deal with the differences between ListModel and List. Here's the class with the most important code snippets. public class ObservableDataObject extends CompositePartialDataObject implements { private XObservable[] properties; protected ObservableDataObject(com.agfa.hap.sdo.Type type) { super(type); this.properties = new XObservable[type.getProperties().size()]; for (int i = 0; i properties.length; i++) { initializeProperty(type.getProperty(i)); } } private XObservableObject initializeProperty(Property prop) { XObservableObject observable = XObservableFactory.create(prop.getType().getInstanceClass(), this); if (prop.isMany()) { observable.init(new DataObjectListModel(this, prop)); } properties[prop.getIndex()] = observable; return observable; } public XObservable getObservable(commonj.sdo.Property property) { XObservable result = properties[property.getIndex()]; return result; } public ListModel
[jira] Commented: (TUSCANY-1527) Allow for custom data binding of DataObjects in a Swing UI
[ https://issues.apache.org/jira/browse/TUSCANY-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538718 ] Kelvin Goodson commented on TUSCANY-1527: - I just came across this link http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.emf.doc/references/javadoc/org/eclipse/emf/common/notify/Notification.html and recalled your enquiry. Allow for custom data binding of DataObjects in a Swing UI -- Key: TUSCANY-1527 URL: https://issues.apache.org/jira/browse/TUSCANY-1527 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: com.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. On the client side we use sdo objects as model objects for our UI. As such, we need a mechanism for binding our objects to the UI controls such that changes in the objects are reflected in the UI and vice versa. At the moment, there is no real standard for data binding and many different implementations exist. As such, it would not be a good idea to build support for this directly into the sdo core. Ideally, the sdo core would allow implementations supporting data binding to be added as extensions [an extension as in jar, module, bundle, component, ...]. This is a request for supporting this in Tuscany SDO. - For our applications, we developed our own implementation of the sdo specification. This implementation is designed to support that kind of extensions. In the rest of this description, I'd like to show more details on our implementation to make this more clear and to serve as food for a possible discussion. Our sdo core module defines the abstract class AbstractPartialDataObject implementing DataObject. This class (together with its superclasses) implements the majority of the bevahiour of DataObject. This includes bi-directional property updates, type-safe properties, containment, ... It doesn't implement however the basic access to property values. Here's a code fragment. public abstract class AbstractPartialDataObject extends AbstractDataObject implements PartialDataObject { protected abstract Object basicGet(Property property); protected abstract void basicSet(Property property, Object value); public Object get(Property property) { ... } public void set(Property property, Object value) { ... } ... } The sdo core module also provides a non-abstract class DataObjectImplementation that provides a simple implementation of this abstract behaviour where the property values are stored in an ArrayList. On top of that we defined an extension that deals with our UI requirements. Our UI is based on a proprietary UI framework. This framework has the following requirements: - single valued properties should be exposed as XObservables. An XObservable is a kind of ValueModel that provides access to a value (get/set) and also allows for registration of change listeners - multi valued properties should be exposed as ListModel instances. A ListModel is a proprietary class (a bit similar to the javax.swing.ListModel) that provides List functionality and also allows for change listeners - the data object itself should allow registration of attribute change listeners that are notified each time a property changes The extension implements these requirements by providing an appropriate subclass ObservableDataObject of AbstractPartialDataObject. The only other pieces of code needed in the extension is an appropriate implementation of DataFactory and a wrapper to deal with the differences between ListModel and List. Here's the class with the most important code snippets. public class ObservableDataObject extends CompositePartialDataObject implements { private XObservable[] properties; protected ObservableDataObject(com.agfa.hap.sdo.Type type) { super(type); this.properties = new XObservable[type.getProperties().size()]; for (int i = 0; i properties.length; i++) { initializeProperty(type.getProperty(i)); } } private XObservableObject initializeProperty(Property prop) { XObservableObject observable = XObservableFactory.create(prop.getType().getInstanceClass(), this); if (prop.isMany()) { observable.init(new DataObjectListModel(this, prop)); } properties[prop.getIndex()] = observable; return observable; } public XObservable getObservable(commonj.sdo.Property property) { XObservable result = properties[property.getIndex
Re: [NOTICE] Michael Yoder voted as Tuscany committer
Michael, good to have you on board, Welcome! Kelvin. On 24/10/2007, Pete Robbins [EMAIL PROTECTED] wrote: The Tuscany PPMC and Incubator PMC have voted for Michael to become a Tuscany committer. Congratulations and welcome! I look forward to your continued excellent contributions to Tuscany. Cheers, -- Pete - 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]
[jira] Updated: (TUSCANY-1868) Schema imports not working in multiple class-loader environment
[ https://issues.apache.org/jira/browse/TUSCANY-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-1868: Component/s: Java SDO Implementation Schema imports not working in multiple class-loader environment --- Key: TUSCANY-1868 URL: https://issues.apache.org/jira/browse/TUSCANY-1868 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-1.0 Environment: n/a Reporter: David T. Adcox Fix For: Java-SDO-Next Attachments: Test1868.java There is a problem with loading schemas that import an additional namespace when in a multiple class-loader environment. The problem exists due to a design flaw in how the EcoreBuilder and package registries interact under a specific circumstance. That circumstance exists when the default helper context is used to load a schema model using the XSDHelper.define() method in two different, peer class-loaders. These peer class-loaders must share the same parentage. --- | CL parent | --- /\ / \ /\ / \ --- --- | CL1 || CL2 | --- --- In this scenario, the same EcoreBuilder is used on both passes of XSDHelper.define(), because the EcoreBuilder is associated with the CL Parent. A unique registry is created for CL1 and another for CL2. During the processing for CL1, the target namespace and all imported namespaces are properly parsed and the models stored in the associated registry, but during the processing for CL2, because the same EcoreBuilder is used, only the target namespace is processed. So, any imported models are missing from the CL2 registry. I've attached an example that will demonstrate this issue. -- 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] Resolved: (TUSCANY-1780) [JAVA-SDO] Incorrect generation of class with default value for a list
[ https://issues.apache.org/jira/browse/TUSCANY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1780. - Resolution: Fixed Resolved in 588261. [JAVA-SDO] Incorrect generation of class with default value for a list -- Key: TUSCANY-1780 URL: https://issues.apache.org/jira/browse/TUSCANY-1780 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0, Java-SDO-Next Environment: Windows XP, JRE 1.4.2 and JRE 1.5 Reporter: Chris Mildebrandt Priority: Critical Fix For: Java-SDO-Next Attachments: Address.xsd, Address2.xsd, SDOClass.java Hello, There seems to be a problem when generating static classes when lists are involved. I have the following lines in my schema: xsd:attribute name=categoryType type=address:CategoryType use=required default=myCat/ simpleType name=CategoryType list itemType=category / /simpleType This generates the following line in the impl class: protected static final Object CATEGORY_TYPE_DEFAULT_ = ((EFactory)ModelFactory.INSTANCE).createFromString(ModelPackageImpl.eINSTANCE.getObject(), myCat); The class ModelPackageImpl doesn't exist. I've tried this with the 1.0 version of SDO and a version I built today. Let me know if you need any more information. Thanks, -Chris -- 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] Updated: (TUSCANY-1780) [JAVA-SDO] Incorrect generation of class with default value for a list
[ https://issues.apache.org/jira/browse/TUSCANY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-1780: Attachment: SDOClass.java As a checkpoint in investigating this issue I'm attaching a sanitised version of SDOClass.java for debug purposes which is logically equivalent to the status quo. Here's where I've got to --- At line 530 of this file we create the static defaults of variables, be they single instance or list type. So the one call to stringBuffer.append(genFeature.getStaticDefaultValue()); is used to handle thing like protected static final String VALUE_DEFAULT_ = null; protected static final boolean DISPLAYABLE_DEFAULT_ = false; as well as the case in hand. The differential logic for creating the string is found in guarded code portions of GenDataTypeImpl#getStaticValue (as reached from GenFeatureImpl#getStaticDefaultValue()) and it is there that the createFromString code that is in error is generated. The problem as I see it at the moment is that all that logic is bound up in one single EMF method, containing some code that I want, and some that I don't. It's not clear to me at the moment whether I need to add guards into SDOClass which replicate the fairly detailed logic in the calling stack to avoid the call to getFeature.getStaticDefaultValue() in the circumstances when it produces the erroneous code (providing an alternative generation in those circumstances), or whether there is some better means of influencing the output. [JAVA-SDO] Incorrect generation of class with default value for a list -- Key: TUSCANY-1780 URL: https://issues.apache.org/jira/browse/TUSCANY-1780 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0, Java-SDO-Next Environment: Windows XP, JRE 1.4.2 and JRE 1.5 Reporter: Chris Mildebrandt Priority: Critical Fix For: Java-SDO-Next Attachments: Address.xsd, Address2.xsd, SDOClass.java Hello, There seems to be a problem when generating static classes when lists are involved. I have the following lines in my schema: xsd:attribute name=categoryType type=address:CategoryType use=required default=myCat/ simpleType name=CategoryType list itemType=category / /simpleType This generates the following line in the impl class: protected static final Object CATEGORY_TYPE_DEFAULT_ = ((EFactory)ModelFactory.INSTANCE).createFromString(ModelPackageImpl.eINSTANCE.getObject(), myCat); The class ModelPackageImpl doesn't exist. I've tried this with the 1.0 version of SDO and a version I built today. Let me know if you need any more information. Thanks, -Chris -- 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: How about a Java SCA 1.0.1 release for October?
snip/ Also, I'd like to nominate Raymond to be release manager for this. +1 ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1853) XSD2JavaGenerator generates Java identifier with dots
[ https://issues.apache.org/jira/browse/TUSCANY-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536641 ] Kelvin Goodson commented on TUSCANY-1853: - Hi Czarek, I'm just looking at what to do with this JIRA on the basis of Frank's comment above. Could you let us know what version of SDO you are running please? Perhaps if the issue turns out to be not already fixed you could also attach a schema demonstrating the issue. XSD2JavaGenerator generates Java identifier with dots - Key: TUSCANY-1853 URL: https://issues.apache.org/jira/browse/TUSCANY-1853 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0 Environment: Windows XP, jre 1.5 Reporter: Cezary Tkaczyk Hello, While I'm trying to compile generated by XSD2JavaGenerator Java classes, I've got such an error: [javac] C:\projekty\eclipse-workspace-rbpl-sdo-1.0\REB-Catalog-SDO-Java\src-autogen\pl\esb\impl\EsbFactoryImpl.java:169: ';' expected [javac] pl.esb.blm.adapter.AdapterFactory pl.esb.blm.adapter.AdapterFactoryInstance = pl.esb.blm.adapter.AdapterFactory.INSTANCE; [javac]^ The problem is: variable identifier cannot contain dots. The place, where this error appears looks like this: public static EsbFactoryImpl init() { if (instance != null ) return instance; instance = new EsbFactoryImpl(); // Initialize dependent packages AdapterFactory AdapterFactoryInstance = AdapterFactory.INSTANCE; RebFactory RebFactoryInstance = RebFactory.INSTANCE; pl.raiffeisen.esb.blm.adapter.AdapterFactory pl.raiffeisen.esb.blm.adapter.AdapterFactoryInstance = pl.raiffeisen.esb.blm.adapter.AdapterFactory.INSTANCE; // Create package meta-data objects instance.createMetaData(); // Initialize created meta-data instance.initializeMetaData(); // Mark meta-data to indicate it can't be changed //theEsbFactoryImpl.freeze(); //FB do we need to freeze / should we freeze return instance; } I think the problem is that I have two namespaces of the same suffix: http://www.esb.pl/blm/adapter http://www.esb.pl/ods1/adapter So, generator is trying to avoid the problem creating unique variable name: pl.esb.blm.adapter.AdapterFactoryInstance Unfortunately, this is not valid identifier. Kind Regards, Czarek -- 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] Updated: (TUSCANY-1842) IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content
[ https://issues.apache.org/jira/browse/TUSCANY-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-1842: Patch Info: [Patch Available] Setting PAtach Available: Ron's suggestion gives us a quick workaround to be committed under this JIRA. TUSCANY-1862 will provide the proper fix. IOException loading DataGraph containing a deleted dataObject with a property whose type extends a complexType w/simple integer content --- Key: TUSCANY-1842 URL: https://issues.apache.org/jira/browse/TUSCANY-1842 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Environment: Windows XP, Sun JDK 1.5.0_09 Reporter: Ron Gavlin Priority: Critical Fix For: Java-SDO-Next In the test method, testComplexTypeWithSimpleContentExtensionChangeSummary() listed below, a DataGraph is created with a dataObject whose property type extends a complexType with simple integer content. After the dataObject is deleted, an attempt is made to save and load the DataGraph. While the DataGraph is being loaded, an unsuccessful attempt is made to convert a zero-length string into a BigInteger. Any suggestions on how to best fix this are most welcome. Thanks, - Ron == substitutionWithExtensionValues.xsd == schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://www.example.com/substitutionEV; xmlns:sev=http://www.example.com/substitutionEV; !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- element name=results type=sev:ResultsType / element name=result type=sev:ResultType / element name=myResult type=sev:MyResultType substitutionGroup=sev:result / complexType name=ResultsType sequence element name=id type=sev:IdType / element ref=sev:result minOccurs=0 maxOccurs=unbounded / element name=comment type=sev:CommentType / /sequence /complexType complexType name=ResultType sequence element name=id type=sev:IdType / element name=name type=string / element name=value type=sev:ValueType / /sequence /complexType complexType name=MyResultType complexContent extension base=sev:ResultType / /complexContent /complexType simpleType name=IdType restriction base=sev:AsciiStringType maxLength value=32 / pattern value=[0-9a-fA-F]* / /restriction /simpleType simpleType name=AsciiStringType restriction base=string pattern value=\p{IsBasicLatin}* / /restriction /simpleType complexType name=ValueType simpleContent extension base=sev:Integer32Bit / /simpleContent /complexType complexType name=Integer32Bit simpleContent restriction base=integer minInclusive value=0 / maxInclusive value=429000 / /restriction /simpleContent /complexType complexType name=CommentType simpleContent extension base=sev:AsciiStringType attribute name=language use=optional simpleType
[jira] Commented: (TUSCANY-1659) SDO DateConversion test cases fail under linux
[ https://issues.apache.org/jira/browse/TUSCANY-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536655 ] Kelvin Goodson commented on TUSCANY-1659: - Luciano, can you confirm whether this is still an issue please, and if so, could you attach the surefire reports. Can you also say what JVM you are using please? Kelvin SDO DateConversion test cases fail under linux -- Key: TUSCANY-1659 URL: https://issues.apache.org/jira/browse/TUSCANY-1659 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Environment: Linux Ubuntu 7.0.4 Reporter: Luciano Resende Fix For: Java-SDO-Next The following tests are failing under revision #571238 Tests in error: testConversionsFromDate(org.apache.tuscany.sdo.test.DateConversionTestCase) testConversionsFromDateTime(org.apache.tuscany.sdo.test.DateConversionTestCase) testConversionsFromDuration(org.apache.tuscany.sdo.test.DateConversionTestCase) testConversionsFromMonth(org.apache.tuscany.sdo.test.DateConversionTestCase) testConversionsFromMonthDay(org.apache.tuscany.sdo.test.DateConversionTestCase) testConversionsFromYear(org.apache.tuscany.sdo.test.DateConversionTestCase) testConversionsFromYearMonth(org.apache.tuscany.sdo.test.DateConversionTestCase) testConversionsFromYearMonthDay(org.apache.tuscany.sdo.test.DateConversionTestCase) Looks like working ok in windows. -- 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] Commented: (TUSCANY-1263) XMLEqualityChecker too strict
[ https://issues.apache.org/jira/browse/TUSCANY-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536659 ] Kelvin Goodson commented on TUSCANY-1263: - An alternative to using another tool is the approach adopted in commit http://svn.apache.org/viewvc/incubator/tuscany/java/sdo/impl/src/test/java/org/apache/tuscany/sdo/test/DupElementTestCase.java?view=markuppathrev=586476 XMLEqualityChecker too strict - Key: TUSCANY-1263 URL: https://issues.apache.org/jira/browse/TUSCANY-1263 Project: Tuscany Issue Type: Bug Components: Java SDO Community Test Suite Affects Versions: Java-SDO-CTS-Next Reporter: Lionel Villard Fix For: Java-SDO-CTS-Next The XMLEqualityChecker is too strict wrt to whitespace checking. For example, this 2 documents are considered different: date xsi:type=xs:date 2003-11-24 /date date xsi:type=xs:date2003-11-24/date when, from the validation point of view, they are the same. -- 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] Commented: (TUSCANY-1178) DynamicTypesFromSchemaTestCase expecting *Object types to be created
[ https://issues.apache.org/jira/browse/TUSCANY-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536660 ] Kelvin Goodson commented on TUSCANY-1178: - TODO: given the discussion above, and the unresolved SDO spec JIRA targeteed for the SDO 3 spec, the assertions in the test case relating to the types mentioned above in the description should be removed. DynamicTypesFromSchemaTestCase expecting *Object types to be created Key: TUSCANY-1178 URL: https://issues.apache.org/jira/browse/TUSCANY-1178 Project: Tuscany Issue Type: Bug Components: Java SDO Community Test Suite Affects Versions: Java-SDO-CTS-Next Reporter: Andy Grove Fix For: Java-SDO-CTS-Next DynamicTypesFromSchemaTestCase expects the following types to be included in the list returned by XSDHelper.define() but there are no types with these names in the XSD (these types minus the Object suffix do exist though). Is there something in the spec that says these extra Object types must be created or is this Tuscany-specific implementation detail that should be excluded from the CTS? evenNumberOfOddOrEvenDigitsObject monthObject oddOrEvenDigitsObject smallIntObject smallOddNumberObject -- 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] Resolved: (TUSCANY-1283) Better organization of the interfaces and classes in the SDO Java project
[ https://issues.apache.org/jira/browse/TUSCANY-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1283. - Resolution: Fixed The basis of the plan described above is in place. The split between emf and non-emf runtime was implemented by an additional project, rather than a division at the java package level. Better organization of the interfaces and classes in the SDO Java project - Key: TUSCANY-1283 URL: https://issues.apache.org/jira/browse/TUSCANY-1283 Project: Tuscany Issue Type: Improvement Components: Java SDO Implementation Reporter: Frank Budinsky Fix For: Java-SDO-Next Currently, there is no clean separation between client API vs. implementation (internal) classes. There's also no separation between the EMF-dependent and independent parts of the RT. We have been recommending clients stick to standard SDO APIs (from the spec) and for anything else use class SDOUtil, which is where we put all the required extensions that people have requested. One other interface, XMLStreamHelper (for working with StAX streams) is the only other interface in Tuscany that clients are expected to use directly. So, clients that are only using standard SDO APIs, SDOUtil, and XMLStreamHelper, should be unaffected by the reorganization for now, because we will keep deprecated versions of SDOUtil and XMLStreamHelper around for a while, but we would like to move them to a better package and have clients gradually move to the new ones. Here is the concrete plan: package org.apache.tuscany.sdo.api (all client API will be under this package) SDOUtil (new one) XMLStreamHelper (new one) other new things ... package org.apache.tuscany.sdo.rtemf (EMF-based runtime implementation classes) subset of existing classes (most of them) that have EMF dependencies (these are existing packages just moved down one level, e.g., org.apache.tuscany.sdo.helper - org.apache.sdo.tuscany.sdo.rtemf.helper) package org.apache.tuscany.sdo.rtlib (common runtime implementation classes) subset of existing classes that have no EMF dependencies package org.apache.tuscany.sdo.util (deprecated) SDOUtil (deprecated - clients should switch to org.apache.tuscany.sdo.api.SDOUtil) package org.apache.tuscany.sdo.helper (deprecated) XMLStreamHelper (deprecated - clients should switch to org.apache.tuscany.sdo.api.XMLStreamHelper) -- 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] Commented: (TUSCANY-1180) Unable to initialize read-only properties
[ https://issues.apache.org/jira/browse/TUSCANY-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536664 ] Kelvin Goodson commented on TUSCANY-1180: - Resolution of this issue is dependent on http://www.xcalia.com/support/browse/SDO-37, currently targeted at SDO 3. Unable to initialize read-only properties - Key: TUSCANY-1180 URL: https://issues.apache.org/jira/browse/TUSCANY-1180 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-Next Reporter: Stepan Ilchenko Fix For: Java-SDO-Next The problem is that we can't initialize read-only property in recently created DataObject, when we fill it with data by own DAS. SDO API says, that Exception should be raized in case of attempting to change that king of property through API. That's why new method in SDO Implementation needs to be created to provide property initialization. Maybe 'isSet' parameter should be used to control initialization process of the property. -- 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] Commented: (TUSCANY-1192) Preserve demand created global properties
[ https://issues.apache.org/jira/browse/TUSCANY-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536669 ] Kelvin Goodson commented on TUSCANY-1192: - Note, related to this issue is that http://www.xcalia.com/support/browse/SDO-263 recently established the principle that ... ... if the last value of an existing open content property list is removed and then another value is added, the same instance property will reappear, ... Preserve demand created global properties - Key: TUSCANY-1192 URL: https://issues.apache.org/jira/browse/TUSCANY-1192 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Affects Versions: Java-SDO-beta1 Reporter: Kelvin Goodson Fix For: Java-SDO-Next TUSCANY-917 addressed the issue of demand creating global properties when needed for an xmlHelper.load operation, but the property is ephemeral and is therefore not available for use after the load operation. This JIRA is opened to alter behaviour such that the demand created property is available in the applications metadata after the load operation. -- 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] Updated: (TUSCANY-152) Java SDO generation from XML Schema needs schema validation.
[ https://issues.apache.org/jira/browse/TUSCANY-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-152: --- Component/s: (was: Java SDO Implementation) Java SDO Tools Java SDO generation from XML Schema needs schema validation. Key: TUSCANY-152 URL: https://issues.apache.org/jira/browse/TUSCANY-152 Project: Tuscany Issue Type: New Feature Components: Java SDO Tools Environment: SVN HEAD java Reporter: Rick Rineholt Fix For: Java-SDO-Next Using the generation through the WSDL tool it appears the XML schema can have invalid schema and still the generator produces code. The particular case I had was the an element that had this case element name=foo type=tns:bar / element name='bar' .../element Note for it to be valid the bar should have been a complexType. The code generated seem to create a Foo that was java.lang.Object. -- 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] Resolved: (TUSCANY-1397) createDataObject() throws NPE if property does not exist
[ https://issues.apache.org/jira/browse/TUSCANY-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1397. - Resolution: Fixed This patch was applied in commit 562586. Please resolve JIRAs when handled, and include a comment of the form TUSCANY- in the svn commit record in order that the commit be added to the subversion commits tab of the JIRA. createDataObject() throws NPE if property does not exist Key: TUSCANY-1397 URL: https://issues.apache.org/jira/browse/TUSCANY-1397 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Reporter: Andy Grove Fix For: Java-SDO-Next Attachments: tuscany1397-v2.patch, tuscany1397.patch Calling createDataObject( foo ) where the data object's type does not define a property foo causes a null pointer exception in DataObjectUtil.createDataObject(DataObject dataObject, Property property, Type type) because it attempts to call property.isContainment without checking if the property is null. Calling createDataObject( foo ) on an open type should create an on-demand property. If the type is not open and the property does not exist then an exception should be thrown. Thanks, Andy. -- 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] Commented: (TUSCANY-1780) [JAVA-SDO] Incorrect generation of class with default value for a list
[ https://issues.apache.org/jira/browse/TUSCANY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536432 ] Kelvin Goodson commented on TUSCANY-1780: - Here's what the generator should be generating I think. protected static final List CATEGORY_TYPE_DEFAULT_ = (List)((XsdlistwitdefaultFactoryImpl)XsdlistwitdefaultFactory.INSTANCE).createFromString(XsdlistwitdefaultFactoryImpl.CATEGORY_TYPE, myCat); [JAVA-SDO] Incorrect generation of class with default value for a list -- Key: TUSCANY-1780 URL: https://issues.apache.org/jira/browse/TUSCANY-1780 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0, Java-SDO-Next Environment: Windows XP, JRE 1.4.2 and JRE 1.5 Reporter: Chris Mildebrandt Priority: Critical Fix For: Java-SDO-Next Attachments: Address.xsd, Address2.xsd Hello, There seems to be a problem when generating static classes when lists are involved. I have the following lines in my schema: xsd:attribute name=categoryType type=address:CategoryType use=required default=myCat/ simpleType name=CategoryType list itemType=category / /simpleType This generates the following line in the impl class: protected static final Object CATEGORY_TYPE_DEFAULT_ = ((EFactory)ModelFactory.INSTANCE).createFromString(ModelPackageImpl.eINSTANCE.getObject(), myCat); The class ModelPackageImpl doesn't exist. I've tried this with the 1.0 version of SDO and a version I built today. Let me know if you need any more information. Thanks, -Chris -- 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] Issue Comment Edited: (TUSCANY-1780) [JAVA-SDO] Incorrect generation of class with default value for a list
[ https://issues.apache.org/jira/browse/TUSCANY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536432 ] kgoodson edited comment on TUSCANY-1780 at 10/20/07 6:46 AM: --- Commented in error was (Author: kgoodson): Here's what the generator should be generating I think. protected static final List CATEGORY_TYPE_DEFAULT_ = (List)((XsdlistwitdefaultFactoryImpl)XsdlistwitdefaultFactory.INSTANCE).createFromString(XsdlistwitdefaultFactoryImpl.CATEGORY_TYPE, myCat); [JAVA-SDO] Incorrect generation of class with default value for a list -- Key: TUSCANY-1780 URL: https://issues.apache.org/jira/browse/TUSCANY-1780 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0, Java-SDO-Next Environment: Windows XP, JRE 1.4.2 and JRE 1.5 Reporter: Chris Mildebrandt Priority: Critical Fix For: Java-SDO-Next Attachments: Address.xsd, Address2.xsd Hello, There seems to be a problem when generating static classes when lists are involved. I have the following lines in my schema: xsd:attribute name=categoryType type=address:CategoryType use=required default=myCat/ simpleType name=CategoryType list itemType=category / /simpleType This generates the following line in the impl class: protected static final Object CATEGORY_TYPE_DEFAULT_ = ((EFactory)ModelFactory.INSTANCE).createFromString(ModelPackageImpl.eINSTANCE.getObject(), myCat); The class ModelPackageImpl doesn't exist. I've tried this with the 1.0 version of SDO and a version I built today. Let me know if you need any more information. Thanks, -Chris -- 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]
[SDO JAVA] JIRA priorities for the next release
I'm looking through the mounting number of JIRAs in SDO Java and hope to knock a few down. It would be good to get another release in plan. What do people want in it? I'm going to be doing a full pass through the open JIRAs in the near term and flag up my own priorities. Regards, Kelvin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-193) Fix eclipse warnings for sdo/tools
[ https://issues.apache.org/jira/browse/TUSCANY-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-193. Resolution: Fixed cleaned up referenced files Fix eclipse warnings for sdo/tools -- Key: TUSCANY-193 URL: https://issues.apache.org/jira/browse/TUSCANY-193 Project: Tuscany Issue Type: Improvement Components: Java SDO Tools Reporter: Daniel Kulp Assignee: Frank Budinsky Priority: Minor Fix For: Java-SDO-Next Attachments: sdo.patch Very small and minor patch to the sdo/tools section to remove the last eclipse warning in there. Also patches one file in sdo/impl. The only eclipse warning left in there is use of a deprecated API. -- 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] Resolved: (TUSCANY-1128) Support attribute and element with same name
[ https://issues.apache.org/jira/browse/TUSCANY-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1128. - Resolution: Fixed Support attribute and element with same name Key: TUSCANY-1128 URL: https://issues.apache.org/jira/browse/TUSCANY-1128 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Affects Versions: Java-SDO-Next Reporter: Yang ZHONG Priority: Minor Fix For: Java-SDO-Next Attachments: 1128.patch, 1128.patch, DifferAttrFromElementTestCase.java, dupelement.xsd, dupelement.xsd, DupElementTestCase.java, DupElementTestCase.java To support attribute and element with same name within one Type such as complexType sequence element name=property type=int/ /sequence attribute name=property type=string/ /complexType and using @property to access attribute and property to access element. This is to support OTA standard schema used in the travel industry. @property notation comes from XPath: http://www.w3.org/TR/xpath#path-abbrev -- 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] Resolved: (TUSCANY-1144) Type Schema Location
[ https://issues.apache.org/jira/browse/TUSCANY-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1144. - Resolution: Later Will await SDO 3 spec group resolution. Type Schema Location Key: TUSCANY-1144 URL: https://issues.apache.org/jira/browse/TUSCANY-1144 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Affects Versions: Java-SDO-Next Reporter: Yang ZHONG Fix For: Java-SDO-Next Attachments: 1144.patch SCA Java2WSDL has an option not to regenerate XSD if a static SDO comes from XSD, therefore the originating XSD location info is required for a (static) SDO Type. -- 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: ApacheCon Europe 2008
Hi, sorry I missed responding to this. Haleh, I like the changes to the abstract. Patrick, a joint session sounds really good. However, having got this far I now find I have an issue with the timing of ApacheCon, so is there someone else from Tuscany community that might like to present this with Patrick? Regards, Kelvin. On 17/10/2007, Simon Laws [EMAIL PROTECTED] wrote: Hi Patrick In lieu of Kelvin responding to this (I was going to help Kelvin out and make the slides) I think it would be really good to have you be part of the presentation. It brings a slightly different perspective and broadens the appeal I think. Regards Simon On 10/16/07, Patrick Leonard [EMAIL PROTECTED] wrote: Haleh, the abstract looks good. Kelvin, I would be happy to join you if you want to do the multi-presenter. From: haleh mahbod [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 16, 2007 1:08 PM To: tuscany-dev@ws.apache.org Subject: Re: ApacheCon Europe 2008 How about the following. The talk is in April and by then there might be other releases beyond release 1.0 which is emphasized in the original text. An update on Apache Tuscany project- Building SOA solutions is easy Apache Tuscany provides an open-source services infrastructure for constructing SOA solutions from heterogeneous and distributed services. This talk will focus on Apache Tuscany's implementation of Service Component Architecture which is based on V1.0 specification that is now under OASIS for standardization. In addition, the talk will cover Apache Tuscany added extensions such as web 2.0, scripting, distribution and multi-language support as well as integration with other Apache projects such as ODE and Geronimo. Some of the interesting topics that are under discussion in Apache Tuscany will be highlighted. The talk will be complemented with a demo to demonstrate how easy it is to use Apache Tuscany to develop SOA solutions. On 10/11/07, Simon Laws [EMAIL PROTECTED] wrote: On 10/9/07, kelvin goodson [EMAIL PROTECTED] wrote: ApacheCon Europe is coming up, 7th to 11th of April 2008 [1], and the deadline for submission of abstracts is coming up fast, on 26th of this month. What should we aim to do here? The options seem to be (60 minutes) Multi-person panel discussion (60 minutes) Normal presentation Intensive topical training (full-day) Intensive topical training (half-day) Intensive topical training (two-day) My guess is that we should submit for a 60 minute presentation, but should we go for a tutorial session as well? I'm happy to coordinate, and although presenting on SCA would take me a little out of my comfort zone, I would welcome the chance to do so. As a possible starting point for thinking about this I was looking at Simon Laws' abstract and presentation for the recent JavaZone conference [2], [3]. What would we want to update or emphasize differently from this? In the short term we just need to get an abstract together and think about who will do the presentation. Regards, Kelvin. [1] http://www.eu.apachecon.com/ [2] http://www4.java.no/web/show.do?page=92articleid=5343 [3] http://cwiki.apache.org/confluence/download/attachments/68184/BuildingSO AWithApacheTuscany.ppt?version=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I would certainly submit an abstract for a 60 minute presentation. I know others in the community have been working on tutorial material. What's the state of that? If that is going ahead then that material could be reused and a proposal made. Would be good to get more mileage out of it. Regards Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ApacheCon Europe 2008
Simon, you are right, I haven't submitted the abstract, so please do, and thanks for stepping in. Kelvin. On 18/10/2007, Simon Laws [EMAIL PROTECTED] wrote: On 10/18/07, Simon Laws [EMAIL PROTECTED] wrote: On 10/18/07, kelvin goodson [EMAIL PROTECTED] wrote: Hi, sorry I missed responding to this. Haleh, I like the changes to the abstract. Patrick, a joint session sounds really good. However, having got this far I now find I have an issue with the timing of ApacheCon, so is there someone else from Tuscany community that might like to present this with Patrick? Regards, Kelvin. On 17/10/2007, Simon Laws [EMAIL PROTECTED] wrote: Hi Patrick In lieu of Kelvin responding to this (I was going to help Kelvin out and make the slides) I think it would be really good to have you be part of the presentation. It brings a slightly different perspective and broadens the appeal I think. Regards Simon On 10/16/07, Patrick Leonard [EMAIL PROTECTED] wrote: Haleh, the abstract looks good. Kelvin, I would be happy to join you if you want to do the multi-presenter. From: haleh mahbod [mailto:[EMAIL PROTECTED] ] Sent: Tuesday, October 16, 2007 1:08 PM To: tuscany-dev@ws.apache.org Subject: Re: ApacheCon Europe 2008 How about the following. The talk is in April and by then there might be other releases beyond release 1.0 which is emphasized in the original text. An update on Apache Tuscany project- Building SOA solutions is easy Apache Tuscany provides an open-source services infrastructure for constructing SOA solutions from heterogeneous and distributed services. This talk will focus on Apache Tuscany's implementation of Service Component Architecture which is based on V1.0 specification that is now under OASIS for standardization. In addition, the talk will cover Apache Tuscany added extensions such as web 2.0, scripting, distribution and multi-language support as well as integration with other Apache projects such as ODE and Geronimo. Some of the interesting topics that are under discussion in Apache Tuscany will be highlighted. The talk will be complemented with a demo to demonstrate how easy it is to use Apache Tuscany to develop SOA solutions. On 10/11/07, Simon Laws [EMAIL PROTECTED] wrote: On 10/9/07, kelvin goodson [EMAIL PROTECTED] wrote: ApacheCon Europe is coming up, 7th to 11th of April 2008 [1], and the deadline for submission of abstracts is coming up fast, on 26th of this month. What should we aim to do here? The options seem to be (60 minutes) Multi-person panel discussion (60 minutes) Normal presentation Intensive topical training (full-day) Intensive topical training (half-day) Intensive topical training (two-day) My guess is that we should submit for a 60 minute presentation, but should we go for a tutorial session as well? I'm happy to coordinate, and although presenting on SCA would take me a little out of my comfort zone, I would welcome the chance to do so. As a possible starting point for thinking about this I was looking at Simon Laws' abstract and presentation for the recent JavaZone conference [2], [3]. What would we want to update or emphasize differently from this? In the short term we just need to get an abstract together and think about who will do the presentation. Regards, Kelvin. [1] http://www.eu.apachecon.com/ [2] http://www4.java.no/web/show.do?page=92articleid=5343 [3] http://cwiki.apache.org/confluence/download/attachments/68184/BuildingSO AWithApacheTuscany.ppt?version=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I would certainly submit an abstract for a 60 minute presentation. I know others in the community have been working on tutorial material. What's the state of that? If that is going ahead then that material could be reused and a proposal made. Would be good to get more mileage out of it. Regards
[jira] Commented: (TUSCANY-1817) Improve SDO test infrastructure to re-use/re-execute most dynamic tests as static tests
[ https://issues.apache.org/jira/browse/TUSCANY-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534846 ] Kelvin Goodson commented on TUSCANY-1817: - Thanks for your suggestions. One small problem we would have to overcome is that maven does not make test code available from one project to another project that expresses a dependency on it. Moving some part of the test code into the implementation wouldn't be nice from the point of view the run-time artifacts that are distributed. Separating testing out into higher level projects means we wouldn't get the automatic benefits of an immediate notification of the introduction of an issue when building with maven. We could insert an intermediate test-core project, that is not part of the SDO distribution, either between the API project and the lib projects (in dependency terms) or between the lib and the impl projects. The bodies of the tests could then be implemented in the _main_ source folder hierarchy of that project (as opposed to the test code hierarchy). The test bodies would be in abstract classes with template methods as you suggest. The lib, impl and tools-tests projects can then declare a test scope dependency on that new project, and the test programs be implemented in the test code hierarchy of the implementation projects, extending the behaviour of the test programs in the new project. Similarly the tools-test project could declare a dependency on the new project. There would be a deficiency here that I haven't got my head round yet. If we want a single location for the schemas, then they would have to be in the new project. This means I think that we wouldn't be able to rely on maven's generate phase to handle the generation for us in the tools-test project. One possibility would be to use svn's externals property to make the same schema files available to the test resources of both projects, but that may be a trip hazard. Improve SDO test infrastructure to re-use/re-execute most dynamic tests as static tests --- Key: TUSCANY-1817 URL: https://issues.apache.org/jira/browse/TUSCANY-1817 Project: Tuscany Issue Type: Improvement Components: Java SDO Tools Affects Versions: Java-SDO-Next Reporter: Ron Gavlin Fix For: Java-SDO-Next Currently, static Tuscany SDO is being inadequately tested. Based on TUSCANY-1812, I suspect there are currently numerous dynamic test cases that would fail if they were executed as static test cases. I suggest the testing infrastructure be enhanced to allow tests to be re-used as both dynamic and static tests with minimal effort. The build should automatically execute these shared tests in both dynamic and static contexts. -- 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: ApacheCon Europe 2008
How about this for an abstract for a 60 minute presentation? Meet Apache Tuscany - Building SOA Solutions With The Service Component Architecture Apache Tuscany provides an open-source services infrastructure for constructing SOA solutions from heterogeneous and distributed services. The project is currently very active; it has achieved the V1.0 milestone (released September 2007), as of V1.0 it implements V1.0 of the Service Component Architecture specifications currently being standardized at OASIS, the software is growing in maturity and the developer and user communities are building rapidly. With Apache Tuscany SCA, application developers can easily create, reuse and customize services in different languages, for example, Java, XQuery, BPEL or various scripting languages, and then assemble and deploy them in a distributed environment using a variety of protocols, for example, WebServices, RMI, JSONRPC, RSS, Atom, DWR and JMS. In this talk we catch up with all of the recent Apache Tuscany SCA project activity and its collaboration with other Apache projects such as ODE and Axis and show you how to build you own service oriented applications using Tuscany SCA. Kelvin. On 11/10/2007, Simon Laws [EMAIL PROTECTED] wrote: On 10/9/07, kelvin goodson [EMAIL PROTECTED] wrote: ApacheCon Europe is coming up, 7th to 11th of April 2008 [1], and the deadline for submission of abstracts is coming up fast, on 26th of this month. What should we aim to do here? The options seem to be (60 minutes) Multi-person panel discussion (60 minutes) Normal presentation Intensive topical training (full-day) Intensive topical training (half-day) Intensive topical training (two-day) My guess is that we should submit for a 60 minute presentation, but should we go for a tutorial session as well? I'm happy to coordinate, and although presenting on SCA would take me a little out of my comfort zone, I would welcome the chance to do so. As a possible starting point for thinking about this I was looking at Simon Laws' abstract and presentation for the recent JavaZone conference [2], [3]. What would we want to update or emphasize differently from this? In the short term we just need to get an abstract together and think about who will do the presentation. Regards, Kelvin. [1] http://www.eu.apachecon.com/ [2] http://www4.java.no/web/show.do?page=92articleid=5343 [3] http://cwiki.apache.org/confluence/download/attachments/68184/BuildingSOAWithApacheTuscany.ppt?version=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I would certainly submit an abstract for a 60 minute presentation. I know others in the community have been working on tutorial material. What's the state of that? If that is going ahead then that material could be reused and a proposal made. Would be good to get more mileage out of it. Regards Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SDO] merging Change Summaries
Amita, The detail of the nature of the merge you want to perform is not completely clear, but you should be aware that inserting a DataObject of a Type that has a ChangeSummary property into a data graph wrapped in a DataGraph instance would violate the constraint that the scope of monitoring of two change summaries may not overlap. It would be interesting to know more about the issue you are trying to solve. It is possible to have a data graph (not DataGraph) with two or more change summaries in, by ensuring that the containment hierarchies of the DataObjects which contain the change summary properties do not overlap. That way you could assemble a composite graph carrying all the change summary info. There's no API for merging change summaries. The only way I can see might be possible for doing what you want would be something like 1) capture the change summary info for the DataObject in the DataGraph; reset the data in the DataGraph to its original state at the start of logging; merge the two graphs and replay the steps necessary to achieve the changes that had been made to the data that was originally in the DataGraph. Regards, Kelvin On 10/10/2007, Amita Vadhavkar [EMAIL PROTECTED] wrote: When I have DO1 embedded in DataGraph and the DataGraph has change summary and I have DO2 with change summary property. Is it possible to merge change summary of DO1(from data graph) with change summary from DO2 to form a final data graph with DO3 with effective change summary? Regards, Amita - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Tuscany as a top level project
+1 Kelvin. On 09/10/2007, Venkata Krishnan [EMAIL PROTECTED] wrote: Ant, thank you for starting the thread. +1 from me. - Venkat On 10/9/07, ant elder [EMAIL PROTECTED] wrote: Looks like we've closed all the discussions around this so we can now vote on it. We've an Incubator discussion thread on our graduation but I don't see why we can't let that run in parallel, so ... Please vote on graduating Tuscany as a top level project and the proposal below. Heres my +1. ...ant WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software that simplifies the development and deployment of service oriented applications and provides a managed service-oriented runtime based on the standards defined by the OASIS OpenCSA group, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Tuscany Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Tuscany Project be and hereby is responsible for the creation and maintenance of software related to Apache Tuscany; and be it further RESOLVED, that the office of Vice President, Apache Tuscany be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Tuscany Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Tuscany Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Tuscany Project: Adriano Crestaniadrianocrestani at apache dot org Andrew Borley ajborley at apache dot org Andy Grove agrove at apache dot org ant elder antelder at apache dot org Brady Johnson bjohnson at apache dot org Frank Budinsky frankb at apache dot org Ignacio Silva-Lepe isilval at apache dot org Jean-Sebastien Delfino jsdelfino at apache dot org kelvin goodson kelvingoodson at apache dot org Luciano Resende lresende at apache dot org Mike Edwards edwardsmj at apache dot org Pete Robbinsrobbinspg at apache dot org Raymond Feng rfeng at apache dot org Simon Laws slaws at apache dot org Simon Nash nash at apache dot org Venkata Krishnan svkrish at apache dot org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder be appointed to the office of Vice President, Apache Tuscany, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Tuscany Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Tuscany podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Tuscany podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1838) HelperContext provided to createObjectOutputStream is inadvertantly ignored
HelperContext provided to createObjectOutputStream is inadvertantly ignored --- Key: TUSCANY-1838 URL: https://issues.apache.org/jira/browse/TUSCANY-1838 Project: Tuscany Issue Type: Bug Affects Versions: Java-SDO-1.0 Reporter: Kelvin Goodson Fix For: Java-SDO-Next Ron Gavlin reported in http://www.mail-archive.com/[EMAIL PROTECTED]/msg01884.html an issue with HelperContexts being unavailable during marshalling. I feel sure that this is due to this piece of code here in HelperProviderBase::ResolvableImpl#writeDataObject XMLHelper xmlHelperLocal = xmlHelper; if(objectOutput instanceof SDOObjectInputStream) { xmlHelperLocal = ((SDOObjectInputStream)objectOutput).getHelperContext().getXMLHelper(); } xmlHelperLocal.save(dataObject, commonj.sdo, dataObject, gzipOutputStream); where the instanceof test and cast should be to SDOObjectOutputStream -- 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] Commented: (TUSCANY-1838) HelperContext provided to createObjectOutputStream is inadvertantly ignored
[ https://issues.apache.org/jira/browse/TUSCANY-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533327 ] Kelvin Goodson commented on TUSCANY-1838: - I made a fix in http://svn.apache.org/viewvc?rev=583095view=rev Could you see if this fixes your issue please? HelperContext provided to createObjectOutputStream is inadvertantly ignored --- Key: TUSCANY-1838 URL: https://issues.apache.org/jira/browse/TUSCANY-1838 Project: Tuscany Issue Type: Bug Affects Versions: Java-SDO-1.0 Reporter: Kelvin Goodson Fix For: Java-SDO-Next Ron Gavlin reported in http://www.mail-archive.com/[EMAIL PROTECTED]/msg01884.html an issue with HelperContexts being unavailable during marshalling. I feel sure that this is due to this piece of code here in HelperProviderBase::ResolvableImpl#writeDataObject XMLHelper xmlHelperLocal = xmlHelper; if(objectOutput instanceof SDOObjectInputStream) { xmlHelperLocal = ((SDOObjectInputStream)objectOutput).getHelperContext().getXMLHelper(); } xmlHelperLocal.save(dataObject, commonj.sdo, dataObject, gzipOutputStream); where the instanceof test and cast should be to SDOObjectOutputStream -- 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]
ApacheCon Europe 2008
ApacheCon Europe is coming up, 7th to 11th of April 2008 [1], and the deadline for submission of abstracts is coming up fast, on 26th of this month. What should we aim to do here? The options seem to be (60 minutes) Multi-person panel discussion (60 minutes) Normal presentation Intensive topical training (full-day) Intensive topical training (half-day) Intensive topical training (two-day) My guess is that we should submit for a 60 minute presentation, but should we go for a tutorial session as well? I'm happy to coordinate, and although presenting on SCA would take me a little out of my comfort zone, I would welcome the chance to do so. As a possible starting point for thinking about this I was looking at Simon Laws' abstract and presentation for the recent JavaZone conference [2], [3]. What would we want to update or emphasize differently from this? In the short term we just need to get an abstract together and think about who will do the presentation. Regards, Kelvin. [1] http://www.eu.apachecon.com/ [2] http://www4.java.no/web/show.do?page=92articleid=5343 [3] http://cwiki.apache.org/confluence/download/attachments/68184/BuildingSOAWithApacheTuscany.ppt?version=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Java SDO CTS] enhancing the CTS
I've been thinking about the CTS a bit lately; trying to take stock of what we've got, and how we measure up. The CTS went through a period of healthy growth a while back, but I didn't manage to get a good feel for how well we were covering the API combined with the range of possible inputs to it. I ran the maven clover plugin to try to get some idea of how well we cover the API, but the results show coverage for the implementation classes, and it's not easy to get a good picture for how good the coverage of SDO API interface from that data (For example, there's much code in the Tuscany SDO implementation to support generated code which of course doesn't get exercised by the CTS). Does anyone know of good techniques for getting pure API coverage data? It would be good to get some structure into the CTS to make it more evident in the test code what is covered, and what is not. I'm thinking about perhaps restructuring and adding to the tests to achieve this. I may end up just adding stub tests in the first place in some places to highlight the fact that we are deficient in that area. Kelvin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[SDO Java] value change event notification
I took a look at some code a week or so back, which provided for adding the feature of notification of value changes to arbitrary observers, designed for use in user interfaces in JIRA https://issues.apache.org/jira/browse/TUSCANY-1527. I made a copy of SDO in my sandbox [1] and modified our SDO code to unblock the underlying EMF notification mechanism [2,3]. This kind of thing has been discussed a few times before, so I thought I'd just raise awareness of this activity to those who may not have spotted this going on in the JIRA to see if you have any comments. Kelvin. [1] http://svn.apache.org/viewvc/incubator/tuscany/sandbox/kgoodson/events/ [2] http://svn.apache.org/viewvc?view=revrevision=572682 [3] http://svn.apache.org/viewvc?rev=572685view=rev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to convert DataObjects to and from Java objects
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531723 ] Kelvin Goodson commented on TUSCANY-1493: - Hi, Thanks for the code. Sorry to take a while to get back to you. I have revisited this a few times to make sure I have a reasonably good feel for it before commenting. I'd love to be able to execute a test program to answer some of the question I have about the code, or at least to see some code that exercises it. Looking at the SnapshotSerializer code I think I'm OK to make the inference that the Type and Property classes used in there are your implementation classes of the SDO concepts, although of course that implementation code is not available. So, given that assumption, I understand that the implementation of your opaque snapshot representation is based on SDOs. It would be interesting to understand the issues you have encountered in using the code; for example, if there are any lossy round-trip transformations that cause problems. It would be great to work towards getting some code running inside the Tuscany code base; it would also be helpful if you could put some more words around any key design concepts and the issues you have encountered and solved, or have yet to solve. How should we proceed? Clearly the code is broken at the moment, given the missing aspects, so it's not suitable for including in the nightly build. I can put it in my sandbox, or I could set up another project under the SDO project, but not include it in the main build. Snapshot mapping framework to convert DataObjects to and from Java objects -- Key: TUSCANY-1493 URL: https://issues.apache.org/jira/browse/TUSCANY-1493 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: sdo-snapshot.zip, sdo.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa). To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts. - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly. - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects). - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily. This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion. I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component. -- 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] Commented: (TUSCANY-1493) Snapshot mapping framework to convert DataObjects to and from Java objects
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531727 ] Kelvin Goodson commented on TUSCANY-1493: - I've been going through the files in preparation for putting them into the code base somewhere, and have been adding apache license headers to the files that have no headers, on the basis of the license you granted when attaching the zip files. There are about 10 files in the archives which have Agfa copyright headers in them (e.g. ExtendablePropertyAccessBuilder.java), saying that . ... // THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF //Agfa-Gevaert Group I don't feel it's right for me to remove those headers, although I guess that would be in the spirit of the submission. Could you please search for files with similar headers to that file, fix the headers as you see fit, and resubmit any files you wish to be included in the submission. Snapshot mapping framework to convert DataObjects to and from Java objects -- Key: TUSCANY-1493 URL: https://issues.apache.org/jira/browse/TUSCANY-1493 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: sdo-snapshot.zip, sdo.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa). To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts. - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly. - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects). - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily. This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion. I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component. -- 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] Commented: (TUSCANY-1493) Snapshot mapping framework to convert DataObjects to and from Java objects
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531744 ] Kelvin Goodson commented on TUSCANY-1493: - I've added as much as I can to my sandbox in commit http://svn.apache.org/viewvc?rev=581184view=rev I've not added anything from the hibernate integration archive due to the licensing issues alluded to earlier. Two of the files with header issues are part of the generic snapshot code, so they are missing from what I have committed (see the commit comment in http://svn.apache.org/viewvc?rev=581184view=rev) Snapshot mapping framework to convert DataObjects to and from Java objects -- Key: TUSCANY-1493 URL: https://issues.apache.org/jira/browse/TUSCANY-1493 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: sdo-snapshot.zip, sdo.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa). To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts. - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly. - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects). - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily. This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion. I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component. -- 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: [SDO+DAS] order of changed data objects in change summary
Comments inline ... Kelvin. On 02/10/2007, Amita Vadhavkar [EMAIL PROTECTED] wrote: Hi, Question in SDO - ChangeSummary changeSummary = root.getDataGraph().getChangeSummary(); List changedDOs = commonj.sdo.ChangeSummary.getChangedDataObjects(); is changedDOs an ordered list with order based on time of the change (i.e. if a user does a particular sequence of create, delete etc. is the sequence preserved in the changedDOs?) A change summary describes the net effect of changes on the data objects in the scope of the change summary since the point that logging began. It doesn't reveal a full temporally sequenced change history. Question in DAS - when das.applyChanges(root) happens with multiple changes, in Changes.execute() - DAS uses buckets of 1) insert, 2)update, 3) delete to fire the SQL statements in that order. Thus DAS does not attempt to preserve the order from changedDOs. As a result, even if a user has done delete(customer.id=1) and then create( customer.id=1), DAS attempts INSERT first and then DELETE and give SQL Integrity exception. If SDO change summary is preserving the order of changes, will it be better to propagate the same order in Changes.execute()? {Please refer to JIRA-1815 for some history.} Regards, Ammita - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Graduation
On 27/09/2007, Mike Edwards [EMAIL PROTECTED] wrote: Folks, My pennyworth: a Project Management Committee charged with the creation and maintenance of open-source software supporting a range of technologies that simplifies the development of service oriented applications and provides a managed service-oriented runtime, based on the standards defined by the OASIS OpenCSA group, for distribution at no charge to the public. I think it worth pointing out that there will be support for a range of technologies - both implementation kinds and protocol kinds -hence the words I've added. +1 Yours, Mike. - 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: Graduation
On 27/09/2007, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Simon Nash wrote: Paul Fremantle wrote: +1 Paul On 9/27/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, My pennyworth: a Project Management Committee charged with the creation and maintenance of open-source software supporting a range of technologies that simplifies the development of service oriented applications and provides a managed service-oriented runtime, based on the standards defined by the OASIS OpenCSA group, for distribution at no charge to the public. This captures the right points, but it feels to me that the insertion of the extra words up front makes this sentence a little cumbersome, and the plural/singular juxtaposition of ...a range of technologies that simplifies... jars a little, though it is strictly correct grammatically. How about the following reordering: a Project Management Committee charged with the creation and maintenance of open-source software that simplifies the development of service oriented applications and provides a managed service-oriented runtime, supporting a range of technologies and based on the standards defined by the OASIS OpenCSA group, for distribution at no charge to the public. Simon This looks good to me, I have a few comments and questions: In addition to the programming model aspects, covered by simplifies the development of service oriented applications, how about adding something to cover the deployment, configuration and management models? Either add service oriented networks or at least change development to development and deployment? I'm not sure how a range of technologies further expands the scope of what we're doing, as the OpenCSA standards already span a range of technologies. Is it really necessary? Do people want to say something about things we're doing that are not covered by OpenCSA, the data access service work, the data binding work, and the SCA implementation and binding extensions that are not covered by OpenCSA? Are they all covered by the based on the standards defined by OpenCSA statement since they are related to either SCA or SDO? You are right, the based on the standards defined by OpenCSA is sufficient to cover SDO. I think it worth pointing out that there will be support for a range of technologies - both implementation kinds and protocol kinds -hence the words I've added. Yours, Mike. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jean-Sebastien - 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]
[jira] Commented: (TUSCANY-1817) Improve SDO test infrastructure to re-use/re-execute most dynamic tests as static tests
[ https://issues.apache.org/jira/browse/TUSCANY-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531015 ] Kelvin Goodson commented on TUSCANY-1817: - Ron, this sounds like a good idea. Do you have specific design thoughts or plans for a contribution for this? Improve SDO test infrastructure to re-use/re-execute most dynamic tests as static tests --- Key: TUSCANY-1817 URL: https://issues.apache.org/jira/browse/TUSCANY-1817 Project: Tuscany Issue Type: Improvement Components: Java SDO Tools Affects Versions: Java-SDO-Next Reporter: Ron Gavlin Currently, static Tuscany SDO is being inadequately tested. Based on TUSCANY-1812, I suspect there are currently numerous dynamic test cases that would fail if they were executed as static test cases. I suggest the testing infrastructure be enhanced to allow tests to be re-used as both dynamic and static tests with minimal effort. The build should automatically execute these shared tests in both dynamic and static contexts. -- 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] Commented: (TUSCANY-1810) SDOUtil.createHelperContext() fails with NPE on HP-UX and Solaris
[ https://issues.apache.org/jira/browse/TUSCANY-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530663 ] Kelvin Goodson commented on TUSCANY-1810: - This looks like an EMF problem. The failure seems to be in the EMF code at at org.eclipse.emf.ecore.impl.EPackageRegistryImpl$Delegator.getEFactory(EPackageRegistryImpl.java:250) which is .. return delegateRegistry().getEFactory(key); suggesting null return from ... protected EPackage.Registry delegateRegistry() { return delegateRegistry(Thread.currentThread().getContextClassLoader()); } which eventually ends up in ... public static synchronized EPackage.Registry getRegistry(ClassLoader classLoader) { EPackage.Registry result = (EPackage.Registry)classLoaderToRegistryMap.get(classLoader); if (result == null) { if (classLoader == null) { result = null; } else { result = new EPackageRegistryImpl(getRegistry(classLoader.getParent())); classLoaderToRegistryMap.put(classLoader, result); } } return result; } it would appear to me by eyeballing that code that the supplied ClassLoader is null (obtained by Thread.currentThread().getContextClassLoader()). I'm not expert in understanding in what circumstances that might happen. Could you please run this tiny program which I think embodies the issue in your environments, with the EMF 2.2.3 jars on your classpath, please and report the result. If this fails then the problem needs to be reported to EMF. package org.apache.tuscany.sdo.test; import org.eclipse.emf.ecore.EDataType; import org.eclipse.emf.ecore.EcoreFactory; public class EMFInit { protected static final EDataType UNINITIALIZED_EDATA_TYPE = EcoreFactory.eINSTANCE.createEDataType(); public static void main(String[] args) { System.out.println(Uninitialised data type is + (UNINITIALIZED_EDATA_TYPE == null ? null : not null)); } } SDOUtil.createHelperContext() fails with NPE on HP-UX and Solaris - Key: TUSCANY-1810 URL: https://issues.apache.org/jira/browse/TUSCANY-1810 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-1.0 Environment: This fails on HP-UX and Solaris. It works fine on all other platforms tested. Reporter: Travis Nelson Priority: Blocker The following exception is thrown when attempting to create the helper context: java.lang.NullPointerException at org.eclipse.emf.ecore.impl.EPackageRegistryImpl$Delegator.getEFactory(EPackageRegistryImpl.java:250) at org.eclipse.emf.ecore.impl.EcoreFactoryImpl.init(EcoreFactoryImpl.java:55) at org.eclipse.emf.ecore.EcoreFactory.clinit(EcoreFactory.java:35) at org.eclipse.emf.ecore.util.BasicExtendedMetaData.clinit(BasicExtendedMetaData.java:2139) at org.apache.tuscany.sdo.helper.DefaultHelperContextImpl.init(DefaultHelperContextImpl.java:31) at org.apache.tuscany.sdo.helper.HelperProviderImpl.createDefaultHelpers(HelperProviderImpl.java:37) at org.apache.tuscany.sdo.spi.HelperProviderBase.init(HelperProviderBase.java:81) at org.apache.tuscany.sdo.helper.HelperProviderImpl.init(HelperProviderImpl.java:30) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at commonj.sdo.impl.HelperProvider.loadImplementation(HelperProvider.java:157) at commonj.sdo.impl.HelperProvider.getInstance(HelperProvider.java:126) at commonj.sdo.impl.HelperProvider.clinit(HelperProvider.java:69) at org.apache.tuscany.sdo.api.SDOUtil.clinit(SDOUtil.java:47) at org.apache.tuscany.sdo.util.SDOUtil.createHelperContext(SDOUtil.java:389) -- 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] Updated: (TUSCANY-1780) [JAVA-SDO] Incorrect generation of class with default value for a list
[ https://issues.apache.org/jira/browse/TUSCANY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-1780: Patch Info: [Patch Available] Franks comment represents a fix - so setting patch available flag. [JAVA-SDO] Incorrect generation of class with default value for a list -- Key: TUSCANY-1780 URL: https://issues.apache.org/jira/browse/TUSCANY-1780 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0, Java-SDO-Next Environment: Windows XP, JRE 1.4.2 and JRE 1.5 Reporter: Chris Mildebrandt Priority: Critical Attachments: Address.xsd, Address2.xsd Hello, There seems to be a problem when generating static classes when lists are involved. I have the following lines in my schema: xsd:attribute name=categoryType type=address:CategoryType use=required default=myCat/ simpleType name=CategoryType list itemType=category / /simpleType This generates the following line in the impl class: protected static final Object CATEGORY_TYPE_DEFAULT_ = ((EFactory)ModelFactory.INSTANCE).createFromString(ModelPackageImpl.eINSTANCE.getObject(), myCat); The class ModelPackageImpl doesn't exist. I've tried this with the 1.0 version of SDO and a version I built today. Let me know if you need any more information. Thanks, -Chris -- 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: OSGi manifests in SDO Jars, was: Tuscany and OSGi
You are right, as far as I understand it's just history/legacy. If there's a volunteer to help clean this up and make the jars more friendly that would be really great; I don't have a detailed understanding of what's best here. Kelvin. On 26/09/2007, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Jean-Sebastien Delfino wrote: Philippe Ombredanne wrote: All: Some of the built binaries alreday have a manifest that is semi-osgi'fied. I suggest that it would be really nice if all the tuscany binaries could be delivered with a complete OSGi manifest. I can see only good stuffs from that as it makes OSGi friendly for Felix or Eclipse or general OSGi consumption. That is something that could be done as part of the build with little to no core code change. There are tools at Felix and http://www.aqute.biz/Code/Bnd that can help there. Ideally we should be to infer most everything from the poms. In practice there may be some subtle devilish details that may require some manual adjustments, but nothing extra ordinary. What do you think? It's not the first time that this comes up: http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200707.mbox/[EMAIL PROTECTED] ... good that you bring it up again as it looks like there was consensus to add OSGi manifest entries to the SCA API Jar, but it has not been done yet :) Only the SDO API Jar manifest contain OSGi entries at the moment, generated using the Felix plugin like that: plugin groupIdorg.apache.felix.plugins/groupId artifactIdmaven-osgi-plugin/artifactId version0.8.0-SNAPSHOT/version extensionstrue/extensions configuration osgiManifest bundleName${pom.name}/bundleName bundleDescription${pom.description}/bundleDescription bundleVendor${pom.organization.name}/bundleVendor bundleLocalizationplugin/bundleLocalization bundleSymbolicNamecommonj.sdo/bundleSymbolicName exportPackage commonj.sdo;version=${specVersion}, commonj.sdo.helper;version=${specVersion}, commonj.sdo.impl;version=${specVersion} /exportPackage /osgiManifest /configuration /plugin The SDO pom.xml probably needs to upgrade from Felix 0.8.0-SNAPSHOT to 1.0.0, and I believe that the plugin has been renamed to maven-bundle-plugin now. +1 from me to start adding OSGi manifest entries to the SCA sca-api and domain-api Jars. I'm not sure about adding OSGi manifests entries to all the other implementation Jars which do not publish any Application programming interfaces. Which configuration / use case will benefit from having OSGi manifest entries in these Jars? Thoughts? Actually more SDO Jars have OSGi manifests entries, generated differently, like that: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.1/version configuration archive manifestEntries Extension-Name${project.artifactId}/Extension-Name Specification-Title${project.name}/Specification-Title Specification-Vendor${project.organization.name}/Specification-Vendor Specification-Version${version}/Specification-Version Implementation-Title${project.artifactId}/Implementation-Title Implementation-Vendor${project.organization.name}/Implementation-Vendor Implementation-Vendor-Idorg.apache/Implementation-Vendor-Id Implementation-Version${project.version}/Implementation-Version !-- Bundle-ManifestVersion2/Bundle-ManifestVersion Bundle-Name${project.name}/Bundle-Name Bundle-SymbolicNameorg.apache.tuscany.sdo.impl/Bundle-SymbolicName Bundle-Version1.0.0/Bundle-Version Bundle-Vendor${project.organization.name}/Bundle-Vendor -- Require-Bundleorg.eclipse.emf.common,org.eclipse.emf.ecore,org.eclipse.emf.ecore.change,org.eclipse.emf.ecore.xmi,org.eclipse.xsd,org.apache.tuscany.sdo.spec;visibility:=reexport/Require-Bundle Export-Packagecommonj.sdo.impl,org.apache.tuscany.sdo,org.apache.tuscany.sdo.helper,org.apache.tuscany.sdo.impl,org.apache.tuscany.sdo.test,org.apache.tuscany.sdo.util/Export-Package /manifestEntries /archive /configuration /plugin This looks a little more complicated than the Felix way... Could the SDO folks shed some light on why some modules use Felix and others not? is it history? legacy? :) or is there a technical reason for that? Thanks -- Jean-Sebastien - 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]
[jira] Commented: (TUSCANY-1788) DataObjectXMLStreamReader doesn't declare the xsi namespace if there is a xsi:type or xsi:nil attribute
[ https://issues.apache.org/jira/browse/TUSCANY-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529826 ] Kelvin Goodson commented on TUSCANY-1788: - There has been one commit for this JIRA. I'm not sure if that's the full extent of the required fix. Can you provide a a test to demonstrate the fix please? DataObjectXMLStreamReader doesn't declare the xsi namespace if there is a xsi:type or xsi:nil attribute --- Key: TUSCANY-1788 URL: https://issues.apache.org/jira/browse/TUSCANY-1788 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Reporter: Raymond Feng Fix For: Java-SDO-Next In the case that we need to produce an xsi:type or xsi:nil attribute, the current code doesn't declare the xsi namespace. As a result, it creates an invalid XML stream. I'll check in a fix. -- 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] Commented: (TUSCANY-1493) Snapshot mapping framework to convert DataObjects to and from Java objects
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529846 ] Kelvin Goodson commented on TUSCANY-1493: - Bogdan, it's not in the code base yet. I'm looking at it now. Snapshot mapping framework to convert DataObjects to and from Java objects -- Key: TUSCANY-1493 URL: https://issues.apache.org/jira/browse/TUSCANY-1493 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: sdo-snapshot.zip, sdo.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa). To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts. - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly. - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects). - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily. This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion. I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component. -- 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] Resolved: (TUSCANY-1726) List DataObject.getList(String path) should return an empty list when there is no value
[ https://issues.apache.org/jira/browse/TUSCANY-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1726. - Resolution: Fixed Patch looks good, so I committed it with an adapted test to exercise equivalent generated classes. List DataObject.getList(String path) should return an empty list when there is no value --- Key: TUSCANY-1726 URL: https://issues.apache.org/jira/browse/TUSCANY-1726 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-1.0 Environment: WinXP Reporter: Fuhwei Lwo Fix For: Java-SDO-Next Attachments: 1726.patch According to SDO 2.1 spec section 3.1.4, it said DataObject methods with a return type of List, on the DataObject interface or generated, return empty lists rather than null when there is no value. This means getList() method should return an empty list when there is no value. Current implementation returns null which is wrong. -- 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] Resolved: (TUSCANY-1574) SDOXSDEcoreBuilder.createResourceSet() is not thread safe
[ https://issues.apache.org/jira/browse/TUSCANY-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1574. - Resolution: Fixed Fixed in rev 578054 SDOXSDEcoreBuilder.createResourceSet() is not thread safe - Key: TUSCANY-1574 URL: https://issues.apache.org/jira/browse/TUSCANY-1574 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-1.0 Environment: n/a Reporter: David T. Adcox Fix For: Java-SDO-Next Attachments: 1574.patch The method createResourceSet() in SDOXSDEcoreBuilder is not thread safe. It performs an enumeration of EPackage resource objects and adds them to the ResourceSet created within the method. The problem is that a ResourceSet object is a container. So, when the Resource objects are added with this statement: resources.add(resource); EMF attempts to first unlink the resource from its previous container. That in itself is an issue, but beyond that, during a stress run, the unlinking can occur simultaneously on multiple threads, causing exceptions. This code was added for Tuscany-513. I'm not clear what are the goals, but I was wondering if we can accomplish the same task in another manner. The goal seems to be to expose the newly created ResourceSet to the built-in models. Perhaps this pattern from DataObjectUtil.configureResourceSet would work: resourceSet.setPackageRegistry(new EPackageRegistryImpl(HelperContextImpl.getBuiltInModelRegistry())); Would this line of code accomplish a similar function? -- 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] Commented: (TUSCANY-1725) XSD2JavaGenerator has a problem with associations navigable from both sides
[ https://issues.apache.org/jira/browse/TUSCANY-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529388 ] Kelvin Goodson commented on TUSCANY-1725: - Thanks for this. I'd like to add the schema as the basis of a test, as a first step. We need you to grant license to the ASF to use it. Would you be able to attach a file with the schema please and tick the Grant License button please? XSD2JavaGenerator has a problem with associations navigable from both sides --- Key: TUSCANY-1725 URL: https://issues.apache.org/jira/browse/TUSCANY-1725 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0 Environment: Linux Reporter: Miro Kandic Fix For: Java-SDO-Next XSD2JavaGenerator does not work in the case of any association type (association, composition) that is navigable from both sides. I have intentionally, just to test generator, made Customer-SoH association in the next schema navigable from both sides and generated code cannot be compiled. Frank, after initial analyses, confirmed that saying Bidirectional references are broken in Tuscany. They seem to have been broken when we switched over to the new (noEMF) codegen patterns. Next is complete XSD built automatically from the UML model. ?xml version=1.0 encoding=UTF-8? !-- Attention: Generated code! Do not modify by hand! Generated by: XmlSchema.vsl in andromda-xmlschema-cartridge. -- xsd:schema targetNamespace=http://www.cisco.com/odns/soa; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:sdo=commonj.sdo xmlns:sdoxml=commonj.sdo/xml xmlns:impl=http://www.cisco.com/odns/soa; elementFormDefault=qualified xsd:import namespace=commonj.sdo/xml schemaLocation=sdoXML.xsd/ xsd:complexType name=Address xsd:sequence xsd:element name=street type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=city type=xsd:string minOccurs=1 maxOccurs=1/ /xsd:sequence xsd:attribute name=xmlId type=xsd:ID/ /xsd:complexType xsd:complexType name=Customer xsd:sequence xsd:element name=orders type=xsd:IDREF sdoxml:propertyType=impl:SoH sdoxml:oppositeProperty=customer minOccurs=0 maxOccurs=unbounded / xsd:element name=name type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=created type=xsd:date minOccurs=1 maxOccurs=1/ xsd:element name=lastUpdated type=xsd:dateTime minOccurs=1 maxOccurs=1/ xsd:element name=modifiedBy type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=id type=xsd:long minOccurs=1 maxOccurs=1/ /xsd:sequence xsd:attribute name=xmlId type=xsd:ID/ /xsd:complexType xsd:complexType name=Part xsd:sequence xsd:element name=uom type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=aggState type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=id type=xsd:long minOccurs=1 maxOccurs=1/ /xsd:sequence xsd:attribute name=xmlId type=xsd:ID/ /xsd:complexType xsd:complexType name=Product xsd:complexContent xsd:extension base=impl:Part xsd:sequence xsd:element name=description type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=modifiedBy type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=lastUpdated type=xsd:dateTime minOccurs=1 maxOccurs=1/ xsd:element name=created type=xsd:date minOccurs=1 maxOccurs=1/ /xsd:sequence /xsd:extension /xsd:complexContent /xsd:complexType xsd:complexType name=SoH xsd:sequence xsd:element name=customer type=xsd:IDREF sdoxml:propertyType=impl:Customer sdoxml:oppositeProperty=orders minOccurs=1 maxOccurs=1 / xsd:element name=lines type=impl:SoL minOccurs=0 maxOccurs=unbounded / xsd:element name=number type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=receivedDate type=xsd:date minOccurs=1 maxOccurs=1/ xsd:element name=modifiedBy type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=lastUpdated type=xsd:dateTime minOccurs=1 maxOccurs=1/ xsd:element name=created type=xsd:date minOccurs=1 maxOccurs=1/ xsd:element name=id type=xsd:long minOccurs=1 maxOccurs=1/ /xsd:sequence xsd:attribute name=xmlId type=xsd:ID/ /xsd:complexType xsd:complexType name=SoL xsd:sequence xsd:element name=product type=xsd:IDREF sdoxml:propertyType=impl:Product
[jira] Issue Comment Edited: (TUSCANY-1725) XSD2JavaGenerator has a problem with associations navigable from both sides
[ https://issues.apache.org/jira/browse/TUSCANY-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529388 ] kgoodson edited comment on TUSCANY-1725 at 9/21/07 4:46 AM: -- Thanks for this. I'd like to add the schema as the basis of a test, as a first step. We need you to grant license to the ASF to use it. Would you be able to attach a file with the schema please and tick the Grant License button please? (for ref: here's the thread that led to this jira -- http://www.mail-archive.com/[EMAIL PROTECTED]/msg01818.html) was (Author: kgoodson): Thanks for this. I'd like to add the schema as the basis of a test, as a first step. We need you to grant license to the ASF to use it. Would you be able to attach a file with the schema please and tick the Grant License button please? XSD2JavaGenerator has a problem with associations navigable from both sides --- Key: TUSCANY-1725 URL: https://issues.apache.org/jira/browse/TUSCANY-1725 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0 Environment: Linux Reporter: Miro Kandic Fix For: Java-SDO-Next XSD2JavaGenerator does not work in the case of any association type (association, composition) that is navigable from both sides. I have intentionally, just to test generator, made Customer-SoH association in the next schema navigable from both sides and generated code cannot be compiled. Frank, after initial analyses, confirmed that saying Bidirectional references are broken in Tuscany. They seem to have been broken when we switched over to the new (noEMF) codegen patterns. Next is complete XSD built automatically from the UML model. ?xml version=1.0 encoding=UTF-8? !-- Attention: Generated code! Do not modify by hand! Generated by: XmlSchema.vsl in andromda-xmlschema-cartridge. -- xsd:schema targetNamespace=http://www.cisco.com/odns/soa; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:sdo=commonj.sdo xmlns:sdoxml=commonj.sdo/xml xmlns:impl=http://www.cisco.com/odns/soa; elementFormDefault=qualified xsd:import namespace=commonj.sdo/xml schemaLocation=sdoXML.xsd/ xsd:complexType name=Address xsd:sequence xsd:element name=street type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=city type=xsd:string minOccurs=1 maxOccurs=1/ /xsd:sequence xsd:attribute name=xmlId type=xsd:ID/ /xsd:complexType xsd:complexType name=Customer xsd:sequence xsd:element name=orders type=xsd:IDREF sdoxml:propertyType=impl:SoH sdoxml:oppositeProperty=customer minOccurs=0 maxOccurs=unbounded / xsd:element name=name type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=created type=xsd:date minOccurs=1 maxOccurs=1/ xsd:element name=lastUpdated type=xsd:dateTime minOccurs=1 maxOccurs=1/ xsd:element name=modifiedBy type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=id type=xsd:long minOccurs=1 maxOccurs=1/ /xsd:sequence xsd:attribute name=xmlId type=xsd:ID/ /xsd:complexType xsd:complexType name=Part xsd:sequence xsd:element name=uom type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=aggState type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=id type=xsd:long minOccurs=1 maxOccurs=1/ /xsd:sequence xsd:attribute name=xmlId type=xsd:ID/ /xsd:complexType xsd:complexType name=Product xsd:complexContent xsd:extension base=impl:Part xsd:sequence xsd:element name=description type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=modifiedBy type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=lastUpdated type=xsd:dateTime minOccurs=1 maxOccurs=1/ xsd:element name=created type=xsd:date minOccurs=1 maxOccurs=1/ /xsd:sequence /xsd:extension /xsd:complexContent /xsd:complexType xsd:complexType name=SoH xsd:sequence xsd:element name=customer type=xsd:IDREF sdoxml:propertyType=impl:Customer sdoxml:oppositeProperty=orders minOccurs=1 maxOccurs=1 / xsd:element name=lines type=impl:SoL minOccurs=0 maxOccurs=unbounded / xsd:element name=number type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=receivedDate type=xsd:date minOccurs=1 maxOccurs=1/ xsd:element name=modifiedBy type=xsd:string minOccurs=1 maxOccurs=1/ xsd:element name=lastUpdated
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Congratulations and welcome Simon! hear hear!! Kelvin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3a
+1 Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3a/http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sample start up time?
RC3 is much faster now, it now runs in 2 seconds --- C:\Release\SCA\1.0\RC3\bin\tuscany-sca-1.0-incubating\samples\calculatorant run Buildfile: build.xml run: [java] 3 + 2=5.0 [java] 3 - 2=1.0 [java] 3 * 2=6.0 [java] 3 / 2=1.5 BUILD SUCCESSFUL Total time: 2 seconds C:\Release\SCA\1.0\RC3\bin\tuscany-sca-1.0-incubating\samples\calculator for me, thanks. On 18/09/2007, Raymond Feng [EMAIL PROTECTED] wrote: Hi, I guess I make all of you anxious to know what's wrong :-). Here is the problem, the OSGi contribution modules starts the OSGi runtime in its contribution listener/class reference resolver. But there is no code to shutdown the OSGi runtime. As a result, there are a few felix threads when the runtime is stopped and it hangs. I'm fixing the problem as follows: 1) Make sure the OSGi runtime won't be inited until it's required 2) Add a module activator for osgi-runtime to shutdown the OSGi runtime upon the stopping of the Tuscany runtime. I'm running a build now and will commit the fix soon (if the maven build doesn't overheat my laptop this time :-(, It took me almost one hour to recover from last crash). Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org; [EMAIL PROTECTED] Sent: Monday, September 17, 2007 3:01 PM Subject: Re: sample start up time? On 9/17/07, ant elder [EMAIL PROTECTED] wrote: Wonderful. ...ant On 9/17/07, Raymond Feng [EMAIL PROTECTED] wrote: Yes, that's what I meant. Thanks, Raymond - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Monday, September 17, 2007 1:54 PM Subject: Re: sample start up time? Is that also going to help the shutdown hang problem? ...ant On 9/17/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, I found the issue and will check in a fix soon. Thanks, Raymond - Original Message - From: kelvin goodson [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Monday, September 17, 2007 8:01 AM Subject: Re: sample start up time? Hmm, I just re-ran this against RC1b and the calculator sample hung after producing its results. All the output appeared pretty quickly, but then it failed to stop. C:\Release\RC1b\tuscany-sca-1.0-incubating\samples\calculatorant ru Buildfile: build.xml run: [java] 3 + 2=5.0 [java] 3 - 2=1.0 [java] 3 * 2=6.0 [java] 3 / 2=1.5 [java] Java Result: 1 BUILD SUCCESSFUL Total time: 8 minutes 4 seconds Terminate batch job (Y/N)? y On 17/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: I can run the calculator in 4 seconds, -- time until I see the Run word on the screen approx 2 secs and then a further 2 before I see the result output. Kelvin. On 17/09/2007, Simon Laws [EMAIL PROTECTED] wrote: I made a local distro from the branch and the samples seem to take ages to get going. A really comical amount of time! It takes 25 seconds before I see any output after running the calculator sample. Anyone else seeing that? 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] That's made a big (+ve) difference. What was the problem Raymond? 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: [VOTE] Release Tuscany Java SCA 1.0 RC3
The source distro now has a reference to quote-xquery in the top level pom, but the sample code is not included in the distro. C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-srcmvn clean [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant (Note, the artifacts are still uploading so if it looks like something's missing please just wait a bit, You can use the tag to verify things in the meantime) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1527) Allow for custom data binding of DataObjects in a Swing UI
[ https://issues.apache.org/jira/browse/TUSCANY-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528702 ] Kelvin Goodson commented on TUSCANY-1527: - The info I have on these events came from Frank's book (http://www.informit.com/store/product.aspx?isbn=0131425420rl=1). There's a whole load of pointers to documents and resources at http://www.eclipse.org/modeling/emf/docs/ which may save you having to lay your hands on the book. Allow for custom data binding of DataObjects in a Swing UI -- Key: TUSCANY-1527 URL: https://issues.apache.org/jira/browse/TUSCANY-1527 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: bert.robben Fix For: Java-SDO-Next Attachments: com.zip We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. On the client side we use sdo objects as model objects for our UI. As such, we need a mechanism for binding our objects to the UI controls such that changes in the objects are reflected in the UI and vice versa. At the moment, there is no real standard for data binding and many different implementations exist. As such, it would not be a good idea to build support for this directly into the sdo core. Ideally, the sdo core would allow implementations supporting data binding to be added as extensions [an extension as in jar, module, bundle, component, ...]. This is a request for supporting this in Tuscany SDO. - For our applications, we developed our own implementation of the sdo specification. This implementation is designed to support that kind of extensions. In the rest of this description, I'd like to show more details on our implementation to make this more clear and to serve as food for a possible discussion. Our sdo core module defines the abstract class AbstractPartialDataObject implementing DataObject. This class (together with its superclasses) implements the majority of the bevahiour of DataObject. This includes bi-directional property updates, type-safe properties, containment, ... It doesn't implement however the basic access to property values. Here's a code fragment. public abstract class AbstractPartialDataObject extends AbstractDataObject implements PartialDataObject { protected abstract Object basicGet(Property property); protected abstract void basicSet(Property property, Object value); public Object get(Property property) { ... } public void set(Property property, Object value) { ... } ... } The sdo core module also provides a non-abstract class DataObjectImplementation that provides a simple implementation of this abstract behaviour where the property values are stored in an ArrayList. On top of that we defined an extension that deals with our UI requirements. Our UI is based on a proprietary UI framework. This framework has the following requirements: - single valued properties should be exposed as XObservables. An XObservable is a kind of ValueModel that provides access to a value (get/set) and also allows for registration of change listeners - multi valued properties should be exposed as ListModel instances. A ListModel is a proprietary class (a bit similar to the javax.swing.ListModel) that provides List functionality and also allows for change listeners - the data object itself should allow registration of attribute change listeners that are notified each time a property changes The extension implements these requirements by providing an appropriate subclass ObservableDataObject of AbstractPartialDataObject. The only other pieces of code needed in the extension is an appropriate implementation of DataFactory and a wrapper to deal with the differences between ListModel and List. Here's the class with the most important code snippets. public class ObservableDataObject extends CompositePartialDataObject implements { private XObservable[] properties; protected ObservableDataObject(com.agfa.hap.sdo.Type type) { super(type); this.properties = new XObservable[type.getProperties().size()]; for (int i = 0; i properties.length; i++) { initializeProperty(type.getProperty(i)); } } private XObservableObject initializeProperty(Property prop) { XObservableObject observable = XObservableFactory.create(prop.getType().getInstanceClass(), this); if (prop.isMany()) { observable.init(new DataObjectListModel(this, prop)); } properties[prop.getIndex()] = observable; return observable; } public XObservable
[jira] Created: (TUSCANY-1759) quote-xquery code missing from RC3 source distro
quote-xquery code missing from RC3 source distro Key: TUSCANY-1759 URL: https://issues.apache.org/jira/browse/TUSCANY-1759 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.0 Environment: windows and http://people.apache.org/~antelder/tuscany/1.0-RC3/apache-tuscany-sca-1.0-incubating-src.zip Reporter: Kelvin Goodson Fix For: Java-SCA-1.0 C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-srcmvn [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) -- 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: [VOTE] Release Tuscany Java SCA 1.0 RC3
If I remove the xquery-quotes reference in the samples pom and try to build further i eventually get to the Tuscany SCA Axis2-based WS Binding Extension project where I see ... === Downloading: http://ws.zones.apache.org/repository//org.apache.woden/jars/woden-1.0-incubating-M7b.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0- incubating-M7b.jar Downloading: http://www.ibiblio.net/pub/packages/maven2/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0-incubating-M 7b.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.woden:woden:jar:1.0-incubating-M7b Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.woden -DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org .apache.woden -DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating 2) org.apache.woden:woden:jar:1.0-incubating-M7b -- 1 required artifact is missing. for artifact: org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating from the specified remote repositories: apache.incubator (http://people.apache.org/repo/m2-incubating-repository), central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache.ws (http://ws.zones.apache.org/repository/) On 19/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: The source distro now has a reference to quote-xquery in the top level pom, but the sample code is not included in the distro. C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-srcmvn clean [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant (Note, the artifacts are still uploading so if it looks like something's missing please just wait a bit, You can use the tag to verify things in the meantime) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Change freeze on 1.0 branch
Hi ant, I had a brief sweep through the build code for SCA to see if I could fix the xquery source distro to see if I could supply a patch with the JIRA, but I couldn't see that it was configurable; I guess either I missed something this is a manual export step. Regards, Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-1759) quote-xquery code missing from RC3 source distro
[ https://issues.apache.org/jira/browse/TUSCANY-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson reassigned TUSCANY-1759: --- Assignee: Kelvin Goodson quote-xquery code missing from RC3 source distro Key: TUSCANY-1759 URL: https://issues.apache.org/jira/browse/TUSCANY-1759 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.0 Environment: windows and http://people.apache.org/~antelder/tuscany/1.0-RC3/apache-tuscany-sca-1.0-incubating-src.zip Reporter: Kelvin Goodson Assignee: Kelvin Goodson Fix For: Java-SCA-1.0 C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-srcmvn [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) -- 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: [VOTE] Release Tuscany Java SCA 1.0 RC3
sorry - should have been more specific ... ant's fix for the repository --- pom.xml (revision 577121) +++ pom.xml (working copy) @@ -42,6 +42,17 @@ idapache.incubator/id urlhttp://people.apache.org/repo/m2-incubating-repository/url /repository +repository +idapache.ws.zone/id +nameApache WS Zone Repository/name +urlhttp://ws.zones.apache.org/repository2/url +releases +enabledtrue/enabled +/releases +snapshots +enabledfalse/enabled +/snapshots +/repository /repositories profiles works for me. Kelvin. On 19/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: Works for me. -- Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: If I remove the xquery-quotes reference in the samples pom and try to build further i eventually get to the Tuscany SCA Axis2-based WS Binding Extension project where I see ... === Downloading: http://ws.zones.apache.org/repository//org.apache.woden/jars/woden-1.0-incubating-M7b.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0- incubating-M7b.jar Downloading: http://www.ibiblio.net/pub/packages/maven2/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0-incubating-M 7b.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.woden:woden:jar:1.0-incubating-M7b Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId= org.apache.woden-DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org .apache.woden -DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating 2) org.apache.woden:woden:jar:1.0-incubating-M7b -- 1 required artifact is missing. for artifact: org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating from the specified remote repositories: apache.incubator ( http://people.apache.org/repo/m2-incubating-repository ), central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), apache.ws (http://ws.zones.apache.org/repository/) On 19/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: The source distro now has a reference to quote-xquery in the top level pom, but the sample code is not included in the distro. C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-srcmvn clean [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany- sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java :378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java :290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java :125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3/ The artifacts are available for review at: http://people.apache.org
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3
That's where mine now fails too. On 19/09/2007, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: If I remove the xquery-quotes reference in the samples pom and try to build further i eventually get to the Tuscany SCA Axis2-based WS Binding Extension project where I see ... === Downloading: http://ws.zones.apache.org/repository//org.apache.woden/jars/woden-1.0-incubating-M7b.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0- incubating-M7b.jar Downloading: http://www.ibiblio.net/pub/packages/maven2/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0-incubating-M 7b.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.woden:woden:jar:1.0-incubating-M7b Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId= org.apache.woden-DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org .apache.woden -DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating 2) org.apache.woden:woden:jar:1.0-incubating-M7b -- 1 required artifact is missing. for artifact: org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating from the specified remote repositories: apache.incubator ( http://people.apache.org/repo/m2-incubating-repository ), central (http://repo1.maven.org/maven2), apache.snapshots ( http://people.apache.org/repo/m2-snapshot-repository ), apache.ws (http://ws.zones.apache.org/repository/) On 19/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: The source distro now has a reference to quote-xquery in the top level pom, but the sample code is not included in the distro. C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-srcmvn clean [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany- sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects( DefaultMaven.java :378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java :290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java :125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant (Note, the artifacts are still uploading so if it looks like something's missing please just wait a bit, You can use the tag to verify things in the meantime) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This is also a result of not having a repo dependency
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3
Works for me. -- Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: If I remove the xquery-quotes reference in the samples pom and try to build further i eventually get to the Tuscany SCA Axis2-based WS Binding Extension project where I see ... === Downloading: http://ws.zones.apache.org/repository//org.apache.woden/jars/woden-1.0-incubating-M7b.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0- incubating-M7b.jar Downloading: http://www.ibiblio.net/pub/packages/maven2/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0-incubating-M 7b.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.woden:woden:jar:1.0-incubating-M7b Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId= org.apache.woden-DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org .apache.woden -DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating 2) org.apache.woden:woden:jar:1.0-incubating-M7b -- 1 required artifact is missing. for artifact: org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating from the specified remote repositories: apache.incubator ( http://people.apache.org/repo/m2-incubating-repository ), central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), apache.ws (http://ws.zones.apache.org/repository/) On 19/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: The source distro now has a reference to quote-xquery in the top level pom, but the sample code is not included in the distro. C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-srcmvn clean [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany- sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java :378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java :290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java :125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant (Note, the artifacts are still uploading so if it looks like something's missing please just wait a bit, You can use the tag to verify things in the meantime) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This is also a result of not having a repo dependency on http://ws.zones.apache.org/repository2 http://ws.zones.apache.org/repository2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1 If I add the dependency to the tpo level pom alongside our repository idapache.incubator/id
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3
I'm having a sequence of non-reproducible issues building from this tag first I got [INFO] - --- [INFO] Building Apache Tuscany SCA Composite Sample [INFO]task-segment: [install] [INFO] - --- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 6 source files to C:\Release\SCA\1.0\RC3a\svn\samples\implement ation-composite\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 1 source file to C:\Release\SCA\1.0\RC3a\svn\samples\implementa tion-composite\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\Release\SCA\1.0\RC3a\svn\samples\implementa tion-composite\target\surefire-reports --- T E S T S --- Running composite.CompositeTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.821 sec FA ILURE! test(composite.CompositeTestCase) Time elapsed: 0.771 sec ERROR! org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.sca.contribution.service.ContributionResolveException: java.lang. ClassNotFoundException: org.apache.tuscany.sca.node.impl.NodeManagerServiceImpl at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCAD omain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain. java:58) at composite.CompositeTestCase.setUp(CompositeTestCase.java:32) but a rebuild in the project directory succeeded now the top level build is hanging indefinitely at ... [INFO] --- [INFO] Building Apache Tuscany SCA Script Implementation Extension [INFO]task-segment: [install] [INFO] --- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://people.apache.org/repo/m2-incubating-repository/groovy/groo y-all/1.0/groovy-all-1.0.pom [WARNING] Unable to get resource 'groovy:groovy-all:pom:1.0' from repository ap che.incubator (http://people.apache.org/repo/m2-incubating-repository) Downloading: http://ws.zones.apache.org/repository2/groovy/groovy-all/1.0/groov -all-1.0.pom [WARNING] Unable to get resource 'groovy:groovy-all:pom:1.0' from repository ap che.ws.zone (http://ws.zones.apache.org/repository2) Downloading: http://www.ibiblio.net/pub/packages/maven2/groovy/groovy-all/1.0/g oovy-all-1.0.pom Anyone else seen anything like this? I'll kill it and try again. Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: That's where mine now fails too. On 19/09/2007, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: If I remove the xquery-quotes reference in the samples pom and try to build further i eventually get to the Tuscany SCA Axis2-based WS Binding Extension project where I see ... === Downloading: http://ws.zones.apache.org/repository//org.apache.woden/jars/woden-1.0-incubating-M7b.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0- incubating-M7b.jar Downloading: http://www.ibiblio.net/pub/packages/maven2/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0-incubating-M 7b.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.woden:woden:jar:1.0-incubating-M7b Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId= org.apache.woden-DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org .apache.woden -DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3
I have just seen Simon Laws' earlier note about my first issue. Kelvin. On 19/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: I'm having a sequence of non-reproducible issues building from this tag first I got [INFO] - --- [INFO] Building Apache Tuscany SCA Composite Sample [INFO]task-segment: [install] [INFO] - --- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 6 source files to C:\Release\SCA\1.0\RC3a\svn\samples\implement ation-composite\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 1 source file to C:\Release\SCA\1.0\RC3a\svn\samples\implementa tion-composite\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\Release\SCA\1.0\RC3a\svn\samples\implementa tion-composite\target\surefire-reports --- T E S T S --- Running composite.CompositeTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.821 sec FA ILURE! test(composite.CompositeTestCase) Time elapsed: 0.771 sec ERROR! org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.sca.contribution.service.ContributionResolveException: java.lang. ClassNotFoundException: org.apache.tuscany.sca.node.impl.NodeManagerServiceImpl at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCAD omain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain. java:58) at composite.CompositeTestCase.setUp(CompositeTestCase.java:32) but a rebuild in the project directory succeeded now the top level build is hanging indefinitely at ... [INFO] --- [INFO] Building Apache Tuscany SCA Script Implementation Extension [INFO]task-segment: [install] [INFO] --- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://people.apache.org/repo/m2-incubating-repository/groovy/groo y-all/1.0/groovy-all-1.0.pom [WARNING] Unable to get resource 'groovy:groovy-all:pom:1.0' from repository ap che.incubator (http://people.apache.org/repo/m2-incubating-repository) Downloading: http://ws.zones.apache.org/repository2/groovy/groovy-all/1.0/groov -all-1.0.pom [WARNING] Unable to get resource 'groovy:groovy-all:pom:1.0' from repository ap che.ws.zone (http://ws.zones.apache.org/repository2) Downloading: http://www.ibiblio.net/pub/packages/maven2/groovy/groovy-all/1.0/g oovy-all-1.0.pom Anyone else seen anything like this? I'll kill it and try again. Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: That's where mine now fails too. On 19/09/2007, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: If I remove the xquery-quotes reference in the samples pom and try to build further i eventually get to the Tuscany SCA Axis2-based WS Binding Extension project where I see ... === Downloading: http://ws.zones.apache.org/repository//org.apache.woden/jars/woden-1.0-incubating-M7b.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0- incubating-M7b.jar Downloading: http://www.ibiblio.net/pub/packages/maven2/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0-incubating-M 7b.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.woden:woden:jar:1.0-incubating-M7b Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId= org.apache.woden-DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3
my last two builds have hung on download.java.net, but the previous one hung on ibiblio.net Kelvin. [EMAIL PROTECTED] /cygdrive/c/Release/SCA/1.0/RC3a/svn $ tail -4 mvn2.log Downloading: http://ws.zones.apache.org/repository2/groovy/groovy-all/1.0/groovy -all-1.0.pom [WARNING] Unable to get resource 'groovy:groovy-all:pom:1.0' from repository apa che.ws.zone (http://ws.zones.apache.org/repository2) Downloading: http://www.ibiblio.net/pub/packages/maven2/groovy/groovy-all/1.0/gr oovy-all-1.0.pom Terminate batch job (Y/N)? [EMAIL PROTECTED] /cygdrive/c/Release/SCA/1.0/RC3a/svn $ tail -4 mvn3.log [WARNING] POM for 'org.jvnet.staxex:stax-ex:pom:1.0:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. Downloading: http://download.java.net/maven/1/com.sun.xml.ws/poms/jaxws-tools-2. 1.pom 628b downloaded Terminate batch job (Y/N)? [EMAIL PROTECTED] /cygdrive/c/Release/SCA/1.0/RC3a/svn $ tail -4 mvn4.log [WARNING] POM for 'com.sun.xml.stream.buffer:streambuffer:pom:0.4:compile' is in valid. It will be ignored for artifact resolution. Reason: Failed to validate PO M [WARNING] POM for 'org.jvnet.staxex:stax-ex:pom:1.0:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. Downloading: http://download.java.net/maven/1/com.sun.xml.ws/poms/jaxws-tools-2. 1.pom 628b downloaded On 19/09/2007, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi, I've tried from the branch and then from the RC3 tag and my top level build too hangs ... its been hanging at [INFO] [INFO] Building Apache Tuscany SCA WSDL2Java Tool [INFO]task-segment: [install] [INFO] [INFO] [build-helper:add-test-source {execution: add-test-source}] [INFO] Test Source directory: F:\Tag_1.0\modules\wsdl2java\target\sdo-source added. [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://download.java.net/maven/1/woodstox/poms/wstx-asl-3.2.1.pom - Venkat On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: I have just seen Simon Laws' earlier note about my first issue. Kelvin. On 19/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: I'm having a sequence of non-reproducible issues building from this tag first I got [INFO] - --- [INFO] Building Apache Tuscany SCA Composite Sample [INFO]task-segment: [install] [INFO] - --- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 6 source files to C:\Release\SCA\1.0\RC3a\svn\samples\implement ation-composite\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 1 source file to C:\Release\SCA\1.0\RC3a\svn\samples\implementa tion-composite\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\Release\SCA\1.0\RC3a\svn\samples\implementa tion-composite\target\surefire-reports --- T E S T S --- Running composite.CompositeTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.821sec FA ILURE! test(composite.CompositeTestCase) Time elapsed: 0.771 sec ERROR! org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.sca.contribution.service.ContributionResolveException : java.lang. ClassNotFoundException: org.apache.tuscany.sca.node.impl.NodeManagerServiceImpl at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCAD omain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance (SCADomain. java:58) at composite.CompositeTestCase.setUp(CompositeTestCase.java :32) but a rebuild in the project directory succeeded now the top level build is hanging indefinitely at ... [INFO] --- [INFO] Building Apache Tuscany SCA Script Implementation Extension [INFO]task-segment: [install] [INFO] --- [INFO
[jira] Resolved: (TUSCANY-1759) quote-xquery code missing from RC3 source distro
[ https://issues.apache.org/jira/browse/TUSCANY-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1759. - Resolution: Fixed fixed in http://svn.apache.org/viewvc?rev=577237view=rev quote-xquery code missing from RC3 source distro Key: TUSCANY-1759 URL: https://issues.apache.org/jira/browse/TUSCANY-1759 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.0 Environment: windows and http://people.apache.org/~antelder/tuscany/1.0-RC3/apache-tuscany-sca-1.0-incubating-src.zip Reporter: Kelvin Goodson Assignee: Kelvin Goodson Fix For: Java-SCA-1.0 C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-srcmvn [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) -- 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: [VOTE] Release Tuscany Java SCA 1.0 RC3
I have now done a clean build on RC3a from the referenced svn tag. Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: This RC3a is looking good to me, i've built it, the distros from that, then built that src distro, run a few samples including webapp ones, built some webapp samples with the Ant scripts. It all seems to work. Anyone else say yes or no soon or shall i just call a vote on it? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: That's where mine now fails too. On 19/09/2007, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, ant elder [EMAIL PROTECTED] wrote: On 9/19/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/19/07, kelvin goodson [EMAIL PROTECTED] wrote: If I remove the xquery-quotes reference in the samples pom and try to build further i eventually get to the Tuscany SCA Axis2-based WS Binding Extension project where I see ... === Downloading: http://ws.zones.apache.org/repository//org.apache.woden/jars/woden-1.0-incubating-M7b.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0- incubating-M7b.jar Downloading: http://www.ibiblio.net/pub/packages/maven2/org/apache/woden/woden/1.0-incubating-M7b/woden-1.0-incubating-M 7b.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.woden:woden:jar:1.0-incubating-M7b Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId= org.apache.woden-DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org .apache.woden -DartifactId=woden \ -Dversion=1.0-incubating-M7b -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating 2) org.apache.woden:woden:jar:1.0-incubating-M7b -- 1 required artifact is missing. for artifact: org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:1.0-incubating from the specified remote repositories: apache.incubator ( http://people.apache.org/repo/m2-incubating-repository ), central (http://repo1.maven.org/maven2), apache.snapshots ( http://people.apache.org/repo/m2-snapshot-repository ), apache.ws (http://ws.zones.apache.org/repository/) On 19/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: The source distro now has a reference to quote-xquery in the top level pom, but the sample code is not included in the distro. C:\Release\SCA\1.0\RC3\src\tuscany- sca-1.0-incubating-src mvn clean [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany- sca-1.0-incubating-src\samples\quote-xquery\po m.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\Release\SCA\1.0\RC3\src\tuscany-sca- 1.0-incubating-src\samples\quote-xquery\pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects( DefaultMaven.java :378) at org.apache.maven.DefaultMaven.doExecute( DefaultMaven.java :290
checking the license file
I just checked the LICENSE file against the lib directory of RC1c. I'm sure this process could be more automated given time, but for reference here's what I did cd lib ls | sed s/[0-9\.]*\.jar// libnoversion.txt then I hand finessed the list to remove more complex version tags such as beta1 or incubating then in a bash window $ for i in `cat libsnoversion.txt`; do echo $i ; grep -c $i LICENSE ; grep $i LICENSE ; echo = ; done jarrefcount.txt I then looked for grep counts of 0 to spot missing references, and where references existed that contained version number I verified by eye that the version numbers matched. Like I say, this could be done better given a bit of time, but I thought it might be worth recording this as a basis for improvement and for adding to release process docs. Kelvin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: checking the license file
a few, i checked in the changes about an hour ago. Kelvin. On 18/09/2007, Simon Laws [EMAIL PROTECTED] wrote: On 9/18/07, kelvin goodson [EMAIL PROTECTED] wrote: I just checked the LICENSE file against the lib directory of RC1c. I'm sure this process could be more automated given time, but for reference here's what I did cd lib ls | sed s/[0-9\.]*\.jar// libnoversion.txt then I hand finessed the list to remove more complex version tags such as beta1 or incubating then in a bash window $ for i in `cat libsnoversion.txt`; do echo $i ; grep -c $i LICENSE ; grep $i LICENSE ; echo = ; done jarrefcount.txt I then looked for grep counts of 0 to spot missing references, and where references existed that contained version number I verified by eye that the version numbers matched. Like I say, this could be done better given a bit of time, but I thought it might be worth recording this as a basis for improvement and for adding to release process docs. Kelvin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks for that Kelvin. Did you find any problems? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-1638) SDO command-line code generator behaves differently than standalone when invoked in Eclipse
[ https://issues.apache.org/jira/browse/TUSCANY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson resolved TUSCANY-1638. - Resolution: Fixed Assuming this is fixed in the live environment, since the test case passes. Please reopen if issues still exist. SDO command-line code generator behaves differently than standalone when invoked in Eclipse --- Key: TUSCANY-1638 URL: https://issues.apache.org/jira/browse/TUSCANY-1638 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0 Environment: OS is Windows XP Professional SP2, and the SDO command line tool is invoked in side an Eclipse 3.3 plugin. Reporter: Sean Zhou Fix For: Java-SDO-Next Attachments: 1638.patch, test1638.zip I am trying to invoke the SDO command-line code generator inside eclipse which is causing it to behave differently than standalone. The following fix is suggested by Frank in Tuscany: 1) In class org.apache.tuscany.sdo.generate.adapter.SDOGenModelGeneratorAdapterFactory add another override method, createGenModelAdapter(), to return a new Tuscany subclass of GenModelGeneratorAdapter (e.g., SDOGenModelGeneratorAdapter). 2) In the new subclass, override the ensureProjectExists() method to do nothing. 3) Override anything else you need to ... -- 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: [VOTE] Release Tuscany Java SCA 1.0-incubating
I'm now seeing a couple of issues with the samples. One is that I have to run ant compile before ant run in all cases I have tried so far. The other is that I now see samples such as calculator executing and completing, but taking 18 seconds to complete rather than the 4 I reported yesterday. Kelvin. On 18/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC2/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC2/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant (Note, the artifacts are still uploading so if it looks like something's missing please just wait a bit, You can use the tag to verify things in the meantime) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 1.0-incubating
Windows XP On 18/09/2007, haleh mahbod [EMAIL PROTECTED] wrote: ant run works fine with a few that I ran using RC2 bin distro. I am running on windows. What are you running on Kelvin? On 9/18/07, kelvin goodson [EMAIL PROTECTED] wrote: I'm now seeing a couple of issues with the samples. One is that I have to run ant compile before ant run in all cases I have tried so far. The other is that I now see samples such as calculator executing and completing, but taking 18 seconds to complete rather than the 4 I reported yesterday. Kelvin. On 18/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC2/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC2/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant (Note, the artifacts are still uploading so if it looks like something's missing please just wait a bit, You can use the tag to verify things in the meantime) - 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]
[jira] Commented: (TUSCANY-1296) Build failure on Linux/IBM JDK
[ https://issues.apache.org/jira/browse/TUSCANY-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528040 ] Kelvin Goodson commented on TUSCANY-1296: - I think I am seeing this issue when trying to build on linux. Is this what you saw? [INFO] Building Apache Tuscany SCA Data Binding for JAXB [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: com.sun.tools.xjc.maven2:maven-jaxb-plugin Reason: Failed to build model from file '/home/kg/.m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.pom'. Error: 'null' for project com.sun.tools.xjc.maven2:maven-jaxb-plugin == my environment is ... [EMAIL PROTECTED] sca-java-1.0]$ uname -a Linux kglinux 2.6.18-8.1.6.el5 #1 SMP Fri Jun 1 18:52:11 EDT 2007 i686 i686 i386 GNU/Linux with [EMAIL PROTECTED] sca-java-1.0]$ $JAVA_HOME/bin/java -version java version 1.5.0 Java(TM) 2 Runtime Environment, Standard Edition (build pxi32devifx-20070806 (SR5a)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20070426 (JIT enabled) J9VM - 20070420_12448_lHdSMR JIT - 20070419_1806_r8 GC - 200704_19) JCL - 20070725 Build failure on Linux/IBM JDK -- Key: TUSCANY-1296 URL: https://issues.apache.org/jira/browse/TUSCANY-1296 Project: Tuscany Issue Type: Bug Components: Build System Affects Versions: Java-SCA-0.90 Environment: Fedora Core 5 Ibm JDK 1.5.0 build 2.3 Maven 2.0.6 Reporter: Simon Laws Assignee: Simon Laws Fix For: Java-SCA-Next SCA fails to build under maven in my Linux/IBM JDK environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character which causes the maven build to fail with the IBM JDK 1.5.0 on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters. The best solution would be to move to a newer version of this plugin (I note that the author name that includes the non-UTF8 characted doesn't appear in later versions) but we need to test these later version on all platforms. -- 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]
jaxp.properties trip hazard -- FAQ material
I've been playing with the RC1a release candidate and came across a problem particular to my environment which took me a while to figure out. When trying to run a sample I was getting ... C:\Release\apache-tuscany-sca-1.0-incubating\tuscany-sca-1.0-incubating\samples\calculatorant run Buildfile: build.xml run: [java] Exception in thread main javax.xml.stream.FactoryConfigurationError: Provider null could not be instantiat ed: java.lang.NullPointerException [java] at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:75) [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:136) [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92) [java] at javax.xml.stream.XMLOutputFactory.newInstance(XMLOutputFactory.java:98) [java] at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntimeBuilder.createContributionService(ReallyS mallRuntimeBuilder.java:176) [java] at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.start(ReallySmallRuntime.java:114) [java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:101) [java] at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230) [java] at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69) [java] at calculator.CalculatorClient.main(CalculatorClient.java:31) [java] Java Result: 1 BUILD SUCCESSFUL Total time: 1 second C:\Release\apache-tuscany-sca-1.0-incubating\tuscany-sca-1.0-incubating\samples\calculatorant run The problem was that I had at some time in the past, altered by IBM 1.5 JRE environment so that it had a jaxp.properties file (I had followed the instructions in the jaxp.properties.sample file). Removing the jaxp.properties file allowed the sample to execute. I'll see about adding this to an FAQ on the wiki. Kelvin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sample start up time?
I can run the calculator in 4 seconds, -- time until I see the Run word on the screen approx 2 secs and then a further 2 before I see the result output. Kelvin. On 17/09/2007, Simon Laws [EMAIL PROTECTED] wrote: I made a local distro from the branch and the samples seem to take ages to get going. A really comical amount of time! It takes 25 seconds before I see any output after running the calculator sample. Anyone else seeing that? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sample start up time?
Hmm, I just re-ran this against RC1b and the calculator sample hung after producing its results. All the output appeared pretty quickly, but then it failed to stop. C:\Release\RC1b\tuscany-sca-1.0-incubating\samples\calculatorant ru Buildfile: build.xml run: [java] 3 + 2=5.0 [java] 3 - 2=1.0 [java] 3 * 2=6.0 [java] 3 / 2=1.5 [java] Java Result: 1 BUILD SUCCESSFUL Total time: 8 minutes 4 seconds Terminate batch job (Y/N)? y On 17/09/2007, kelvin goodson [EMAIL PROTECTED] wrote: I can run the calculator in 4 seconds, -- time until I see the Run word on the screen approx 2 secs and then a further 2 before I see the result output. Kelvin. On 17/09/2007, Simon Laws [EMAIL PROTECTED] wrote: I made a local distro from the branch and the samples seem to take ages to get going. A really comical amount of time! It takes 25 seconds before I see any output after running the calculator sample. Anyone else seeing that? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1685) XSD2JavaGenerator should support name mangling (dashes to underscores, etc.)
[ https://issues.apache.org/jira/browse/TUSCANY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528095 ] Kelvin Goodson commented on TUSCANY-1685: - Any name overrides must be done with schema annotations, so the input to the generator must contain those annotations, such as sdo:name=Bogus_1 in the input schema. The SDO spec allows for a generator to insert annotations into an updated schema before generating, in which case the generator must be able to output the annotated schema, but we don't have that capacity currently. XSD2JavaGenerator should support name mangling (dashes to underscores, etc.) Key: TUSCANY-1685 URL: https://issues.apache.org/jira/browse/TUSCANY-1685 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0 Reporter: Ron Gavlin Priority: Critical Fix For: Java-SDO-Next I have the following complex type in a schema: xsd:complexType name=Bogus-1 xsd:sequence xsd:element name=name1 type=xsd:string/ /xsd:sequence /xsd:complexType When I use XSD2JavaGenerator to code-generate classes for this schema, an invalidly named Bogus-1.java class is generated. The class name should be mangled into a valid Java class name, such as Bogus_1.java. EMF provides this behavior in its NameMangler which Tuscany currently disables. -- 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] Commented: (TUSCANY-1638) SDO command-line code generator behaves differently than standalone when invoked in Eclipse
[ https://issues.apache.org/jira/browse/TUSCANY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527498 ] Kelvin Goodson commented on TUSCANY-1638: - I was trying this, but don't see Run as .. = Eclipse Application in the context menu of the emitterTest project SDO command-line code generator behaves differently than standalone when invoked in Eclipse --- Key: TUSCANY-1638 URL: https://issues.apache.org/jira/browse/TUSCANY-1638 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0 Environment: OS is Windows XP Professional SP2, and the SDO command line tool is invoked in side an Eclipse 3.3 plugin. Reporter: Sean Zhou Fix For: Java-SDO-Next Attachments: 1638.patch, test1638.zip I am trying to invoke the SDO command-line code generator inside eclipse which is causing it to behave differently than standalone. The following fix is suggested by Frank in Tuscany: 1) In class org.apache.tuscany.sdo.generate.adapter.SDOGenModelGeneratorAdapterFactory add another override method, createGenModelAdapter(), to return a new Tuscany subclass of GenModelGeneratorAdapter (e.g., SDOGenModelGeneratorAdapter). 2) In the new subclass, override the ensureProjectExists() method to do nothing. 3) Override anything else you need to ... -- 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] Commented: (TUSCANY-1638) SDO command-line code generator behaves differently than standalone when invoked in Eclipse
[ https://issues.apache.org/jira/browse/TUSCANY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527546 ] Kelvin Goodson commented on TUSCANY-1638: - I have now run the test, seen the failure, applied the patch and seen clean code generation, so I will commit the patch. For reference I had to download the Eclipse Classic version of Europa, since the Java developers version doesn't include the eclipse plugin stuff. After that, when configuring the paths in the SampleAction class, I couldn't use an absolute path for the targetDirectory, since the test adds this to the base runtime directory of the spawned eclipse environment , so my config element looked like this ... IPath installIPath = new Path(C:/Dev/test1638/apache-tuscany-sca-0.99-incubating/tuscany-sca-0.99-incubating); String targetDirectory = /../test1638/output/; String wsdlURI = C:/Dev/test1638/AddressBook.wsdl; I could work this out by looking at the Run as dialog entry for the Eclipse Application and seeing that the runtime directory was .. ${workspace_loc}/../runtime-EclipseApplication SDO command-line code generator behaves differently than standalone when invoked in Eclipse --- Key: TUSCANY-1638 URL: https://issues.apache.org/jira/browse/TUSCANY-1638 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0 Environment: OS is Windows XP Professional SP2, and the SDO command line tool is invoked in side an Eclipse 3.3 plugin. Reporter: Sean Zhou Fix For: Java-SDO-Next Attachments: 1638.patch, test1638.zip I am trying to invoke the SDO command-line code generator inside eclipse which is causing it to behave differently than standalone. The following fix is suggested by Frank in Tuscany: 1) In class org.apache.tuscany.sdo.generate.adapter.SDOGenModelGeneratorAdapterFactory add another override method, createGenModelAdapter(), to return a new Tuscany subclass of GenModelGeneratorAdapter (e.g., SDOGenModelGeneratorAdapter). 2) In the new subclass, override the ensureProjectExists() method to do nothing. 3) Override anything else you need to ... -- 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]