[ https://issues.jboss.org/browse/JBIDE-10743?page=com.atlassian.jira.plugi... ] Hendy Irawan commented on JBIDE-10743: -------------------------------------- @Alexey : You are absolutely correct. Scala projects may contain Java and Scala sources mixed freely, and may contain inter-references between them. The Scala builder replaces the Java builder and compiles both sources. In other words, Scala builder is a superset of Java builder. Java EE does not require Java programming language, only the JVM platform (which Scala, Groovy, Clojure, etc. run on). I have no problems at all using Scala with Java EE tech including CDI (JBoss Weld/AS7.1 works excellent!). It's much better and more convenient than Java. Here's a snippet of a CDI Bean in Scala: {code} package com.satukancinta.ui import collection.JavaConversions._ import javax.enterprise.context.RequestScoped import javax.inject.Named import com.satukancinta.annotation.Person import javax.inject.Inject import com.satukancinta.domain.User import scala.reflect.BeanProperty import com.soluvas.social.story.StoryRepository import com.soluvas.social.story.Story import com.soluvas.social.story.BasicTarget import com.soluvas.social.story.SocialTarget @RequestScoped @Named class HomeView { @Inject @Person private var storyRepo: StoryRepository = _ @Inject @Named("currentUser") private var user: User = _ private lazy val stories: java.util.List[Story] = storyRepo.findByTarget(user) def getStories = stories implicit def user2SocialTarget(user: User): SocialTarget = BasicTarget(user.getNodeId) } {code} This should result in 'homeView' named bean accessible via JSF (which it is in runtime) but JBoss Tools/JSF Visual Editor does not recognize it. -- 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

[ https://issues.jboss.org/browse/JBIDE-10743?page=com.atlassian.jira.plugi... ] Hendy Irawan commented on JBIDE-10743: -------------------------------------- @Alexey : I'm not familiar with IDE/JDT internals so I try my best to be helpful here. In my mixed Java/Scala project, the CDI beans in .java sources are recognized properly by CDI/JSF tools. This despite that the project lacks a Java builder. However the CDI beans in .scala sources are not shown in JSF completion. If you want to try this for yourself you can get Scala IDE from: http://www.scala-ide.org/ Let me know if I can help... -- 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

[ https://issues.jboss.org/browse/JBIDE-10743?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-10743: ---------------------------------------- I believe that it's not an Eclipse IDE which provides autocompletion and navigation for .scala files. It's Scala IDE (for Eclipse). So to support CDI in .scala files we have to extend this Scala IDE. Unfortunately we don't have resources for such a big work. Anyway thank you for your comments and explanation. -- 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

[ https://issues.jboss.org/browse/JBIDE-10743?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-10743: ---------------------------------------- Heddy, take a look at http://anonsvn.jboss.org/repos/jbosstools/trunk/cdi/plugins/org.jboss.too... For example http://anonsvn.jboss.org/repos/jbosstools/trunk/cdi/plugins/org.jboss.too... -- 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

[ https://issues.jboss.org/browse/JBIDE-10743?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-10743: ----------------------------------- Fix Version/s: LATER -- 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

[ https://issues.jboss.org/browse/JBIDE-10743?page=com.atlassian.jira.plugi... ] Hendy Irawan commented on JBIDE-10743: -------------------------------------- Note to self, the check happens here around line 141: {code} ./jst/plugins/org.jboss.tools.jst.web/src/org/jboss/tools/jst/web/WebModelPlugin.java: getDefault().logError("Can't enable " + builderId + " support on the project " + project.getName() + " without Java builder."); //$NON-NLS-1$ //$NON-NLS-2$//$NON-NLS-3$ {code} supposedly, it should be possible to simply replace this line: {code} if(JAVA_BUILDER_ID.equals(existing[i].getBuilderName())) { {code} with: (Scala's builder is "org.scala-ide.sdt.core.scalabuilder") {code} if(JAVA_BUILDER_ID.equals(existing[i].getBuilderName()) || "org.scala-ide.sdt.core.scalabuilder".equals(existing[i].getBuilderName())) { {code} -- 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