[jbosstools-issues] [JBoss JIRA] (JBIDE-10618) GWT's client classes deployed to App Server

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655445#comment-12655445 ] 

Max Rydahl Andersen edited comment on JBIDE-10618 at 1/12/12 4:56 AM:
----------------------------------------------------------------------

Here is how I understand it for now:

It is not actually a problem GWT client classes gets deployed to the server - what triggers this is Errai is generating classes with CDI annotations in them and thus AS7/Weld loads these unconditionally.

Options being considered: 

#1: Have the client classes generated to separate project (will work everywhere, but might not be supported by eclipse GWT way of working)

#2: Use AS7 custom descriptors to exclude classes (will work on AS7/Eclipse and mvn command line builds)

#3: Extend AS adapters to exclude classes (will only work in JBoss Tools)

#4: Tweak m2e-wtp to support war exclude/includes (will only work on mvn projects, not standalone eclipse)

#5: Fix WTP to support excludes (not before Eclipse 3.8/4.0 at best)

#6: Use CDI to declare beans that should only load when another resource is present (https://issues.jboss.org/browse/CDI-50)


                
      was (Author: maxandersen):
    Here is how I understand it for now:

It is not actually a problem GWT client classes gets deployed to the server - what triggers this is Errai is generating classes with CDI annotations in them and thus AS7/Weld loads these unconditionally.

Options being considered: 

#1: Have the client classes generated to separate project (will work everywhere, but might not be supported by eclipse GWT way of working)

#2: Use AS7 custom descriptors to exclude classes (will only work on AS7 and mvn command line builds)

#3: Extend AS adapters to exclude classes (will only work in JBoss Tools)

#4: Tweak m2e-wtp to support war exclude/includes (will only work on mvn projects, not standalone eclipse)

#5: Fix WTP to support excludes (not before Eclipse 3.8/4.0 at best)

#6: Use CDI to declare beans that should only load when another resource is present (https://issues.jboss.org/browse/CDI-50)


                  
> GWT's client classes deployed to App Server
> -------------------------------------------
>
>                 Key: JBIDE-10618
>                 URL: https://issues.jboss.org/browse/JBIDE-10618
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: GWT, JBossAS/Servers, maven
>            Reporter: Burr Sutter
>            Assignee: Fred Bricon
>            Priority: Critical
>             Fix For: 3.3.0.Beta1
>
>         Attachments: Screen Shot 2012-01-11 at 9.27.48 PM.png
>
>
> When using Run-As, Add-Remove or other WTP-based deployment mechanisms on a GWT app - the client Java classes are deployed to the server (under WEB-INF) - these .java files are supposed to be converted to .js files and not deployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira