YAML - "ArgumentError: ScannerException while scanning for the next token we 
had this found character   (9) that cannot start any token"
---------------------------------------------------------------------------------------------------------------------------------------

                 Key: JRUBY-2135
                 URL: http://jira.codehaus.org/browse/JRUBY-2135
             Project: JRuby
          Issue Type: Bug
    Affects Versions: JRuby 1.1RC2
         Environment: Operating System:
   OS X - Leopard

Communicating between Ruby and JRuby with YAML
            Reporter: cj
            Assignee: Thomas E Enebo


I have two processes communicating via YAML. On the left side, a Ruby process 
produces objects and outputs them via YAML to a pipe where a JRuby process on 
the right side picks them up and turns them back into objects. The following 
YAML string was picked up by the JRuby process

--- \nmessage_class: syslog_message\nmessage: 
MSWinEventLog\t0\tApplication\t612\tWed Jun 06 20:26:26 2007\t4001\tMSExchange 
System Attendant Mailbox\tUnknown 
User\tN/A\tError\tMAILDKCPH01\tUnknown\t\t56\t119187\ntimestamp: 
1182892312\nvariables: {}\n\nclassifier: -1\ndevice_id: 1\nuid: 
3zjpp14l3g75xg4qw\nlog_priority_id: 1\nlog_program_id: 1\nsaved: 
false\nlog_facility_id: 1\n

Using IRB to load the data works sufficiently, but JRuby fails with the 
following error:
ArgumentError: ScannerException while scanning for the next token we had this 
found character   (9) that cannot start any token

A quick test shows that replacing the \t characters with a tab in Textmate 
produces a usable string by JRuby. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to