Re: JMS Client
On Fri, Jun 6, 2008 at 4:14 PM, Nishant Joshi [EMAIL PROTECTED] wrote: Hi All, Here is the more detail regarding error... I have trace the error and found that exceptino source is from method getInitialContext() of org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactory Here is the complete stack trace org.apache.tuscany.sca.binding.jms.impl.JMSBindingException: JMS Destination HelloWorldService not found with create mode of ifnotexist while registering binding serviceA invoker at org.apache.tuscany.sca.binding.jms.provider.JMSBindingInvoker.lookupDestinationQueue(JMSBindingInvoker.java:169) at org.apache.tuscany.sca.binding.jms.provider.JMSBindingInvoker.lookupDestination(JMSBindingInvoker.java:83) at org.apache.tuscany.sca.binding.jms.provider.JMSBindingInvoker.init(JMSBindingInvoker.java:66) at org.apache.tuscany.sca.binding.jms.provider.JMSBindingReferenceBindingProvider.createInvoker(JMSBindingReferenceBindingProvider.java:117) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBindingInterceptor(RuntimeWireImpl.java:228) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:167) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:243) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:148) at $Proxy15.sayHello(Unknown Source) at helloworld.HelloWorldClientImpl.sayHello(HelloWorldClientImpl.java:25) 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 org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154) at org.apache.tuscany.sca.core.invocation.CglibProxyFactory$CglibMethodInterceptor.intercept(CglibProxyFactory.java:149) at helloworld.HelloWorldClientImpl$$EnhancerByCGLIB$$2ae21c1f.sayHello(generated) at helloworld.JMSClient.main(JMSClient.java:20) at helloworld.ClientTest.testServiceCall(ClientTest.java:20) 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 org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) 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 org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) Has anybody idea why should i m not able to connect to a Queue of WAS ? -- Thanks Nishant Joshi The easiest way to get this to work is using the jars from the WebSphere J2SE JMS client -
Re: Moving from Spring 2.0.6 to 2.0.8, was: Can't generate a Java interface from a WSDL portType
Jean-Sebastien Delfino wrote: CXF 2.1 uses Spring 2.0.8, while our implementation-spring module uses 2.0.6. I'd like to test and change our Spring integration to use 2.0.8 as well. If there's no objection (and if it works) I'll make that change in the next few days. Sebastien, I'll be happy to do the work to migrate Spring to 2.0.8 if you like... Yours, Mike.
Re: Release 1.3?
Simon Laws wrote: It's been a little while now since we did our 1.2 release. Since then there has been lots of activity and of course we have graduated. It feels like the right time to do a 1.3 release. Looking back at the mail list over the last couple of months there are quite a few candidates for inclusion that I can see; Better BPEL support Improvements to the domain manager app Improved runtime Java2WSDL processing Support for validation monitoring Databinding improvements Performance improvements JSR250 annotation support OSGi support improvements and a simple OSGi runtime test Java 2 security enablement Quite a few more tests for various parts of the runtime Lots of JIRA fixes. and of course we can remove the incubating assignment and drum up a bit of publicity for our TLP graduation I'd also like to have a bit of a tidy up for this release and remove the old domain modules we are no longer using (I'll post on this separately) What else has been added or changed? I think the things I would like to get done can be closed off next week ready to cut a branch. Thoughts? Simon Yes, I give a +1. BPEL is looking a lot better now. I'd like to add a couple of more sophisticated itests/samples as well and the release will be a good spur. Yours, Mike.
Re: Endpoints was: Re: [BRAINSTORM] Flexibility in distributed operation and extension implementations - was: Re: Request to propogate the value of a references target= attribute on its associated bin
On Sat, Jun 7, 2008 at 12:46 PM, Simon Laws [EMAIL PROTECTED] wrote: snip I've created an itest (late-reference-resolution) to show how late resolution could be done using endpoint resolvers. In the itest BindingScaEndpointResolverImpl it says I can cheat here because... could you say a little about how a real use of this could work? And what do you think about having some code somewhere - in an itest or module somwhere - which demonstrates that? I'd be happy to help write that, I'm asking as in runtime-tomcat i need to do the same thing but haven't been able to figure out how its intended to be done for real. ...ant
Build error in sca\itest\properties
I am seeing a compilation failure in sca\itest\properties. Is anyone else
hitting this error? Command output given below.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Apache Tuscany SCA Properties Integration Tests
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\T\java\sca\itest\properties\target
[INFO] [tuscany-sdo:generate {execution: generate-customer-sdo}]
[INFO] Generating SDO interfaces from
D:\T\java\sca\itest\properties\src\main\resources\customer.xsd
Generating code
Generating packages
Generating package SdoPackageImpl
Generating Java interface com.example.customer.sdo.SdoFactory
Generating /TargetProject/com/example/customer/sdo/SdoFactory.java
Generating Java class com.example.customer.sdo.impl.SdoFactoryImpl
Generating
/TargetProject/com/example/customer/sdo/impl/SdoFactoryImpl.java
Generating Customer
Generating Java interface com.example.customer.sdo.Customer
Generating /TargetProject/com/example/customer/sdo/Customer.java
Generating Java class com.example.customer.sdo.impl.CustomerImpl
Generating
/TargetProject/com/example/customer/sdo/impl/CustomerImpl.java
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 26 source files to
D:\T\java\sca\itest\properties\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[29,22]
package javax.xml.bind does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[30,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[31,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[31,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[32,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[33,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[34,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[74,11]
cannot find symbol
symbol : class JAXBElement
location: class test.jaxb.props.ObjectFactory
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[49,1]
cannot find symbol
symbol: class XmlRegistry
@XmlRegistry
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[57,1]
cannot find symbol
symbol: class XmlAccessorType
@XmlAccessorType(XmlAccessType.FIELD)
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[58,1]
cannot find symbol
symbol: class XmlType
@XmlType(name = ReturnCodeProperties, namespace =
http://test.sca.jaxb/rcprops;, propOrder = {
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[73,5]
cannot find symbol
symbol : class XmlElementDecl
location: class test.jaxb.props.ObjectFactory
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[64,5]
cannot find symbol
symbol : class XmlElement
location: class test.jaxb.props.ReturnCodeProperties
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[66,5]
cannot find symbol
symbol : class XmlElement
location: class test.jaxb.props.ReturnCodeProperties
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\package-info.java:[26,26]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[75,19]
cannot find symbol
symbol : class JAXBElement
location: class test.jaxb.props.ObjectFactory
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 6 seconds
[INFO] Finished at: Sun Jun 08 14:15:34 IST 2008
[INFO] Final Memory: 14M/26M
[INFO]
Re: [GSoC] [DISCUSS] Development of GData biding
The link to the patch: https://issues.apache.org/jira/browse/TUSCANY-2376 On Fri, Jun 6, 2008 at 10:51 PM, Douglas Leite [EMAIL PROTECTED] wrote: I have started to define the structure and some classes to allow the GData binding, as discussed above. This project was created following the binding-atom-abdera project structure. So there is some dependencies that need to be revised. The initial created classes aim to handle with the reference side of a component. So, at this moment, an component would invoke only a Google service, instead of a service provided by another SCA component. I have started to implement the invokers, starting with the GetAllInvoker, as simple as possible (just for some tests). I have got an error at the moment to retrieve the feed object (com.google.gdata.data.Feed) from the message object (org.apache.tuscany.sca.invocation.Message). I am not updated about the discussion evolving the license of the GData Java Client. However, this first implementation is using the GData Java Client. Douglas On Tue, Jun 3, 2008 at 4:26 AM, Mike Edwards [EMAIL PROTECTED] wrote: Luciano Resende wrote: Hey Mike What are your concerns with regards to license ? Looking at [1], it looks like the GData Java Client is Apache License 2. [1] http://code.google.com/p/gdata-java-client/ On Mon, Jun 2, 2008 at 10:01 PM, Mike Edwards [EMAIL PROTECTED] wrote: Douglas Leite wrote: After analyzing the Google Data API and the code of binding-atom, binding-atom-abdera, and binding-feed, I propose an approach to start the development of the GData biding. I propose creating a new type of binding: biding-gdata. Similarly as binding-atom-abdera, that extends the binding-atom, this new kind of binding would extend the binding-atom too. The implementation of the invokers (linke GetInvoker, PostInvoker, and PutInvoker) would be done using the GData Java Client, that provides tools and an abstract layer, abstracting the necessity of handling with HTTP requests/responses and XML's processing. The binding-gdata could extend the binding-rss aiming to allow RSS feeds. This approach looks like the binding-feed, but reusing the binding-atom and binding-rss, and using the GData Java Client to implement the invokers. What do you think about? Douglas, We need to take some care over the idea of using the GData Java Client - we need to check out the legal terms that apply to the client code, since it does not appear to have a license that is compatible with the Apache open source license, as far as I can tell. I'm not saying that you can't use the Google code, but we do need to ask to see what the right way would be to use this code. Yours, Mike. Luciano, What about this page, linked off the one above: http://code.google.com/tos.html Yours, Mike. -- Douglas Siqueira Leite Computer Science Master's degree student of University of Campinas (Unicamp) -- Douglas Siqueira Leite Computer Science Master's degree student of University of Campinas (Unicamp)
[jira] Updated: (TUSCANY-2357) CORBA objects invocation mechanism
[ https://issues.apache.org/jira/browse/TUSCANY-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wojtek Janiszewski updated TUSCANY-2357: Attachment: exceptions-references.patch.tar.gz Thanks for applying previous patch. This one adds: 1. Translating remote exceptions into user declared exceptions 2. Some exception handling 3. Obtaining and using CORBA references 4. Tests for 1 and 3 - idl files and generated classes added 5. tester.idl was moved to general_tests.idl CORBA objects invocation mechanism -- Key: TUSCANY-2357 URL: https://issues.apache.org/jira/browse/TUSCANY-2357 Project: Tuscany Issue Type: New Feature Reporter: Wojtek Janiszewski Attachments: add-license-headers.patch.tar.gz, corba-operation-invoker.patch.tar.gz, exceptions-references.patch.tar.gz Implementation of generic mechanism for remote operation invocation: passing CORBA structures, sequences, primitives as arguments, retrieving return values (also structs, seq, prims.). There is no exception handling yet. It's not connected to CORBA binding extension yet - it won't be hard, and I think it's now more important to complete this generic mechanism. Some tests are provided - you need to have tnameserv in your PATH to run tests correctly! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: GSoC Project - CORBA Support for Apache Tuscany
Hi,
I've gathered all current/past issues regarding project on wiki page:
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/CORBA+reference+binding+features%2C+bugs%2C+issues
Comments are always welcome.
Thanks,
Wojtek
Wojtek Janiszewski wrote:
Wojtek Janiszewski wrote:
Simon Nash wrote:
One comment inline.
Simon
6. If CORBA objects operation argument is object reference, then
user should provide object which was previously obtained from
binding or other CORBA object. User cannot use users-side object
as an argument.
Yes. Let's don't worry object reference too much at this point. We
are in the SOA world instead of distributed object :-).
This is OK if we are exposing a SCA service via CORBA. If we are using
SCA to invoke existing CORBA services that expect object references
to be passed, we will need to come up with an approach for handling
them.
I'd suggest that we start first with exposing SCA services via CORBA
as this seems to be the simplest and most useful form of integration.
Unfortunately I started earlier with reference bindings - even
submitted a patch today.
My thoughts for object references are that after obtaining some remote
reference, it will be enhanced by cglib and connected to users
declared interface. By enhancing I mean interception of methods
invocations and adding dynamic CORBA invocations. Such enhanced object
could be recognizable by dynamic invocation mechanism, and it could be
passed while invoking operations on remote objects.
In this solution we would have two types of CORBA objects - ones that
were intentionally declared, and ones that were obtained from roots,
and which are transparent. It's maybe kind of out of control by
Tuscany runtime, but is there any other way to obtain and use CORBA
references which are not registered in name services?
Thanks,
Wojtek
Hi,
I recently submitted some code, which helps invoking remote objects.
Mechanism for invoking remote CORBA objects is determining operation
arguments types by Java types and I'm not sure that Java to CORBA
mapping model I proposed is OK.
There is quite nice description of Java to CORBA mapping under [1]. It
shows how idlj compiler creates Java structure basing on idl file and I
believe we shouldn't precisely follow those rules and try to make them
as simple as possible. Am I right?
1. Structures
I proposed that CORBA structures will be Java classes, with public
fields and no get/set methods. So every class field is member for CORBA
structure. Or maybe we should map JavaBean classes to CORBA structures?
2. Sequences and arrays
Sequences and arrays can be mapped to Java by arrays or lists.
Unfortunately both CORBA types behaves bit different, additionally CORBA
arrays have fixed length so there should be possibility to distinguish
those types somehow. For now on I cannot find any other solution, but
annotating arrays with it's target length. Any opinions?
3. Arguments with inout/out modifiers
In CORBA, operation argument value can be changed. As we know Java
supports passing arguments by values only, so update on argument is not
possible. Such was solved in Java by wrapping arguments in holder
classes, ie:
public class IntHolder {
public int value;
}
This means if user wants to get his argument updated he needs to create
argument in holder class, which could be tough (maybe there are
low-level techniques which allows to manipulate such arguments?).
I know I should provide some method to recognize if users class is
holder for inout/out argument:
a. annotation
b. by implementing interface, ie:
public interface Holder {
void setValue(Object value);
Object getValue();
}
Or maybe there is some other solution? Which one should I choose?
I'll appreciate any comments. Just ask if you need more details.
[1] - http://members.tripod.com/gsraj/corba/chapter/
Thanks,
Wojtek
Re: Build error in sca\itest\properties
I fixed it under r664614. When I applied the patch, I forgot to adjust the
dependencies as the Eclipse compiled it.
Thanks,
Raymond
--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Sunday, June 08, 2008 1:47 AM
To: tuscany-dev@ws.apache.org
Subject: Build error in sca\itest\properties
I am seeing a compilation failure in sca\itest\properties. Is anyone else
hitting this error? Command output given below.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Apache Tuscany SCA Properties Integration Tests
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\T\java\sca\itest\properties\target
[INFO] [tuscany-sdo:generate {execution: generate-customer-sdo}]
[INFO] Generating SDO interfaces from
D:\T\java\sca\itest\properties\src\main\resources\customer.xsd
Generating code
Generating packages
Generating package SdoPackageImpl
Generating Java interface com.example.customer.sdo.SdoFactory
Generating /TargetProject/com/example/customer/sdo/SdoFactory.java
Generating Java class com.example.customer.sdo.impl.SdoFactoryImpl
Generating
/TargetProject/com/example/customer/sdo/impl/SdoFactoryImpl.java
Generating Customer
Generating Java interface com.example.customer.sdo.Customer
Generating /TargetProject/com/example/customer/sdo/Customer.java
Generating Java class com.example.customer.sdo.impl.CustomerImpl
Generating
/TargetProject/com/example/customer/sdo/impl/CustomerImpl.java
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 26 source files to
D:\T\java\sca\itest\properties\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[29,22]
package javax.xml.bind does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[30,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[31,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[31,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[32,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[33,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[34,33]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[74,11]
cannot find symbol
symbol : class JAXBElement
location: class test.jaxb.props.ObjectFactory
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[49,1]
cannot find symbol
symbol: class XmlRegistry
@XmlRegistry
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[57,1]
cannot find symbol
symbol: class XmlAccessorType
@XmlAccessorType(XmlAccessType.FIELD)
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[58,1]
cannot find symbol
symbol: class XmlType
@XmlType(name = ReturnCodeProperties, namespace =
http://test.sca.jaxb/rcprops;, propOrder = {
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[73,5]
cannot find symbol
symbol : class XmlElementDecl
location: class test.jaxb.props.ObjectFactory
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[64,5]
cannot find symbol
symbol : class XmlElement
location: class test.jaxb.props.ReturnCodeProperties
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[66,5]
cannot find symbol
symbol : class XmlElement
location: class test.jaxb.props.ReturnCodeProperties
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\package-info.java:[26,26]
package javax.xml.bind.annotation does not exist
D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[75,19]
cannot find symbol
symbol : class JAXBElement
location: class test.jaxb.props.ObjectFactory
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 6 seconds
[INFO] Finished at: Sun Jun 08 14:15:34 IST 2008
[INFO] Final
