Re: [seam-dev] Servlet module structure
by Lincoln Baxter, III
Done.
Seam-servlet module has been updated to follow the module anatomy
guidelines:
http://seamframework.org/Seam3/ModuleAnatomy
--Lincoln
On Fri, Apr 9, 2010 at 8:03 AM, Lincoln Baxter, III <lincolnbaxter(a)gmail.com
> wrote:
> Yeah but I don't like to keep people waiting. ;)
>
> Lincoln Baxter's Droid
> http://ocpsoft.com
> http://scrumshark.com
> Keep it simple.
>
> On Apr 9, 2010 8:02 AM, "Nicklas Karlsson" <nickarls(a)gmail.com> wrote:
>
> No panic, it's still unpublished so I don't think it has that many users...
>
>
>
> On Fri, Apr 9, 2010 at 2:57 PM, Lincoln Baxter, III <
> lincolnbaxter(a)gmail.com> wrote:
> >
> > Of course...
> --
> ---
> Nik
>
>
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
14 years, 1 month
Re: [seam-dev] [JBoss JIRA] Closed: (WELD-490) Weld parent POM uses deprecated maven APIs
by Lincoln Baxter, III
Seam-parent's parent updated to version 9 of weld-parent POM.
That was a mouthful... ;)
On Tue, Apr 13, 2010 at 2:47 PM, Pete Muir (JIRA) <
jira-events(a)lists.jboss.org> wrote:
>
> [
> https://jira.jboss.org/jira/browse/WELD-490?page=com.atlassian.jira.plugi...]
>
> Pete Muir closed WELD-490.
> --------------------------
>
> Resolution: Out of Date
> Assignee: Pete Muir
>
>
> This has already been fixed in release 9. Seam's parent POM needs updating
> to use version 9, not 8.
>
> > Weld parent POM uses deprecated maven APIs
> > ------------------------------------------
> >
> > Key: WELD-490
> > URL: https://jira.jboss.org/jira/browse/WELD-490
> > Project: Weld
> > Issue Type: Bug
> > Reporter: Lincoln Baxter III
> > Assignee: Pete Muir
> > Priority: Minor
> >
> > [WARNING]
> > [WARNING] Some problems were encountered while building the effective
> model for org.jboss.seam:seam-parent:pom:3.0.0-SNAPSHOT
> > [WARNING] The expression ${pom.url} is deprecated. Please use
> ${project.url} instead. @ org.jboss.seam:seam-parent:3.0.0-SNAPSHOT,
> /home/lb3/JBoss/seam3/build/parent/pom.xml
> > [WARNING] The expression ${pom.name} is deprecated. Please use ${
> project.name} instead. @ org.jboss.seam:seam-parent:3.0.0-SNAPSHOT,
> /home/lb3/JBoss/seam3/build/parent/pom.xml
> > [WARNING] The expression ${pom.organization.name} is deprecated. Please
> use ${project.organization.name} instead. @
> org.jboss.seam:seam-parent:3.0.0-SNAPSHOT,
> /home/lb3/JBoss/seam3/build/parent/pom.xml
> > [WARNING] The expression ${pom.name} is deprecated. Please use ${
> project.name} instead. @ org.jboss.seam:seam-parent:3.0.0-SNAPSHOT,
> /home/lb3/JBoss/seam3/build/parent/pom.xml
> > [WARNING] The expression ${pom.organization.name} is deprecated. Please
> use ${project.organization.name} instead. @
> org.jboss.seam:seam-parent:3.0.0-SNAPSHOT,
> /home/lb3/JBoss/seam3/build/parent/pom.xml
> > [WARNING]
> > Line 318 of weld-parent/pom.xml:
> >
> <Implementation-URL>${pom.url}</Implementation-URL>
> > <Implementation-Title>${pom.name
> }</Implementation-Title>
> >
> <Implementation-Version>${parsedVersion.osgiVersion}</Implementation-Version>
> > <Implementation-Vendor>${pom.organization.name
> }</Implementation-Vendor>
> > <Specification-Title>${pom.name
> }</Specification-Title>
> >
> <Specification-Version>${parsedVersion.osgiVersion}</Specification-Version>
> > <Specification-Vendor>${pom.organization.name
> }</Specification-Vendor>
>
> --
> 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
>
>
>
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
14 years, 1 month
Xml module and preventing bean installation
by Stuart Douglas
After some discussion with Tihomir I have added an @XmlConfigured annotation to seam-xml. This prevents the bean from being installed, so it is possible to create beans with ambiguous dependencies and allow the user to pick which one they want with XML configuration.
The problem with this is that if you want to use it you now need a compile time dependency on seam-xml just to get one annotation. Should we have a @DoNotInstall (or whatever) annotation in weld-extensions instead, or is a compile time dependency on seam-xml ok?
Tihomir has pointed out that @XmlConfigured makes it much clearer what is going on, and tells anyone reading the code to look in beans.xml, and I am inclined to agree with him, but I would like to know what everyone else thinks.
Stuart
14 years, 1 month
Loading resources from the ServletContext
by Stuart Douglas
I know there are plans to add loading resources from the ServletContext to the resource loading stuff in weld extensions, and I was wondering if anyone had any idea's as to how to implement this?
I was thinking about registering a ServletContextListener to get hold of the ServletContext. For a war deployment this could be registered automatically with a web fragment, while for an ear this will probably have to be registered manually.
The only thing I am not really sure about is where to store the references to the ServletContexts. As this is before Weld has started, I can't just stick it in an application scoped bean or similar, and storing it in a static would require weld-extensions (and thus seam-xml, and any other modules that depend upon weld-extensions) to be included in the deployment, and not in the app servers lib directory. I don't think that this is really acceptable, however I can't think of any other way off the the top of my head.
I really need this before the next release of seam-xml, as I currently can't load beans.xml from WEB-INF.
Stuart
14 years, 1 month
Problem With Entity Bean Manager Factory
by mukul.object
Hello Seam Users,
I am quite new to Jboss seam. It sounds very exciting and enthused me to
learn more about it. I am trying to do a simple POC on it.
I created a new seam application on Jboss Developer Studio 3.0. and created
an entity bean from File->New->Entity Bean. eg Test It created two .xhtml
files with save button along with two session beans. I made the connection
to the database while creating the application, so I am assuming that all
the jndi settings were taken care by the IDE.
Issue Description: On clicking the save button, I am getting below error :
entityBeanManager is not bound to the TestEntityBeanManagerFactory ! The
jdbc is giving success in ping. The jndi is also created of the application.
I am sure it might be a small issue what I am not able to make out. Kindly
help me to fix it.
Thanks in advance.
--
View this message in context: http://old.nabble.com/Problem-With-Entity-Bean-Manager-Factory-tp28203444...
Sent from the seam-dev mailing list archive at Nabble.com.
14 years, 1 month
Seam Mail Patch for 2.2.1CR2
by Cody Lerum
All-
I've created a patch for seam-mail that should fix some lingering issues
with regards to attachment handling (
https://jira.jboss.org/jira/browse/JBSEAM-4630). In the past I've pinged
Norman on these to see that they get some attention before the next seam 2.x
release but seeing that he is gone I don't know who to hit up.
I would really like to get this in before 2.2.1GA and before module work
starts for the seam 3 mail module.
Who is currently leading the 2.2.x branch?
-C
14 years, 1 month
