> So, I red somewhere, the Cypal is able to export the GWT's generated
> output automatically as a war file.
> I have looked for this behavior, but I found a trivial solution: on
> the Preferences page's Cypal section I made the WebContent folder to
> the Output folder. Is it the only solution, or do we have an other
> elegant chance?

       Look at the File -> Export -> WAR :-)

Look at the documentation for adding an RPC: http://www.cypal.in/studiodocs

 - Prakash

"People are meant to be loved and things are meant to be used.
But unfortunately, people are being used and things are being loved"



2009/1/5 szebeni <kha...@gmail.com>:
>
> Hi all!
>  I'm new on this group, I'm learning GWT for some weeks, I have tried
> the GWT's console scripts and this plugin, too.
> So, I red somewhere, the Cypal is able to export the GWT's generated
> output automatically as a war file.
> I have looked for this behavior, but I found a trivial solution: on
> the Preferences page's Cypal section I made the WebContent folder to
> the Output folder. Is it the only solution, or do we have an other
> elegant chance?
> Other thing: I prefer the Dynamic Web project, because I usually
> develop J2EE Web applications, so, it is working, with a little
> modification: I must add the gwt-dev-*.jar as a Library (before the
> server runtime), else I get an error message (tomcat doesn't found the
> tomcat-juli.jar).
> Third thing: running an RPC example project, i must rewrite the RPC's
> url in the web.xml, or copy the hostpage from the package to the
> WebContent's root, because:
> annotated service url: 
> http://host:port/projectContext/modulepackage/serviceFacadeRPC
> @RemoteServiceRelativePath("serviceFacadeRPC")
> public interface ServiceFacade extends RemoteService {
>        public String getHello(String name);
>        public static class Util {
>                public static ServiceFacadeAsync getInstance() {
>                        return GWT.create(ServiceFacade.class);
>                }
>        }
> }
> And the generated servlet mapping in the web.xml:
> <servlet>
>        <servlet-name>ServiceFacade</servlet-name>
>        <servlet-class>
>        modulepackage.server.ServiceFacadeImpl</servlet-class>
>  </servlet>
>  <servlet-mapping>
>        <servlet-name>ServiceFacade</servlet-name>
>        <url-pattern>/serviceFacadeRPC</url-pattern>
>  </servlet-mapping>
>
> So, the main point is: the RPC servlet's url: 
> http://host:port/projectContext/serviceFacadeRPC
> (there isn't the modulepackage)
> Is it a bug or a feature?
>
> Thanks
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Cypal Studio for GWT" group.
To post to this group, send email to cypal-studio-for-gwt@googlegroups.com
To unsubscribe from this group, send email to 
cypal-studio-for-gwt+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/cypal-studio-for-gwt?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to