May 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4364) "Open Mapping File" doesn't when there are no project associated with a console configuration

by Vitali Yemialyanchyk (JIRA)

"Open Mapping File" doesn't when there are no project associated with a console configuration --------------------------------------------------------------------------------------------- Key: JBIDE-4364 URL: https://jira.jboss.org/jira/browse/JBIDE-4364 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.0.1.GA, 3.1.0.M1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.M2 there are no exceptions, it doesn't open file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4325) Rename Seam Component wizard can't be called from context menu in .java file in seam War project.

by Anton Klimkovich (JIRA)

Rename Seam Component wizard can't be called from context menu in .java file in seam War project. ------------------------------------------------------------------------------------------------- Key: JBIDE-4325 URL: https://jira.jboss.org/jira/browse/JBIDE-4325 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M1 Reporter: Anton Klimkovich Assignee: Alexey Kazakov EXECUTE: Create seam war project EXECUTE: Create seam action with "first" as component name EXECUTE: Open First.java file EXECUTE: Select Seam->Rename Seam Component from context menu ASSERT: Rename Seam Component wizard should appear FAILURE: Rename Seam Component wizard can't be called from context menu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4371) Seam Web Project wizard doesn't generate the security rules files and doesn't deploy a datasource file to the server's root directory

by nitzan tomer (JIRA)

Seam Web Project wizard doesn't generate the security rules files and doesn't deploy a datasource file to the server's root directory ------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4371 URL: https://jira.jboss.org/jira/browse/JBIDE-4371 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.1.GA Environment: windows xp, eclipse 3.4.2, JBoss AS 5.0.1GA, Seam 2.1.1GA Reporter: nitzan tomer The project being created by the Seam Web Project wizard "forgets" two files: (1) the data source file (projectName-ds.xml) is not being deployed to the root directory of the application server (for example "default"), the files itself is generated (and is under the resources directory of the projectName-ear) but isn't deployed. this causes the following exceptions while deploying the project: [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "persistence.unit:unitName=projectName-ear.ear/projectName-ejb.jar#projectName" is missing the following dependencies: Dependency "jboss.jca:name=projectNameDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=projectNameDatasource,service=DataSourceBinding' **") DEPLOYMENTS IN ERROR: Deployment "jboss.jca:name=projectNameDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=projectNameDatasource,service=DataSourceBinding' ** "Make deployable" on the ds file prompt this message: "There are no servers that support deploying single files", instead this was solved by manually adding the data source file to the default directory of the server. (2) the security file is not being generated, even though it is configured in the components.xml (as security.drl) this causes the following exceptions when running the project (viewing it through the browser for the first time after deployment): ERROR [[/projectName]] Session event listener threw exception org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.security.ruleBasedPermissionResolver at org.jboss.seam.Component.newInstance(Component.java:2106) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278) at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:209) at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:141) at org.jboss.seam.servlet.SeamListener.sessionCreated(SeamListener.java:45) at org.apache.catalina.session.StandardSession.tellNew(StandardSession.java:397) at org.apache.catalina.session.StandardSession.setId(StandardSession.java:369) at org.apache.catalina.session.ManagerBase.createSession(ManagerBase.java:829) at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:291) at org.apache.catalina.connector.Request.doGetSession(Request.java:2367) at org.apache.catalina.connector.Request.getSession(Request.java:2094) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:844) at org.jboss.seam.web.IdentityRequestWrapper.<init>(IdentityRequestWrapper.java:23) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: securityRules at org.jboss.seam.Component.newInstance(Component.java:2106) at org.jboss.seam.Component.getInstance(Component.java:1988) at org.jboss.seam.Component.getInstance(Component.java:1950) at org.jboss.seam.Component.getInstance(Component.java:1944) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166) at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:112) at org.jboss.seam.Component$ELInitialValue.getValue(Component.java:2493) at org.jboss.seam.Component.initialize(Component.java:1494) at org.jboss.seam.Component.postConstructJavaBean(Component.java:1420) at org.jboss.seam.Component.postConstruct(Component.java:1343) at org.jboss.seam.Component.newInstance(Component.java:2091) ... 53 more Caused by: java.lang.RuntimeException: exception invoking: compileRuleBase at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:154) at org.jboss.seam.Component.callComponentMethod(Component.java:2211) at org.jboss.seam.Component.callCreateMethod(Component.java:2134) at org.jboss.seam.Component.newInstance(Component.java:2094) ... 69 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) ... 72 more Caused by: java.lang.NoClassDefFoundError: org/mvel/integration/impl/LocalVariableResolverFactory at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:63) at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:546) at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:506) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:504) at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:481) at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:134) at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131) at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:452) at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:258) at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:152) at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:259) at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102) at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772) at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at org.drools.rule.builder.dialect.java.JavaDialect.<init>(JavaDialect.java:73) at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.getDialect(JavaDialectConfiguration.java:64) at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:166) at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:142) at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:108) at org.jboss.seam.drools.RuleBase.compileRuleBase(RuleBase.java:41) ... 78 more Caused by: java.lang.ClassNotFoundException: org.mvel.integration.impl.LocalVariableResolverFactory at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279) at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102) at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772) at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) ... 103 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3034) Generate Hibernate/JPA gives double source menu for all non-java editors

