RE: Sample framework
One thing concerns me would be the out-of-box user experience. For a first time Tuscany user, don't you think it is more user friendly if users only need to follow the readme, go to a directory, run a common, then everything works out-of-box? Speaking in my experience, it does encourage me to explore a new product further if I can set up and run a typical helloworld sample successfully in 5 minutes without any coding. Well, maybe just me being too lazy... ;-) Cheers, Jervis -Original Message- From: Jeremy Boynes [mailto:[EMAIL PROTECTED] Sent: Thursday, August 17, 2006 6:54 AM To: tuscany-dev@ws.apache.org Subject: Sample framework We have had a rapid increase in the number of samples recently many of which do essentially the same thing. Some feedback from M1 also said that we seemed to have invented the greatest number of varieties of HelloWorld but that it was hard to tell if SCA could do anything else. I'd like to propose a change in how we structure the samples so that we make it clearer to illustrate the technology to users. Rather than having separate projects for each technology variant, I'd like to suggest we have just a couple of projects that provide a framework and then have instructions in the documentation for each technology that clearly show how to apply it. For example, I can see two framework environments: a) a client environment with a simple command line client wires together a couple of local components b) a webapp environment with a simple JSP client that also wires together a couple of local components Then, for example, the JavaScript extension could say: To illustrate the use of JavaScript as a component, take the client a) and 1) replace implementation.java class=Foo/ with implementation.javascript script=foo.js/ 2) Install javascript extension 2) rebuild/run sample Or, to illustrate the WebService binding: Server 1) Take webapp and add servicebinding.ws ... 2) Install Axis binding extension 3) Deploy server app to Tomcat Client 1) Take client application and replace component name=foo ... with referencebinding.ws ... 2) Install Axis binding extension 3) Run client The basic idea being, have a common framework and the instructions on how to use the particular extension. -- Jeremy - 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-639) support for dependencies when referencing artifacts
[ http://issues.apache.org/jira/browse/TUSCANY-639?page=comments#action_12428586 ] Jeremy Boynes commented on TUSCANY-639: --- Another place where this applies is on include eg: include name=foo group=org.bar version=1.0/ support for dependencies when referencing artifacts --- Key: TUSCANY-639 URL: http://issues.apache.org/jira/browse/TUSCANY-639 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Reporter: Jervis Liu support for dependencies when referencing artifacts, for example, . implementation.composite name=foo group=org.bar version=1.0/. In this case, we can probably use some maven APIs to access the repo to resolve dependencies. See ArtifactRepository and it's implementation as a starting point. Enclosed below is IRC chat related to this topic. (01:55:14) jervisliu: I dont quite understand what you mean by I think this can be handled by the dependency mechanism and the use of the applicable location attributes e.g. wsdlLocation (01:55:35) jervisliu: what kind of dependency mechanism are you refering to? (01:56:08) jboynes: the ability to add dependency elements into SCDL to extend the classpath for the composite (01:56:55) jervisliu: this is not part of spec, right? (01:57:07) jboynes: no, it's a tuscany feature (01:57:33) jboynes: given the spec doesn't talk about packaging yet :-( (01:58:19) jervisliu: see. but it looks like there is an easier way to achieve same result. for example, the celtix-binding.jar can have a default.scdl (01:58:31) jboynes: sure (01:58:34) jboynes: you can do both (01:58:37) jervisliu: and the dependency of celtix-binding.jar can be specified in MANIFEST (01:58:48) jboynes: ah, no not really (01:59:09) jboynes: people hate manifest Class-Paths (01:59:19) jboynes: they still work and can be used (01:59:24) jervisliu: this can be done very easily in maven, and is a well understood way to resolve classpath dependencies (01:59:31) jboynes: yes (01:59:53) jboynes: dependency is quite maven friendly ;-) (02:00:36) jboynes: I also mentioned having the implementation use maven metadata if present in the jar (02:00:48) jervisliu: sure. I remember there was talk about a maven like dependency element. (02:00:58) jboynes: yep - - I just went and did it (02:01:19) jboynes: see ArtifactRepository and it's implementation (02:01:54) jboynes: having an implementation that used maven itself to locate the artifacts would be real cool (02:01:54) jervisliu: oh, i dont know its done already. ;-) (02:03:57) jervisliu: cool. so the scdl file under ext dir (using dependency) can only used for one binding implementation. right? (02:04:32) jboynes: well, it's a composite so it could contain components implemented by other nested composites (02:05:35) jervisliu: but then all dependencies will be merged to compose a classpath, (02:05:50) jboynes: no, the composite classloader is hierarchical (02:06:20) jboynes: the nested composites would be in child classloades (02:06:40) jervisliu: oklets have a concrete example. (02:07:08) jervisliu: how to write this scdl if we have both axis and celtix libraries under ext? (02:07:27) jboynes: well, you could just put them both in the ext directory (02:07:43) jboynes: then you wouldn't need any scdl (02:07:54) jboynes: s/libraries/bindings (02:08:41) jboynes: i.e put binding-axis.jar and binding-celtix.jar in ext (02:08:56) jervisliu: then when using binding.ws, which one is actually being used? (02:09:07) jboynes: why does it matter? (02:09:24) jervisliu: well, i just sent out an email to discuss this. (02:09:24) jboynes: it could be either but they both impl the spec (02:09:43) jboynes: by saying binding.ws the user us saying they don't care (02:10:01) jervisliu: maybe it does not matter. but users still wants to know whichi implementation they are actually using (02:10:41) jboynes: why? (02:10:56) jervisliu: and in the real world, it still matters. for example, both axis2 and celtix have their own configuration files, the default config file shipped with binding probably works for 99% situations (02:11:12) jervisliu: but it might be the case that they need to modify the config file. (02:11:29) jboynes: so in the real world how many users will actually use both concurrently? (02:11:32) jervisliu: in this case, they do need to know which implementation is loaded by tuscany (02:11:35) jboynes: no (02:11:48) jboynes: they need to make sure that they use the implementation they modified (02:12:05) jboynes: so if they modified celtix they should use binding.celtix.ws (02:12:21) jboynes: as that application will not work on a runtime that only has axis (02:12:59) jervisliu: ok. i think i m convinced on this. (02:14:06) jervisliu: the reason why i came
Re: svn commit: r432149 - in /incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/main/java/org/apache/tuscany/databinding/xmlbeans: Node2XmlObject.java XMLStreamReader2XmlObject.java XmlO
Raymond,
I notice a whole series of commits here with identical commit
messages - my guess is that you are using some IDE that does a poor
job of committing across the tree and inappropriately breaks it down
by project or something.
It is much easier for people to understand what is going on if you
commit everything in one go. Most people do not use the IDE function
to commit things but do it from the SVN command line so they have
precise control over what they are committing.
--
Jeremy
On Aug 16, 2006, at 10:42 PM, [EMAIL PROTECTED] wrote:
Author: rfeng
Date: Wed Aug 16 22:42:11 2006
New Revision: 432149
URL: http://svn.apache.org/viewvc?rev=432149view=rev
Log:
Applied my own patch sent before vacation and some other SDO
binding adjustments for Axis2 integration
Modified:
incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/Node2XmlObject.java
incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
XMLStreamReader2XmlObject.java
incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/XmlObject2Node.java
incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
XmlObject2XMLStreamReader.java
Modified: incubator/tuscany/java/sca/databinding/databinding-
xmlbeans/src/main/java/org/apache/tuscany/databinding/xmlbeans/
Node2XmlObject.java
URL: http://svn.apache.org/viewvc/incubator/tuscany/java/sca/
databinding/databinding-xmlbeans/src/main/java/org/apache/tuscany/
databinding/xmlbeans/Node2XmlObject.java?
rev=432149r1=432148r2=432149view=diff
==
--- incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
Node2XmlObject.java (original)
+++ incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
Node2XmlObject.java Wed Aug 16 22:42:11 2006
@@ -21,11 +21,12 @@
import org.apache.tuscany.databinding.TransformationContext;
import org.apache.tuscany.databinding.TransformationException;
import org.apache.tuscany.databinding.PullTransformer;
+import org.apache.tuscany.databinding.extension.TransformerExtension;
import org.apache.xmlbeans.XmlException;
import org.apache.xmlbeans.XmlObject;
import org.w3c.dom.Node;
-public class Node2XmlObject implements PullTransformerNode,
XmlObject {
+public class Node2XmlObject extends TransformerExtensionNode,
XmlObject implements PullTransformerNode, XmlObject {
// private XmlOptions options;
public XmlObject transform(Node source, TransformationContext
context) {
@@ -36,11 +37,11 @@
}
}
-public ClassXmlObject getTargetType() {
+public Class getTargetType() {
return XmlObject.class;
}
-public ClassNode getSourceType() {
+public Class getSourceType() {
return Node.class;
}
Modified: incubator/tuscany/java/sca/databinding/databinding-
xmlbeans/src/main/java/org/apache/tuscany/databinding/xmlbeans/
XMLStreamReader2XmlObject.java
URL: http://svn.apache.org/viewvc/incubator/tuscany/java/sca/
databinding/databinding-xmlbeans/src/main/java/org/apache/tuscany/
databinding/xmlbeans/XMLStreamReader2XmlObject.java?
rev=432149r1=432148r2=432149view=diff
==
--- incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
XMLStreamReader2XmlObject.java (original)
+++ incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
XMLStreamReader2XmlObject.java Wed Aug 16 22:42:11 2006
@@ -23,10 +23,11 @@
import org.apache.tuscany.databinding.TransformationContext;
import org.apache.tuscany.databinding.TransformationException;
import org.apache.tuscany.databinding.PullTransformer;
+import org.apache.tuscany.databinding.extension.TransformerExtension;
import org.apache.xmlbeans.XmlException;
import org.apache.xmlbeans.XmlObject;
-public class XMLStreamReader2XmlObject implements
PullTransformerXMLStreamReader, XmlObject {
+public class XMLStreamReader2XmlObject extends
TransformerExtensionXMLStreamReader, XmlObject implements
PullTransformerXMLStreamReader, XmlObject {
// private XmlOptions options;
public XmlObject transform(XMLStreamReader source,
TransformationContext context) {
@@ -37,11 +38,11 @@
}
}
-public ClassXmlObject getTargetType() {
+public Class getTargetType() {
return XmlObject.class;
}
-public ClassXMLStreamReader getSourceType() {
+public Class getSourceType() {
return XMLStreamReader.class;
}
Modified:
Fwd: svn commit: r432156
Raymond, I've noticed an SDO and databinding implementation dependencies have been introduced into the Axis2 binding. Based on your comments in the code, it appears this is temporary and related to implementing an interceptor into the policy framework. I'd prefer that we work on getting the correct solution in place ASAP and am uncomfortable with introducing hacks such as this one. There was an email thread the other day about introducing an interceptor and am happy to provide assistance if required. Could you please outline what is required so we can work towards a proper solution? Thanks, Jim Modified: incubator/tuscany/java/sca/bindings/binding.axis2/pom.xml incubator/tuscany/java/sca/bindings/binding.axis2/src/main/java/ org/apache/tuscany/binding/axis2/Axis2BindingBuilder.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/java/ org/apache/tuscany/binding/axis2/Axis2Reference.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/java/ org/apache/tuscany/binding/axis2/Axis2Service.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/java/ org/apache/tuscany/binding/axis2/ Axis2ServiceInOutSyncMessageReceiver.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/java/ org/apache/tuscany/binding/axis2/Axis2TargetInvoker.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/java/ org/apache/tuscany/binding/axis2/util/SDODataBinding.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/java/ org/apache/tuscany/binding/axis2/util/TuscanyAxisConfigurator.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ resources/META-INF/sca/default.scdl incubator/tuscany/java/sca/bindings/binding.axis2/src/test/java/ org/apache/tuscany/binding/axis2/Axis2ReferenceTestCase.java incubator/tuscany/java/sca/bindings/binding.axis2/src/test/java/ org/apache/tuscany/binding/axis2/Axis2ServiceTestCase.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: svn commit: r432157
Raymond, Sorry to keep harping on the dependencies issue but I now see we have the webapp project dependent on the Axis binding and SDO. I realize you did not introduce the Axis dependency and asked last week why it was introduced but never received a response...I assume it was because of issues we have with resolving dependencies. Could you please explain the issues that are forcing us down this path so we can find a solution? Significant hacks like this, if necessary, should really be discussed on the list prior to making them. Again, I am very uncomfortable with this as it appears we are loosing site of our modularity goal. Jim Begin forwarded message: From: [EMAIL PROTECTED] Date: August 16, 2006 10:47:48 PM PDT To: tuscany-commits@ws.apache.org Subject: svn commit: r432157 - in /incubator/tuscany/java/sca/ runtime/webapp/src/main/resources/META-INF/sca: binding.axis2.scdl composite.scdl databinding.sdo.scdl webapp.system.scdl Reply-To: tuscany-dev@ws.apache.org Author: rfeng Date: Wed Aug 16 22:47:47 2006 New Revision: 432157 URL: http://svn.apache.org/viewvc?rev=432157view=rev Log: Integrate Axis2 and SDO databinding for Web Service Added: incubator/tuscany/java/sca/runtime/webapp/src/main/resources/ META-INF/sca/binding.axis2.scdl incubator/tuscany/java/sca/runtime/webapp/src/main/resources/ META-INF/sca/databinding.sdo.scdl Modified: incubator/tuscany/java/sca/runtime/webapp/src/main/resources/ META-INF/sca/composite.scdl incubator/tuscany/java/sca/runtime/webapp/src/main/resources/ META-INF/sca/webapp.system.scdl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r432157
On Aug 17, 2006, at 12:28 AM, Jim Marino wrote: Raymond, Sorry to keep harping on the dependencies issue but I now see we have the webapp project dependent on the Axis binding and SDO. I realize you did not introduce the Axis dependency and asked last week why it was introduced but never received a response...I assume it was because of issues we have with resolving dependencies. Could you please explain the issues that are forcing us down this path so we can find a solution? Significant hacks like this, if necessary, should really be discussed on the list prior to making them. Again, I am very uncomfortable with this as it appears we are loosing site of our modularity goal. It also doesn't work as the axis binding uses dependency elements that require the AritfactRepository to be running and that is not part of the primordial deployer. These really should be deployed as extensions. A work-around might be to set the installDirectory in the RuntimeInfo for the webapp to the real path (as returned by getRealPath()) of an extension directory in the webapp e.g. WEB-INF/tuscany. This would be used by the DirectoryScanExtender as the base for resolving relative paths; with default config this would result in jars in WEB-INF/ tuscany/extension being loaded as extensions. Just an idea - YMMV -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-640) Service and Reference do not support multiple binding elements
Service and Reference do not support multiple binding elements Key: TUSCANY-640 URL: http://issues.apache.org/jira/browse/TUSCANY-640 Project: Tuscany Issue Type: Bug Components: Java SCA Core Reporter: Jeremy Boynes Priority: Critical According to the spec, Service and Reference definitions can have multiple bindings associated with them. Our config model and the associated loaders and builders only support a single binding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-641) Warning messages during compilation
Warning messages during compilation --- Key: TUSCANY-641 URL: http://issues.apache.org/jira/browse/TUSCANY-641 Project: Tuscany Issue Type: Bug Components: C++ SDO Affects Versions: Cpp-current Environment: WinXP Reporter: Caroline Maynard Priority: Trivial It would be nice to eliminate the warning messages that are seen during the compilation of Tuscany SDO C++ for the SDO for PHP Windows libraries: PropertyImpl.cpp C:\PROGRA~1\MICROS~2\VC98\INCLUDE\xmemory(34) : warning C4786: 'std::_Treestd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::pairstd::basic_stringchar,std::char_traitschar,std::allocatorchar const ,commonj::sdo::DASValue *,std::mapstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,commonj::sdo::DASValue *,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Kfn,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Nil' : identifier was truncated to '255' characters in the debug information C:\PROGRA~1\MICROS~2\VC98\INCLUDE\xmemory(34) : warning C4786: 'std::_Treestd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::pairstd::basic_stringchar,std::char_traitschar,std::allocatorchar const ,commonj::sdo::DASValue *,std::mapstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,commonj::sdo::DASValue *,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Kfn,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Nilrefs' : identifier was truncated to '255' characters in the debug information C:\PROGRA~1\MICROS~2\VC98\INCLUDE\xmemory(34) : warning C4786: 'std::_Treestd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::pairstd::basic_stringchar,std::char_traitschar,std::allocatorchar const ,commonj::sdo::DASValue *,std::mapstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,commonj::sdo::DASValue *,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Kfn,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ' : identifier was truncated to '255' characters in the debug information C:\PROGRA~1\MICROS~2\VC98\INCLUDE\xmemory(34) : warning C4786: 'std::_Treestd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::pairstd::basic_stringchar,std::char_traitschar,std::allocatorchar const ,commonj::sdo::DASValue *,std::mapstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,commonj::sdo::DASValue *,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Kfn,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::const_iterator' : identifier was truncated to '255' characters in the debug information C:\PROGRA~1\MICROS~2\VC98\INCLUDE\xmemory(34) : warning C4786: 'std::_Treestd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::pairstd::basic_stringchar,std::char_traitschar,std::allocatorchar const ,commonj::sdo::DASValue *,std::mapstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,commonj::sdo::DASValue *,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Kfn,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::iterator' : identifier was truncated to '255' characters in the debug information C:\PROGRA~1\MICROS~2\VC98\INCLUDE\xmemory(34) : warning C4786: 'std::_Treestd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::pairstd::basic_stringchar,std::char_traitschar,std::allocatorchar const ,commonj::sdo::DASValue *,std::mapstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,commonj::sdo::DASValue *,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Kfn,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue * ::_Node' : iPropertyList.cpp dentifier was truncated to '255' characters in the debug information C:\PROGRA~1\MICROS~2\VC98\INCLUDE\xmemory(34) : warning C4786: 'std::_Treestd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::pairstd::basic_stringchar,std::char_traitschar,std::allocatorchar const ,commonj::sdo::DASValue *,std::mapstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,commonj::sdo::DASValue *,std::lessstd::basic_stringchar,std::char_traitschar,std::allocatorchar ,std::allocatorcommonj::sdo::DASValue *
BUILD BREAK looking for: ws-commons:axiom-api:jar:SNAPSHOT
I think this is a real build break (not a bad pom in my maven repo)... I pasted my Maven output below after pulling the entire 'java' SVN branch and building I don't see that any of the remote repo sites contain SNAPSHOT versions of the Axis2 jars such as axiom-api, so I'm wondering how people are building against these... Are you manually grabbing the jars from somewhere and hand-copying them into your local Maven repo under 'SNAPSHOT' version names? Thanks mvn output pasted: [INFO] [INFO] Building Apache Tuscany Data Binding for Axiom [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-impl/SNAPSHOT/axiom-impl-SNAPSHOT.pom [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-api/SNAPSHOT/axiom-api-SNAPSHOT.pom [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-api/SNAPSHOT/axiom-api-SNAPSHOT.jar [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) ws-commons:axiom-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=ws-commons -DartifactId=axiom-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.tuscany.databinding:databinding-axiom:jar:1.0-SNAPSHOT 2) ws-commons:axiom-api:jar:SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.tuscany.databinding:databinding-axiom:jar:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), ibiblio (http://www.ibiblio.org/maven2)
Re: BUILD BREAK looking for: ws-commons:axiom-api:jar:SNAPSHOT
Just checked something in that fixed this. With that my build ran to completion. Scott Kurz wrote: I think this is a real build break (not a bad pom in my maven repo)... I pasted my Maven output below after pulling the entire 'java' SVN branch and building I don't see that any of the remote repo sites contain SNAPSHOT versions of the Axis2 jars such as axiom-api, so I'm wondering how people are building against these... Are you manually grabbing the jars from somewhere and hand-copying them into your local Maven repo under 'SNAPSHOT' version names? Thanks mvn output pasted: [INFO] [INFO] Building Apache Tuscany Data Binding for Axiom [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-impl/SNAPSHOT/axiom-impl-SNAPSHOT.pom [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-api/SNAPSHOT/axiom-api-SNAPSHOT.pom [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-api/SNAPSHOT/axiom-api-SNAPSHOT.jar [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) ws-commons:axiom-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=ws-commons -DartifactId=axiom-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.tuscany.databinding:databinding-axiom:jar:1.0-SNAPSHOT 2) ws-commons:axiom-api:jar:SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.tuscany.databinding:databinding-axiom:jar:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), ibiblio (http://www.ibiblio.org/maven2) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r432149 - in /incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/main/java/org/apache/tuscany/databinding/xmlbeans: Node2XmlObject.java XMLStreamReader2XmlObject.java XmlO
Hi,
Thank you for pointing it out and sorry for the pain. I was using the
Eclipse SVN plugin to commit the changes. Unfortunately the plugin didn't
group them in one chunk, instead, it splited them by project. One of the
reasons I decided to use IDE for this checkin is that I had multiple pending
changes overlapping in the code structure and I don't know how to use SVN
commond line to pick a list of files out of all the changes in my workspace.
I'm still learning and any help will be greatly appreciated.
Thanks,
Raymond
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, August 17, 2006 12:10 AM
Subject: Re: svn commit: r432149 - in
/incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/main/java/org/apache/tuscany/databinding/xmlbeans:
Node2XmlObject.java XMLStreamReader2XmlObject.java XmlObject2Node.java
XmlObject2XMLStreamReader.java
Raymond,
I notice a whole series of commits here with identical commit messages -
my guess is that you are using some IDE that does a poor job of
committing across the tree and inappropriately breaks it down by project
or something.
It is much easier for people to understand what is going on if you commit
everything in one go. Most people do not use the IDE function to commit
things but do it from the SVN command line so they have precise control
over what they are committing.
--
Jeremy
On Aug 16, 2006, at 10:42 PM, [EMAIL PROTECTED] wrote:
Author: rfeng
Date: Wed Aug 16 22:42:11 2006
New Revision: 432149
URL: http://svn.apache.org/viewvc?rev=432149view=rev
Log:
Applied my own patch sent before vacation and some other SDO binding
adjustments for Axis2 integration
Modified:
incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/Node2XmlObject.java
incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
XMLStreamReader2XmlObject.java
incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/XmlObject2Node.java
incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
XmlObject2XMLStreamReader.java
Modified: incubator/tuscany/java/sca/databinding/databinding-
xmlbeans/src/main/java/org/apache/tuscany/databinding/xmlbeans/
Node2XmlObject.java
URL: http://svn.apache.org/viewvc/incubator/tuscany/java/sca/
databinding/databinding-xmlbeans/src/main/java/org/apache/tuscany/
databinding/xmlbeans/Node2XmlObject.java?
rev=432149r1=432148r2=432149view=diff
==
--- incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/ Node2XmlObject.java
(original)
+++ incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/ Node2XmlObject.java
Wed Aug 16 22:42:11 2006
@@ -21,11 +21,12 @@
import org.apache.tuscany.databinding.TransformationContext;
import org.apache.tuscany.databinding.TransformationException;
import org.apache.tuscany.databinding.PullTransformer;
+import org.apache.tuscany.databinding.extension.TransformerExtension;
import org.apache.xmlbeans.XmlException;
import org.apache.xmlbeans.XmlObject;
import org.w3c.dom.Node;
-public class Node2XmlObject implements PullTransformerNode, XmlObject
{
+public class Node2XmlObject extends TransformerExtensionNode,
XmlObject implements PullTransformerNode, XmlObject {
// private XmlOptions options;
public XmlObject transform(Node source, TransformationContext
context) {
@@ -36,11 +37,11 @@
}
}
-public ClassXmlObject getTargetType() {
+public Class getTargetType() {
return XmlObject.class;
}
-public ClassNode getSourceType() {
+public Class getSourceType() {
return Node.class;
}
Modified: incubator/tuscany/java/sca/databinding/databinding-
xmlbeans/src/main/java/org/apache/tuscany/databinding/xmlbeans/
XMLStreamReader2XmlObject.java
URL: http://svn.apache.org/viewvc/incubator/tuscany/java/sca/
databinding/databinding-xmlbeans/src/main/java/org/apache/tuscany/
databinding/xmlbeans/XMLStreamReader2XmlObject.java?
rev=432149r1=432148r2=432149view=diff
==
--- incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
XMLStreamReader2XmlObject.java (original)
+++ incubator/tuscany/java/sca/databinding/databinding-xmlbeans/src/
main/java/org/apache/tuscany/databinding/xmlbeans/
XMLStreamReader2XmlObject.java Wed Aug 16 22:42:11 2006
@@ -23,10 +23,11 @@
import org.apache.tuscany.databinding.TransformationContext;
import
Account request Tuscany for new committer: Brent Daniel
Can you please create a committer account for Brent Daniel since he has been voted in. Preferred userid: 1) bdaniel 2) bhdaniel Full name: Brent Daniel Forwarding email address: [EMAIL PROTECTED] Requested Karma for: ws-tuscany Vote: http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200608.mbox/[EMAIL PROTECTED] Thanks, --Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r432156
On Aug 17, 2006, at 9:29 AM, Raymond Feng wrote: Hi, Jim. Sorry for the confusion. First of all, I want to reassure you that we're still on the same page for the overrall direction: Based on your comments below, I'm not sure we are :-) 1. I fully agree with you that it's a real hack and it's only a temporary fix for one or two weeks while I'm working out the databinding integration. The hack will be definitely removed before we release the Axis2 binding. 2. Axis2 binding is an extension instead of part of the core. We need to deploy it as an extension instead of poluting the webapp runtime. Here's some background that I decided to add such a hack. Rick had pinged me to see if we can bring up the Axis2 binding to the same functionality as it had for M1 so that we can perform the Axis2 intergration tests without having to rewrite all the interop tests using AXIOM. I thought it's reasonable and a working end-to-end case might also help me to better understand the core/extension/ databinding integration picture so that I can get it right quickly. I apologized that I didn't communicate it clearly before the check-in. Could you explain why all of the interop tests require SDO? That seems a bit strange. I don't think this should be checked into the main line but rather done in the sandbox as it violates one of the architecture principles we set forth. In terms of working out databinding integration, this should really be done through unit testing as much as possible first. Note that none of the steps you mentioned below need to be done outside the context of core, much less require breaking modularity. Anyway, here's the path I'm full-time on now to work toward the solution that we have been discussing on this list. 1. Integrate the DataBinding framework with the ServiceContract/ Operation/DataType model 2. Integrate the DataBinding framework with the wiring fabric using an Interceptor * Associate some databinding-related context to the composite hierachary * Adjust the builder delegation strategy * Attach an interceptor the wiring fabric to perform the data transformation based on the databinding context * Question: Do we model databinding as a policy or part of the core? Data binding should be done as part of the wiring infrastructure in core. Policy is a euphemism for the the part of core that introduces interceptors and handlers, and is itself extensible. We may need to modify it somewhat so that the databinding policy builder has information about the target and source of a wire. Thanks, Raymond - Original Message - From: Jim Marino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, August 17, 2006 12:14 AM Subject: Fwd: svn commit: r432156 Raymond, I've noticed an SDO and databinding implementation dependencies have been introduced into the Axis2 binding. Based on your comments in the code, it appears this is temporary and related to implementing an interceptor into the policy framework. I'd prefer that we work on getting the correct solution in place ASAP and am uncomfortable with introducing hacks such as this one. There was an email thread the other day about introducing an interceptor and am happy to provide assistance if required. Could you please outline what is required so we can work towards a proper solution? Thanks, Jim Modified: incubator/tuscany/java/sca/bindings/binding.axis2/pom.xml incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ java/ org/apache/tuscany/binding/axis2/Axis2BindingBuilder.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ java/ org/apache/tuscany/binding/axis2/Axis2Reference.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ java/ org/apache/tuscany/binding/axis2/Axis2Service.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ java/ org/apache/tuscany/binding/axis2/ Axis2ServiceInOutSyncMessageReceiver.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ java/ org/apache/tuscany/binding/axis2/Axis2TargetInvoker.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ java/ org/apache/tuscany/binding/axis2/util/SDODataBinding.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ java/ org/apache/tuscany/binding/axis2/util/ TuscanyAxisConfigurator.java incubator/tuscany/java/sca/bindings/binding.axis2/src/main/ resources/META-INF/sca/default.scdl incubator/tuscany/java/sca/bindings/binding.axis2/src/test/ java/ org/apache/tuscany/binding/axis2/Axis2ReferenceTestCase.java incubator/tuscany/java/sca/bindings/binding.axis2/src/test/ java/ org/apache/tuscany/binding/axis2/Axis2ServiceTestCase.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build break
Does it work on a Sun JVM? On Aug 17, 2006, at 9:53 AM, Kevin Williams wrote: Just updated and I am having trouble building ... [surefire] Tests run: 3, Failures: 0, Errors: 2, Time elapsed: 1.983 sec [surefire] [surefire] testTransformation2 (org.apache.tuscany.databinding.TransformationTest Case) Time elapsed: 0.05 sec ERROR! java.lang.NoClassDefFoundError: com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLea fInfoImpl (initialization failure) at java.lang.J9VMInternals.initialize(J9VMInternals.java:123) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.init(RuntimeT - 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] Closed: (TUSCANY-623) DAS Samples modular distribution
[ http://issues.apache.org/jira/browse/TUSCANY-623?page=all ] Kevin Williams closed TUSCANY-623. -- Fix Version/s: Java-Mx (was: Java-M2) Resolution: Fixed Verified with revision: 432297 DAS Samples modular distribution Key: TUSCANY-623 URL: http://issues.apache.org/jira/browse/TUSCANY-623 Project: Tuscany Issue Type: New Feature Components: Java DAS Samples Affects Versions: Java-M2 Reporter: Luciano Resende Assigned To: Luciano Resende Fix For: Java-Mx Attachments: lresende.das-samples.distribution.20060815.zip Need to provide modular distribution for DAS Samples component under Tuscany Samples should go in source format to be usefull for reading by users -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build break
Hi, I remember that we hit this issue before but it was fixed by upgrading the SureFire plugin to 2.2. Here are the two related JIRAs for Surefire. http://jira.codehaus.org/browse/MSUREFIRE-81 http://jira.codehaus.org/browse/MSUREFIRE-74 Thanks, Raymond - Original Message - From: Jeremy Boynes [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, August 17, 2006 9:57 AM Subject: Re: Build break Does it work on a Sun JVM? On Aug 17, 2006, at 9:53 AM, Kevin Williams wrote: Just updated and I am having trouble building ... [surefire] Tests run: 3, Failures: 0, Errors: 2, Time elapsed: 1.983 sec [surefire] [surefire] testTransformation2 (org.apache.tuscany.databinding.TransformationTest Case) Time elapsed: 0.05 sec ERROR! java.lang.NoClassDefFoundError: com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLea fInfoImpl (initialization failure) at java.lang.J9VMInternals.initialize(J9VMInternals.java:123) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.init(RuntimeT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r432297 - in /incubator/tuscany/java/distribution/das-samples: ./ LICENSE.txt NOTICE.txt pom.xml src/ src/main/ src/main/assembly/ src/main/assembly/das-samples.xml
On Aug 17, 2006, at 10:01 AM, [EMAIL PROTECTED] wrote: + !-- include companyweb source -- + fileSet + directory../../samples/das/companyweb/src/directory + lineEndingkeep/lineEnding + includes +include**/*.java/include +include**/*.xml/include + /includes + fileMode644/fileMode + /fileSet Although it works, references outside the project like this are generally problematic. I would suggest an alternative would be to have the companyweb module output a source jar as its artifact rather than the usual binary jar - after all for a sample it is the source that is interesting to users. You could then reference it as a dependency and have that exploded into the distribution. -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BUILD BREAK looking for: ws-commons:axiom-api:jar:SNAPSHOT
Hi I too pulled the code this morning and ran into this problem. Since I was to look into something and not add anything I resorted to changing the pom.xml to get the build going and it went thro. - Venkat On 8/17/06, Rick [EMAIL PROTECTED] wrote: Just checked something in that fixed this. With that my build ran to completion. Scott Kurz wrote: I think this is a real build break (not a bad pom in my maven repo)... I pasted my Maven output below after pulling the entire 'java' SVN branch and building I don't see that any of the remote repo sites contain SNAPSHOT versions of the Axis2 jars such as axiom-api, so I'm wondering how people are building against these... Are you manually grabbing the jars from somewhere and hand-copying them into your local Maven repo under 'SNAPSHOT' version names? Thanks mvn output pasted: [INFO] [INFO] Building Apache Tuscany Data Binding for Axiom [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-impl/SNAPSHOT/axiom-impl-SNAPSHOT.pom [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-api/SNAPSHOT/axiom-api-SNAPSHOT.pom [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) Downloading: http://www.ibiblio.org/maven2/ws-commons/axiom-api/SNAPSHOT/axiom-api-SNAPSHOT.jar [WARNING] Unable to get resource from repository ibiblio ( http://www.ibiblio.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) ws-commons:axiom-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=ws-commons -DartifactId=axiom-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.tuscany.databinding:databinding-axiom:jar:1.0-SNAPSHOT 2) ws-commons:axiom-api:jar:SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.tuscany.databinding:databinding-axiom:jar:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), ibiblio (http://www.ibiblio.org/maven2) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WebappLauncher
On IRC, Ant and I came up with the following plan for moving the runtime classes off the webapp classpath. We are going to have a TuscanyContextListener that will: 1) create a classloader containing the content of a directory specified as a tuscany.bootDir context param this will default to WEB-INF/tuscany/boot 2) load a WebappLauncher from that classloader (classname overridable as a context param) which will implement ServletContextListener 3) forward the contextStart event to it For now the WebappLauncher implementation will live in core just like MainLauncher does. At some point it will move to a new module webapp- host. We think this pattern of two modules (one on the app classpath, one on the boot classpath) will be typical for hosts The WebappLauncher will locate a service in the runtime that implements a ServletRequestInjector interface (defined in the webapp module). The implementation of this will be bound into the servlet context. The TuscanyServlet will retrieve this implementation from the context during init and forward all requests to it. -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build break
I tried this on OS X with the Sun JVM and get a different error in the same area: java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.clinit(RuntimeBuiltinLeafInfoImpl.java:186) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.init(RuntimeTypeInfoSetImpl.java:25) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:78) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:41) at com.sun.xml.bind.v2.model.impl.ModelBuilder.init(ModelBuilder.java:97) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.init(RuntimeModelBuilder.java:44) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:343) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.init(JAXBContextImpl.java:215) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:124) 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 javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:132) at javax.xml.bind.ContextFinder.find(ContextFinder.java:286) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244) at org.apache.tuscany.databinding.jaxb.JAXBContextHelper.createJAXBContext(JAXBContextHelper.java:45) at org.apache.tuscany.databinding.jaxb.XMLStreamReader2JAXB.transform(XMLStreamReader2JAXB.java:40) at org.apache.tuscany.databinding.JAXBTestCase.testTransform(JAXBTestCase.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at Jeremy Boynes wrote: Does it work on a Sun JVM? On Aug 17, 2006, at 9:53 AM, Kevin Williams wrote: Just updated and I am having trouble building ... [surefire] Tests run: 3, Failures: 0, Errors: 2, Time elapsed: 1.983 sec [surefire] [surefire] testTransformation2 (org.apache.tuscany.databinding.TransformationTest Case) Time elapsed: 0.05 sec ERROR! java.lang.NoClassDefFoundError: com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLea fInfoImpl (initialization failure) at java.lang.J9VMInternals.initialize(J9VMInternals.java:123) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.init(RuntimeT - 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] Updated: (TUSCANY-582) Date fields sometimes not preserved when using DataHelper.
[ http://issues.apache.org/jira/browse/TUSCANY-582?page=all ]
Brian Murray updated TUSCANY-582:
-
Attachment: DateConversionTestCase.java
I have attached an updated version of DateConversionTestCase.java that does
show the problem caused by daylight savings time which existed in the original
test case. (If somebody has the authority to do so, could you please remove
the initial version?)
In the newer version the verification is done by comparing individual fields
from a Calendar object.
Date fields sometimes not preserved when using DataHelper.
--
Key: TUSCANY-582
URL: http://issues.apache.org/jira/browse/TUSCANY-582
Project: Tuscany
Issue Type: Bug
Components: Java SDO Implementation
Reporter: Brian Murray
Assigned To: Frank Budinsky
Priority: Minor
Attachments: DateConversionTestCase.java,
DateConversionTestCase.java, Tuscany582.patch
While I find it mildly surprising that you can convert from a Day to a Date,
I would expect that in doing so the Day (Date.getDate()) value within Date
would be accurate (even if all other fields are meaningless).
// The output of each println (from a single run) is placed in comments
beside it
public void testShowErrorsInSimpleFashion() throws Exception
{
Date temp = new Date(System.currentTimeMillis());
// In following sequence - would expect the Day value (here, 21) to be
maintained.
System.out.println(temp = + temp); // temp = Fri Jul 21 03:51:01 EDT
2006
String day = data_helper.toDay(temp);
System.out.println(day = + day); // day = ---21 EDT
Date date2 = data_helper.toDate(day);
System.out.println(date2 = + date2); // date2 = Thu Feb 29 23:00:00
EST 1968
String day2 = data_helper.toDay(date2);
System.out.println(day2 = + day2); // day2 = ---29 EST
}
When I look in DataHelperImpl.java, I see a series of Date Patterns. It
seems that Day is being matched to an earlier pattern than the expected one
(the expected one is ---dd zz). When I move that pattern to first in the
list, the outcome is affected. Were it not matching an earlier pattern, I
would think that moving the correct one to the front of the list would not
have an effect.
Leaving DataHelperImpl.java unaltered, Day = 21 EDT, and Day2 = 29 EST (in
the case above). However, if I put the appropriate pattern first in the list,
Day2 is instead = 20 EST. Interestingly, it is still not the correct day
(21).
Frank pointed out that there have been recent updates to DataHelper, however
I've retested with build level 425652 and see the same behavior.
Side note:
The following is not a JIRA issue, but it is related. In the second table
on page 146 the Date conversions for most types are essentially to the same
type, to Date, and to String. It seems that several more are possible. The
following seem capable of being added:
DateTime- Month, MonthDay, YearMonth, YearMonthDay, Time, Year,
Duration, Day
Duration-Month, MonthDay, YearMonth, YearMonthDay, Time, Year,
DateTime, Day
MonthDay-Month, Day
YearMonth-Month, Year
YearMonthDay-Month, Year, Day, YearMonth, MonthDay
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build break
That's the culprit that I found. The previous expeption you experienced is the result of this error. There are multiple QNames brought in by maven dependencies and SureFire used to have a bug to deal with it. Thanks, Raymond - Original Message - From: Kevin Williams [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, August 17, 2006 10:31 AM Subject: Re: Build break I tried this on OS X with the Sun JVM and get a different error in the same area: java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.clinit(RuntimeBuiltinLeafInfoImpl.java:186) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.init(RuntimeTypeInfoSetImpl.java:25) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:78) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:41) at com.sun.xml.bind.v2.model.impl.ModelBuilder.init(ModelBuilder.java:97) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.init(RuntimeModelBuilder.java:44) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:343) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.init(JAXBContextImpl.java:215) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:124) 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 javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:132) at javax.xml.bind.ContextFinder.find(ContextFinder.java:286) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244) at org.apache.tuscany.databinding.jaxb.JAXBContextHelper.createJAXBContext(JAXBContextHelper.java:45) at org.apache.tuscany.databinding.jaxb.XMLStreamReader2JAXB.transform(XMLStreamReader2JAXB.java:40) at org.apache.tuscany.databinding.JAXBTestCase.testTransform(JAXBTestCase.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at Jeremy Boynes wrote: Does it work on a Sun JVM? On Aug 17, 2006, at 9:53 AM, Kevin Williams wrote: Just updated and I am having trouble building ... [surefire] Tests run: 3, Failures: 0, Errors: 2, Time elapsed: 1.983 sec [surefire] [surefire] testTransformation2 (org.apache.tuscany.databinding.TransformationTest Case) Time elapsed: 0.05 sec ERROR! java.lang.NoClassDefFoundError: com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLea fInfoImpl (initialization failure) at java.lang.J9VMInternals.initialize(J9VMInternals.java:123) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.init(RuntimeT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WebappLauncher
On Aug 17, 2006, at 10:26 AM, Jeremy Boynes wrote: On IRC, Ant and I came up with the following plan for moving the runtime classes off the webapp classpath. We are going to have a TuscanyContextListener that will: 1) create a classloader containing the content of a directory specified as a tuscany.bootDir context param this will default to WEB-INF/tuscany/boot 2) load a WebappLauncher from that classloader (classname overridable as a context param) which will implement ServletContextListener 3) forward the contextStart event to it We'll also need a mechanism to forward request start/stop and session start/stop events into the runtime as well. For now the WebappLauncher implementation will live in core just like MainLauncher does. At some point it will move to a new module webapp-host. We think this pattern of two modules (one on the app classpath, one on the boot classpath) will be typical for hosts - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Composite references - wiring and model and runtime representations
On Aug 17, 2006, at 11:29 AM, Ignacio Silva-Lepe wrote: One more thing. AIUI, the assembly spec defines a service/ element as containing a required reference URI. This means that getTarget and setTarget really belong in spi.model.ServiceDefinition and not just in BoundServiceDefinition. So unless there are any objections, I'll promote these methods to ServiceDefinition. That's for a service definition in a composite but not in the component type. I it seems like the issue we are running into is it depends on how you look at things. Jim - Original Message - From: Ignacio Silva-Lepe [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Wednesday, August 16, 2006 2:04 PM Subject: Re: Composite references - wiring and model and runtime representations - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Composite references - wiring and model and runtime representations
Yep, you're right. However, to have a ReferenceDefinition with a reference target but not a binding, I would have to create a new spi.model class. Unless it has a big impact on, for instance, the loader code, it would be nice if we could say that a ReferenceDefinition _can_ have a target URI but it does not have to. I have not delved into the loader code enough to tell whether its worth the class savings. So let me know whether you think it would or would not work. - Original Message - From: Jim Marino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, August 17, 2006 2:45 PM Subject: Re: Composite references - wiring and model and runtime representations On Aug 17, 2006, at 11:29 AM, Ignacio Silva-Lepe wrote: One more thing. AIUI, the assembly spec defines a service/ element as containing a required reference URI. This means that getTarget and setTarget really belong in spi.model.ServiceDefinition and not just in BoundServiceDefinition. So unless there are any objections, I'll promote these methods to ServiceDefinition. That's for a service definition in a composite but not in the component type. I it seems like the issue we are running into is it depends on how you look at things. Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Composite references - wiring and model and runtime representations
On Aug 17, 2006, at 12:02 PM, Ignacio Silva-Lepe wrote: Yep, you're right. However, to have a ReferenceDefinition with a reference target but not a binding, I would have to create a new spi.model class. Unless it has a big impact on, for instance, the loader code, it would be nice if we could say that a ReferenceDefinition _can_ have a target URI but it does not have to. I have not delved into the loader code enough to tell whether its worth the class savings. So let me know whether you think it would or would not work. I'd prefer to try the extra class route first since having things that are valid in one context but not another on the same class can lead to trouble. Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Change summary on DataObject representation for non XML DAS
Looking at writing some test cases for the change summary on a DataObject. If a DataObject can have a change summary then the Type must include a property of type ChangeSummary. I am assuming that a DataObject graph heirachy can have multiple instances of this Type and there is a violation only there are mulitple DataObjects with a non null property of type ChangeSummary. Does that seem correct ? I am curious how this approach is going to be implemented for non XML persistence mechanisms/DAS implementaitons. For the rdb DAS for example would one expect to add another column to the table schema? Or is there perhaps going to be a set of tables in the DB for storing this type of SDO specific information? Perhaps since there seems to be very little protection anyhow ( another issue ) perhaps is there just going to be a default property of changeSummary on all DataObjects when created from an RDB DAS ? -- * * * Charlie * * * Check out some pics of little Charlie at http://www.flickr.com/photos/[EMAIL PROTECTED]/sets/ * * * Addresss * * * 1914 Overland Drive Chapel Hill NC 27517 * * * Number * * * 919-225-1553
C++ DAS
Hi All I'd like to hear from C++ team and the comunity in general about the need for a C++ implementation of DAS.. Could you guys elaborate about this ? -- - Luciano Resende SOA Opensource - Apache Tuscany -
[jira] Created: (TUSCANY-642) Composite references and services - model and runtime representations
Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[C++] SCA Extensions architecture
I've started playing around with loading extension libraries to support other language extensions and so a wee bit of re-architecture has cpp being an extension language. In other words I'm trying to make a core that is not tied to cpp implementation. This core will roughly be a model loader in line with the assembly model spec with extensions for stuff like implementation.cpp.. and a runtime for resolving wiring and locating services. This is nearly what we have now but without the cpp CI spec api implmentation code (anything under runtime/core/src/osoa...). This will involve a bit of refactoring to remove the unnecessary dependencies from the core to the cpp specific code. What I expect to end up with is libraries for: tuscany_sca - the core assembly model and internal message structure tuscany_sca_cpp - the cpp language extension (extension functions for loading cpp model etc.) tuscany_sca_cpp_osoa - the client side functions defined by the C++ CI spec (ComponentContext etc.) I'm not yet sure if the latter 2 should be the same library, that will depend on their interdependencies. This is not a trivial change and it's tricky to break it down into sensible small chunks so I may start a branch/sandbox to play in for the moment...or if it suddenly all works I'll get it checked in to the trunk asap ;-) It's nearly there but will probably take another day or maybe 2 and it would probably be good for anyone else interested in the cpp code to review it. It won't be near perfect but it will provide a good base for a more modular and extensible runtime. Cheers,
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: CompositeRefsAndSvcs.txt Here's the patch with the code to support composite reference and services. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: CompositeRefsAndSvcs.txt Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-610) Initial OSGi support effort
[ http://issues.apache.org/jira/browse/TUSCANY-610?page=comments#action_12428795 ] Joel Hawkins commented on TUSCANY-610: -- Hi Jim, I think I'll have some cycles to devote to this code shortly - is there anything I can do to help with the initial commit? Cheers, Joel Initial OSGi support effort --- Key: TUSCANY-610 URL: http://issues.apache.org/jira/browse/TUSCANY-610 Project: Tuscany Issue Type: New Feature Environment: Equinox implementation of OSGi Reporter: Joel Hawkins Assigned To: Jim Marino Attachments: ClassloaderHook.java, OSGI-SCA.zip An initial implementation of an OSGi binding for exposing SCA services as OSGi services. An initial implementation of an OSGi implementation for reusing OSGi services as SCA atomic components An OSGi-aware bootstrap environment (which can probably be reduced a bit) A repackaging of some of the SupplyChain example There's one class derived from an EPL-copyrighted class - I left the EPL copyright intact. The zip contains the samples, the OSGi binding, and a patch for the core. Most of the patch is the OSGi launcher code. I don't think it belongs in the core, but that's where I had it while developing. The only other bit in the patch is a change of two of the Defaultbootstrapper's fields from private to protected. Also, some of the OSGi packaging for existing jars (spi, commands, etc) aren't part of the zip. Not sure how you want to deal with the repackaging issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: REST bindings for Tuscany SCA runtime
Hi Bert,
I am still at the point where I am trying to get my head really
wrapped around how Tuscany works
I will be travelling the same road soon ;)
Have you put much thought towards the subject of a REST binding? Are
there things about which you believe we should be aware?
Well, the thing that comes to mind first is the mismatch between
the basic REST approach of using a fixed set of 'verbs' richly flexible
data and the Interfaces approach, which uses an open-ended set of
'verbs' (read: operations) and constrained strongly-typed data.
[small REST primer - skip if you know all this stuff]
The short document at [0] below characterises some of the issues of
developing a (Web) service using REST principles and is useful and
the wikipedia link at [1] has a good example (generic, not Tuscany
specific) :
Say you have a service that has methods
getUser()
addUser()
removeUser()
updateUser()
then you might use code like:
exampleAppObject = new ExampleApp(example.com:1234)
exampleAppObject.getUser()
to get details of a user. This is the interface or unconstrained
verbs approach.
Now, let's flip over to a REST means of getting the same
information. In this case, you are limited to small set of
well-defined operations, which map very well to the CRUD [3]
operators that a persistence system must provide. Because
of this stricture, you need to ramp up the diversity of
nouns (or resources, or maybe objects, but really the concept
of a resource may not equal an object in programming terms,
many resources could be 'supported' by a single object).
These resources (which is the accepted term) are represented,
uniquely, and immutably, by URIs. So taking the example
above and REST-ing it you get resources:
http://example.com/users/
http://example.com/users/{user} (one for each user)
and then you might use code like:
userResource = new Resource(http://example.com/users/001;)
userResource.get()
and you get the same information as the Interface-y example
previously.
REST is liked by many, for many reasons, but one good on is
that it's scalable (the web is an
example, although there is an extra factor that makes the
web scalable and that is the 404) in the sense that everyone
supports the same 'interface' and the semantics of the interface
are simple and clear.
In practical terms, this means that you can just join the
web, as a resource, and you will immediately fit in. No adapters
required :)
[end of small REST primer]
My interest in responding to your initial mail was that I am
currently attempting to use RESTian principles in another
project and I am finding myself making lots of interesting
decisions that I would not have made using the Interface
approach that I have used for more years than I care to
remember. Using the REST principles has deeply impacted they
way I've approached the development of the development of
the project -- in a good way :)
I'm sure you've noticed the example I gave earlier on the
programming model is client-specific and so impacts on only
part of a prospective RESTian addition to Tuscany. There is an
impact on the server too, and that's a direct consequence of
the 'few verbs' approach - talking from a programming language
perspective, every 'servant' (or resource implementation may
be a better way to put it) will have a tiny interface.
My point is that if Tuscany wants to support REST style -
a goal which I think is good, right and true - it's a job
that will involve constructing a binding extension,
re-working the Basic Client Model (see 1.3 in Java CI spec)
and adding some new annotations to the Java interface (or
maybe adding a new interface type). Note that the same will
apply to other language mappings too since REST is language
neutral (it's also protocol neutral too as an architectural
style, but assuming HTTP as the #1 priority would be safe
enough :)
On the annotations I mentioned, consider something like:
package services.hello;
import org.osoa.sca.annotations.*;
@Remotable
public interface HelloService {
@RESTMethod(RestMethods.RETRIEVE)
@RESTBaseURIContext(/foo/bar/sossages)
String hello();
}
Here I've decorated the ubiquitous HW example from JCI 1.2.1.1
with some spanky new annotations. This example indicates to the
runtime that the hello() method should be called on this interface
should the 'RETRIEVE' REST method (for HTTP this is 'GET') appear
on the dispatch, directed to a URI that starts with the string
specified in with the RESTBaseURIContext (now - this is probably
the wrong way to do it, but I just trying to illustrate the
broad outlines of an approach, i.e. I am making it up).
Note that the concept of XML/HTTP interchange may be RESTful,
but indeed may not. However, it is the basis for an implementation
of a RESTful approach (given HTTP as the transport) and is
useful in an of itself (especially for so-called Web 2.0 apps).
Methinks I've said enough for now, thank you for reading this
far if indeed you have ;)
Re: REST bindings for Tuscany SCA runtime
Oisin may have been referring to how REST would impact the programming model rather than the implementation of bindings. For example, how would cache information in the request be handled by the binding and/or exposed to the application code? What is the mapping between REST resources and SCA services? Caching, which is only made possible by the fact the RESTful retrieves are idempotent, might be difficult to do effectively since it's not really possible to control what the programmer does from within a mapped retrieve method in the implementation short of giving them a new execution environment to be bad in :) IMO we can tackle this in to stages. First one is to get the basic transports working (like JSON-RPC, XML over messaging, HTML over HTTP etc.); that would at least allow SCA applications to provide/ access REST resources. The second stage would be to support more of the semantics of RESTful interactions. +1 --oh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: REST bindings for Tuscany SCA runtime
On 8/16/06, Jeremy Boynes [EMAIL PROTECTED] wrote: In terms of the basic transport, in M1 we had a JSON-RPC binding that supported JSON encoded data over HTTP. We have not got around yet to porting that to the new structure in the trunk. Looking at that would be a good way to dig into how Tuscany works. I can make an attempt to try and port the jsonrpc binding from M1 over to trunk style extensions if this would be appreciated. I agree that should help me get an understanding of how some of Tuscany works. Oisin may have been referring to how REST would impact the programming model rather than the implementation of bindings. For example, how would cache information in the request be handled by the binding and/or exposed to the application code? What is the mapping between REST resources and SCA services? Yes, the more I read, the more I wonder if trying to support REST style web applications in SCA is going to become a square peg in a round hole problem. I've only begun really looking at this though, and welcome any thoughts on the subject of how one might attempt to interface REST resources in SCA. -Bert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[C++] Requirements for a pluggable C++ Tuscany implementation
Hi guys, I thought I might kick off a thread on pluggability in the C++ implementation to get some ideas rolling around, so while these are not 'requirements' at all, they might eventually lead to some ;) 1. Language independence is not an issue here, so all plugins are described and implemented in C++. 2. It should be reasonably straightforward to make a plugin with minimum code, so things like base plugin classes as part of the core are a good thing. 3. Plugins can be loaded on-demand, from dynamic libraries, and many plugins can be put into a library. 4. Plugins can be statically linked with an application. 5. Plugins should be evictable too, provided that this feature is supported on the target platform. 6. There will need to be some kind of manager thingie to keep track of plugins and their state at runtime. 7. Plugins need to support an interface for initialization and shutdown at the least. There will need to be some kind of simple lifecycle put together. Request for lifecycle transitions will need to support parameters 8. Plugins have names. Easy. 9. Plugins have versions, and dependencies on other plugins too. 10. Plugins describe and can validate their own configuration. 11. Plugins need to be signable, or equivalent. Comments? --oh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (TUSCANY-610) Initial OSGi support effort
Hi Joel, I was working on this yesterday and got sidetracked with some other things as well as a machine problem. I'll be back up by tomorrow, hopefully with a check in and some things to discuss. Jim On Aug 17, 2006, at 2:11 PM, Joel Hawkins (JIRA) wrote: [ http://issues.apache.org/jira/browse/TUSCANY-610? page=comments#action_12428795 ] Joel Hawkins commented on TUSCANY-610: -- Hi Jim, I think I'll have some cycles to devote to this code shortly - is there anything I can do to help with the initial commit? Cheers, Joel Initial OSGi support effort --- Key: TUSCANY-610 URL: http://issues.apache.org/jira/browse/TUSCANY-610 Project: Tuscany Issue Type: New Feature Environment: Equinox implementation of OSGi Reporter: Joel Hawkins Assigned To: Jim Marino Attachments: ClassloaderHook.java, OSGI-SCA.zip An initial implementation of an OSGi binding for exposing SCA services as OSGi services. An initial implementation of an OSGi implementation for reusing OSGi services as SCA atomic components An OSGi-aware bootstrap environment (which can probably be reduced a bit) A repackaging of some of the SupplyChain example There's one class derived from an EPL-copyrighted class - I left the EPL copyright intact. The zip contains the samples, the OSGi binding, and a patch for the core. Most of the patch is the OSGi launcher code. I don't think it belongs in the core, but that's where I had it while developing. The only other bit in the patch is a change of two of the Defaultbootstrapper's fields from private to protected. Also, some of the OSGi packaging for existing jars (spi, commands, etc) aren't part of the zip. Not sure how you want to deal with the repackaging issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/ Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/ software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Keep getting undeclared prefix in client soap message :(
Hi everyone,
Is there a list of WSDL/schema limitations somewhere ? I am having the
following problem just calling a Web service using Tuscany (similar to
the hello world ws client sample). The created SOAP message is
incorrect, mainly because the namespace prefix is left undefined. Any
ideas welcome !
The WSDL is very simple: one portType with one operation: takes and
returns a string. Binding is doc/lit.
I am copying the relevant files below. This is all using the M1
Distribution.
thanks!
Rania
ps: I even tried to generate an interface using the WSDL2JavaGenerator
and use that one instead of just a hand crafted one because I thought
maybe it does something with the package name .. but I still have the
same problem. They look the same anyway
pps: I also don't know why it's putting an xml in front of the soap
envelope and what this '12a' is but it still just complains about the
prefix.
SOAP MESSAGES
Request
POST /scaBPELSampleEcho/services/EchoService HTTP/1.1
SOAPAction:
Content-Type: text/xml; charset=utf-8
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.5.0_05
Host: 127.0.0.1
Connection: keep-alive
Transfer-Encoding: chunked
12a
?xml version=1.0 encoding=utf-8 ?
SOAP-ENV:Envelope
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
SOAP-ENV:Body
echo:echomeWorld/echo:echome
/SOAP-ENV:Body
/SOAP-ENV:Envelope0
Response
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=5D49F92340C18ACB88994AEEC83B1708;
Path=/scaBPELSampleEcho
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Thu, 17 Aug 2006 22:01:19 GMT
Connection: close
c6
?xml version='1.0' encoding='utf-8'?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header /
soapenv:Body
soapenv:Fault
faultcodesoapenv:Client/faultcode91
faultstringcom.ctc.wstx.exc.WstxParsingException:
Undeclared namespace prefix echo#13; at [row,col {unknown-source}]:
[1,243]/faultstring
(etc.. )
sca.module
modulexmlns=http://www.osoa.org/xmlns/sca/0.9;
xmlns:v=http://www.osoa.org/xmlns/sca/values/0.9;
xmlns:bpel=http://www.osoa.org/xmlns/bpel/0.9;
name=bpel.samples.echoclient
import.wsdl wsdlLocation=Echo.wsdl/
import.sdo wsdlLocation=Echo.wsdl/
externalService name=EchoService
interface.java interface=echo.EchoService/
!-- interface.wsdl interface=http://echo#echoPT/ --
binding.ws port=http://echo#wsdl.endpoint(EchoService/EchoPort)/
/externalService
/module
echo.wsdl
definitions targetNamespace=http://echo;
xmlns:tns=http://echo;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:ns1 =http://echo;
xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
types
xsd:schema targetNamespace=http://echo;
xsd:element name=echome type=xsd:string/
/xsd:schema
/types
message name=StringMessageType
part name=echoString element=ns1:echome/
/message
portType name=echoPT
operation name=echo
input message=tns:StringMessageType /
output message=tns:StringMessageType /
/operation
/portType
binding name=EchoBinding type=tns:echoPT
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
operation name=echo
soap:operation/
input
soap:body use=literal/
/input
output
soap:body use=literal/
/output
/operation
/binding
service name=EchoService
port name=EchoPort binding=tns:EchoBinding
soap:address
location=http://localhost:4040/scaBPELSampleEcho/services/EchoService/
/port
/service
/definitions
**
CLIENT CODE (knocked off from helloworld)
**
public class EchoClient {
public static final void main(String[] args) throws Exception {
// Setup Tuscany monitoring to use java.util.logging
LogManager.getLogManager().readConfiguration(EchoClient.class.getResourceAsStream(/logging.properties));
Properties levels = new Properties();
MonitorFactory monitorFactory = new
JavaLoggingMonitorFactory(levels, Level.FINEST, MonitorMessages);
// Create a Tuscany runtime for the sample module component
TuscanyRuntime tuscany = new
TuscanyRuntime(EchoModuleComponent, http://echo;, monitorFactory);
// Start the Tuscany runtime and associate it with this thread
tuscany.start();
// Get the SCA module context.
ModuleContext moduleContext = CurrentModuleContext.getContext();
// Locate and Invoke the echo service
String to Date in SDO Specification
I have a couple of questions related to Date formats:
1) Date, DateTime, and Duration all have an optional leading hyphen (As
seen in the table on the bottom of page 72 of the SDO spec.). Should the
presence or absence of this hyphen have an effect on how a String is
interpretted as a Date, DateTime, or Duration?
On page 74 of the spec, a SimpleDateFormat is given that should be
sufficient for converting from String to Date. Using this format, the
inclusion of the optional leading hyphen does have an effect - as is shown
by the following method:
public void testSpec()
{
SimpleDateFormat f = new
SimpleDateFormat(-MM-dd'T'HH:mm:ss'.'SSSz);
try
{
String dateString = 2006-08-17T04:45:55.9EDT;
System.out.println(f.parse(dateString.replaceFirst(([+\\-]..):,
$1)));
dateString = -2006-08-17T04:45:55.9EDT;
System.out.println(f.parse(dateString.replaceFirst(([+\\-]..):,
$1)));
dateString = 2007-08-17T04:45:55.9EST;
System.out.println(f.parse(dateString.replaceFirst(([+\\-]..):,
$1)));
dateString = -2007-08-17T04:45:55.9EST;
System.out.println(f.parse(dateString.replaceFirst(([+\\-]..):,
$1)));
}
catch (Exception e) {}
SimpleDateFormat duration = new SimpleDateFormat('P''Y' MM'M'
dd'D T' HH'H' mm'M' ss'S.'S);
try
{
String dateString = P2006Y 08M 17D T 04H 45M 55S.854;
System.out.println(duration.parse(dateString));
dateString = -P2008Y 09M 13D T 04H 45M 55S.854;
System.out.println(duration.parse(dateString));
}
catch (Exception e) { System.out.println(Exception thrown);}
}
Here is the output:
Thu Aug 17 04:45:55 EDT 2006
Sun Aug 17 03:45:55 EST 2007
Thu Aug 17 05:45:55 EDT 2007
Sun Aug 17 04:45:55 EST 2008
Thu Aug 17 04:45:55 EDT 2006
Exception thrown
Note that the inclusion of the optional leading '-' has the following
effects:
* Increments the year.
* Prevents the handling of Daylight Savings Time. (I verified this in BST
by changing my laptop's time zone to Brasilia, and the month to February in
the method.)
* For the case of Duration, prevents the string from being parsed.
Given this behavior by SimpleDateFormat - should DataHelper accomodate? (
I.e. Should DataHelperImpl.java be written to explicity remove leading '-'
for Date, DateTime and Duration strings?) Or is the above behavior (the
three asterisks) desirable and expected? I have already made changes to
DataHelperImpl.java for Tuscany-582 and could easily incorporate the
additional work.
2) What is the intent of the replaceFirst found in the specification with
regard to converting String to Date?
The replaceFirst I'm speaking of is on page 74 of the 2.1 SDO Specification:
The following example use of java.text.SimpleDateFormat is compliant for
converting String to Date when all fields are present:
DateFormat f = new SimpleDateFormat(-MM-dd'T'HH:mm:ss'.'SSSz);
Date date = f.parse(dateString.replaceFirst(([+\\-]..):, $1));
I was curious so I wrote the following method:
public void testSpec()
{
String [] array = {+ab:blah, -ab:blah, \\ab:blah,
+ab:blah+ab:blah,
++ab:blah, +++:blah, 2006-08-17T04:45:55.9EDT};
for (int i = 0; i array.length; i++)
{
System.out.println(array[i] + -- +
array[i].replaceFirst(([+\\-]..):, $1));
}
}
Here is the output
+ab:blah -- +abblah
-ab:blah -- -abblah
\ab:blah -- \ab:blah
+ab:blah+ab:blah -- +abblah+ab:blah
++ab:blah -- ++abblah
+++:blah -- +++blah
2006-08-17T04:45:55.9EDT -- 2006-08-17T04:45:55.9EDT
It has no impact on a string of the expected format. Also, the intent seems
to be to have the same effect for +, -, and \, however in the third line it
seems '\' is treated differently than '+' or '-'. And again, I don't
understand the intent. Can somebody please explain?
Re: New site sample
Hi David It's looking very good... Do we have PHP support at apache.org/incubator ? - Luciano On 8/16/06, David Wheeler [EMAIL PROTECTED] wrote: Hello again, I worked some more on the site and here is what I have come up with. http://www.zerovec.com/tuscany/ I created a php script to parse the xml docs in site-author and display them. This make it pretty easy to migrate over all the content that was previously there. The only change was making links that pointed to pageName.html point to index.php?page=pageName . Does this work for everyone? On 8/14/06, David Wheeler [EMAIL PROTECTED] wrote: Hi, I've got the site layout to the point where some things are now functional. Content pages need only contain what is relevant to the themselves, with no formatting information Currently it uses javascript to take a local page and inject it into the main page. (This causes the page to feel more responsive, but breaks the back button.) An easy alternative would be to use PHP if javascript isn't ok. I've attached the source as well as posted it here: http://66.160.135.98/tuscany/ -David W -- - Luciano Resende SOA Opensource - Apache Tuscany -
Re: String to Date in SDO Specification
I think SDO is borrowing date/time format from XSD, SDO XML representation has to follow XSD spec after all. (and the Java serialization uses the XML format too) The SDO spec might not have covered all date/time format details, however I think you can seek references from XSD spec (Part 2: Datatypes HTTP://WWW.w3.org/TR/xmlschema-2 http://WWW.w3.org/TR/xmlschema-2). I don't expect there will be ambiguity about the format (including hyphens). Java 1.5 has javax.xml.datatype.XMLGregorianCalendar to deal with XSD date/time, even if we can't utilize it directly, maybe we can leverage its implementation somehow... -- Yang ZHONG
More build problems and compartmentalizing the build to avoid these in the future
It appears if the latest Axis2 and Axiom snapshots may not be in sync and are causing another build break. I'm not sure how to resolve this in the short-term other than wait until they do get in sync or revert back to 1.0 which will bring up the classloader issues that forced us to use the snapshots in the first place. This does, however, raise the issue of the numerous build breaks we have had over the last week and I think it is only going to get worse as more extensions come into place. As a way to address this, I believe we should have a compartmentalized build where, by default, extensions are built separately. In this scenario, the following would happen: - api, spi, core, host-api, host-util, launcher, test, webapp, and wsdl projects would be built together as the default - each extension would be built individually - there would be a maven tower of babel goal that would build everything but would not be required to be run unless a change was introduced into api, spi, or host-spi Thoughts? Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r432297 - in /incubator/tuscany/java/distribution/das-samples: ./ LICENSE.txt NOTICE.txt pom.xml src/ src/main/ src/main/assembly/ src/main/assembly/das-samples.xml
Hi Jeremy Would it be better to have the output of this be the companyweb war file with the sources, this way a user would be able to deploy the sample app + see the sample source code and investigate what's going on on the sample app ? - Luciano On 8/17/06, Jeremy Boynes [EMAIL PROTECTED] wrote: On Aug 17, 2006, at 10:01 AM, [EMAIL PROTECTED] wrote: + !-- include companyweb source -- + fileSet + directory../../samples/das/companyweb/src/directory + lineEndingkeep/lineEnding + includes +include**/*.java/include +include**/*.xml/include + /includes + fileMode644/fileMode + /fileSet Although it works, references outside the project like this are generally problematic. I would suggest an alternative would be to have the companyweb module output a source jar as its artifact rather than the usual binary jar - after all for a sample it is the source that is interesting to users. You could then reference it as a dependency and have that exploded into the distribution. -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - Luciano Resende SOA Opensource - Apache Tuscany -
Re: Keep getting undeclared prefix in client soap message :(
Thank you for letting us know.
On 8/17/06, Rania Khalaf [EMAIL PROTECTED] wrote:
Got it to work
itwas a classpath issue !
It was trying to use celtix. I changed the CP to match the helloworld
sample and now it declares the prefix.
Didn't check exactly which jar caused this (although i could run some
guesses) , but it is a a bit of a bizarre manifestation esp since I know
nearly zero about celtix anyway.
of course, it had to get fixed just a few minutes after I sent the
message ...
rania
Rania Khalaf wrote:
Hi everyone,
Is there a list of WSDL/schema limitations somewhere ? I am having the
following problem just calling a Web service using Tuscany (similar to
the hello world ws client sample). The created SOAP message is
incorrect, mainly because the namespace prefix is left undefined. Any
ideas welcome !
The WSDL is very simple: one portType with one operation: takes and
returns a string. Binding is doc/lit.
I am copying the relevant files below. This is all using the M1
Distribution.
thanks!
Rania
ps: I even tried to generate an interface using the WSDL2JavaGenerator
and use that one instead of just a hand crafted one because I thought
maybe it does something with the package name .. but I still have the
same problem. They look the same anyway
pps: I also don't know why it's putting an xml in front of the soap
envelope and what this '12a' is but it still just complains about the
prefix.
SOAP MESSAGES
Request
POST /scaBPELSampleEcho/services/EchoService HTTP/1.1
SOAPAction:
Content-Type: text/xml; charset=utf-8
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.5.0_05
Host: 127.0.0.1
Connection: keep-alive
Transfer-Encoding: chunked
12a
?xml version=1.0 encoding=utf-8 ?
SOAP-ENV:Envelope
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
SOAP-ENV:Body
echo:echomeWorld/echo:echome
/SOAP-ENV:Body
/SOAP-ENV:Envelope0
Response
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=5D49F92340C18ACB88994AEEC83B1708;
Path=/scaBPELSampleEcho
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Thu, 17 Aug 2006 22:01:19 GMT
Connection: close
c6
?xml version='1.0' encoding='utf-8'?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header /
soapenv:Body
soapenv:Fault
faultcodesoapenv:Client/faultcode91
faultstringcom.ctc.wstx.exc.WstxParsingException:
Undeclared namespace prefix echo#13; at [row,col {unknown-source}]:
[1,243]/faultstring
(etc.. )
sca.module
modulexmlns=http://www.osoa.org/xmlns/sca/0.9;
xmlns:v=http://www.osoa.org/xmlns/sca/values/0.9;
xmlns:bpel=http://www.osoa.org/xmlns/bpel/0.9;
name=bpel.samples.echoclient
import.wsdl wsdlLocation=Echo.wsdl/
import.sdo wsdlLocation=Echo.wsdl/
externalService name=EchoService
interface.java interface=echo.EchoService/
!-- interface.wsdl interface=http://echo#echoPT/ --
binding.ws port=http://echo#wsdl.endpoint(EchoService/EchoPort)
/
/externalService /module
echo.wsdl
definitions targetNamespace=http://echo;
xmlns:tns=http://echo;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:ns1 =http://echo;
xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
types
xsd:schema targetNamespace=http://echo;
xsd:element name=echome type=xsd:string/
/xsd:schema
/types
message name=StringMessageType
part name=echoString element=ns1:echome/
/message
portType name=echoPT
operation name=echo
input message=tns:StringMessageType /
output message=tns:StringMessageType /
/operation
/portType
binding name=EchoBinding type=tns:echoPT
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
operation name=echo
soap:operation/
input
soap:body use=literal/
/input
output
soap:body use=literal/
/output
/operation
/binding
service name=EchoService
port name=EchoPort binding=tns:EchoBinding
soap:address
location=http://localhost:4040/scaBPELSampleEcho/services/EchoService
/
/port
/service
/definitions
**
CLIENT CODE (knocked off from helloworld)
**
public class EchoClient {
public static final void main(String[] args) throws Exception {
// Setup Tuscany monitoring to use java.util.logging
LogManager.getLogManager().readConfiguration(
EchoClient.class.getResourceAsStream(/logging.properties));
