Hi Luciano,
I followed JIRA-899 and the J2SE (my old client etc.) works fine.
But for the war, (even the one from your sandbox, without any changes), I am
getting the
below error. This error was not there on 20th Nov :), So not sure if this is
a result of
some other JIRA/compatibility issues? I will try to get you online tonight
IST and see
if can get this working. Appreciate any clues/help in this. Due to this I am
delaying
on the JSP and other test cases. My sincere apologies.
____________________________________________________________________
SEVERE: Exception sending context initialized event to listener instance of
class org.apache.tuscany.runtime.webapp.TuscanyContextListener
org.apache.tuscany.runtime.webapp.ServletLauncherInitException:
org.apache.tuscany.spi.loader.UnrecognizedElementException: {
http://tuscany.apache.org/xmlns/das/1.0}implementation.das [{
http://tuscany.apache.org/xmlns/das/1.0}implementation.das]
Context stack trace: [Tuscany DAS Container Sample Client
Application][CustomersOrdersComponent]
at org.apache.tuscany.runtime.webapp.WebappRuntimeImpl.initialize(
WebappRuntimeImpl.java:147)
at
org.apache.tuscany.runtime.webapp.TuscanyContextListener.contextInitialized(
TuscanyContextListener.java:74)
at org.apache.catalina.core.StandardContext.listenerStart(
StandardContext.java:3763)
at org.apache.catalina.core.StandardContext.start(StandardContext.java
:4211)
at org.apache.catalina.core.ContainerBase.addChildInternal(
ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java
:608)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java
:535)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:310)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Caused by: org.apache.tuscany.spi.loader.UnrecognizedElementException: {
http://tuscany.apache.org/xmlns/das/1.0}implementation.das [{
http://tuscany.apache.org/xmlns/das/1.0}implementation.das]
Context stack trace: [Tuscany DAS Container Sample Client
Application][CustomersOrdersComponent]
at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(
LoaderRegistryImpl.java:90)
at org.apache.tuscany.core.loader.ComponentLoader.loadImplementation(
ComponentLoader.java:183)
at org.apache.tuscany.core.loader.ComponentLoader.load(ComponentLoader.java
:127)
at org.apache.tuscany.core.loader.ComponentLoader.load(ComponentLoader.java
:70)
at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(
LoaderRegistryImpl.java:92)
at org.apache.tuscany.core.implementation.composite.CompositeLoader.load(
CompositeLoader.java:81)
at org.apache.tuscany.core.implementation.composite.CompositeLoader.load(
CompositeLoader.java:55)
at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(
LoaderRegistryImpl.java:92)
at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(
LoaderRegistryImpl.java:109)
at
org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.loadFromSidefile
(CompositeComponentTypeLoader.java:65)
at
org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load
(CompositeComponentTypeLoader.java:57)
at
org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load
(CompositeComponentTypeLoader.java:39)
at org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(
LoaderRegistryImpl.java:159)
at org.apache.tuscany.core.deployer.DeployerImpl.load(DeployerImpl.java
:101)
at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.java
:76)
at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl(
AbstractRuntime.java:136)
at org.apache.tuscany.runtime.webapp.WebappRuntimeImpl.initialize(
WebappRuntimeImpl.java:138)
... 25 more
__________________________________________________________________________
Regards,
AmitaOn 11/20/06, Luciano Resende <[EMAIL PROTECTED]> wrote:
Just in case, by working with patches I mean to do something like : svn diff > /path/to/patchfile.patch This would create a patchfile.patch with only the difference from your code relative to the one on the trunk (on this case sandbox) and I can easily just apply the patch in my end. Let me know if you have questions... -- Luciano Resende http://people.apache.org/~lresende On 11/20/06, Luciano Resende <[EMAIL PROTECTED]> wrote: > > Would you mind if we start working with patches from what I have on the > sandbox ? that way i don't have to diff all files to check what you have > modified.... also, you can be in sync with what I'm doing by calling svn > updates.... > > - Luciano > > On 11/20/06, Amita Vadhavkar <[EMAIL PROTECTED]> wrote: > > > > Hi Luciano, > > I have made the web app and the das container combination working. There > > were some class cast etc. problems in orginal code. Now the jsp is > > showcasing > > a working SELECT through getAllCompanies(). This work is attached to > > JIRA-904. Please check it. I can modify it to showcase all CRUD + SP > > in 1 more day. Please see if you can put it after that ( I will mail you > > once > > work is completed and attached to JIRA). I feel, it will be better if > > I attach any > > work to JIRA and after you validate it, you can put it in your sandbox. > > Please > > let me know if this is not convenient. > > > > Regards, > > Amita > > > > On 11/18/06, Luciano Resende < [EMAIL PROTECTED]> wrote: > > > I have commited some small changes and a simple web app to my sandbox. > > > https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/lresende/ > > > > > > -- > > > Luciano Resende > > > http://people.apache.org/~lresende< http://people.apache.org/%7Elresende> > > > > > > > > > On 11/17/06, Luciano Resende < [EMAIL PROTECTED]> wrote: > > > > > > > > Jim and Kevin, thanks... I'm working on that... > > > > > > > > On 11/17/06, Kevin Williams <[EMAIL PROTECTED] > wrote: > > > > > > > > > > Jim Marino wrote: > > > > > > > > > > >> If I understood your question correctly, DAS allows a 1:1 and > > 1:N > > > > > >> relationship, > > > > > >> An application could have multiple components using the same > > config > > > > > >> file, > > > > > >> or could split the config file based on the components model... > > > > > but the > > > > > >> choice is really made by the app developer. > > > > > >> > > > > > > This sounds similar to the model JPA has with PersistenceUnit > > and > > > > > > Hibernate has with a SessionFactory. If I decide to share the > > > > > > configuration, does DAS process the configuration once and put > > it is > > > > > > some object? For example, JPA has an EntityManagerFactory which > > > > > > processes a configuration. The factory is used to create an > > > > > > EntityManager which is used by a JPA client. > > > > > > > > > > > > In the JPA integration work, the EntityManagerFactory is created > > and > > > > > > cached as a system component in the application > > composite. Something > > > > > > similar could be done with DAS if this model fits. > > > > > > > > > > > Currently, The DAS Factory does not cache a processed config > > model. > > > > > Sounds like this is something we should consider. > > > > > > > > > > > Jim > > > > > > > > > > > >> - Luciano > > > > > >> > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > -- > > > > Luciano Resende > > > > http://people.apache.org/~lresende > > <http://people.apache.org/%7Elresende> < > > http://people.apache.org/%7Elresende> > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Luciano Resende > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende > >
