[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5374) edi-to-java smooks quickstart fails to read edi input
Xue Peng (JIRA)
jira-events at lists.jboss.org
Thu Dec 3 21:45:29 EST 2009
[ https://jira.jboss.org/jira/browse/JBIDE-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12498166#action_12498166 ]
Xue Peng commented on JBIDE-5374:
---------------------------------
I bet because the "mapping model" value if incorrect ( can't find the EDI mapping file) so the EDI reader of Smooks can't parse the edi file , so this exception happen.
I can do somethings to judge that is mapping model path correct .
Actually , "Unable to filter InputStream for target profile" is not only appear in EDI , if you try to use CSV or JSON , sometimes this error will happen , , so I think maybe Tom should make the the exception message more easy to understand.
> edi-to-java smooks quickstart fails to read edi input
> -----------------------------------------------------
>
> Key: JBIDE-5374
> URL: https://jira.jboss.org/jira/browse/JBIDE-5374
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: smooks
> Affects Versions: 3.1.0.CR1
> Reporter: Brian Fitzpatrick
> Assignee: Xue Peng
> Fix For: 3.1.0.GA
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Was able to copy the Java classes, edi sample, and smooks config over from the edi-to-java quickstart. When I tried to open it, I get a warning saying the edi namespace needs to be updated from 1.1 to 1.2. Once I update it, the editor refreshes and I'm able to set the edi sample data on the config.
> Unfortunately, I then get "Input Error: Unable to filter InputStream for target profile [org.milyn.profile.Profile#default_profile]." I'm not sure what to do with this and can go no further.
> I was able to run the edi-to-java sample when I tried it on Monday, so I'm not sure if something has been broken as far as EDI validation maybe?
--
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
More information about the jbosstools-issues
mailing list