June 2011 - jbosstools-dev - Jboss List Archives

Re: [jbosstools-dev] questions about eclipse project facet

by Max Rydahl Andersen

please use jbosstools-dev for dev questions Grid. (moved it) > 1 when I add the bpel facet, I only use codes to add the facet, don't do others, but in the org.eclipse.wst.common.project.facet.core.xml: > <fixed facet="bpel.facet.core"/> > Who and why add the fixed facet? I'll assume the facet system. > 2 when I remove the bpel facet, using facetproject.uninstallprojectfacet(), I only can remove: > <installed facet="bpel.facet.core" version="2.0"/> from > org.eclipse.wst.common.project.facet.core.xml. The > <fixed facet="bpel.facet.core"/> is still there. > How do I can remove the fixed facet? fixed facets are locked in based on the project type - so if you created it as a BPEL project that is fixed in as I understand it. See http://www.eclipse.org/articles/Article-BuildingProjectFacets/tutorial.html /max http://about.me/maxandersen

12 years, 10 months

2
3
0 / 0

JBoss AS 7 webinars

by Max Rydahl Andersen

Hi, In case you guys missed it there are webinars coming up the next couple of days introducing JBoss AS 7 and JEE6/CDI - and you might see JBoss Tools have some presence there too :) Info at http://www.jboss.org/as7 /max http://about.me/maxandersen

12 years, 10 months

1
0
0 / 0

.settings in o.j.ide.eclipse.as.core

by Alexey Kazakov

Hi Rob, Andre, I removed -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5 from trunk/as/plugins/org.jboss.ide.eclipse.as.core/.settings/org.eclipse.jdt.core.prefs to get rid of compilation error in Eclipse for this plug-in since it uses Java 1.6 syntax and MANIFES.MF has Bundle-RequiredExecutionEnvironment: JavaSE-1.6 Committed to trunk.

12 years, 10 months

2
2
0 / 0

Re: [jbosstools-dev] Ambiguous EL names

by Alexey Kazakov

Thanks Pete. I created the issue - https://issues.jboss.org/browse/WELD-930 On 06/25/2011 04:52 AM, Pete Muir wrote: > This looks to me like a bug in Weld (one that crept in from a pre-final spec revision) - that it checks if the declaring bean class is an alternative, and if it is, makes the producer an alternative. Can you file a WELD issue for this? I'll update the quickstart to explicitly make the producer an alternative. > > Pete

12 years, 10 months

1
0
0 / 0

JBoss Tools 3.3.0.M2 (Core and SOA Tooling) available for QE / early testing

by Nick Boldt

http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M2/ http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M2.soa-tool... http://download.jboss.org/jbosstools/builds/development/3.3.0.M2/ http://download.jboss.org/jbosstools/builds/development/3.3.0.M2.soa-tool... Once these pass QE they will be pushed up to sourceforge and www.jboss.org for more widespread consumption. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 10 months

2
1
0 / 0

Compilation error in ForgeLauncheHelper

by Alexey Kazakov

Hi Koen, there is a compilation error in org.jboss.tools.forge.core.ForgeLauncheHelper.java in trunk: The method getName() is undefined for the type ForgeRuntime (line 149)

12 years, 10 months

1
0
0 / 0

Ambiguous EL names

by Alexey Kazakov

Hi Pete, I'm looking at examples from https://github.com/pmuir/jboss-as-developer-guide/tree/master/quickstarts and I have a question... There is org.jboss.as.quickstarts.login.EJBUserManager: /... @Named("userManager") @RequestScoped @Alternative @Stateful public class EJBUserManager implements UserManager { ... @Produces @Named @RequestScoped public List<User> getUsers() throws Exception { ... } ... } / It's an alternative bean class which declare a @Named producer. And there is also another bean org.jboss.as.quickstarts.login.ManagedBeanUserManager: /@Named("userManager") @RequestScoped public class ManagedBeanUserManager implements UserManager { @SuppressWarnings("unchecked") @Produces @Named @RequestScoped public List<User> getUsers() throws Exception { ... } ... } / So EL names of both bean classes ("userManager") are the same. This is OK and JBoss Tools doesn't treat it as a problem because EJBUserManager is an alternative. But EL names of the producers are treated as ambiguous EL names ("users"). I looked at the spec. and still don't understand where our tooling is wrong: /5.3.1. Ambiguous EL names An ambiguous EL name exists in an EL expression when an EL name resolves to multiple beans. When an ambiguous EL name exists, the container attempts to resolve the ambiguity. If any of the beans are alternatives, the container eliminates all beans that are not alternatives, *except for producer methods and fields of beans that are alternatives*. If there is exactly one bean remaining, the container will select this bean, and the ambiguous EL name is called resolvable./ Thanks.

12 years, 10 months

1
0
0 / 0

whats new for review

by Max Rydahl Andersen

Hi, I've fixed and cleaned M2 N&N and pushed it for review on http://docs.jboss.org/tools/whatsnew/ Please take a moment and look through and ensure your stuff is there and see if things are sane/complete for other parts too ;) Thanks, /max http://about.me/maxandersen

12 years, 10 months

2
2
0 / 0

internal non-supported Hibernate libraries being exposed to users ...is...bad!

by Max Rydahl Andersen

Hi Dima/all, I just noticed https://issues.jboss.org/browse/JBIDE-6098 while reading through updated N&N That issue exposes hibernate tools libraries to users projects and that must *not* happen. Not sure why that got implemented and committed and i've asked it to be removed in https://issues.jboss.org/browse/JBIDE-9238 assuming this really works as described/shown. Getting libraries should *not* happen by exposing internal jars which doesn't have latest fixes, aren't supported and for sure isn't intended for anything but internal details of our plugins. I'll work with Dima to figure out what happened but just wanted to raise awareness that adding jars to our users project should not be done lighthearted and it for sure shouldn't just be internal jars that are incomplete. Another related antipattern is http://relation.to/Bloggers/NavelgazingClasspathContainersAnEclipseAntiPa... Much better solution is to use maven repositories to provide user with libraries! Thanks for reading, /max http://about.me/maxandersen

12 years, 10 months

1
0
0 / 0

M2 has zero issues left - triggering build today - branch closed for business!

by Max Rydahl Andersen

Hi, The M2 branch should now be considered completely offlimits while Nick respins the TP to include m2/wtp 1.0 and from there do the M2 rebuild we expect to be our final build to release next week. /max http://about.me/maxandersen

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev June 2011