by Max Rydahl Andersen (JIRA)

Generate Hibernate/JPA gives double source menu for all non-java editors ------------------------------------------------------------------------ Key: JBIDE-3034 URL: https://jira.jboss.org/jira/browse/JBIDE-3034 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.beta1 Reporter: Max Rydahl Andersen Assignee: Vitali Yemialyanchyk Fix For: 3.0.0.beta1 see attached. it is sometimes enabled other times not....but the unecessary menu is always there! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2991) Hibernate/JPA generation - if the class in the editor or seleciton is an interface or enum

by Vitali Yemialyanchyk (JIRA)

Hibernate/JPA generation - if the class in the editor or seleciton is an interface or enum ------------------------------------------------------------------------------------------- Key: JBIDE-2991 URL: https://jira.jboss.org/jira/browse/JBIDE-2991 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.0.0.beta1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Trivial Fix For: 3.0.0.cr1 the dialog should just say "Cannot generate annotations for an interface or enum" from JBIDE-2987. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3790) Hibernate console configuration require driver in classpath for selected Eclipse db connection

by Vitali Yemialyanchyk (JIRA)

Hibernate console configuration require driver in classpath for selected Eclipse db connection ---------------------------------------------------------------------------------------------- Key: JBIDE-3790 URL: https://jira.jboss.org/jira/browse/JBIDE-3790 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor The same HCC, like in https://jira.jboss.org/jira/browse/JBIDE-3787. Here HCC require driver in classpath for selected Eclipse db connection: screenshot-3.jpg in JBIDE-3787. It should work without driver setup here, cause Eclipse db connection has the driver settings internally. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4322) Generate Hibernate/JPA Annotation gives NPE for .java files without any classes

by Dmitry Geraskov (JIRA)

Generate Hibernate/JPA Annotation gives NPE for .java files without any classes ------------------------------------------------------------------------------- Key: JBIDE-4322 URL: https://jira.jboss.org/jira/browse/JBIDE-4322 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M1 Reporter: Dmitry Geraskov Assignee: Vitali Yemialyanchyk Fix For: 3.1.0.M1 This is also true for package-info.java files. java.lang.NullPointerException at org.hibernate.eclipse.jdt.ui.internal.jpa.collect.AllEntitiesInfoCollector.collect(AllEntitiesInfoCollector.java:708) at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActor.updateSelected(JPAMapToolActor.java:173) at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActionDelegate.run(JPAMapToolActionDelegate.java:43) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251) ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBDS-621) Add Custom Capabilities dialog description

by Svetlana mukhina (JIRA)

Add Custom Capabilities dialog description ------------------------------------------- Key: JBDS-621 URL: https://jira.jboss.org/jira/browse/JBDS-621 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.0.0.cr2 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.1 it's necessary to describe Add Custom Capabilities dialog, as there is no info on it in: JSF tutorial and ref guide, Visual Web tools, Migration, GSG call context menu on JSF project -> Jboss Tools -> Add Custom Capabilities. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3857) There is no any warning message when ESB version from list doesn't concur with Runtime version in New JBoss ESB Runtime wizard

by Anton Klimkovich (JIRA)

There is no any warning message when ESB version from list doesn't concur with Runtime version in New JBoss ESB Runtime wizard ------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-3857 URL: https://jira.jboss.org/jira/browse/JBIDE-3857 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich EXECUTE: Preferences-> JBoss Tools -> JBoss ESB Runtimes EXECUTE: Press Add button EXECUTE: Select ESB version as 4.4 from list EXECUTE: Select jboosesb-4.3.GA as runtime ASSERT: Warning message: Selected runtime doesn't support requested version. Finish button should be disabled. FAILURE: There is no any warning message. Finish button is enabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4368) Seam components autocompletion is broken in mavenized projects

by Fred Bricon (JIRA)

Seam components autocompletion is broken in mavenized projects -------------------------------------------------------------- Key: JBIDE-4368 URL: https://jira.jboss.org/jira/browse/JBIDE-4368 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.GA Environment: Vista, Eclipse 3.4.2.SR2, JBoss Tools 3.0.0.GA-R200903141626-H5, m2eclipse 0.9.8 Reporter: Fred Bricon Priority: Minor Hi, It looks like Seam components can't be found when editing xhtml pages for Mavenized projects. Try with the Seam Booking Mavenized example : - open hotelview.xhtml in the booking project, - Hold ctrl+ click on an EL like #{hotel.name} : An error message appears in the lower left corner of eclipse : Current text selection doesn't resolve to a file - type #{ and press Ctrl+space : components defined in booking-ejb are unavailable, but components from seam.jar are present There's a workaround : if you add booking-ejb as a provided dependency in the booking pom.xml, links and autocompletion work as expected. This is odd as regular seam web projects dont need their ejb project counterpart in their classpath regards, Fred Bricon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2009