Suppressing parameter inclusion for s:link
by Shane Bryzak
A couple of our more vocal users have been pushing for JBSEAM-3609 and
JBSEAM-2310 to be fixed, and while the issue is legitimate Pete and I
couldn't arrive at a definite conclusion as to how to correctly address
it. To summarise the problem, when a user has a page with a menu
containing a lot of links (each using s:link), each of the page
parameters defined in pages.xml for the views referenced in the links
cause instantiation of whatever Seam component is configured in the
parameter value. The main problem with this is the performance hit from
having to create so many components just to render the links.
We identified two possible solutions - either introduce an attributes in
pages.xml which when set to true suppresses the parameter values from
being rendered, or introduce an additional attribute in s:link and
s:button which does a similar thing for that link only. The advantage
of controlling it in the view is that it offers more flexibility, being
that you can choose when to include or exclude the parameter values.
However, the real question is which would be the more semantically
correct place to control it. Does anyone have any opinion either way
about this?
16 years, 3 months
Re: JBoss Wicket Seam Project
by Pete Muir
We currently use Docbook 4.3.
On 23 Oct 2008, at 06:12, Jarrod Folino wrote:
> Is it fair to assume that this is for the 4.5 version?
>
> On Wed, Oct 22, 2008 at 10:29 PM, Pete Muir <pete.muir(a)jboss.org>
> wrote:
> Hi Jarrod
>
> I recently wrote a couple of tutorials at http://in.relation.to on
> Wicket and Seam - a good starting point would be to convert these
> into documentation/docbook markup :-)
>
> Pete
>
> On 22 Oct 2008, at 12:18, Jarrod Folino wrote:
>
>> Dear Peter,
>>
>>
>> I am an J2EE developer and a big fan of Wicket and component based
>> frameworks. I wish to offer my assistance in Documenting the Wicket/
>> Seam integration, namely JBSEAM-2993.
>>
>> I am more than happy to review any current documentation that you
>> may have or to help develop new documentation and/or examples.
>> Could you please give some more advice how I could be of any
>> assistance to the documentation effort or even the Wicket/Seam
>> project in general?
>>
>> Hope to hear from you soon,
>>
>> Jarrod Folino
>
>
16 years, 3 months
Re: Seam 2.1.0.GA testing on AS 5 CR2 status
by Pete Muir
On 19 Oct 2008, at 01:05, Jay Balunas wrote:
> I wanted to provide a status on the testing of Seam 2.1.0.GA on AS 5
> CR2. I believe these issues are a mixture of Seam and AS 5 issues.
> Please review and let me know what you think.
>
> I have a couple of examples and seam-gen testing to complete. I
> will also be doing a spot check on windows, and with jdk5.
>
> Thanks,
> Jay
>
> So far I have tested only with JDK6 on Fedora 8. I can provide
> additional details for most of these if needed.
>
> * Blog example
> - When I deploy the blog example I get the exception below.
> - "Caused by: org.hibernate.cache.NoCachingEnabledException: Second-
> level cache is not enabled for usage
> [hibernate.cache.use_second_level_cache |
> hibernate.cache.use_query_cache]"
> - Made several changes that I reviewed with Pete, Norman.
> - Still getting this issue with these changes.
> - Waiting to hear from Stan on this.
> - Should this be a JBAS or JBSEAM jira?
Report this in JBSEAM for now, I will investigate.
>
>
> * GroovyBooking example
> - JBSEAM-3579
> - Getting the sql error below. Jozef also saw this with Seam
> 2.0.3.CR2 on AS 5 CR2
> - Caused by: java.sql.SQLException: Violation of unique constraint
> SYS_PK_49: duplicate value(s) for column(s) $$
> - during import.sql import
Are you sure you have a clean data dir?
>
>
> * JPA/Hiberante example are showing a ZipException on jboss-seam-
> ui.jar
> - Entered JBAS-6107
> - Original issue JBAS-6076
> - Ales said that this should be fixed in trunk
>
> * Wicket undeploy exceptions
> - When undeploying the wicket example I see the following exceptions:
> - I will enter a jira - although I am not sure if this is Seam or
> AS related?
> Caused by: java.io.IOException: Child not found jboss-seam-wicket-
> booking.ear/lib/wicket.jar/org/apache/wicket/Application.properties
> for FileHandler@21707409[path context=file:/jboss/projects/seam/
> 2.1.0.GA/jboss-5.0.0.CR2/server/default/deploy/ real=file:/jboss/
> projects/seam/2.1.0.GA/jboss-5.0.0.CR2/server/default/deploy/]
> at org.jboss.virtual.VFS.findChild(VFS.java:211)
> at
> org
> .jboss
> .virtual
> .plugins
> .vfs
> .VirtualFileURLConnection
> .resolveCachedVirtualFile(VirtualFileURLConnection.java:122)
> at
> org
> .jboss
> .virtual
> .plugins
> .vfs
> .VirtualFileURLConnection
> .getVirtualFile(VirtualFileURLConnection.java:144)
> at
> org
> .jboss
> .virtual
> .plugins
> .vfs
> .VirtualFileURLConnection
> .getLastModified(VirtualFileURLConnection.java:89)
> ... 4 more
Please report in JBAS, with instructions to reproduce. Assign to Ales
I think.
> * Spring example deployment exception
> - See spring_deploy_error.txt for listing
> - Persistence.xml is using "RESOURCE_LOCAL" and not define any data
> source
> - this works fine on other jboss versions.
Report in JBSEAM, assign to Mike Youngstrom
> * SeamSpace example
> - I believe two separate issues found
> - 1) If you click on "create user" or "create role" twice you get
> the following exception:
> - IllegalStateException: begin method invoked from a long-running
> conversation, try using @Begin(join=true) on method: createRole
> - 2) When adjusting security settings either on images, or users/
> roles the tables are empty
> - The application still functions as it should so this is
> probably an issue with view not the data
>
> * itext example
> - When you attempt to access the example you see a 404 not found
> page.
> - This may be fixed by the changes that Pete did for AS 5 -
> JBSEAM-3575
> - This may also be related to hotdeploy changes in Seam - need to
> wait for new tag to test
> - See the attached itext_error.txt for output.
Just try AS5 trunk, Ales upgraded to the seam-int which contains the
fix.
> * Can't deploy 2 Seam Applications
> - javax.management.InstanceAlreadyExistsException:
> jboss.j2ee:jar=jboss-seam.jar,service=EJB3 already registered.
> - See full stack trace in 2_seam_app.txt
> - I believe we have seen this, but I was not able to find the jira
Stan assigned this to Carlo
>
>
> Minor or Known issues:
> ----------------------
>
> * EntityManagerFactory Issue with AS 5 CR1 effects several examples
> - dvdstore, contactlist, quartz, others...
> - Followed workaround here
> - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142385&start=-10
> - Also needed to add the following to the persistence.xml
> -<property name="hibernate.transaction.manager_lookup_class"
> value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
> - I believe this is a side effect of the workaround
>
> * "Welcome to Seam null" shows in nearly every example when
> deployed. I have also seen "Welcome to Seam 5.0.0.CR2" in cases.
> - Adrian fixed this for AS 5 GA
>
> * Excessive logging for every request of seam - JBSEAM-3575 entered
> 14:51:54,551 INFO [Initialization] Installing components...
> 14:51:54,551 INFO [Initialization] done redeploying
> 14:51:55,293 INFO [Initialization] redeploying
> - Pete fixed this in AS 5 trunk and should be in AS 5 GA
>
> * Paths/links in the booking examples popup details are out of date.
> - Will report but this is minor
>
> <2_seam_app.txt><itext_error.txt><wicket_undeploy_errortxt>
16 years, 3 months
Seam 2.1 issues in Tools
by Max Rydahl Andersen
Hi,
Walking through jira issues for JBT 3 beta1 and I just stumbled into
https://jira.jboss.org/jira/browse/JBIDE-2702 which is caused by
<security:rule-based-permission-resolver
security-rules="#{securityRules}"/>
now being in components.xml by default.
That is for some reason failing for us - probably we are missing a drools
jar or something ;)
Before I start finding these changes in 2.1 that might break current tools
behavior the hard way,
do you guys got a list of major 2.1 changes that changes lib
dependencies/startup sequence etc. ?
--
/max
16 years, 3 months
Seam 2.1.0.GA testing on windows
by Jay Balunas
Testing status for Seam 2.1.0.GA testing on windows XP.
JDK 6, AS 5 CR2
----------------------------
itext - good
drools - good
seam-gen ear
- amazingly slow
- part of it was ajax4jsf logging below (but not all of it - need to get
this changed to trace).
org.ajax4jsf.io.parser.FastHtmlParser] (http-127.0.0.1-8080-1) Parser
reached state is StateManager.DOCTYPE
JDK 5, AS 5 CR2
---------------------------
booking - good
excel - good
seam-gen war - failed with war deployment error.
testsuite - 1 fail - testPayMultiple
- java.lang.AssertionError
at
org.jboss.seam.example.seampay.test.PaymentProcessorTest.testPayMultiple(PaymentProcessorTest.java:71)
--
blog: http://in.relation.to/Bloggers/Jay
16 years, 3 months
Updated Seam 2.1.0.GA examples status on AS 5
by Jay Balunas
Seam 2.1.0.GA examples on AS 5
------------------------------
Below is a listing of the Seam examples and how they work with AS 5. Some
will work fine with AS 5 CR2, some require the latest trunk build (until GA
is released), and other do not currently work with AS 5.
AS 5 CR2 +
------------
- booking
- drools
- excel
- icefaces
- itext
- JBSEAM-3593 minor issue
- JBSEAM-3472 swing doc error
- JBSEAM-3470 jchart html page errors
- mail
- messages
- numberguess
- nestedbooking
- registration
- remoting/gwt
- remoting/helloworld
- remoting/progressbar
- todo
- rss
- wicket
- JBAS-6117 - example functions, but errors on undeploy
AS 5 trunk
----------
- remoting/chatroom
Examples that do not fuction on AS 5
-------------------------------------
- blog
- JBSEAM-3586 caching error
- groovybooking
- JBSEAM-3579
- hibernate & jpa examples
- JBAS-6076, JBAS-6107
- seamspace
- JBSEAM-3589
- JBSEAM-3588
- spring
- JBSEAM-3587
- SMPC not working due to EJBTHREE-1526"
- contactlist
- dvdstore
- quartz
- seambay
- seamdiscs
- seampay
- ui
- seam-gen
--
blog: http://in.relation.to/Bloggers/Jay
16 years, 3 months
Switching to a requirement-orientated deployment system
by Pete Muir
I just committed some queued changes I had to switch us from a
resource orientated (inspect each scanned file/class; each file/class
gets passed to each deployer which can do what it wants with it) to
requirement orientated (expose requirements and the scanner hands a
list of matching files/classes to the deployer). This is good because
it allows us to delegate resource/class discovery to the container
(JBoss 5).
I've tested all the deployers I know about (including the wiki), and
the testsuite passes; however there may be bugs, please assign them to
me in JIRA if they come up.
So, this requires us to produce a stable SPI for exposing these
requirements; so far it's pretty simple, you can require files that
have a certain suffix (e.g. .jpdl.xml) or classes with any of the
specified annotations. If you need to further processing, you can call
the postProcess() hook to further trim down the list. If anyone would
like to add extra requirements, then we need to do that before
2.1.1.GA, so please raise issues in JIRA.
You can find all this in trunk, inside org.jboss.seam.deployment, some
of it javadoc'd ;-)
Ales, I added SeamResourceDiscovery for you to jboss-seam-int as an
example of how to get requirements from seam, and how to set back the
discovered classes/files.
16 years, 3 months
Returned mail: Data format error
by MAILER-DAEMON
The original message was received at Wed, 22 Oct 2008 15:19:53 +0200 from lists.jboss.org [207.2.80.209]
----- The following addresses had permanent fatal errors -----
<seam-dev(a)lists.jboss.org>
----- Transcript of the session follows -----
... while talking to 221.48.167.107:
>>> RCPT To:<seam-dev(a)lists.jboss.org>
<<< 550 5.1.1 <seam-dev(a)lists.jboss.org>... User unknown
16 years, 3 months
Re: JBoss Wicket Seam Project
by Pete Muir
Hi Jarrod
I recently wrote a couple of tutorials at http://in.relation.to on
Wicket and Seam - a good starting point would be to convert these into
documentation/docbook markup :-)
Pete
On 22 Oct 2008, at 12:18, Jarrod Folino wrote:
> Dear Peter,
>
>
> I am an J2EE developer and a big fan of Wicket and component based
> frameworks. I wish to offer my assistance in Documenting the Wicket/
> Seam integration, namely JBSEAM-2993.
>
> I am more than happy to review any current documentation that you
> may have or to help develop new documentation and/or examples. Could
> you please give some more advice how I could be of any assistance to
> the documentation effort or even the Wicket/Seam project in general?
>
> Hope to hear from you soon,
>
> Jarrod Folino
16 years, 3 months