You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by ejc <er...@gmail.com> on 2011/01/14 17:05:24 UTC
Broken java client link on main site
I'm not exactly sure who to send this to, and I can't edit the page myself, but
http://esme.apache.org
The Java client link at http://esme.apache.org/#Index-Clients points to:
http://svn.apache.org/viewvc/incubator/esme/trunk/esme-java-client/
which is broken, it should be:
http://svn.apache.org/viewvc/esme/trunk/esme-java-client/
Thanks,
Eric
Re: Broken java client link on main site
Posted by Richard Hirsch <hi...@gmail.com>.
Thanks.
I've updated the JIRA ticket.
D.
On Wed, Jan 19, 2011 at 3:52 PM, ejc <er...@gmail.com> wrote:
> On Wed, Jan 19, 2011 at 8:39 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> You are right - that is the same issue. We forgot to create a ticket
>> for lift, so the problem was never corrected.
>>
>> Could you create a ticket in lift for this issue? This will solve the
>> problem in the long-term. A short-term solution is probably to
>> reinsert the character strings.
>>
>
> Done
>
> https://www.assembla.com/spaces/liftweb/tickets/855-non-scoped-localized-strings
>
> Thanks,
> Eric
>
>> On Wed, Jan 19, 2011 at 3:34 PM, ejc <er...@gmail.com> wrote:
>>> Does the e-mail thread I referenced relate to this? If so, I don't
>>> see that anyone submitted a
>>> ticket for lift, as David suggested, but the S.? in that case was removed.
>>>
>>> Thanks,
>>> Eric
>>>
>>>
>>> On Wed, Jan 19, 2011 at 6:53 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> I just had a quick look at the Sendmail problem:
>>>>
>>>> The problem is here:
>>>>
>>>> Mailer.sendMail(From(S.?("custom_mail_from_adress")),
>>>> Subject(S.?("custom_mail_subject")),
>>>> To(who), body)
>>>>
>>>> I've updated the Jira issue accordingly.
>>>>
>>>> The easiest solution would be to put the strings back in. But it would
>>>> be better to find a way to allow the user configure these values via
>>>> property file.
>>>>
>>>> D.
>>>>
>>>>
>>>>
>>>> On Wed, Jan 19, 2011 at 1:37 PM, ejc <er...@gmail.com> wrote:
>>>>> I can at least do some more research to pinpoint the problems. If
>>>>> anyone else says "oh I know that answer" feel free to jump in,
>>>>> otherwise I'll take them.
>>>>>
>>>>> Thanks,
>>>>> Eric
>>>>>
>>>>> On Wednesday, January 19, 2011, Ethan Jewett <es...@gmail.com> wrote:
>>>>>> Thanks a lot! I've put these both in the "Backlog" for now, but if we
>>>>>> can get them fixed for the 1.2 release then I think we'll all agree to
>>>>>> include them.
>>>>>>
>>>>>> Are you planning on looking into the problem more or are these open
>>>>>> for someone else to work on?
>>>>>>
>>>>>> Ethan
>>>>>>
>>>>>> On Tue, Jan 18, 2011 at 7:22 PM, ejc <er...@gmail.com> wrote:
>>>>>>> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>> These both look like bugs. Thanks for the effort on your
>>>>>>>> investigations. Would you be able to create Jira issues at
>>>>>>>> https://issues.apache.org/jira/browse/ESME ?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Ethan
>>>>>>>
>>>>>>> Sure thing
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/ESME-324 -- login message
>>>>>>> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Eric
>>>>>>>
>>>>>>>
>>>>>>>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>>>>>>>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>>>>>>>>> I now have actions working on my installation. There were a couple of
>>>>>>>>>>> things I ran into.
>>>>>>>>>>> The login message doesn't seem to be generated unless I log in via
>>>>>>>>>>> openID, hence my
>>>>>>>>>>> confusion about login messages.
>>>>>>>>>>
>>>>>>>>>> Try and login as a normal user and then set the open-id url via the
>>>>>>>>>> user profile.
>>>>>>>>>
>>>>>>>>> It is set, and login via open-id works fine and generates the login
>>>>>>>>> message. Logging
>>>>>>>>> in via username/password works, but doesn't generate login message. I don't see
>>>>>>>>> any errors, just no login message.
>>>>>>>>>
>>>>>>>>>> The mailto: action doesn't appear to
>>>>>>>>>>> work, either on
>>>>>>>>>>> stax, or locally. I plan to debug this today. I probably have
>>>>>>>>>>> something mis-configured.
>>>>>>>>>>
>>>>>>>>>> Haven't tried that in a while. I just looked at the stax log and I
>>>>>>>>>> didn't find any exceptions.
>>>>>>>>>>
>>>>>>>>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>>>>>>>>
>>>>>>>>> Yes, I've noticed it will not accept incorrect syntax (including a
>>>>>>>>> space between : and email address)
>>>>>>>>> I get the following when I try a mailto: action. This is running from sbt:
>>>>>>>>>
>>>>>>>>> ERROR - Actor threw an exception
>>>>>>>>> java.lang.IllegalStateException: Attempted to use resource bundles
>>>>>>>>> outside of an initialized S scope. S only usable when initialized,
>>>>>>>>> such as during request processing. Did you call S.? from Boot?
>>>>>>>>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>>>>>>>>> at net.liftweb.http.S$.$qmark(S.scala:748)
>>>>>>>>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>>>>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>>>>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>>>>>>>>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>>>>>>>>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>>>>>>>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>>>>>>>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftA
>>>>>
>>>>
>>>
>>
>
Re: Broken java client link on main site
Posted by Richard Hirsch <hi...@gmail.com>.
LOL
You were faster - I'm deleting my JIRA comment.
On Wed, Jan 19, 2011 at 3:52 PM, ejc <er...@gmail.com> wrote:
> On Wed, Jan 19, 2011 at 8:39 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> You are right - that is the same issue. We forgot to create a ticket
>> for lift, so the problem was never corrected.
>>
>> Could you create a ticket in lift for this issue? This will solve the
>> problem in the long-term. A short-term solution is probably to
>> reinsert the character strings.
>>
>
> Done
>
> https://www.assembla.com/spaces/liftweb/tickets/855-non-scoped-localized-strings
>
> Thanks,
> Eric
>
>> On Wed, Jan 19, 2011 at 3:34 PM, ejc <er...@gmail.com> wrote:
>>> Does the e-mail thread I referenced relate to this? If so, I don't
>>> see that anyone submitted a
>>> ticket for lift, as David suggested, but the S.? in that case was removed.
>>>
>>> Thanks,
>>> Eric
>>>
>>>
>>> On Wed, Jan 19, 2011 at 6:53 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> I just had a quick look at the Sendmail problem:
>>>>
>>>> The problem is here:
>>>>
>>>> Mailer.sendMail(From(S.?("custom_mail_from_adress")),
>>>> Subject(S.?("custom_mail_subject")),
>>>> To(who), body)
>>>>
>>>> I've updated the Jira issue accordingly.
>>>>
>>>> The easiest solution would be to put the strings back in. But it would
>>>> be better to find a way to allow the user configure these values via
>>>> property file.
>>>>
>>>> D.
>>>>
>>>>
>>>>
>>>> On Wed, Jan 19, 2011 at 1:37 PM, ejc <er...@gmail.com> wrote:
>>>>> I can at least do some more research to pinpoint the problems. If
>>>>> anyone else says "oh I know that answer" feel free to jump in,
>>>>> otherwise I'll take them.
>>>>>
>>>>> Thanks,
>>>>> Eric
>>>>>
>>>>> On Wednesday, January 19, 2011, Ethan Jewett <es...@gmail.com> wrote:
>>>>>> Thanks a lot! I've put these both in the "Backlog" for now, but if we
>>>>>> can get them fixed for the 1.2 release then I think we'll all agree to
>>>>>> include them.
>>>>>>
>>>>>> Are you planning on looking into the problem more or are these open
>>>>>> for someone else to work on?
>>>>>>
>>>>>> Ethan
>>>>>>
>>>>>> On Tue, Jan 18, 2011 at 7:22 PM, ejc <er...@gmail.com> wrote:
>>>>>>> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>> These both look like bugs. Thanks for the effort on your
>>>>>>>> investigations. Would you be able to create Jira issues at
>>>>>>>> https://issues.apache.org/jira/browse/ESME ?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Ethan
>>>>>>>
>>>>>>> Sure thing
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/ESME-324 -- login message
>>>>>>> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Eric
>>>>>>>
>>>>>>>
>>>>>>>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>>>>>>>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>>>>>>>>> I now have actions working on my installation. There were a couple of
>>>>>>>>>>> things I ran into.
>>>>>>>>>>> The login message doesn't seem to be generated unless I log in via
>>>>>>>>>>> openID, hence my
>>>>>>>>>>> confusion about login messages.
>>>>>>>>>>
>>>>>>>>>> Try and login as a normal user and then set the open-id url via the
>>>>>>>>>> user profile.
>>>>>>>>>
>>>>>>>>> It is set, and login via open-id works fine and generates the login
>>>>>>>>> message. Logging
>>>>>>>>> in via username/password works, but doesn't generate login message. I don't see
>>>>>>>>> any errors, just no login message.
>>>>>>>>>
>>>>>>>>>> The mailto: action doesn't appear to
>>>>>>>>>>> work, either on
>>>>>>>>>>> stax, or locally. I plan to debug this today. I probably have
>>>>>>>>>>> something mis-configured.
>>>>>>>>>>
>>>>>>>>>> Haven't tried that in a while. I just looked at the stax log and I
>>>>>>>>>> didn't find any exceptions.
>>>>>>>>>>
>>>>>>>>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>>>>>>>>
>>>>>>>>> Yes, I've noticed it will not accept incorrect syntax (including a
>>>>>>>>> space between : and email address)
>>>>>>>>> I get the following when I try a mailto: action. This is running from sbt:
>>>>>>>>>
>>>>>>>>> ERROR - Actor threw an exception
>>>>>>>>> java.lang.IllegalStateException: Attempted to use resource bundles
>>>>>>>>> outside of an initialized S scope. S only usable when initialized,
>>>>>>>>> such as during request processing. Did you call S.? from Boot?
>>>>>>>>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>>>>>>>>> at net.liftweb.http.S$.$qmark(S.scala:748)
>>>>>>>>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>>>>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>>>>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>>>>>>>>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>>>>>>>>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>>>>>>>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>>>>>>>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftA
>>>>>
>>>>
>>>
>>
>
Re: Broken java client link on main site
Posted by ejc <er...@gmail.com>.
On Wed, Jan 19, 2011 at 8:39 AM, Richard Hirsch <hi...@gmail.com> wrote:
> You are right - that is the same issue. We forgot to create a ticket
> for lift, so the problem was never corrected.
>
> Could you create a ticket in lift for this issue? This will solve the
> problem in the long-term. A short-term solution is probably to
> reinsert the character strings.
>
Done
https://www.assembla.com/spaces/liftweb/tickets/855-non-scoped-localized-strings
Thanks,
Eric
> On Wed, Jan 19, 2011 at 3:34 PM, ejc <er...@gmail.com> wrote:
>> Does the e-mail thread I referenced relate to this? If so, I don't
>> see that anyone submitted a
>> ticket for lift, as David suggested, but the S.? in that case was removed.
>>
>> Thanks,
>> Eric
>>
>>
>> On Wed, Jan 19, 2011 at 6:53 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>> I just had a quick look at the Sendmail problem:
>>>
>>> The problem is here:
>>>
>>> Mailer.sendMail(From(S.?("custom_mail_from_adress")),
>>> Subject(S.?("custom_mail_subject")),
>>> To(who), body)
>>>
>>> I've updated the Jira issue accordingly.
>>>
>>> The easiest solution would be to put the strings back in. But it would
>>> be better to find a way to allow the user configure these values via
>>> property file.
>>>
>>> D.
>>>
>>>
>>>
>>> On Wed, Jan 19, 2011 at 1:37 PM, ejc <er...@gmail.com> wrote:
>>>> I can at least do some more research to pinpoint the problems. If
>>>> anyone else says "oh I know that answer" feel free to jump in,
>>>> otherwise I'll take them.
>>>>
>>>> Thanks,
>>>> Eric
>>>>
>>>> On Wednesday, January 19, 2011, Ethan Jewett <es...@gmail.com> wrote:
>>>>> Thanks a lot! I've put these both in the "Backlog" for now, but if we
>>>>> can get them fixed for the 1.2 release then I think we'll all agree to
>>>>> include them.
>>>>>
>>>>> Are you planning on looking into the problem more or are these open
>>>>> for someone else to work on?
>>>>>
>>>>> Ethan
>>>>>
>>>>> On Tue, Jan 18, 2011 at 7:22 PM, ejc <er...@gmail.com> wrote:
>>>>>> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>> These both look like bugs. Thanks for the effort on your
>>>>>>> investigations. Would you be able to create Jira issues at
>>>>>>> https://issues.apache.org/jira/browse/ESME ?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ethan
>>>>>>
>>>>>> Sure thing
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/ESME-324 -- login message
>>>>>> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
>>>>>>
>>>>>> Thanks,
>>>>>> Eric
>>>>>>
>>>>>>
>>>>>>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>>>>>>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>>>>>>>> I now have actions working on my installation. There were a couple of
>>>>>>>>>> things I ran into.
>>>>>>>>>> The login message doesn't seem to be generated unless I log in via
>>>>>>>>>> openID, hence my
>>>>>>>>>> confusion about login messages.
>>>>>>>>>
>>>>>>>>> Try and login as a normal user and then set the open-id url via the
>>>>>>>>> user profile.
>>>>>>>>
>>>>>>>> It is set, and login via open-id works fine and generates the login
>>>>>>>> message. Logging
>>>>>>>> in via username/password works, but doesn't generate login message. I don't see
>>>>>>>> any errors, just no login message.
>>>>>>>>
>>>>>>>>> The mailto: action doesn't appear to
>>>>>>>>>> work, either on
>>>>>>>>>> stax, or locally. I plan to debug this today. I probably have
>>>>>>>>>> something mis-configured.
>>>>>>>>>
>>>>>>>>> Haven't tried that in a while. I just looked at the stax log and I
>>>>>>>>> didn't find any exceptions.
>>>>>>>>>
>>>>>>>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>>>>>>>
>>>>>>>> Yes, I've noticed it will not accept incorrect syntax (including a
>>>>>>>> space between : and email address)
>>>>>>>> I get the following when I try a mailto: action. This is running from sbt:
>>>>>>>>
>>>>>>>> ERROR - Actor threw an exception
>>>>>>>> java.lang.IllegalStateException: Attempted to use resource bundles
>>>>>>>> outside of an initialized S scope. S only usable when initialized,
>>>>>>>> such as during request processing. Did you call S.? from Boot?
>>>>>>>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>>>>>>>> at net.liftweb.http.S$.$qmark(S.scala:748)
>>>>>>>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>>>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>>>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>>>>>>>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>>>>>>>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>>>>>>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>>>>>>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftA
>>>>
>>>
>>
>
Re: Broken java client link on main site
Posted by Richard Hirsch <hi...@gmail.com>.
You are right - that is the same issue. We forgot to create a ticket
for lift, so the problem was never corrected.
Could you create a ticket in lift for this issue? This will solve the
problem in the long-term. A short-term solution is probably to
reinsert the character strings.
D.
On Wed, Jan 19, 2011 at 3:34 PM, ejc <er...@gmail.com> wrote:
> Does the e-mail thread I referenced relate to this? If so, I don't
> see that anyone submitted a
> ticket for lift, as David suggested, but the S.? in that case was removed.
>
> Thanks,
> Eric
>
>
> On Wed, Jan 19, 2011 at 6:53 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> I just had a quick look at the Sendmail problem:
>>
>> The problem is here:
>>
>> Mailer.sendMail(From(S.?("custom_mail_from_adress")),
>> Subject(S.?("custom_mail_subject")),
>> To(who), body)
>>
>> I've updated the Jira issue accordingly.
>>
>> The easiest solution would be to put the strings back in. But it would
>> be better to find a way to allow the user configure these values via
>> property file.
>>
>> D.
>>
>>
>>
>> On Wed, Jan 19, 2011 at 1:37 PM, ejc <er...@gmail.com> wrote:
>>> I can at least do some more research to pinpoint the problems. If
>>> anyone else says "oh I know that answer" feel free to jump in,
>>> otherwise I'll take them.
>>>
>>> Thanks,
>>> Eric
>>>
>>> On Wednesday, January 19, 2011, Ethan Jewett <es...@gmail.com> wrote:
>>>> Thanks a lot! I've put these both in the "Backlog" for now, but if we
>>>> can get them fixed for the 1.2 release then I think we'll all agree to
>>>> include them.
>>>>
>>>> Are you planning on looking into the problem more or are these open
>>>> for someone else to work on?
>>>>
>>>> Ethan
>>>>
>>>> On Tue, Jan 18, 2011 at 7:22 PM, ejc <er...@gmail.com> wrote:
>>>>> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>> Hi Eric,
>>>>>>
>>>>>> These both look like bugs. Thanks for the effort on your
>>>>>> investigations. Would you be able to create Jira issues at
>>>>>> https://issues.apache.org/jira/browse/ESME ?
>>>>>>
>>>>>> Thanks,
>>>>>> Ethan
>>>>>
>>>>> Sure thing
>>>>>
>>>>> https://issues.apache.org/jira/browse/ESME-324 -- login message
>>>>> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
>>>>>
>>>>> Thanks,
>>>>> Eric
>>>>>
>>>>>
>>>>>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>>>>>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>>>>>>> I now have actions working on my installation. There were a couple of
>>>>>>>>> things I ran into.
>>>>>>>>> The login message doesn't seem to be generated unless I log in via
>>>>>>>>> openID, hence my
>>>>>>>>> confusion about login messages.
>>>>>>>>
>>>>>>>> Try and login as a normal user and then set the open-id url via the
>>>>>>>> user profile.
>>>>>>>
>>>>>>> It is set, and login via open-id works fine and generates the login
>>>>>>> message. Logging
>>>>>>> in via username/password works, but doesn't generate login message. I don't see
>>>>>>> any errors, just no login message.
>>>>>>>
>>>>>>>> The mailto: action doesn't appear to
>>>>>>>>> work, either on
>>>>>>>>> stax, or locally. I plan to debug this today. I probably have
>>>>>>>>> something mis-configured.
>>>>>>>>
>>>>>>>> Haven't tried that in a while. I just looked at the stax log and I
>>>>>>>> didn't find any exceptions.
>>>>>>>>
>>>>>>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>>>>>>
>>>>>>> Yes, I've noticed it will not accept incorrect syntax (including a
>>>>>>> space between : and email address)
>>>>>>> I get the following when I try a mailto: action. This is running from sbt:
>>>>>>>
>>>>>>> ERROR - Actor threw an exception
>>>>>>> java.lang.IllegalStateException: Attempted to use resource bundles
>>>>>>> outside of an initialized S scope. S only usable when initialized,
>>>>>>> such as during request processing. Did you call S.? from Boot?
>>>>>>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>>>>>>> at net.liftweb.http.S$.$qmark(S.scala:748)
>>>>>>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>>>>>>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>>>>>>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>>>>>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>>>>>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftA
>>>
>>
>
Re: Broken java client link on main site
Posted by ejc <er...@gmail.com>.
Does the e-mail thread I referenced relate to this? If so, I don't
see that anyone submitted a
ticket for lift, as David suggested, but the S.? in that case was removed.
Thanks,
Eric
On Wed, Jan 19, 2011 at 6:53 AM, Richard Hirsch <hi...@gmail.com> wrote:
> I just had a quick look at the Sendmail problem:
>
> The problem is here:
>
> Mailer.sendMail(From(S.?("custom_mail_from_adress")),
> Subject(S.?("custom_mail_subject")),
> To(who), body)
>
> I've updated the Jira issue accordingly.
>
> The easiest solution would be to put the strings back in. But it would
> be better to find a way to allow the user configure these values via
> property file.
>
> D.
>
>
>
> On Wed, Jan 19, 2011 at 1:37 PM, ejc <er...@gmail.com> wrote:
>> I can at least do some more research to pinpoint the problems. If
>> anyone else says "oh I know that answer" feel free to jump in,
>> otherwise I'll take them.
>>
>> Thanks,
>> Eric
>>
>> On Wednesday, January 19, 2011, Ethan Jewett <es...@gmail.com> wrote:
>>> Thanks a lot! I've put these both in the "Backlog" for now, but if we
>>> can get them fixed for the 1.2 release then I think we'll all agree to
>>> include them.
>>>
>>> Are you planning on looking into the problem more or are these open
>>> for someone else to work on?
>>>
>>> Ethan
>>>
>>> On Tue, Jan 18, 2011 at 7:22 PM, ejc <er...@gmail.com> wrote:
>>>> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>>> Hi Eric,
>>>>>
>>>>> These both look like bugs. Thanks for the effort on your
>>>>> investigations. Would you be able to create Jira issues at
>>>>> https://issues.apache.org/jira/browse/ESME ?
>>>>>
>>>>> Thanks,
>>>>> Ethan
>>>>
>>>> Sure thing
>>>>
>>>> https://issues.apache.org/jira/browse/ESME-324 -- login message
>>>> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
>>>>
>>>> Thanks,
>>>> Eric
>>>>
>>>>
>>>>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>>>>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>>>>>> I now have actions working on my installation. There were a couple of
>>>>>>>> things I ran into.
>>>>>>>> The login message doesn't seem to be generated unless I log in via
>>>>>>>> openID, hence my
>>>>>>>> confusion about login messages.
>>>>>>>
>>>>>>> Try and login as a normal user and then set the open-id url via the
>>>>>>> user profile.
>>>>>>
>>>>>> It is set, and login via open-id works fine and generates the login
>>>>>> message. Logging
>>>>>> in via username/password works, but doesn't generate login message. I don't see
>>>>>> any errors, just no login message.
>>>>>>
>>>>>>> The mailto: action doesn't appear to
>>>>>>>> work, either on
>>>>>>>> stax, or locally. I plan to debug this today. I probably have
>>>>>>>> something mis-configured.
>>>>>>>
>>>>>>> Haven't tried that in a while. I just looked at the stax log and I
>>>>>>> didn't find any exceptions.
>>>>>>>
>>>>>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>>>>>
>>>>>> Yes, I've noticed it will not accept incorrect syntax (including a
>>>>>> space between : and email address)
>>>>>> I get the following when I try a mailto: action. This is running from sbt:
>>>>>>
>>>>>> ERROR - Actor threw an exception
>>>>>> java.lang.IllegalStateException: Attempted to use resource bundles
>>>>>> outside of an initialized S scope. S only usable when initialized,
>>>>>> such as during request processing. Did you call S.? from Boot?
>>>>>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>>>>>> at net.liftweb.http.S$.$qmark(S.scala:748)
>>>>>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>>>>>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>>>>>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>>>>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>>>>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftA
>>
>
Re: Broken java client link on main site
Posted by Richard Hirsch <hi...@gmail.com>.
I just had a quick look at the Sendmail problem:
The problem is here:
Mailer.sendMail(From(S.?("custom_mail_from_adress")),
Subject(S.?("custom_mail_subject")),
To(who), body)
I've updated the Jira issue accordingly.
The easiest solution would be to put the strings back in. But it would
be better to find a way to allow the user configure these values via
property file.
D.
On Wed, Jan 19, 2011 at 1:37 PM, ejc <er...@gmail.com> wrote:
> I can at least do some more research to pinpoint the problems. If
> anyone else says "oh I know that answer" feel free to jump in,
> otherwise I'll take them.
>
> Thanks,
> Eric
>
> On Wednesday, January 19, 2011, Ethan Jewett <es...@gmail.com> wrote:
>> Thanks a lot! I've put these both in the "Backlog" for now, but if we
>> can get them fixed for the 1.2 release then I think we'll all agree to
>> include them.
>>
>> Are you planning on looking into the problem more or are these open
>> for someone else to work on?
>>
>> Ethan
>>
>> On Tue, Jan 18, 2011 at 7:22 PM, ejc <er...@gmail.com> wrote:
>>> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>> Hi Eric,
>>>>
>>>> These both look like bugs. Thanks for the effort on your
>>>> investigations. Would you be able to create Jira issues at
>>>> https://issues.apache.org/jira/browse/ESME ?
>>>>
>>>> Thanks,
>>>> Ethan
>>>
>>> Sure thing
>>>
>>> https://issues.apache.org/jira/browse/ESME-324 -- login message
>>> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
>>>
>>> Thanks,
>>> Eric
>>>
>>>
>>>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>>>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>>>>> I now have actions working on my installation. There were a couple of
>>>>>>> things I ran into.
>>>>>>> The login message doesn't seem to be generated unless I log in via
>>>>>>> openID, hence my
>>>>>>> confusion about login messages.
>>>>>>
>>>>>> Try and login as a normal user and then set the open-id url via the
>>>>>> user profile.
>>>>>
>>>>> It is set, and login via open-id works fine and generates the login
>>>>> message. Logging
>>>>> in via username/password works, but doesn't generate login message. I don't see
>>>>> any errors, just no login message.
>>>>>
>>>>>> The mailto: action doesn't appear to
>>>>>>> work, either on
>>>>>>> stax, or locally. I plan to debug this today. I probably have
>>>>>>> something mis-configured.
>>>>>>
>>>>>> Haven't tried that in a while. I just looked at the stax log and I
>>>>>> didn't find any exceptions.
>>>>>>
>>>>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>>>>
>>>>> Yes, I've noticed it will not accept incorrect syntax (including a
>>>>> space between : and email address)
>>>>> I get the following when I try a mailto: action. This is running from sbt:
>>>>>
>>>>> ERROR - Actor threw an exception
>>>>> java.lang.IllegalStateException: Attempted to use resource bundles
>>>>> outside of an initialized S scope. S only usable when initialized,
>>>>> such as during request processing. Did you call S.? from Boot?
>>>>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>>>>> at net.liftweb.http.S$.$qmark(S.scala:748)
>>>>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>>>>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>>>>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>>>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>>>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftA
>
Re: Broken java client link on main site
Posted by ejc <er...@gmail.com>.
I can at least do some more research to pinpoint the problems. If
anyone else says "oh I know that answer" feel free to jump in,
otherwise I'll take them.
Thanks,
Eric
On Wednesday, January 19, 2011, Ethan Jewett <es...@gmail.com> wrote:
> Thanks a lot! I've put these both in the "Backlog" for now, but if we
> can get them fixed for the 1.2 release then I think we'll all agree to
> include them.
>
> Are you planning on looking into the problem more or are these open
> for someone else to work on?
>
> Ethan
>
> On Tue, Jan 18, 2011 at 7:22 PM, ejc <er...@gmail.com> wrote:
>> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
>>> Hi Eric,
>>>
>>> These both look like bugs. Thanks for the effort on your
>>> investigations. Would you be able to create Jira issues at
>>> https://issues.apache.org/jira/browse/ESME ?
>>>
>>> Thanks,
>>> Ethan
>>
>> Sure thing
>>
>> https://issues.apache.org/jira/browse/ESME-324 -- login message
>> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
>>
>> Thanks,
>> Eric
>>
>>
>>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>>>> I now have actions working on my installation. There were a couple of
>>>>>> things I ran into.
>>>>>> The login message doesn't seem to be generated unless I log in via
>>>>>> openID, hence my
>>>>>> confusion about login messages.
>>>>>
>>>>> Try and login as a normal user and then set the open-id url via the
>>>>> user profile.
>>>>
>>>> It is set, and login via open-id works fine and generates the login
>>>> message. Logging
>>>> in via username/password works, but doesn't generate login message. I don't see
>>>> any errors, just no login message.
>>>>
>>>>> The mailto: action doesn't appear to
>>>>>> work, either on
>>>>>> stax, or locally. I plan to debug this today. I probably have
>>>>>> something mis-configured.
>>>>>
>>>>> Haven't tried that in a while. I just looked at the stax log and I
>>>>> didn't find any exceptions.
>>>>>
>>>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>>>
>>>> Yes, I've noticed it will not accept incorrect syntax (including a
>>>> space between : and email address)
>>>> I get the following when I try a mailto: action. This is running from sbt:
>>>>
>>>> ERROR - Actor threw an exception
>>>> java.lang.IllegalStateException: Attempted to use resource bundles
>>>> outside of an initialized S scope. S only usable when initialized,
>>>> such as during request processing. Did you call S.? from Boot?
>>>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>>>> at net.liftweb.http.S$.$qmark(S.scala:748)
>>>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>>>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>>>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftA
Re: Broken java client link on main site
Posted by Ethan Jewett <es...@gmail.com>.
Thanks a lot! I've put these both in the "Backlog" for now, but if we
can get them fixed for the 1.2 release then I think we'll all agree to
include them.
Are you planning on looking into the problem more or are these open
for someone else to work on?
Ethan
On Tue, Jan 18, 2011 at 7:22 PM, ejc <er...@gmail.com> wrote:
> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
>> Hi Eric,
>>
>> These both look like bugs. Thanks for the effort on your
>> investigations. Would you be able to create Jira issues at
>> https://issues.apache.org/jira/browse/ESME ?
>>
>> Thanks,
>> Ethan
>
> Sure thing
>
> https://issues.apache.org/jira/browse/ESME-324 -- login message
> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
>
> Thanks,
> Eric
>
>
>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>>> I now have actions working on my installation. There were a couple of
>>>>> things I ran into.
>>>>> The login message doesn't seem to be generated unless I log in via
>>>>> openID, hence my
>>>>> confusion about login messages.
>>>>
>>>> Try and login as a normal user and then set the open-id url via the
>>>> user profile.
>>>
>>> It is set, and login via open-id works fine and generates the login
>>> message. Logging
>>> in via username/password works, but doesn't generate login message. I don't see
>>> any errors, just no login message.
>>>
>>>> The mailto: action doesn't appear to
>>>>> work, either on
>>>>> stax, or locally. I plan to debug this today. I probably have
>>>>> something mis-configured.
>>>>
>>>> Haven't tried that in a while. I just looked at the stax log and I
>>>> didn't find any exceptions.
>>>>
>>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>>
>>> Yes, I've noticed it will not accept incorrect syntax (including a
>>> space between : and email address)
>>> I get the following when I try a mailto: action. This is running from sbt:
>>>
>>> ERROR - Actor threw an exception
>>> java.lang.IllegalStateException: Attempted to use resource bundles
>>> outside of an initialized S scope. S only usable when initialized,
>>> such as during request processing. Did you call S.? from Boot?
>>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>>> at net.liftweb.http.S$.$qmark(S.scala:748)
>>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply$mcV$sp(LiftActor.scala:182)
>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182)
>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182)
>>> at net.liftweb.actor.SpecializedLiftActor$class.around(LiftActor.scala:196)
>>> at org.apache.esme.actor.HttpSender$.around(HttpSender.scala:38)
>>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$processMailbox(LiftActor.scala:181)
>>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$2$$anonfun$apply$mcV$sp$1.apply$mcV$sp(LiftActor.scala:145)
>>> at net.liftweb.actor.LAScheduler$$anonfun$9$$anon$1$$anon$2.run(LiftActor.scala:51)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> at java.lang.Thread.run(Thread.java:619)
>>>
>>> I think I saw something like this on either this list or liftweb list.
>>> I'm going to look into this today.
>>>
>>> Thanks,
>>> Eric
>>>
>>
>
Re: Broken java client link on main site
Posted by ejc <er...@gmail.com>.
On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <es...@gmail.com> wrote:
> Hi Eric,
>
> These both look like bugs. Thanks for the effort on your
> investigations. Would you be able to create Jira issues at
> https://issues.apache.org/jira/browse/ESME ?
>
> Thanks,
> Ethan
Sure thing
https://issues.apache.org/jira/browse/ESME-324 -- login message
https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure
Thanks,
Eric
> On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>>> I now have actions working on my installation. There were a couple of
>>>> things I ran into.
>>>> The login message doesn't seem to be generated unless I log in via
>>>> openID, hence my
>>>> confusion about login messages.
>>>
>>> Try and login as a normal user and then set the open-id url via the
>>> user profile.
>>
>> It is set, and login via open-id works fine and generates the login
>> message. Logging
>> in via username/password works, but doesn't generate login message. I don't see
>> any errors, just no login message.
>>
>>> The mailto: action doesn't appear to
>>>> work, either on
>>>> stax, or locally. I plan to debug this today. I probably have
>>>> something mis-configured.
>>>
>>> Haven't tried that in a while. I just looked at the stax log and I
>>> didn't find any exceptions.
>>>
>>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>>
>> Yes, I've noticed it will not accept incorrect syntax (including a
>> space between : and email address)
>> I get the following when I try a mailto: action. This is running from sbt:
>>
>> ERROR - Actor threw an exception
>> java.lang.IllegalStateException: Attempted to use resource bundles
>> outside of an initialized S scope. S only usable when initialized,
>> such as during request processing. Did you call S.? from Boot?
>> at net.liftweb.http.S$.resourceBundles(S.scala:722)
>> at net.liftweb.http.S$.$qmark(S.scala:748)
>> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
>> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
>> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
>> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply$mcV$sp(LiftActor.scala:182)
>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182)
>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182)
>> at net.liftweb.actor.SpecializedLiftActor$class.around(LiftActor.scala:196)
>> at org.apache.esme.actor.HttpSender$.around(HttpSender.scala:38)
>> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$processMailbox(LiftActor.scala:181)
>> at net.liftweb.actor.SpecializedLiftActor$$anonfun$2$$anonfun$apply$mcV$sp$1.apply$mcV$sp(LiftActor.scala:145)
>> at net.liftweb.actor.LAScheduler$$anonfun$9$$anon$1$$anon$2.run(LiftActor.scala:51)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:619)
>>
>> I think I saw something like this on either this list or liftweb list.
>> I'm going to look into this today.
>>
>> Thanks,
>> Eric
>>
>
Re: Broken java client link on main site
Posted by Ethan Jewett <es...@gmail.com>.
Hi Eric,
These both look like bugs. Thanks for the effort on your
investigations. Would you be able to create Jira issues at
https://issues.apache.org/jira/browse/ESME ?
Thanks,
Ethan
On Tue, Jan 18, 2011 at 5:33 PM, ejc <er...@gmail.com> wrote:
> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>>> I now have actions working on my installation. There were a couple of
>>> things I ran into.
>>> The login message doesn't seem to be generated unless I log in via
>>> openID, hence my
>>> confusion about login messages.
>>
>> Try and login as a normal user and then set the open-id url via the
>> user profile.
>
> It is set, and login via open-id works fine and generates the login
> message. Logging
> in via username/password works, but doesn't generate login message. I don't see
> any errors, just no login message.
>
>> The mailto: action doesn't appear to
>>> work, either on
>>> stax, or locally. I plan to debug this today. I probably have
>>> something mis-configured.
>>
>> Haven't tried that in a while. I just looked at the stax log and I
>> didn't find any exceptions.
>>
>> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
>
> Yes, I've noticed it will not accept incorrect syntax (including a
> space between : and email address)
> I get the following when I try a mailto: action. This is running from sbt:
>
> ERROR - Actor threw an exception
> java.lang.IllegalStateException: Attempted to use resource bundles
> outside of an initialized S scope. S only usable when initialized,
> such as during request processing. Did you call S.? from Boot?
> at net.liftweb.http.S$.resourceBundles(S.scala:722)
> at net.liftweb.http.S$.$qmark(S.scala:748)
> at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
> at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
> at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
> at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply$mcV$sp(LiftActor.scala:182)
> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182)
> at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182)
> at net.liftweb.actor.SpecializedLiftActor$class.around(LiftActor.scala:196)
> at org.apache.esme.actor.HttpSender$.around(HttpSender.scala:38)
> at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$processMailbox(LiftActor.scala:181)
> at net.liftweb.actor.SpecializedLiftActor$$anonfun$2$$anonfun$apply$mcV$sp$1.apply$mcV$sp(LiftActor.scala:145)
> at net.liftweb.actor.LAScheduler$$anonfun$9$$anon$1$$anon$2.run(LiftActor.scala:51)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
> I think I saw something like this on either this list or liftweb list.
> I'm going to look into this today.
>
> Thanks,
> Eric
>
Re: Broken java client link on main site
Posted by ejc <er...@gmail.com>.
On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
> On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
>> I now have actions working on my installation. There were a couple of
>> things I ran into.
>> The login message doesn't seem to be generated unless I log in via
>> openID, hence my
>> confusion about login messages.
>
> Try and login as a normal user and then set the open-id url via the
> user profile.
It is set, and login via open-id works fine and generates the login
message. Logging
in via username/password works, but doesn't generate login message. I don't see
any errors, just no login message.
> The mailto: action doesn't appear to
>> work, either on
>> stax, or locally. I plan to debug this today. I probably have
>> something mis-configured.
>
> Haven't tried that in a while. I just looked at the stax log and I
> didn't find any exceptions.
>
> Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
Yes, I've noticed it will not accept incorrect syntax (including a
space between : and email address)
I get the following when I try a mailto: action. This is running from sbt:
ERROR - Actor threw an exception
java.lang.IllegalStateException: Attempted to use resource bundles
outside of an initialized S scope. S only usable when initialized,
such as during request processing. Did you call S.? from Boot?
at net.liftweb.http.S$.resourceBundles(S.scala:722)
at net.liftweb.http.S$.$qmark(S.scala:748)
at org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58)
at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41)
at org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39)
at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371)
at org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38)
at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261)
at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply$mcV$sp(LiftActor.scala:182)
at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182)
at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182)
at net.liftweb.actor.SpecializedLiftActor$class.around(LiftActor.scala:196)
at org.apache.esme.actor.HttpSender$.around(HttpSender.scala:38)
at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$processMailbox(LiftActor.scala:181)
at net.liftweb.actor.SpecializedLiftActor$$anonfun$2$$anonfun$apply$mcV$sp$1.apply$mcV$sp(LiftActor.scala:145)
at net.liftweb.actor.LAScheduler$$anonfun$9$$anon$1$$anon$2.run(LiftActor.scala:51)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
I think I saw something like this on either this list or liftweb list.
I'm going to look into this today.
Thanks,
Eric
Re: Broken java client link on main site
Posted by Richard Hirsch <hi...@gmail.com>.
On Tue, Jan 18, 2011 at 3:55 PM, ejc <er...@gmail.com> wrote:
> I now have actions working on my installation. There were a couple of
> things I ran into.
> The login message doesn't seem to be generated unless I log in via
> openID, hence my
> confusion about login messages.
Try and login as a normal user and then set the open-id url via the
user profile.
The mailto: action doesn't appear to
> work, either on
> stax, or locally. I plan to debug this today. I probably have
> something mis-configured.
Haven't tried that in a while. I just looked at the stax log and I
didn't find any exceptions.
Are you using the correct action syntax? "mailto:wille.coyote@acme.com"
D.
>
> Thanks,
> Eric
>
> On Sat, Jan 15, 2011 at 1:12 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> On Sat, Jan 15, 2011 at 3:39 AM, ejc <er...@gmail.com> wrote:
> <snip>
>> I've
>>> run into a couple of issues. Actions don't work on my server and I
>>> don't see login messages like on the stax server.
>>
>> Are there any log entries for the Action errors. What actions are you
>> trying to create?
>>
>> Have you tried to use jetty to see if that solves the problem? It
>> might be a Tomcat specific problem.
>>
>> Some thing to
>>> troubleshoot on Tuesday -- maybe later tonight. Snow shovelling is
>>> calling.
>
Re: Broken java client link on main site
Posted by ejc <er...@gmail.com>.
I now have actions working on my installation. There were a couple of
things I ran into.
The login message doesn't seem to be generated unless I log in via
openID, hence my
confusion about login messages. The mailto: action doesn't appear to
work, either on
stax, or locally. I plan to debug this today. I probably have
something mis-configured.
Thanks,
Eric
On Sat, Jan 15, 2011 at 1:12 AM, Richard Hirsch <hi...@gmail.com> wrote:
> On Sat, Jan 15, 2011 at 3:39 AM, ejc <er...@gmail.com> wrote:
<snip>
> I've
>> run into a couple of issues. Actions don't work on my server and I
>> don't see login messages like on the stax server.
>
> Are there any log entries for the Action errors. What actions are you
> trying to create?
>
> Have you tried to use jetty to see if that solves the problem? It
> might be a Tomcat specific problem.
>
> Some thing to
>> troubleshoot on Tuesday -- maybe later tonight. Snow shovelling is
>> calling.
Re: Broken java client link on main site
Posted by Richard Hirsch <hi...@gmail.com>.
On Sat, Jan 15, 2011 at 3:39 AM, ejc <er...@gmail.com> wrote:
> On Friday, January 14, 2011, Richard Hirsch <hi...@gmail.com> wrote:
>> On Fri, Jan 14, 2011 at 5:54 PM, ejc <er...@gmail.com> wrote:
>>> I've noticed that not all of the clients seem to have kept up. I had
>>> some issues with
>>> the AIR client and my server, which I suspect is due to the client
>>> looking for an older
>>> server version.
>>
>> We know that we haven't been able to keep up with all the clients -
>> lack of resources has out of necessity made us concentrate on the
>> server component (especially the APIs) and the Web UI.
>>
>> The Air client source is still available on Google Code. What sort of
>> problems are you having with it?
>
> I didn't use it much, but it seemed to keep putting the esme.us site
> in the config file. Also, the link to "get a token" takes one to
> esme.us. It could very well be an issue with my server config.
You have to change the preferences file for the AIR Client [1]
I've
> run into a couple of issues. Actions don't work on my server and I
> don't see login messages like on the stax server.
Are there any log entries for the Action errors. What actions are you
trying to create?
Have you tried to use jetty to see if that solves the problem? It
might be a Tomcat specific problem.
Some thing to
> troubleshoot on Tuesday -- maybe later tonight. Snow shovelling is
> calling.
Have fun - all the snow is gone here - too much rain and warm weather
the last week - which means no more shoveling but also no more skiing
:-<
>
> Thanks,
> Eric
>
D.
[1] http://code.google.com/p/esmeproject/wiki/ESME_Desktop_Client_Server_config
Re: Broken java client link on main site
Posted by ejc <er...@gmail.com>.
On Friday, January 14, 2011, Richard Hirsch <hi...@gmail.com> wrote:
> On Fri, Jan 14, 2011 at 5:54 PM, ejc <er...@gmail.com> wrote:
>> I've noticed that not all of the clients seem to have kept up. I had
>> some issues with
>> the AIR client and my server, which I suspect is due to the client
>> looking for an older
>> server version.
>
> We know that we haven't been able to keep up with all the clients -
> lack of resources has out of necessity made us concentrate on the
> server component (especially the APIs) and the Web UI.
>
> The Air client source is still available on Google Code. What sort of
> problems are you having with it?
I didn't use it much, but it seemed to keep putting the esme.us site
in the config file. Also, the link to "get a token" takes one to
esme.us. It could very well be an issue with my server config. I've
run into a couple of issues. Actions don't work on my server and I
don't see login messages like on the stax server. Some thing to
troubleshoot on Tuesday -- maybe later tonight. Snow shovelling is
calling.
Thanks,
Eric
Re: Broken java client link on main site
Posted by Richard Hirsch <hi...@gmail.com>.
On Fri, Jan 14, 2011 at 5:54 PM, ejc <er...@gmail.com> wrote:
> I've noticed that not all of the clients seem to have kept up. I had
> some issues with
> the AIR client and my server, which I suspect is due to the client
> looking for an older
> server version.
We know that we haven't been able to keep up with all the clients -
lack of resources has out of necessity made us concentrate on the
server component (especially the APIs) and the Web UI.
The Air client source is still available on Google Code. What sort of
problems are you having with it?
D.
>
> Thanks,
> Eric
>
> On Fri, Jan 14, 2011 at 10:21 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> Thanks,
>>
>> I missed that link - I've fixed the error and have exported the wiki.
>>
>> FYI: the Java client in SVN is based on our original REST API. Here is
>> another client based on the latest Streaming API [1]
>>
>> D.
>>
>> [1] http://issues.apache.org/jira/secure/attachment/12426366/esme2java.jar
>>
>>
>>
>> On Fri, Jan 14, 2011 at 5:05 PM, ejc <er...@gmail.com> wrote:
>>> I'm not exactly sure who to send this to, and I can't edit the page myself, but
>>>
>>> http://esme.apache.org
>>>
>>> The Java client link at http://esme.apache.org/#Index-Clients points to:
>>>
>>> http://svn.apache.org/viewvc/incubator/esme/trunk/esme-java-client/
>>>
>>> which is broken, it should be:
>>>
>>> http://svn.apache.org/viewvc/esme/trunk/esme-java-client/
>>>
>>> Thanks,
>>> Eric
>>>
>>
>
Re: Broken java client link on main site
Posted by ejc <er...@gmail.com>.
I've noticed that not all of the clients seem to have kept up. I had
some issues with
the AIR client and my server, which I suspect is due to the client
looking for an older
server version.
Thanks,
Eric
On Fri, Jan 14, 2011 at 10:21 AM, Richard Hirsch <hi...@gmail.com> wrote:
> Thanks,
>
> I missed that link - I've fixed the error and have exported the wiki.
>
> FYI: the Java client in SVN is based on our original REST API. Here is
> another client based on the latest Streaming API [1]
>
> D.
>
> [1] http://issues.apache.org/jira/secure/attachment/12426366/esme2java.jar
>
>
>
> On Fri, Jan 14, 2011 at 5:05 PM, ejc <er...@gmail.com> wrote:
>> I'm not exactly sure who to send this to, and I can't edit the page myself, but
>>
>> http://esme.apache.org
>>
>> The Java client link at http://esme.apache.org/#Index-Clients points to:
>>
>> http://svn.apache.org/viewvc/incubator/esme/trunk/esme-java-client/
>>
>> which is broken, it should be:
>>
>> http://svn.apache.org/viewvc/esme/trunk/esme-java-client/
>>
>> Thanks,
>> Eric
>>
>
Re: Broken java client link on main site
Posted by Richard Hirsch <hi...@gmail.com>.
Thanks,
I missed that link - I've fixed the error and have exported the wiki.
FYI: the Java client in SVN is based on our original REST API. Here is
another client based on the latest Streaming API [1]
D.
[1] http://issues.apache.org/jira/secure/attachment/12426366/esme2java.jar
On Fri, Jan 14, 2011 at 5:05 PM, ejc <er...@gmail.com> wrote:
> I'm not exactly sure who to send this to, and I can't edit the page myself, but
>
> http://esme.apache.org
>
> The Java client link at http://esme.apache.org/#Index-Clients points to:
>
> http://svn.apache.org/viewvc/incubator/esme/trunk/esme-java-client/
>
> which is broken, it should be:
>
> http://svn.apache.org/viewvc/esme/trunk/esme-java-client/
>
> Thanks,
> Eric
>