Brian Leathem | 1 Feb 04:46 2011
Picon

Solder log levels in glassfish 3.1

Hello all,

I'm having a tough time getting a Seam Faces application going in 
Glassfish RC1.  In the glassfish log I see:
INFO: Seam Solder 3.0.0.Beta1 (build id: 20101220-2046)
SEVERE: Exception while loading the app
SEVERE: Exception while shutting down application container
INFO: closing

where there is a long pause after the "INFO: Seam Solder".

How can I juice up the Solder logging in glassfish?  I'm assuming I put 
an entry in the glassfish logging.properties file, but the following 
line had no effect:
org.jboss.seam.solder.level=FINE

Thanks,
Brian Leathem
Shane Bryzak | 1 Feb 04:55 2011
Picon

Re: Solder log levels in glassfish 3.1

Try the Beta3 version, I believe this has been fixed.

On 01/02/11 13:46, Brian Leathem wrote:
> Hello all,
>
> I'm having a tough time getting a Seam Faces application going in
> Glassfish RC1.  In the glassfish log I see:
> INFO: Seam Solder 3.0.0.Beta1 (build id: 20101220-2046)
> SEVERE: Exception while loading the app
> SEVERE: Exception while shutting down application container
> INFO: closing
>
> where there is a long pause after the "INFO: Seam Solder".
>
> How can I juice up the Solder logging in glassfish?  I'm assuming I put
> an entry in the glassfish logging.properties file, but the following
> line had no effect:
> org.jboss.seam.solder.level=FINE
>
> Thanks,
> Brian Leathem
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

Brian Leathem | 1 Feb 05:22 2011
Picon

Re: Solder log levels in glassfish 3.1

Thanks Shane, that worked.  I'm seeing the log messages now.

Brian

On 01/31/2011 07:55 PM, Shane Bryzak wrote:
> Try the Beta3 version, I believe this has been fixed.
>
> On 01/02/11 13:46, Brian Leathem wrote:
>> Hello all,
>>
>> I'm having a tough time getting a Seam Faces application going in
>> Glassfish RC1.  In the glassfish log I see:
>> INFO: Seam Solder 3.0.0.Beta1 (build id: 20101220-2046)
>> SEVERE: Exception while loading the app
>> SEVERE: Exception while shutting down application container
>> INFO: closing
>>
>> where there is a long pause after the "INFO: Seam Solder".
>>
>> How can I juice up the Solder logging in glassfish?  I'm assuming I put
>> an entry in the glassfish logging.properties file, but the following
>> line had no effect:
>> org.jboss.seam.solder.level=FINE
>>
>> Thanks,
>> Brian Leathem
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
(Continue reading)

Lincoln Baxter, III | 1 Feb 17:00 2011
Picon

Re: Solder log levels in glassfish 3.1

Hey Brian, which file did you use to configure logging in the end?

On Mon, Jan 31, 2011 at 11:22 PM, Brian Leathem <bleathem <at> gmail.com> wrote:
Thanks Shane, that worked.  I'm seeing the log messages now.

Brian

On 01/31/2011 07:55 PM, Shane Bryzak wrote:
> Try the Beta3 version, I believe this has been fixed.
>
> On 01/02/11 13:46, Brian Leathem wrote:
>> Hello all,
>>
>> I'm having a tough time getting a Seam Faces application going in
>> Glassfish RC1.  In the glassfish log I see:
>> INFO: Seam Solder 3.0.0.Beta1 (build id: 20101220-2046)
>> SEVERE: Exception while loading the app
>> SEVERE: Exception while shutting down application container
>> INFO: closing
>>
>> where there is a long pause after the "INFO: Seam Solder".
>>
>> How can I juice up the Solder logging in glassfish?  I'm assuming I put
>> an entry in the glassfish logging.properties file, but the following
>> line had no effect:
>> org.jboss.seam.solder.level=FINE
>>
>> Thanks,
>> Brian Leathem
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev-yyZXR9kdEHCnNFVqDHBX1A@public.gmane.orgrg
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>

_______________________________________________
seam-dev mailing list
seam-dev-yyZXR9kdEHCUeimprIcsAw@public.gmane.org
https://lists.jboss.org/mailman/listinfo/seam-dev



