[JBoss JIRA] Created: (SEAMCONFIG-51) Using seam-config-xml 3.1.0.Beta2 fails with NoClassDefFoundError: org/jboss/seam/logging/Logger
by Geoffrey De Smet (JIRA)
Using seam-config-xml 3.1.0.Beta2 fails with NoClassDefFoundError: org/jboss/seam/logging/Logger
------------------------------------------------------------------------------------------------
Key: SEAMCONFIG-51
URL: https://issues.jboss.org/browse/SEAMCONFIG-51
Project: Seam Config
Issue Type: Bug
Components: Build Infrastructure
Reporter: Geoffrey De Smet
Assignee: Stuart Douglas
3.0.0.Final doesn't have this problem.
It even looks like seam-config-xml 3.1.0.Beta2 is borked because adding the logging dependency explicitly
{code}
<dependency><!-- WORKAROUND because seam-config-xml doesn't have a transitive dependency on this -->
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging</artifactId>
<version>3.0.0.Beta5</version>
</dependency>
{code}
results in java.lang.ClassNotFoundException: org.drools.guvnor.server.repository.RepositoryShutdownService
something that works by using 3.0.1-SNAPSHOT instead
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (SOLDER-120) Deployment error when having more than one @Named @Unwraps producer in the project
by Cody Lerum (JIRA)
Deployment error when having more than one @Named @Unwraps producer in the project
----------------------------------------------------------------------------------
Key: SOLDER-120
URL: https://issues.jboss.org/browse/SOLDER-120
Project: Seam Solder
Issue Type: Bug
Affects Versions: 3.0.0.Final
Reporter: Cody Lerum
Having two @Producer methods in an application which are @Named throws a deployment error. If you remove the @Named it deploys fine. The two producers are in different classes with different method names.
WELD-001414 Bean name is ambiguous. Name resolves to beans [org.jboss.seam.solder.unwraps.UnwrapsProducerBean@eb3516, org.jboss.seam.solder.unwraps.UnwrapsProducerBean@923822]
Looking at this error and the source it does appear that the UnwrapsProducer doesn't read the producer method name if the value is not defined in the annotation as it should. However even If I explicitly set the name in the @Named Weld still fails to deploy
org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name newServiceReturn resolves to beans [org.jboss.seam.solder.unwraps.UnwrapsProducerBean@8807d7, Producer Method [ServiceReturn] with qualifiers [@Any @CreateBean @Named] declared as [[method] @Produces @Unwraps @CreateBean @Named public co.domain.service.returns.ServiceReturnUtil.newServiceReturn()]]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (SEAMFACES-183) I cannot insert value expressions with the composite components property
by luca stancapiano (JIRA)
I cannot insert value expressions with the composite components property
------------------------------------------------------------------------
Key: SEAMFACES-183
URL: https://issues.jboss.org/browse/SEAMFACES-183
Project: Seam Faces
Issue Type: Bug
Components: UI Components
Affects Versions: 3.0.1
Environment: seam 3.0.1 + mojarra 2.0.3.b5
Reporter: luca stancapiano
Fix For: 3.0.1
If I use a value expression in a composite component, it is rejected and moved to a default value. Here an example of a jsp:
<ui:composition ................
xmlns:p="http://java.sun.com/jsf/composite/components/property"
.........
<p:input id="number" label="#{bundles.messages.receipt_number}">
............
</p:input>
<h:button id="cancel" value="#{bundles.messages.template_linkReset}" outcome="/receipt.xhtml"/>
...........
The problem is inside the encodeBegin method of org.jboss.seam.faces.component.UIInputContainer class:
...............
if (!getAttributes().containsKey(getRequiredAttributeName()) && elements.hasRequiredInput()) {
getAttributes().put(getRequiredAttributeName(), true);
}
if (!getAttributes().containsKey(getLabelAttributeName())) {
getAttributes().put(getLabelAttributeName(), generateLabel(elements, context));
}
...............
The containsKey method of the javax.faces.component.UIComponentBase$AttribuetsMap class ignores all keys from a subclass of the UIComponentBase, in our case the UIInputContainer. Doing an:
getAttributes().get(getLabelAttributeName())
we get the correct result. This achievement is showed in the JSF javadocs (http://javaserverfaces.java.net/nonav/docs/2.1/javadocs/javax/faces/compo...):
If the attribute name specified as a key matches a property of this UIComponent's implementation class, the following methods will have special behavior:
containsKey - Return false.
get() - If the property is readable, call the getter method and return the returned value (wrapping primitive values in their corresponding wrapper classes); otherwise throw IllegalArgumentException.
put() - If the property is writeable, call the setter method to set the corresponding value (unwrapping primitive values in their corresponding wrapper classes). If the property is not writeable, or an attempt is made to set a property of primitive type to null, throw IllegalArgumentException.
remove - Throw IllegalArgumentException.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (SEAMFACES-197) Exceptions passed to Catch should have a qualifier
by Jason Porter (JIRA)
Exceptions passed to Catch should have a qualifier
--------------------------------------------------
Key: SEAMFACES-197
URL: https://issues.jboss.org/browse/SEAMFACES-197
Project: Seam Faces
Issue Type: Feature Request
Components: Exception Handling
Affects Versions: 3.0.2
Reporter: Jason Porter
Priority: Minor
It could be possible for an exception to be passed to Catch that is outside of JSF, or is manually fired into Catch. To help the users determine which this is a qualifier should be added to the event fired to Catch.
A phase qualifier may also be helpful, but not sure if this is needed as we can get it from the FacesContext easily.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months