Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340518 - non connected port produces null pointer exception during runtime
Summary: non connected port produces null pointer exception during runtime
Status: CLOSED FIXED
Alias: None
Product: eTrice
Classification: Modeling
Component: Runtime (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: 0.1.0
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-20 13:45 EDT by Thomas Jung CLA
Modified: 2011-12-16 02:48 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Jung CLA 2011-03-20 13:45:59 EDT 
if a model contains a not connected port, regardless if a message is sent via this port, a Null Pointer Exception occurse.
Comment 1 Thomas Schuetz CLA 2011-03-25 13:26:46 EDT 
please always add at least stacktrace for all errors if possible
-> fixed, but not really tested yet 
-> I will close this bug after implementation of integration tests
Comment 2 Henrik Rentz-Reichert CLA 2011-10-25 11:06:22 EDT 
Integration tests work for this case.
Comment 3 Henrik Rentz-Reichert CLA 2011-12-16 02:45:30 EST 
closed resolved bug
Comment 4 Henrik Rentz-Reichert CLA 2011-12-16 02:48:09 EST 
tagged as version 0.1.0