--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
<div>
<p>Hey Brian, which file did you use to configure logging in the end?<br><br></p>
<div class="gmail_quote">On Mon, Jan 31, 2011 at 11:22 PM, Brian Leathem <span dir="ltr">&lt;<a href="mailto:bleathem@...">bleathem <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">Thanks Shane, that worked. &nbsp;I'm seeing the log messages now.<br><br>
Brian<br><div>
<div></div>
<div class="h5">
<br>
On 01/31/2011 07:55 PM, Shane Bryzak wrote:<br>
&gt; Try the Beta3 version, I believe this has been fixed.<br>
&gt;<br>
&gt; On 01/02/11 13:46, Brian Leathem wrote:<br>
&gt;&gt; Hello all,<br>
&gt;&gt;<br>
&gt;&gt; I'm having a tough time getting a Seam Faces application going in<br>
&gt;&gt; Glassfish RC1. &nbsp;In the glassfish log I see:<br>
&gt;&gt; INFO: Seam Solder 3.0.0.Beta1 (build id: 20101220-2046)<br>
&gt;&gt; SEVERE: Exception while loading the app<br>
&gt;&gt; SEVERE: Exception while shutting down application container<br>
&gt;&gt; INFO: closing<br>
&gt;&gt;<br>
&gt;&gt; where there is a long pause after the "INFO: Seam Solder".<br>
&gt;&gt;<br>
&gt;&gt; How can I juice up the Solder logging in glassfish? &nbsp;I'm assuming I put<br>
&gt;&gt; an entry in the glassfish logging.properties file, but the following<br>
&gt;&gt; line had no effect:<br>
&gt;&gt; org.jboss.seam.solder.level=FINE<br>
&gt;&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt; Brian Leathem<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; seam-dev mailing list<br>
&gt;&gt; <a href="mailto:seam-dev@...">seam-dev@...rg</a><br>
&gt;&gt; <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
&gt;<br><br>
_______________________________________________<br>
seam-dev mailing list<br><a href="mailto:seam-dev@...">seam-dev@...</a><br><a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>
</div>
Brian Leathem | 1 Feb 17:05 2011
Picon

Re: Solder log levels in glassfish 3.1

Hey Lincoln,

I configured the log levels for glassfish in the "config/logging.properties" file of the domain.  Once you've added a log level in the properties file, you can change it's level via the web interface - you just can't add them via the web.  Although it is by far quicker to just edit the file :P

Brian

On 02/01/2011 08:00 AM, Lincoln Baxter, III wrote:
Hey Brian, which file did you use to configure logging in the end?

On Mon, Jan 31, 2011 at 11:22 PM, Brian Leathem <bleathem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Thanks Shane, that worked.  I'm seeing the log messages now.

Brian

On 01/31/2011 07:55 PM, Shane Bryzak wrote:
> Try the Beta3 version, I believe this has been fixed.
>
> On 01/02/11 13:46, Brian Leathem wrote:
>> Hello all,
>>
>> I'm having a tough time getting a Seam Faces application going in
>> Glassfish RC1.  In the glassfish log I see:
>> INFO: Seam Solder 3.0.0.Beta1 (build id: 20101220-2046)
>> SEVERE: Exception while loading the app
>> SEVERE: Exception while shutting down application container
>> INFO: closing
>>
>> where there is a long pause after the "INFO: Seam Solder".
>>
>> How can I juice up the Solder logging in glassfish?  I'm assuming I put
>> an entry in the glassfish logging.properties file, but the following
>> line had no effect:
>> org.jboss.seam.solder.level=FINE
>>
>> Thanks,
>> Brian Leathem
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev-yyZXR9kdEHCUeimprIcsAw@public.gmane.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>

_______________________________________________
seam-dev mailing list
seam-dev-yyZXR9kdEHCUeimprIcsAw@public.gmane.org
https://lists.jboss.org/mailman/listinfo/seam-dev



--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"

<div>
Hey Lincoln,<br><br>
I configured the log levels for glassfish in the
"config/logging.properties" file of the domain.&nbsp; Once you've added a
log level in the properties file, you can change it's level via the web
interface - you just can't add them via the web.&nbsp; Although it is by far
quicker to just edit the file :P<br><br>
Brian<br><br>
On 02/01/2011 08:00 AM, Lincoln Baxter, III wrote:
<blockquote cite="mid:AANLkTimnQ_kyHT37aT7ctBin911siKsnSqcp0dVXwAZp@..." type="cite">Hey Brian, which file did you use to configure logging in
the end?<br><br><div class="gmail_quote">On Mon, Jan 31, 2011 at 11:22 PM, Brian
Leathem <span dir="ltr">&lt;<a moz-do-not-send="true" href="mailto:bleathem@...">bleathem@...</a>&gt;</span>
wrote:<br><blockquote class="gmail_quote">Thanks
Shane, that worked. &nbsp;I'm seeing the log messages now.<br><br>
Brian<br>
    <div>
    <div class="h5">
