[JBoss JIRA] Created: (SOLDER-62) Process logger annotations a build time
by Dan Allen (JIRA)
Process logger annotations a build time
---------------------------------------
Key: SOLDER-62
URL: https://issues.jboss.org/browse/SOLDER-62
Project: Seam Solder
Issue Type: Task
Components: Logging
Affects Versions: 3.0.0.Beta1
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 3.0.0.Beta2
Use the org.jboss.logging:jboss-logging-tools project to process the logger annotations at build time. We should not be relying on the jboss.i18n.generate-proxies system property inside a Seam module.
If we remove the system property assignment, we need to document how developers can still enable that feature in their applications.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (SOLDER-45) Support @Veto at package level
by Dan Allen (JIRA)
Support @Veto at package level
------------------------------
Key: SOLDER-45
URL: https://jira.jboss.org/browse/SOLDER-45
Project: Seam Solder
Issue Type: Feature Request
Components: Core
Reporter: Dan Allen
Fix For: 1.0.0.Beta2
It would be useful to be able to veto an entire package of beans. The most typical use case is when you want to veto the JPA entities, which typically reside in the same package. It may be reasonable to add a recursive flag to veto all nested packages as well.
Veto single package
@org.jboss.seam.solder.Veto
package com.acme.model;
Veto package and descendants
@org.jboss.seam.solder.Veto(recurse = true)
package com.acme.model;
If the recurse feature slows things down to much, we can forgo implementing it.
Obviously recurse would be meaningless when @Veto is applied to a type, perhaps even considered a deployment error if set to true in that case.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (SOLDER-65) LoggerProducers is not initialized
by Alexey Elkin (JIRA)
LoggerProducers is not initialized
----------------------------------
Key: SOLDER-65
URL: https://issues.jboss.org/browse/SOLDER-65
Project: Seam Solder
Issue Type: Bug
Affects Versions: 3.0.0.Beta1
Environment: JBossAS 6.0.0.final
Reporter: Alexey Elkin
Priority: Critical
I want to use logger in my java web application.
I'm using JBossAS 6.0.0.final, cdi (weld), jsf ... etc. Seam solder proposes to use an abstract logger is not tying to a concrete implementation (slf4j, log4j, etc) using jboss-logging api.
In order to get this logger in your code will need to write
@ Inject
org.jboss.logging.Logger log
seam-solder.jar has the producer for this logger.
package org.jboss.seam.solder.log;
...
class LoggerProducers
{
@ Produces
org.jboss.logging.Logger produceLog (InjectionPoint injectionPoint) {}
}
When I deploying my application, I get an error
15:51:18,300 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=vfs:///C:/Java/jboss-6.0.0.Final/server/default/deploy/kamis-web-client.5.0.0-SNAPSHOT.ear_WeldBootstrapBean state=Create: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Logger] with qualifiers [@Default] at injection point [[field] @Inject private ru.kamis.suite.webclient.web.breadcrumbs.BreadcrumbsManager.log]
This is due to the seam-solder.jar has not META-INF/beans.xml file, and it is necessary for cdi container.
If to add beans.xml file in seam-solder.jar manually, then the application works WELL.
How to do without hacks?
To build my application I use maven, so my solution is not comfortable and NOT fine.
PS: Former weld-extensions project contained META-INF/beans.xml file in jar.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months