[JBoss JIRA] Created: (SEAM-38) new-entity command throws java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.impl.CompilerOptions.getSeverity(J)I
by Martin Gencur (JIRA)
new-entity command throws java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.impl.CompilerOptions.getSeverity(J)I
-----------------------------------------------------------------------------------------------------------------------------
Key: SEAM-38
URL: https://issues.jboss.org/browse/SEAM-38
Project: Seam 3
Issue Type: Bug
Components: Build Infrastructure
Environment: Affects CR2 version.
Reporter: Martin Gencur
Fix For: 3.0.0.Final
When I run the new-entity command from within Forge's console I'm getting the following exception. This works fine with standalone Forge 1.0.0.Alpha2 but in the Seam distribution is fails which implies some packaging defect.
[test] test $ new-entity --named Martin
In which package you'd like to create this @Entity, or enter for default: [com.mgencur.domain]
***ERROR*** [new-entity] org.eclipse.jdt.internal.compiler.impl.CompilerOptions.getSeverity(J)I
org.jboss.seam.forge.shell.exceptions.CommandExecutionException: org.eclipse.jdt.internal.compiler.impl.CompilerOptions.getSeverity(J)I
at org.jboss.seam.forge.shell.command.Execution.perform(Execution.java:144)
at org.jboss.seam.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:125)
at org.jboss.seam.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:63)
at org.jboss.seam.forge.shell.ShellImpl.execute(ShellImpl.java:659)
at org.jboss.seam.forge.shell.ShellImpl.doShell(ShellImpl.java:552)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
at org.jboss.seam.forge.shell.org$jboss$weld$bean-classpath-ManagedBean-class_org$jboss$seam$forge$shell$ShellImpl_$$_WeldClientProxy.doShell(org$jboss$weld$bean-classpath-ManagedBean-class_org$jboss$seam$forge$shell$ShellImpl_$$_WeldClientProxy.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222)
at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:632)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:619)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:613)
at org.jboss.seam.forge.shell.Bootstrap.init(Bootstrap.java:75)
at org.jboss.seam.forge.shell.Bootstrap.main(Bootstrap.java:63)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.seam.forge.shell.command.Execution.perform(Execution.java:140)
... 30 more
Caused by: java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.impl.CompilerOptions.getSeverity(J)I
at org.eclipse.jdt.internal.core.util.CommentRecorderParser.initializeScanner(CommentRecorderParser.java:241)
at org.eclipse.jdt.internal.compiler.parser.Parser.<init>(Parser.java:877)
at org.eclipse.jdt.internal.core.util.CommentRecorderParser.<init>(CommentRecorderParser.java:38)
at org.eclipse.jdt.core.dom.CompilationUnitResolver.parse(CompilationUnitResolver.java:391)
at org.eclipse.jdt.core.dom.ASTParser.internalCreateAST(ASTParser.java:885)
at org.eclipse.jdt.core.dom.ASTParser.createAST(ASTParser.java:651)
at org.jboss.seam.forge.parser.JavaParser.parse(JavaParser.java:125)
at org.jboss.seam.forge.parser.JavaParser.create(JavaParser.java:164)
at org.jboss.seam.forge.spec.jpa.NewEntityPlugin.newEntity(NewEntityPlugin.java:86)
... 35 more
new-project --named test --topLevelPackage com.mgencur
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (SEAM-31) Booking example improvements
by Shane Bryzak (JIRA)
Booking example improvements
----------------------------
Key: SEAM-31
URL: https://issues.jboss.org/browse/SEAM-31
Project: Seam 3
Issue Type: Enhancement
Components: Shared Examples
Affects Versions: 3.0.0.CR1
Reporter: Shane Bryzak
Fix For: 3.0.0.Final
Some suggestions for the booking example:
1. Increase the conversation timeout to 10 minutes
2. If the conversation times out, display a pretty error page not a stack trace
3. The star icons for the hotel class should be inversed (i.e. the number of 'filled in' stars should be used to indicate the hotel class)
4. Use Seam security module for application security
5. The smoking/non smoking radio boxes take up a lot of vertical space, consider a horizontal layout for these
6. It would be nice to have a date picker for check-in/check-out dates
7. It should be 'Credit card' not 'CreditCard'
8. It would be nice to localize the application for at least one other language, and allow the user to select his language (and store that selection in his user record)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (SEAM-54) Document the purpose of the seam-bom in the seam refguide
by Dan Allen (JIRA)
Document the purpose of the seam-bom in the seam refguide
---------------------------------------------------------
Key: SEAM-54
URL: https://issues.jboss.org/browse/SEAM-54
Project: Seam 3 Distribution
Issue Type: Task
Components: Common Documentation
Affects Versions: 3.0.0.CR3
Reporter: Dan Allen
Fix For: 3.0.0.Final
Developers are going to be confused about what seam-bom is all about unless we document it more clearly. The documentation should cover:
1. What it is
2. How to use it
3. That it's okay to specify a module version in an application if you want to upgrade
4. How modules use the seam-bom (and when can they specify an explicit version of a dependent module)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (SOLDER-89) Document utilities provided by AnnotationInspector
by Dan Allen (JIRA)
Document utilities provided by AnnotationInspector
--------------------------------------------------
Key: SOLDER-89
URL: https://issues.jboss.org/browse/SOLDER-89
Project: Seam Solder
Issue Type: Feature Request
Components: Reflections
Affects Versions: 3.0.0.CR2
Reporter: Dan Allen
Fix For: 3.0.0.Final
Several developers are asking how to find qualifiers of a bean that are inherited from stereotypes. The AnnotationInspector API from Solder provides these, and other annotation inspection utilities. However, the methods are not documented in the reference guide. Given their significance, they should be covered in a dedicated section. The section should point out why it's important to honor stereotypes when looking for qualifiers on a bean.
Also update the JavaDoc for the methods if necessary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (SOLDER-73) Misc documentation issues
by Jozef Hartinger (JIRA)
Misc documentation issues
-------------------------
Key: SOLDER-73
URL: https://issues.jboss.org/browse/SOLDER-73
Project: Seam Solder
Issue Type: Bug
Components: Documentation
Affects Versions: 3.0.0.Beta3
Reporter: Jozef Hartinger
Priority: Minor
* Section 1.2
** remove org.jboss.logging:jboss-logging as a transitive dependency
** change "Most of Seam Solder has very few dependencies, only one of which is not provided by Java EE 6:" to reflect reality
* Chapter 3 - "Annotations without *listitems* provide a static INSTANCE *listitem* that should be used rather than creating a new instance every time." - this probably talks about annotations without *members* - IMHO it is not correct to reference annotation members as "listitems" - at least the CDI spec uses the term *member*
* Chapter 6
** "Access to MDC and NDC" - personally, I have no idea what *MDC* and *NDC* mean - consider explaining / using full name / providing a link
* Chapter 7
** " This chapter will walk you each utility" - should be "This chapter will walk you *through* each utility"
** s/javaodoc/javadoc
* Section 7.1
** s/Seam Solder provides an AnnotatedType implementation that should be suitable for most portable extensions needs./Seam Solder provides an AnnotatedType implementation that should be suitable for most portable *extensions'* needs.
* Chapter 14 - s/intercepter/interceptor
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (SEAMFACES-82) injection of managed beans in face converter always null if multiple seam 3 components present in the web-inf/lib
by yangju (JIRA)
injection of managed beans in face converter always null if multiple seam 3 components present in the web-inf/lib
-----------------------------------------------------------------------------------------------------------------
Key: SEAMFACES-82
URL: https://issues.jboss.org/browse/SEAMFACES-82
Project: Seam Faces
Issue Type: Bug
Components: CDI Integration
Affects Versions: 3.0.0.Beta2
Environment: jboss AS 6 final, windows, war deployment
Reporter: yangju
Priority: Critical
I have a big war with seam 3 faces, persistence, internationalization, xml config, solder modules in the web-inf/lib.
I have tried to inject managed beans into the jsf converter, but it does not matter it is my own bean or seam's bean or weld's bean, the bean is always null. It seems that the injection fails silently. The converter code is as follows:
package com.pearson.epen.managedBean.converter;
import java.io.Serializable;
import java.util.List;
import javax.annotation.PostConstruct;
import javax.enterprise.context.SessionScoped;
import javax.faces.component.UIComponent;
import javax.faces.context.FacesContext;
import javax.faces.convert.Converter;
import javax.faces.convert.FacesConverter;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import org.slf4j.Logger;
import com.pearson.epen.account.model.api.TestAdmin;
import com.pearson.epen.cdi.qualifier.CentralRepo;
import com.pearson.epen.cdi.qualifier.StaticData;
@SessionScoped
@FacesConverter("convert.TestAdmin")
public class TestAdminConverter implements Converter, Serializable {
private static final long serialVersionUID = 1L;
@Inject
@StaticData
private List<TestAdmin> admins;
@Inject
private FacesContext context;
@Inject
@CentralRepo
private EntityManager em;
@Inject
private Logger log;
@PostConstruct
public void init() {
log.info("%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%init");
}
@Override
public Object getAsObject(FacesContext context, UIComponent component, String value) {
try {
Long id = Long.valueOf(value);
for (TestAdmin admin : admins) {
if (admin.getId().longValue() == id.longValue()) {
return admin;
}
}
} catch (Throwable t) {
log.error("got exception", t);
}
return null;
}
@Override
public String getAsString(FacesContext context, UIComponent component, Object value) {
TestAdmin testAdmin = (TestAdmin) value;
return Long.toString(testAdmin.getId());
}
}
In above code, all injections are null and the @PostConstruct method is never called. However, getAsObject(FacesContext context, UIComponent component, String value) and getAsString(FacesContext context, UIComponent component, Object value) did get called.
According to some other users, the injection works for them. But I am not sure they have multiple seam modules being used in the same war.
Our war is big and it is difficult to isolate our application to just use seam faces, not others. So I am not creating a sample war. But it should be easy for seam faces developer to test this.
I ended up doing bean lookup in my converter and it seems working and the bean is found in my converter.
public List<T> findBeanRef(FacesContext context, String beanELName) {
BeanManager bm = (BeanManager) (((ServletContext) context.getExternalContext().getContext())
.getAttribute("org.jboss.seam.faces.javax.enterprise.spi.BeanManager"));
Bean bean = bm.getBeans(beanELName).iterator().next();
CreationalContext ctx = bm.createCreationalContext(bean);
List<T> list = (List<T>) bm.getReference(bean, bean.getClass(), ctx);
return list;
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years