<br>
On 01/31/2011 07:55 PM, Shane Bryzak wrote:<br>
&gt; Try the Beta3 version, I believe this has been fixed.<br>
&gt;<br>
&gt; On 01/02/11 13:46, Brian Leathem wrote:<br>
&gt;&gt; Hello all,<br>
&gt;&gt;<br>
&gt;&gt; I'm having a tough time getting a Seam Faces application going
in<br>
&gt;&gt; Glassfish RC1. &nbsp;In the glassfish log I see:<br>
&gt;&gt; INFO: Seam Solder 3.0.0.Beta1 (build id: 20101220-2046)<br>
&gt;&gt; SEVERE: Exception while loading the app<br>
&gt;&gt; SEVERE: Exception while shutting down application container<br>
&gt;&gt; INFO: closing<br>
&gt;&gt;<br>
&gt;&gt; where there is a long pause after the "INFO: Seam Solder".<br>
&gt;&gt;<br>
&gt;&gt; How can I juice up the Solder logging in glassfish? &nbsp;I'm
assuming I put<br>
&gt;&gt; an entry in the glassfish logging.properties file, but the
following<br>
&gt;&gt; line had no effect:<br>
&gt;&gt; org.jboss.seam.solder.level=FINE<br>
&gt;&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt; Brian Leathem<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; seam-dev mailing list<br>
&gt;&gt; <a moz-do-not-send="true" href="mailto:seam-dev@...">seam-dev@...</a><br>
&gt;&gt; <a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
&gt;<br><br>
_______________________________________________<br>
seam-dev mailing list<br><a moz-do-not-send="true" href="mailto:seam-dev@...">seam-dev@...</a><br><a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div>
    </div>
  </blockquote>
  </div>
  <br><br clear="all"><br>
-- <br>
Lincoln Baxter, III<br><a moz-do-not-send="true" href="http://ocpsoft.com">http://ocpsoft.com</a><br><a moz-do-not-send="true" href="http://scrumshark.com">http://scrumshark.com</a><br>
"Keep it Simple"<br>
</blockquote>
<br>
</div>
PicketBox JBoss | 1 Feb 18:26 2011
Picon

Test Volunteers for Seam/PicketLink

Hi All,


Project PicketLink is looking for test volunteers.

Regards,
Anil
<div>
<p>Hi All,</p>
<div><br></div>
<div>Project PicketLink is looking for test volunteers.</div>
<div><a href="http://community.jboss.org/thread/162048?tstart=0">http://community.jboss.org/thread/162048?tstart=0</a></div>
<div><br></div>
<div>Regards,</div>
<div>Anil</div>
</div>
Ondřej Skutka | 3 Feb 17:09 2011
Picon

Seam 3.0.0.Beta1 testing status

Hi!

QE team has finished testing Seam 3.0.0.Beta1.

What has been tested?

  - Unit tests for each module
  - Manually test examples
    (The complex examples of Seam 3 were not tested since they were not finished)
  - Ensure that the tagged version of a module is the same as the bundled jar (diffJars)
  - Verify that all dependencies are bundled in the dist zip
  - Simple cluster failover test (seam-catch/princess-rescue)
  - Documentation spot checking
  - Search for broken links

Tests requiring a container have been tested against JBoss AS 6.0.0.Final server.

What has been found (so far)?

Total issues (currently 50) in Seam 3.0.0.Beta1 and its components:
https://issues.jboss.org/secure/IssueNavigator.jspa?requestId=12314116

1 blocker issue
29 major issues
29 minor issues
1 trivial issue

Many thanks to all community members, who have helped testing the release!

Ondra
Shane Bryzak | 3 Feb 22:59 2011
Picon

Seam 3.0.0.Beta2

Hey guys,

It's crunch time!

I'm planning on releasing Seam 3 beta 2 on the 11th February, which is 
one week from today.  The QA team has been extremely busy testing beta 
1, and have identified a substantial number of issues.  It would be 
great if everyone could review the issues for their own module in JIRA 
and have them addressed by 10 February.  Ideally, I would like to see 
some of the modules enter CR by that date, as our Seam 3 CR1 release 
date is due for release on 25 February.  If you are waiting on something 
(such as another module release, or for some action by another person) 
please speak up now and I will assist with coordination.  If you need 
help with releasing your own module, please let me know and I'll do it 
for you.

Something that Dan also mentioned recently was code coverage goals.  Our 
ultimate goal is to achieve 70% code coverage for unit tests within each 
module - currently the QA guys are busy setting up code coverage for 
each of the module builds.  Shortly I'll begin publishing code coverage 
figures on seam-dev, so we can identify which modules may require 
assistance with writing tests (don't worry, I'll win the prize for 
least-covered module as I haven't even started writing tests for the 
security module yet).  We don't have any firm goals for code coverage 
for the beta 2 release, however for the CR1 release the goal is for 40% 
coverage, with 70% being the goal for the final release.

