[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3028) add ContainerManagedPersistenceContext
by Dan Allen (JIRA)
add ContainerManagedPersistenceContext
--------------------------------------
Key: JBSEAM-3028
URL: http://jira.jboss.com/jira/browse/JBSEAM-3028
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1, 2.0.2.GA
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Minor
Fix For: 2.1.0.GA
Attachments: JBSEAM-3028-v1.txt
Perhaps this is silly, perhaps not. I have developed a wrapper around a container-managed persistence manager, avoiding the need to have to lookup the EntityManagerFactory in JNDI. The main limitation here is that you cannot use this with EJB components, so it is really just a convenience of configuration if the Java EE application server happens to offer the ability to create an EntityManager for you. This also only works with the default persistence unit.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1590) Problem when deploying seam application as directory deployment in glassfish
by ivica c (JIRA)
Problem when deploying seam application as directory deployment in glassfish
----------------------------------------------------------------------------
Key: JBSEAM-1590
URL: http://jira.jboss.com/jira/browse/JBSEAM-1590
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.BETA1
Environment: glassfish V2 build 53
seam 2.0.0 beta1
jdk 1.6.0 update1
netbeans 6 daily build
Reporter: ivica c
Fix For: 2.0.0.CR1
Problem occurs when deploying seam application as directory deployment in glassfish. I am getting this exception:
Exception occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb.
Note:
1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [ctg-main] -- Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb.
Note:
1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:388)
at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:226)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:905)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:774)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
Caused by: java.lang.IllegalArgumentException: Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb.
Note:
1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:95)
at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:82)
at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:729)
at com.sun.enterprise.deployment.Application.visit(Application.java:1754)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:470)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:790)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
... 10 more
but when I deploy as norma arhive(when upload it) everything works fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2658) s:defaultAction only works 1 submit
by Susanne Jarl (JIRA)
s:defaultAction only works 1 submit
-----------------------------------
Key: JBSEAM-2658
URL: http://jira.jboss.com/jira/browse/JBSEAM-2658
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.1.GA
Environment: JBoss 4.2.2, RichFaces 3.1.4, Firefox 2.0.0.12, Windows XP
Reporter: Susanne Jarl
I use the s:defaultAction and it works the first time i hit enter, but if the inputtextfield is not validated and/or I get an error message, and then hit enter in the inputtextfield again it does not work. But if I click the submitbutton instead the second time it works. So there is a difference between clicking the button and hit enter the second time.
This is my code:
<h:form>
<s:validateAll>
<h:panelGrid columns="2">
<h:outputLabel value="#{messages['programkey.writePin']}:" for="pinCode" title="#{messages['handin.pinCode.title']}" />
<s:decorate for="pinCode">
<h:inputSecret id="pinCode" label="#{messages['programkey.writePin']}" value="#{agentHandler.pinCode}" size="4" required="true" />
<h:message for="pinCode" styleClass="errorMessage" />
</s:decorate>
<a4j:commandButton action="#{handin.handin}" value="#{messages['generic.button.ok']}" reRender="pollForProgrammingResult, pinCodePanel, feedbackPanel">
<s:defaultAction/>
</a4j:commandButton>
<s:button value="#{messages['generic.button.cancel']}" onclick="Richfaces.hideModalPanel('programModalPanel')"/>
</h:panelGrid>
</s:validateAll>
</h:form>
I have this form in a RichFaces modal panel.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months