I'd also like to thank everyone for their hard work on Seam 3.  It's 
been such a huge effort to get this far, considering that we had to 
start from scratch for a lot of the features that existed in Seam 2.  As 
we make the final push towards the final release, I just wanted to let 
everyone know that their efforts are definitely appreciated, and 
together I'm sure that we can release a top quality project that really 
makes a big difference to the Java EE landscape.

Thanks,
Shane
Jordan Ganoff | 4 Feb 02:33 2011
Picon

Seam JMS Alpha 2 Incoming...

Shane, Dan, et al,


The list of issues slated for Seam JMS Alpha 2 [1] are nearly completion. I'd like to be able to release Alpha 2 early next week and, provided the API is complete at that point, release a beta shortly after. I'll need help pushing out the release so I don't end up spending hours on it so here's your fair warning! ;)

Again, anyone interested in helping out is more than welcome. We could use some help in nearly all areas but specifically creating an example or two. I plan on updating the doc before any release is made.

Best Regards,
Jordan


--
Jordan Ganoff
<div>
<p>Shane, Dan, et al,</p>
<div><br></div>
<div>The list of issues slated for Seam JMS Alpha 2 [1] are nearly completion. I'd like to be able to release Alpha 2 early next week and, provided the API is complete at that point, release a beta shortly after. I'll need help pushing out the release so I don't end up spending hours on it so here's your fair warning! ;)</div>
<div><br></div>
<div>Again, anyone interested in helping out is more than welcome. We could use some help in nearly all areas but specifically creating an example or two. I plan on updating the doc before any release is made.</div>
<div><br></div>
<div>Best Regards,</div>
<div>Jordan</div>
<div><br></div>
<div>[1]:&nbsp;<a href="https://issues.jboss.org/browse/SEAMJMS/fixforversion/12315281">https://issues.jboss.org/browse/SEAMJMS/fixforversion/12315281</a>
</div>
<div>
<br>-- <br>Jordan Ganoff<br>
</div>
</div>
Dan Allen | 4 Feb 02:34 2011
Picon

later time for community meeting?

I'm hearing from several community members that the current community meeting time falls in between things...specifically travel on the US east coast.


I have three proposals. If you regularly attend the meeting, or you haven't been because of conflicts, please chime in w/ your vote.

1. Stay the same - 22:00:00 UTC every Thursday (Friday in Australia)

2. Shifting forward by two hours - 00:00:00 UTC every Thursday (Friday in Europe and Australia)

3. Moving to Wednesday and back 1 hour - 21:00:00 UTC every Wednesday (Thursday in Australia)

I know, someone always gets the short straw. Let's raise our glass in the name of diversity :)

-Dan

--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597


<div>
<p>I'm hearing from several community members that the current community meeting time falls in between things...specifically travel on the US east coast.</p>
<div><br></div>
<div>I have three proposals. If you regularly attend the meeting, or you haven't been because of conflicts, please chime in w/ your vote.</div>

<div><br></div>
<div>1. Stay the same - 22:00:00 UTC every Thursday (Friday in Australia)</div>
<div>
<a href="http://www.timeanddate.com/worldclock/fixedtime.html?day=13&amp;month=1&amp;year=2011&amp;hour=22&amp;min=00&amp;sec=0&amp;p1=90">http://www.timeanddate.com/worldclock/fixedtime.html?day=13&amp;month=1&amp;year=2011&amp;hour=22&amp;min=00&amp;sec=0&amp;p1=90</a> (sample times)</div>

<div><br></div>
<div>2. Shifting forward by two hours - 00:00:00 UTC every Thursday (Friday in Europe and&nbsp;Australia)</div>
<div>
<a href="http://www.timeanddate.com/worldclock/fixedtime.html?day=14&amp;month=1&amp;year=2011&amp;hour=0&amp;min=00&amp;sec=0&amp;p1=90">http://www.timeanddate.com/worldclock/fixedtime.html?day=14&amp;month=1&amp;year=2011&amp;hour=0&amp;min=00&amp;sec=0&amp;p1=90</a> (sample times)</div>

<div><br></div>
<div>3. Moving to Wednesday and back 1 hour - 21:00:00 UTC every Wednesday (Thursday in Australia)</div>
<div>
<a href="http://www.timeanddate.com/worldclock/fixedtime.html?day=12&amp;month=1&amp;year=2011&amp;hour=21&amp;min=00&amp;sec=0&amp;p1=90">http://www.timeanddate.com/worldclock/fixedtime.html?day=12&amp;month=1&amp;year=2011&amp;hour=21&amp;min=00&amp;sec=0&amp;p1=90</a> (sample times)</div>

<div><br></div>
<div>I know, someone always gets the short straw. Let's raise our glass in the name of diversity :)</div>
<div><br></div>
<div><div><div>-Dan<br clear="all"><br>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>

Registered Linux User #231597<br><br><div>
<a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
</div>
<br>
</div></div></div>
</div>

Gmane